[Touch-packages] [Bug 1690506] [NEW] bug description must contain standard apport format data
Public bug reported: Artful system Fail to use apport-retrace: sudo apport-retrace 1690502 ERROR: Broken report: bug description must contain standard apport format data ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport-retrace 2.20.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportLog: ApportVersion: 2.20.5-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 13 08:20:24 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful package-from-proposed -- 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/1690506 Title: bug description must contain standard apport format data Status in apport package in Ubuntu: New Bug description: Artful system Fail to use apport-retrace: sudo apport-retrace 1690502 ERROR: Broken report: bug description must contain standard apport format data ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport-retrace 2.20.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportLog: ApportVersion: 2.20.5-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 13 08:20:24 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1690506/+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 1607390] Re: serious bug on bluetooth (Ubuntu 16.04 LTS)
I fixed it with `sudo systemctl enable bluetooth` followed by a reboot. It will print something to the terminal when you enable. Something else must have disabled bluetooth. -- 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/1607390 Title: serious bug on bluetooth (Ubuntu 16.04 LTS) Status in bluez package in Ubuntu: Confirmed Bug description: I've recently installed ubuntu 16.04 LTS twice -and i discovered that the problem was from the tool katoolin so i didn't install it- after i installed ubuntu the bluetooth didn't work for me. P.S:the bluetooth was working when my laptop was ubuntu 15.04 when i turn bluetooth on to connect my mouse the switch was on but it said that Bluetooth is disabled i entered the command sudo rfkill unblock bluetooth it worked but didn't connect to the mouse even after the next restart i also tried to editing the file /etc/rc.local (putting sudo rfkill unblock bluetooth before last line and restarting) and i've tried **sudo hciconfig hci0 reset** with output > Can't init device hci0: Connection timed out (110) my lsusb; rfkill list output: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 014: ID 04ca:3005 Lite-On Technology Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 11: hci0: Bluetooth Soft blocked: no Hard blocked: no and output of **dmesg | grep -Ei 'ath3k|blue'** [1.727681] usb 1-1.1: Product: Bluetooth USB Host Controller [ 34.157120] Bluetooth: Core ver 2.21 [ 34.157135] Bluetooth: HCI device and connection manager initialized [ 34.157138] Bluetooth: HCI socket layer initialized [ 34.157140] Bluetooth: L2CAP socket layer initialized [ 34.157145] Bluetooth: SCO socket layer initialized [ 35.604410] usbcore: registered new interface driver ath3k [ 51.744300] usb 1-1.1: Product: Bluetooth USB Host Controller [ 53.810045] Bluetooth: hci0 command 0x0c25 tx timeout [ 55.814079] Bluetooth: hci0 command 0x0c38 tx timeout [ 57.818111] Bluetooth: hci0 command 0x0c39 tx timeout [ 59.822149] Bluetooth: hci0 command 0x0c05 tx timeout [ 66.997548] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 66.997552] Bluetooth: BNEP filters: protocol multicast [ 66.997556] Bluetooth: BNEP socket layer initialized [ 195.105902] usb 1-1.1: Product: Bluetooth USB Host Controller [ 195.328480] Bluetooth: RFCOMM TTY layer initialized [ 195.328488] Bluetooth: RFCOMM socket layer initialized [ 195.328495] Bluetooth: RFCOMM ver 1.11 [ 199.131870] Bluetooth: hci0 command 0x1009 tx timeout [ 276.169130] usb 1-1.1: Product: Bluetooth USB Host Controller [ 294.258992] Bluetooth: hci0 command 0x1005 tx timeout [ 296.263065] Bluetooth: hci0 command 0x0c23 tx timeout [ 298.267076] Bluetooth: hci0 command 0x0c14 tx timeout [ 306.361529] usb 1-1.1: Product: Bluetooth USB Host Controller [ 346.417970] Bluetooth: hci0 command 0x0c56 tx timeout [ 348.421916] Bluetooth: hci0 command 0x0c45 tx timeout [ 350.425782] Bluetooth: hci0 command 0x0c58 tx timeout [ 352.429744] Bluetooth: hci0 command 0x1004 tx timeout [ 366.099802] usb 1-1.1: Product: Bluetooth USB Host Controller [ 368.145218] Bluetooth: hci0 command 0x1001 tx timeout [ 370.149130] Bluetooth: hci0 command 0x1009 tx timeout [ 410.346611] usb 1-1.1: Product: Bluetooth USB Host Controller [ 421.612041] Bluetooth: hci0 command 0x0c23 tx timeout [ 423.616060] Bluetooth: hci0 command 0x0c14 tx timeout [ 425.620018] Bluetooth: hci0 command 0x0c25 tx timeout [ 427.623984] Bluetooth: hci0 command 0x0c38 tx timeout [ 442.650168] usb 1-1.1: Product: Bluetooth USB Host Controller [ 444.727752] Bluetooth: hci0 command 0x0c52 tx timeout [ 446.731800] Bluetooth: hci0 command 0x0c45 tx timeout [ 448.735743] Bluetooth: hci0 command 0x0c58 tx timeout [ 450.739762] Bluetooth: hci0 command 0x1004 tx timeout [ 4000.639722] usb 1-1.1: Product: Bluetooth USB Host Controller [ 4011.801141] Bluetoo
[Touch-packages] [Bug 1688730] Re: click-apparmor ubuntu-app-launch url-dispatcher
The following commands resolved my error: sudo apt install url-dispatcher-tools sudo apt install ubuntu-app-launch-tools sudo apt install python3-apparmor-click sudo apt install python3-click sudo apt --fix-broken install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1688730 Title: click-apparmor ubuntu-app-launch url-dispatcher Status in click-apparmor package in Ubuntu: New Bug description: Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: warning: subprocess old pre-removal script returned error exit status 1 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chanchal 2274 F pulseaudio /dev/snd/controlC0: chanchal 2274 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat May 6 18:58:27 2017 HibernationDevice: RESUME=UUID=459f0094-1f0b-4da8-9fac-1f2e7d6e36bc InstallationDate: Installed on 2016-02-20 (440 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 5537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=b87f269a-0aef-4bb0-93fa-18454ad51275 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-21-generic N/A linux-backports-modules-4.10.0-21-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-06 (0 days ago) dmi.bios.date: 08/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 04NGGW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/19/2013:svnDellInc.:pnInspiron5537:pvrA04:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA04: dmi.product.name: Inspiron 5537 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1688730/+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 1672394] Re: Random crash with multiple apps open
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1672394 Title: Random crash with multiple apps open Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Expired Bug description: STEPS: 1. Open multiple apps and pin them to the corners 2. Use the system EXPECTED: I expect the system to remain working like this all day ACTUAL: At some point unity8 crashes and takes out all of the apps and the system. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672394/+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 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt
Fix confirmed for trusty as well. ** Tags removed: verification-needed ** Tags added: verification-done-trusty -- 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/1679784 Title: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Trusty: Fix Committed Status in software-properties source package in Xenial: Fix Committed Status in software-properties source package in Yakkety: Fix Released Bug description: [SRU Justification] software-properties does not display debconf prompts. while most debconf prompts have default answers and this is fine, for installing dkms modules on a SecureBoot-capable system we specifically have a critical debconf prompt with no possible default answer that users need to step through in order for their dkms modules to be usable. [Test case] 1. sudo apt-add-repository ppa:vorlon/debconf-tests 2. sudo apt update 3. Launch Settings -> Software & Updates -> Additional Drivers 4. Confirm that you are offered the option of using the 'noisy-fake-driver' package. 5. Select this driver and apply changes. 6. Confirm that no debconf prompt is shown, and the driver package fails to install ('dpkg -l noisy-fake-driver' shows 'iF'). 7. Reset the package state by removing the driver again. 8. Enable -proposed. 9. Run update-manager and verify that the new software-properties package is successfully installed from -proposed, pulling in libgtk2-perl in the process. 10. Close Software & Updates and re-launch it. 11. Select the 'noisy-fake-driver' package again. 12. Confirm that you are shown a debconf prompt, and the driver package installs successfully. [Regression potential] The actual code change is small and self-contained, but the fix also requires pulling in new package dependencies which will also need to be promoted from universe to main in the process. We need to take extra care to ensure the upgrade path is correct. This SRU should also be done serially one release at a time to gather feedback at each stage. [Original bug description] I've encountered this repeatedly. In the first installation -- on updating via Software Updater, this crashed on upgrading the shim-signed package. On suggestions from here: I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work, however when I now try to swap the display driver, from xorg --> nvidia. This now triggered the same issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Apr 4 18:21:32 2017 DuplicateSignature: package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 Processing triggers for shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ... Running in non-interactive mode, doing nothing. dpkg: error processing package shim-signed (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: shim-signed Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script 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/software-properties/+bug/1679784/+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 1689408] Re: System hang when utilising OpenGL 4.5 features
** Changed in: mesa Status: Unknown => Confirmed ** Changed in: mesa Importance: Unknown => Medium -- 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/1689408 Title: System hang when utilising OpenGL 4.5 features Status in Mesa: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: I've found this to be easily reproducible via unigine's heaven benchmark, which uses tessellation and other features extensively. Simply creating a OpenGL 4.5 context will not trigger the hang, and you must explicitly request an OGL 4+ context as the default will only be 3.0. On a successful trigger, the screen may flicker on and off a few times and eventually hang completely on a black screen, there's no way to recover the system from this state bar a power cycle (ie hold the power button). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paulh 1405 F pulseaudio /dev/snd/controlC0: paulh 1405 F pulseaudio CurrentDesktop: KDE Date: Tue May 9 09:14:09 2017 InstallationDate: Installed on 2017-01-05 (123 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1C dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8133 dmi.board.vendor: HP dmi.board.version: KBC Version 98.0E dmi.chassis.asset.tag: 5CG6124XBK dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1689408/+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 1690493] [NEW] el sistema operativo no carga correctamente
Public bug reported: no carga la pantalla principal y he modificado el grub colocando pci=nomsi para que funcione ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri May 12 21:41:23 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:12a0] InstallationDate: Installed on 2017-05-12 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: ASUSTeK COMPUTER INC. X441UA ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic root=UUID=a7a8e101-a485-4ef5-ba0b-926df14f3b42 ro quiet splash pci=nomsi vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441UA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441UA.305:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnX441UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X441UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri May 12 07:39:17 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1690493 Title: el sistema operativo no carga correctamente Status in xorg package in Ubuntu: New Bug description: no carga la pantalla principal y he modificado el grub colocando pci=nomsi para que funcione ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri May 12 21:41:23 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:12a0] InstallationDate: Installed on 2017-05-12 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: ASUSTeK COMPUTER INC. X441UA ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic root=UUID=a7a8e101-a485-4ef5-ba0b-926df14f3b42 ro quiet splash pci=nomsi vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441UA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1
[Touch-packages] [Bug 939947] Re: crash with SIGSEGV in _pixman_image_get_solid()
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 LTS reached End of Life in April. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again. I apologize that we are not always to respond to bug reports promptly. Do feel free to report any other bugs you may find. ** No longer affects: pixman (Ubuntu) ** No longer affects: evince (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pixman in Ubuntu. https://bugs.launchpad.net/bugs/939947 Title: crash with SIGSEGV in _pixman_image_get_solid() Status in Unity: Won't Fix Status in gnome-shell package in Ubuntu: Invalid Status in unity package in Ubuntu: Won't Fix Bug description: Random. Clicking on Ubuntu icon causes Compiz to crash. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.92-0ubuntu1 Architecture: amd64 Date: Thu Feb 23 21:16:53 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f6eb6dec300:add%al,(%rax) PC (0x7f6eb6dec300) in non-executable VMA region: 0x7f6eb65ff000-0x7f6eb6dff000 rw-p None source "%al" ok destination "(%rax)" (0xd836f778) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing writable VMA None writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 pixman_image_composite32 () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/939947/+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 874757] Re: Cannot toggle additional sources until authentication has been granted through other means
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 LTS reached End of Life in April. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again. I apologize that we are not always to respond to bug reports promptly. Do feel free to report any other bugs you may find. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Changed in: software-properties (Ubuntu) Status: Confirmed => Invalid -- 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/874757 Title: Cannot toggle additional sources until authentication has been granted through other means Status in gnome-shell package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Open Software Sources as an admin user (not as root; don't do this through Synaptic). 2. Try to check or uncheck the Cdrom source or a source in the Other Software section. Nothing will happen. 3. Do another action that triggers a PolicyKit authentication dialog (toggle the multiverse or universe source, or add a source in Other Software) 4. Repeat step 3. This time, the source will be toggled appropriately. In step 2, the following lands in stderr: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 647, in on_isv_source_toggled self.backend.ToggleSourceUse(str(source_entry)) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy: com.ubuntu.softwareproperties.applychanges Attempting to toggle a software source in the Other Software section should trigger an authentication dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/874757/+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 1326105] Re: AppArmor policy for scope zmq access is too lenient
** Changed in: unity-scopes-api (Ubuntu) Assignee: Michi Henning (michihenning) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1326105 Title: AppArmor policy for scope zmq access is too lenient Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: Currently in apparmor-easyprof-ubuntu 1.2.3 we have: owner /run/user/[0-9]*/zmq/Registry-s rw, owner /run/user/[0-9]*/zmq/Registry-pr, owner /run/user/[0-9]*/zmq/c-*-r rw, Note that all scopes, regardless of whether they use the ubuntu-scope- network or ubuntu-scope-local-content templates have access to these overlapped accesses. While we discussed the apparmor policy at length at the recent sprint, in thinking about this more there are still a few issues: 1. How will the scope-registry handle when either /run/user/[0-9]*/zmq/Registry-s or /run/user/[0-9]*/zmq/Registry-p already exists? 2. In addition to dealing with /run/user/[0-9]*/zmq/c-*-r possibly already existing, there is an additional issue with this access-- because the ubuntu-scope-network and ubuntu-scope-local-content templates both allow this access, this allows a malicious scope author to create a scope using the ubuntu-scope-local-content template, then collect files off the filesystem and store them in /run/user/[0-9]*/zmq/c-I_can_leak_your_files.tar.gz-c, then upload a new version of the scope using the ubuntu-scope-network template, which can then ship /run/user/[0-9]*/zmq/c-I_can_leak_your_files.tar.gz-c off to a remote server when the user upgrades (the fact that it is in /run doesn't really help-- the malicious scope can save the file in its scope- specific directory then copy it in to place to make sure it is always there). For '1', standard defensive programming should be sufficient and someone should verify that the scopes API is handling when these files already exist (as sockets, regular files, etc, etc). For '2', standard defensive programming should also be used, but that isn't enough. I suggested at the sprint that these endpoints should be made application specific by their name like with the other endpoints, but was told this is problematic. I can (and will) update the apparmor policy to use this rule: owner /run/user/[0-9]*/zmq/c-[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]-r rw, but this doesn't solve the problem since a malicious app writer will just pick something matching that apparmor regular expression (AARE). AIUI, it is difficult/impossible to make these endpoints application specific (eg, "/run/user/[0-9]*/zmq/c-@{APP_PKGNAME}-r" which would be the preferred fix). If that is the case, we can either namespace this endpoint in zmq/local-fs/c-*r and zmq/local-net/c-*r and adjust the policy templates accordingly. I have a feeling this will have the same problems (or worse) as making the endpoint application specific since you'd need to track the type of scope this is. Alternatively, you could have a garbage collector to unconditionally remove any non-unix domain socket files and unused unix domain socket files that match zmq/c-*-r. While making these endpoints application specific would be cleanest from a policy point of view, implementing good garbage collection (perhaps triggered on scope start/register) would be sufficient to close this bug. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1326105/+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 1545600] Re: Need to track abigail updates
** Changed in: unity-scopes-api (Ubuntu) Assignee: Michi Henning (michihenning) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1545600 Title: Need to track abigail updates Status in unity-scopes-api package in Ubuntu: In Progress Bug description: There are some issues with abigail, such as getting false positives when running abidiff with base.xml and lib.so, but not when running with abidiff base.xml lib.xml. We need to track progress here and, once a new version lands, re-test the abi checker and see if we can make it go faster by extracting directly from the latest library instead of going via an intermediate dump file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1545600/+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 1540876] Re: Not all results recieved when there is a lot of them (>=3000?)
** Changed in: unity-scopes-api (Ubuntu) Assignee: Michi Henning (michihenning) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1540876 Title: Not all results recieved when there is a lot of them (>=3000?) Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: It looks like ZMQ high water-mark limits the number of results that can succesfuly be received by a client to something around 2000; this may depend on the result size and delays between pushes though. With 3000 results in my test code I was receiving approximately 1900, the remainder was dropped on the floor. While these numbers are probably more than we will ever need, it may be worth looking into it. Perhaps ZMQ queue size can be increased, also a meaningful error in the logs about hitting such cases would be nice (if possible at all). I'll add a pointer to a sample test case from unity-scopes-shell at a later time, please contact me if I forget to do so ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1540876/+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 1302656] Re: Scoperunner needs to be versioned using SOVERSION
** Changed in: unity-scopes-api (Ubuntu) Assignee: Michi Henning (michihenning) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1302656 Title: Scoperunner needs to be versioned using SOVERSION Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: If we want to provide compatibility with scopes compiled against older versions of the library, we need to properly version also scoperunner, not just the library itself. Otherwise the runner would link against latest version of libunity-scopes and the loaded .so against an older version, and things would be pretty likely to blow up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1302656/+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 1469770] Re: ZmqConfig is missing tests
** Changed in: unity-scopes-api (Ubuntu) Assignee: Michi Henning (michihenning) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1469770 Title: ZmqConfig is missing tests Status in unity-scopes-api package in Ubuntu: New Bug description: ZmqConfig is missing unit tests (and because of that it doesn't even count for coverage reports). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1469770/+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 1546364] Re: Links not detected in scopes
** Changed in: unity-scopes-api (Ubuntu) Assignee: Michi Henning (michihenning) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1546364 Title: Links not detected in scopes Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Expected Result: When texts from data sources includes links, these links should be automatically detected and should be clickable. Actual Result: The links are treated as simple texts and are not clickable. Best example of this is the twitter scope. There are usually links on posts however you need to open the tweet first just to open the link instead of directly clicking it from the scope. I think it should be automatic or let the developers decide to do it or maybe add a new action to open links from the post instead of making the link clickable the actual content. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546364/+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 1690485] [NEW] openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'
Public bug reported: The 'sshd' process gets 'authentication failure' and refuses to allow any login. dmesg indicates that the problem is SIGSYS on a call to 'socket' (syscall #41, signal #31). On a hunch, I decided to test whether the problem is related to 'seccomp' and changed /etc/ssh/sshd_config from the default # UsePrivilegeSeparation sandbox to the former standard value UsePrivilegeSeparation yes and logins started to work again. Obviously, I'd like to have the additional protection that sandboxing would give me. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: openssh-server 1:7.4p1-10 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Fri May 12 21:06:20 2017 InstallationDate: Installed on 2017-04-08 (35 days ago) InstallationMedia: SourcePackage: openssh UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1690485 Title: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox' Status in openssh package in Ubuntu: New Bug description: The 'sshd' process gets 'authentication failure' and refuses to allow any login. dmesg indicates that the problem is SIGSYS on a call to 'socket' (syscall #41, signal #31). On a hunch, I decided to test whether the problem is related to 'seccomp' and changed /etc/ssh/sshd_config from the default # UsePrivilegeSeparation sandbox to the former standard value UsePrivilegeSeparation yes and logins started to work again. Obviously, I'd like to have the additional protection that sandboxing would give me. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: openssh-server 1:7.4p1-10 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Fri May 12 21:06:20 2017 InstallationDate: Installed on 2017-04-08 (35 days ago) InstallationMedia: SourcePackage: openssh UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+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 1690482] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1690482/+attachment/4875892/+files/ThreadStacktrace.txt ** Tags added: apport-failed-retrace ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1690482 Title: hud-service crashed with SIGSEGV Status in hud package in Ubuntu: New Bug description: Notification appeared while running updater; updater stalled 'waiting for dpkg to exit; then resumed after a couple of minutes. Not knowledgeable to comment further. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: hud 14.10+17.04.20170106.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic i686 ApportVersion: 2.20.4-0ubuntu7 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Thu May 11 17:45:46 2017 ExecutablePath: /usr/lib/i386-linux-gnu/hud/hud-service InstallationDate: Installed on 2017-04-28 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170426) ProcCmdline: /usr/lib/i386-linux-gnu/hud/hud-service ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0xb7748a74:cwtl PC (0xb7748a74) in non-executable VMA region: 0xb7748000-0xb7749000 rw-p /lib/i386-linux-gnu/ld-2.24.so SegvReason: executing writable VMA /lib/i386-linux-gnu/ld-2.24.so Signal: 11 SourcePackage: hud Stacktrace: #0 0xb7748a74 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7 StacktraceTop: ?? () Title: hud-service crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1690482/+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 1690482]
Stacktrace: #0 0xb7748a74 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7 StacktraceSource: #0 0xb7748a74 in ?? () StacktraceTop: ?? () -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1690482 Title: hud-service crashed with SIGSEGV Status in hud package in Ubuntu: New Bug description: Notification appeared while running updater; updater stalled 'waiting for dpkg to exit; then resumed after a couple of minutes. Not knowledgeable to comment further. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: hud 14.10+17.04.20170106.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic i686 ApportVersion: 2.20.4-0ubuntu7 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Thu May 11 17:45:46 2017 ExecutablePath: /usr/lib/i386-linux-gnu/hud/hud-service InstallationDate: Installed on 2017-04-28 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170426) ProcCmdline: /usr/lib/i386-linux-gnu/hud/hud-service ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0xb7748a74:cwtl PC (0xb7748a74) in non-executable VMA region: 0xb7748000-0xb7749000 rw-p /lib/i386-linux-gnu/ld-2.24.so SegvReason: executing writable VMA /lib/i386-linux-gnu/ld-2.24.so Signal: 11 SourcePackage: hud Stacktrace: #0 0xb7748a74 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7 StacktraceTop: ?? () Title: hud-service crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1690482/+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 1690482] [NEW] hud-service crashed with SIGSEGV
Public bug reported: Notification appeared while running updater; updater stalled 'waiting for dpkg to exit; then resumed after a couple of minutes. Not knowledgeable to comment further. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: hud 14.10+17.04.20170106.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic i686 ApportVersion: 2.20.4-0ubuntu7 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Thu May 11 17:45:46 2017 ExecutablePath: /usr/lib/i386-linux-gnu/hud/hud-service InstallationDate: Installed on 2017-04-28 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170426) ProcCmdline: /usr/lib/i386-linux-gnu/hud/hud-service ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0xb7748a74: cwtl PC (0xb7748a74) in non-executable VMA region: 0xb7748000-0xb7749000 rw-p /lib/i386-linux-gnu/ld-2.24.so SegvReason: executing writable VMA /lib/i386-linux-gnu/ld-2.24.so Signal: 11 SourcePackage: hud Stacktrace: #0 0xb7748a74 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7 StacktraceTop: ?? () Title: hud-service crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: hud (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash artful i386 need-i386-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1690482 Title: hud-service crashed with SIGSEGV Status in hud package in Ubuntu: New Bug description: Notification appeared while running updater; updater stalled 'waiting for dpkg to exit; then resumed after a couple of minutes. Not knowledgeable to comment further. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: hud 14.10+17.04.20170106.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic i686 ApportVersion: 2.20.4-0ubuntu7 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Thu May 11 17:45:46 2017 ExecutablePath: /usr/lib/i386-linux-gnu/hud/hud-service InstallationDate: Installed on 2017-04-28 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170426) ProcCmdline: /usr/lib/i386-linux-gnu/hud/hud-service ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0xb7748a74:cwtl PC (0xb7748a74) in non-executable VMA region: 0xb7748000-0xb7749000 rw-p /lib/i386-linux-gnu/ld-2.24.so SegvReason: executing writable VMA /lib/i386-linux-gnu/ld-2.24.so Signal: 11 SourcePackage: hud Stacktrace: #0 0xb7748a74 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7 StacktraceTop: ?? () Title: hud-service crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1690482/+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 1687981] Proposed package upload rejected
An upload of libxfont to xenial-proposed has been rejected from the upload queue for the following reason: "libxfont1 vs. libxfont2 source layout to be discussed". -- 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/1687981 Title: Backport packages for 16.04.3 HWE stack Status in debhelper package in Ubuntu: Invalid Status in dh-autoreconf package in Ubuntu: Invalid Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont1 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in debhelper source package in Xenial: Won't Fix Status in dh-autoreconf source package in Xenial: Won't Fix Status in libclc source package in Xenial: New Status in libdrm source package in Xenial: New Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: New Status in libxfont source package in Xenial: New Status in libxfont1 source package in Xenial: New Status in llvm-toolchain-4.0 source package in Xenial: New Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: New Status in wayland source package in Xenial: New Status in x11proto-core source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1687981] Re: Backport packages for 16.04.3 HWE stack
I don't think we should change around the libxfont and libxfont1 source packages in SRU; this would e.g. make it more confusing to try to do security updates of libxfont in xenial if necessary. It also doesn't look to me like the version bump from libxfont 1.5.1 to libxfont1 1.5.2 is justified under SRU policy. I would prefer to see: - libxfont source SRU, renaming libxfont-dev to libxfont1-dev - libxfont2 introduced as a new source package, which can be the libxfont from artful with a source rename. For now, rejecting these two uploads from the queue pending discussion. -- 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/1687981 Title: Backport packages for 16.04.3 HWE stack Status in debhelper package in Ubuntu: Invalid Status in dh-autoreconf package in Ubuntu: Invalid Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont1 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in debhelper source package in Xenial: Won't Fix Status in dh-autoreconf source package in Xenial: Won't Fix Status in libclc source package in Xenial: New Status in libdrm source package in Xenial: New Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: New Status in libxfont source package in Xenial: New Status in libxfont1 source package in Xenial: New Status in llvm-toolchain-4.0 source package in Xenial: New Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: New Status in wayland source package in Xenial: New Status in x11proto-core source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1687981] Re: Backport packages for 16.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted x11proto-core into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/x11proto- core/7.0.31-1~ubuntu16.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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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: x11proto-core (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1687981 Title: Backport packages for 16.04.3 HWE stack Status in debhelper package in Ubuntu: Invalid Status in dh-autoreconf package in Ubuntu: Invalid Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont1 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in debhelper source package in Xenial: Won't Fix Status in dh-autoreconf source package in Xenial: Won't Fix Status in libclc source package in Xenial: New Status in libdrm source package in Xenial: New Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: New Status in libxfont source package in Xenial: New Status in libxfont1 source package in Xenial: New Status in llvm-toolchain-4.0 source package in Xenial: New Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: New Status in wayland source package in Xenial: New Status in x11proto-core source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS
The updated package works for my OTP user. Thanks a lot! Jochen ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1683237 Title: krb5-user: kinit fails for OTP user when using kdc discovery via DNS Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Zesty: Fix Committed Status in krb5 package in Debian: Fix Released Bug description: This is fixed in krb5 1.15-2 in artful Upstream bug : http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554 Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307 Debian patch in 1.15-2 in artful: 0013-Fix-udp_preference_limit-with-SRV-records.patch [Impact] kinit does not respect udp_preference_limit and always uses TCP to talk to the KDC when using the DNS SRV records to locate the service and these records show both udp and tcp entries. One particular scenario that fails is when OTP (one time password) is used, as reported. The provided patch is applied upstream and debian testing. [Test Case] Steps to reproduce on zesty, with all services on one machine for simplicity (I suggest to use LXD): a) install the packages from zesty (not the proposed ones yet): $ sudo apt install krb5-kdc krb5-admin-server bind9 When prompted for the realm, choose EXAMPLE.COM When prompted for the KDC and Admin services server address, use the IP of your test machine/container (not localhost or 127.0.0.1) The KDC will fail to start because there is no realm yet, that's not relevant for this bug. b) Edit /etc/krb5.conf and make the following changes: - remove the "default_realm" line from the [libdefaults] section - remove the EXAMPLE.COM realm block from the [realms] section - add "dns_lookup_realm = true" to the [libdefaults] section - add "dns_lookup_kdc = true" to the [libdefaults] section - add "udp_preference_limit = 1" to the [libdefaults] section c) Edit /etc/bind/named.conf.local and add this zone block (for simplicity, we are skipping the reverse zone): zone "example.com" { type master; file "/etc/bind/db.example.com"; }; d) Create /etc/bind/db.example.com with this content: $TTL604800 @ IN SOA example.com. ubuntu.example.com. ( 1 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS zesty-bug1683237.example.com. zesty-bug1683237IN A 10.0.100.249 _kerberos TXT "EXAMPLE.COM" _kerberos._udp SRV 0 0 88 zesty-bug1683237 _kerberos._tcp SRV 0 0 88 zesty-bug1683237 _kerberos-master._udp SRV 0 0 88 zesty-bug1683237 _kerberos-master._tcp SRV 0 0 88 zesty-bug1683237 _kerberos-adm._tcp SRV 0 0 749 zesty-bug1683237 _kpasswd._udp SRV 0 0 464 zesty-bug1683237 Use the real IP of your test machine/container where I used "10.0.100.249". You can also choose another hostname if you want, just be consistent across the board. I chose "zesty-bug1683237". e) Restart bind $ sudo service bind9 restart f) Do a few quick DNS tests: $ dig +short @10.0.100.249 zesty-bug1683237.example.com 10.0.100.249 $ dig +short @10.0.100.249 -t TXT _kerberos.example.com "EXAMPLE.COM" $ dig +short @10.0.100.249 -t SRV _kerberos._udp.example.com 0 0 88 zesty-bug1683237.example.com. $ dig +short @10.0.100.249 -t SRV _kerberos._tcp.example.com 0 0 88 zesty-bug1683237.example.com. g) Edit /etc/resolv.conf, ignoring the warning since we are not going to reboot or change network interfaces: nameserver 10.0.100.249 # USE YOUR IP HERE search example.com h) Create the EXAMPLE.COM kerberos realm: $ sudo krb5_newrealm When prompted for a password, use whatever you like. If you get an error about no default realm, then your TXT record in DNS is not working. Retrace your DNS configuration steps. i) Start the kerberos services: $ sudo service krb5-kdc start sudo service krb5-admin-server start j) Create a principal and test it: $ sudo kadmin.local addprinc -pw ubuntu ubuntu $ kinit ubuntu Password for ubu...@example.com: $ klist (...) 05/05/2017 13:10:01 05/05/2017 23:10:01 krbtgt/example@example.com (...) Now we are ready to test the bug. Given that we have udp_preference_limit = 1 in /etc/krb5.conf, kinit should use TCP instead of UDP. Let's check: $ KRB5_TRACE=/dev/stderr kinit [7609] 1493989890.568980: Getting initial credentials for ubu...@example.com [7609] 1493989890.569904: Sending request (172 bytes) to EXAMPLE.COM [7609] 1493989890.571991: Resolving hostname zesty-bug1683237.example.com. [7609] 1493989890.576853: Sending initial UDP r
[Touch-packages] [Bug 1690455] [NEW] not output sound, I can hear it by headphones
Public bug reported: I make sure that the speakers is the default output. but usually i hear by headphones no speakers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elfaleh1797 F pulseaudio Date: Fri May 12 22:49:56 2017 InstallationDate: Installed on 2017-01-04 (128 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to xenial on 2017-01-04 (128 days ago) dmi.bios.date: 07/31/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 047MWF dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd07/31/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1690455 Title: not output sound, I can hear it by headphones Status in pulseaudio package in Ubuntu: New Bug description: I make sure that the speakers is the default output. but usually i hear by headphones no speakers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elfaleh1797 F pulseaudio Date: Fri May 12 22:49:56 2017 InstallationDate: Installed on 2017-01-04 (128 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to xenial on 2017-01-04 (128 days ago) dmi.bios.date: 07/31/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 047MWF dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd07/31/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690455/+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 1654676] Re: lxc-user-nic does not ensure that target netns is caller-owned
** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1654676 Title: lxc-user-nic does not ensure that target netns is caller-owned Status in lxc package in Ubuntu: Fix Released Bug description: The documentation for lxc-user-nic claims: It ensures that the calling user is privileged over the network namespace to which the interface will be attached. Actually, the code only verifies that a process of the calling user is running in the network namespace to which the interface will be attached. To verify this: - As root, create a new bridge "lxcbr0". - As root, add an entry like "user veth lxcbr0 10" to /etc/lxc/lxc-usernet. - As the user specified in /etc/lxc/lxc-usernet, run the following command: /usr/lib/x86_64-linux-gnu/lxc/lxc-user-nic a b $$ veth lxcbr0 foobar - Run "ip link show foobar". The output shows that a network interface with the name "foobar" was created in the init namespace (in which the user is not privileged). I suspect that it would also be possible to trick lxc-user-nic into operating on namespaces the caller can't access by reassigning the PID while lxc-user-nic is running, between the access check and the netlink calls - this is probably quite hard to fix, considering that the netlink interface just uses a PID to identify the target namespace. I haven't found any way to actually exploit this; however, it seems interesting that this can e.g. be used to create network interfaces whose names contain special characters like dollar, semicolon and backtick. I'm not sure how dangerous that is - I'm reporting it as a security bug for now, but if you feel that this has no security impact, feel free to derestrict it. One way to fix this might be to temporarily drop privileges (setresuid(ruid, ruid, 0)) in rename_in_ns() after the first setns() call. This way, the renaming could only succeed if the caller is actually privileged in the network namespace. release: Ubuntu 16.10 version: lxc-common: 2.0.6-0ubuntu1~ubuntu16.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1654676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1689585] Re: ntp doesn't unload its apparmor profile on purge
On 2017-05-12 03:34 PM, Seth Arnold wrote: > On Fri, May 12, 2017 at 06:56:35PM -, Simon Déziel wrote: >> If purging a package doesn't kill the running process, that's a >> packaging bug, not something Apparmor should try to paper over, IMHO. > > Yikes, package pre/post inst/rm scripts already do way too many things. > Deciding what processes to kill is way too much. No thanks. :) Sorry, I meant it's the service's job to properly/forcefully stop a daemon. I agree that killing processes in postrm is dangerous. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1689585 Title: ntp doesn't unload its apparmor profile on purge Status in apparmor package in Ubuntu: Won't Fix Status in ntp package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) install ntp apt install ntp 2) confirm it has loaded its AA profile aa-status | grep ntpd 3) purge ntp apt purge ntp 4) the profile is left behind but shouldn't aa-status | grep ntpd Additional info: This was found by first install ntp then changing my mind and deciding to go with OpenNTPD. FYI, just installing openntpd while ntp is still there works because openntpd has a kludge to unload ntpd's profile but that only works if the ntp package wasn't purged before. /var/lib/dpkg/info/openntpd.preinst: if [ -f /etc/apparmor.d/usr.sbin.ntpd ] && pathfind apparmor_parser ; then apparmor_parser -R /etc/apparmor.d/usr.sbin.ntpd fi Since a purge deletes /etc/apparmor.d/usr.sbin.ntpd, openntpd.preinst's kludge is ineffective. In any case, having implementation B include workaround for implementation A not cleaning up after itself seems wrong and the issue should be fixed at the source IMHO. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 # apt-cache policy ntp ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.4 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.4 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.4 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.8p4+dfsg-3ubuntu5.3 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1:4.2.8p4+dfsg-3ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 9 15:48:42 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1689585/+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 1689093] Re: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04
This is now in the queue for review by the SRU team (but maybe not me). ** Changed in: apport (Ubuntu Trusty) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1689093 Title: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04 Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Triaged Status in apport source package in Xenial: Triaged Bug description: Impact -- As announced, the GNOME3 PPAs for Ubuntu 16.04 LTS are no longer being maintained as of April 2017. Therefore, the Ubuntu GNOME project would like to stop receiving bugs from packages installed from those PPAs for that version, or for 14.04 LTS which is no longer supported by Ubuntu GNOME. See https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3 Test Case - sudo add-apt-repository ppa:gnome3-team/gnome3 sudo apt update sudo apt upgrade Ubuntu 14.04: ubuntu-bug gnome-system-monitor Ubuntu 16.04: ubuntu-bug nautilus What should happen: After several moments, you should see a popup with The GNOME3 PPA you are using is no longer supported for this Ubuntu release. Please run "ppa-purge ppa:gnome3-team/gnome3". Clean up: sudo apt install ppa-purge sudo ppa-purge ppa:gnome3-team/gnome3 Other Info -- Ubuntu GNOME has always installed ppa-purge by default. Regression Potential People will be unable to report bugs with PPA packages like they used to but they'll be told why. The message unfortunately likely won't be translated right away, but since it will land in the development release, it should eventually be translated for future Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1689585] Re: ntp doesn't unload its apparmor profile on purge
On Fri, May 12, 2017 at 06:56:35PM -, Simon Déziel wrote: > If purging a package doesn't kill the running process, that's a > packaging bug, not something Apparmor should try to paper over, IMHO. Yikes, package pre/post inst/rm scripts already do way too many things. Deciding what processes to kill is way too much. No thanks. :) Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1689585 Title: ntp doesn't unload its apparmor profile on purge Status in apparmor package in Ubuntu: Won't Fix Status in ntp package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) install ntp apt install ntp 2) confirm it has loaded its AA profile aa-status | grep ntpd 3) purge ntp apt purge ntp 4) the profile is left behind but shouldn't aa-status | grep ntpd Additional info: This was found by first install ntp then changing my mind and deciding to go with OpenNTPD. FYI, just installing openntpd while ntp is still there works because openntpd has a kludge to unload ntpd's profile but that only works if the ntp package wasn't purged before. /var/lib/dpkg/info/openntpd.preinst: if [ -f /etc/apparmor.d/usr.sbin.ntpd ] && pathfind apparmor_parser ; then apparmor_parser -R /etc/apparmor.d/usr.sbin.ntpd fi Since a purge deletes /etc/apparmor.d/usr.sbin.ntpd, openntpd.preinst's kludge is ineffective. In any case, having implementation B include workaround for implementation A not cleaning up after itself seems wrong and the issue should be fixed at the source IMHO. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 # apt-cache policy ntp ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.4 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.4 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.4 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.8p4+dfsg-3ubuntu5.3 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1:4.2.8p4+dfsg-3ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 9 15:48:42 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1689585/+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 1399734] Re: Current tab is not highlighted
It is NOT fixed in gnome-terminal 3.18.3. Here's my fix for the Ambiant-MATE theme: toor@ubuntu:/usr/share/themes/Ambiant-MATE/gtk-3.0$ cat gtk.css TerminalWindow .notebook tab.top:active { font: bold; background-color: alpha(grey, 0.0); } TerminalWindow .notebook tab.top { background-color: alpha(grey, 0.4); } @import url("gtk-main.css"); -- 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/1399734 Title: Current tab is not highlighted Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: With the Ambiance or Radiance theme, in windows using a GtkNotebook the current tab is not highlighted to distinguish it from hidden tabs. In some apps you can just about see a faint line under the inactive tabs, but some apps, such as roxterm, don't use the border option, so it's impossible to tell which tab is selected. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: light-themes 14.04+14.10.20141015-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 5 17:27:41 2014 InstallationDate: Installed on 2014-06-13 (174 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to utopic on 2014-10-24 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1399734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1689585] Re: ntp doesn't unload its apparmor profile on purge
On 2017-05-12 02:15 PM, Christian Boltz wrote: > You are technically correct that the still-loaded profile doesn't > match a clean uninstall. However, I have a different opinion on this > and thing keeping the profile loaded is the better choice. > > Unloading a profile means removing the confinement from running > processes. So if a process is still running and (Hi Murphy!) does > something bad after being uninstalled and becoming unconfined, you > are screwed up. If purging a package doesn't kill the running process, that's a packaging bug, not something Apparmor should try to paper over, IMHO. > If the profile stays loaded, still running processes stay confined. > The disadvantages are a) you waste some bytes in the RAM and b) if > you install a different package shipping a binary with the same path, > but without an AppArmor profile, it will suffer from the > still-loaded profile. Asking someone to know about that: echo -n "" > /sys/kernel/security/apparmor/.remove Is asking too much IMHO and increases the friction between sysadmins and Apparmor in general. The colleague that experience the issue was about to do an Apparmor teardown to get going... > Both ways are not perfect, but I really prefer keeping the profile > loaded because it does less harm. > > > For comparison: Does the uninstall script also run "killall -9 ntp"? > If so, feel free to unload the profile ;-) I still think that having dh_apparmor do the unload is the best way :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1689585 Title: ntp doesn't unload its apparmor profile on purge Status in apparmor package in Ubuntu: Won't Fix Status in ntp package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) install ntp apt install ntp 2) confirm it has loaded its AA profile aa-status | grep ntpd 3) purge ntp apt purge ntp 4) the profile is left behind but shouldn't aa-status | grep ntpd Additional info: This was found by first install ntp then changing my mind and deciding to go with OpenNTPD. FYI, just installing openntpd while ntp is still there works because openntpd has a kludge to unload ntpd's profile but that only works if the ntp package wasn't purged before. /var/lib/dpkg/info/openntpd.preinst: if [ -f /etc/apparmor.d/usr.sbin.ntpd ] && pathfind apparmor_parser ; then apparmor_parser -R /etc/apparmor.d/usr.sbin.ntpd fi Since a purge deletes /etc/apparmor.d/usr.sbin.ntpd, openntpd.preinst's kludge is ineffective. In any case, having implementation B include workaround for implementation A not cleaning up after itself seems wrong and the issue should be fixed at the source IMHO. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 # apt-cache policy ntp ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.4 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.4 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.4 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.8p4+dfsg-3ubuntu5.3 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1:4.2.8p4+dfsg-3ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 9 15:48:42 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1689585/+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 1690437] Re: xenial autopkgtest fails because its using an End of Life release
** Changed in: apport (Ubuntu Xenial) Status: New => In Progress ** Changed in: apport (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1690437 Title: xenial autopkgtest fails because its using an End of Life release Status in apport package in Ubuntu: Invalid Status in apport source package in Xenial: In Progress Bug description: [Impact] A xenial autopackagetest, test_backend_apt_dpkg.py, for apport is failing because they try and get data from ddebs.ubuntu.com for an End of Life release. [Test Case] 1) Observe the autopkgtest failure "SystemError: W:The repository 'http://ddebs.ubuntu.com wily Release' does not have a Release file., W:Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., E:Failed to fetch http://ddebs.ubuntu.com/dists/wily/main/binary-armhf/Packages 404 Not Found, E:Some index files failed to download. They have been ignored, or old ones used instead." With the version of apport in -proposed their will not be an autopkgtest failure. [Regression Potential] We are switching to the version of the autopkgtest which is currently working in apport and has been working since yakkety's development. Additionally, its just a test change so there should be no regressions. Here's a link to a failure: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- xenial/xenial/amd64/a/apport/20170426_142511_fd07d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1690437/+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 1689585] Re: ntp doesn't unload its apparmor profile on purge
Christian is right and this is precisely why dh_apparmor intentionally does not unload the profile. Marking the apparmor task as Won't Fix since this has been discussed several times in the past (if apparmor upstream wants to revisit, we can open the bug). The ntp package is still in a position to unload the profile if it desires, so leaving its task open, but I believe this would be a mistake and if done in Ubuntu, I would file a bug requesting the previous behavior. I don't particularly care for the openntpd kludge, but you can unload a profile that was deleted from disk with: sudo sh -c 'echo -n /usr/sbin/ntpd > /sys/kernel/security/apparmor/.remove' (note, the '-n' with echo is important). ** Changed in: apparmor (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1689585 Title: ntp doesn't unload its apparmor profile on purge Status in apparmor package in Ubuntu: Won't Fix Status in ntp package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) install ntp apt install ntp 2) confirm it has loaded its AA profile aa-status | grep ntpd 3) purge ntp apt purge ntp 4) the profile is left behind but shouldn't aa-status | grep ntpd Additional info: This was found by first install ntp then changing my mind and deciding to go with OpenNTPD. FYI, just installing openntpd while ntp is still there works because openntpd has a kludge to unload ntpd's profile but that only works if the ntp package wasn't purged before. /var/lib/dpkg/info/openntpd.preinst: if [ -f /etc/apparmor.d/usr.sbin.ntpd ] && pathfind apparmor_parser ; then apparmor_parser -R /etc/apparmor.d/usr.sbin.ntpd fi Since a purge deletes /etc/apparmor.d/usr.sbin.ntpd, openntpd.preinst's kludge is ineffective. In any case, having implementation B include workaround for implementation A not cleaning up after itself seems wrong and the issue should be fixed at the source IMHO. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 # apt-cache policy ntp ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.4 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.4 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.4 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.8p4+dfsg-3ubuntu5.3 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1:4.2.8p4+dfsg-3ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 9 15:48:42 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1689585/+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 1690437] [NEW] xenial autopkgtest fails because its using an End of Life release
Public bug reported: [Impact] A xenial autopackagetest, test_backend_apt_dpkg.py, for apport is failing because they try and get data from ddebs.ubuntu.com for an End of Life release. [Test Case] 1) Observe the autopkgtest failure "SystemError: W:The repository 'http://ddebs.ubuntu.com wily Release' does not have a Release file., W:Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., E:Failed to fetch http://ddebs.ubuntu.com/dists/wily/main/binary-armhf/Packages 404 Not Found, E:Some index files failed to download. They have been ignored, or old ones used instead." With the version of apport in -proposed their will not be an autopkgtest failure. [Regression Potential] We are switching to the version of the autopkgtest which is currently working in apport and has been working since yakkety's development. Additionally, its just a test change so there should be no regressions. Here's a link to a failure: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/amd64/a/apport/20170426_142511_fd07d@/log.gz ** Affects: apport (Ubuntu) Importance: Undecided Status: Invalid ** Affects: apport (Ubuntu Xenial) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apport (Ubuntu) Status: New => Invalid -- 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/1690437 Title: xenial autopkgtest fails because its using an End of Life release Status in apport package in Ubuntu: Invalid Status in apport source package in Xenial: In Progress Bug description: [Impact] A xenial autopackagetest, test_backend_apt_dpkg.py, for apport is failing because they try and get data from ddebs.ubuntu.com for an End of Life release. [Test Case] 1) Observe the autopkgtest failure "SystemError: W:The repository 'http://ddebs.ubuntu.com wily Release' does not have a Release file., W:Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., E:Failed to fetch http://ddebs.ubuntu.com/dists/wily/main/binary-armhf/Packages 404 Not Found, E:Some index files failed to download. They have been ignored, or old ones used instead." With the version of apport in -proposed their will not be an autopkgtest failure. [Regression Potential] We are switching to the version of the autopkgtest which is currently working in apport and has been working since yakkety's development. Additionally, its just a test change so there should be no regressions. Here's a link to a failure: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- xenial/xenial/amd64/a/apport/20170426_142511_fd07d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1690437/+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 1651623] Re: adt tests fail on zesty for apport
Some autopkgtests fail on xenial but not for this reason, so I'm setting the task to Invalid. ** Changed in: apport (Ubuntu Xenial) Status: New => Invalid -- 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/1651623 Title: adt tests fail on zesty for apport Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Invalid Status in apport source package in Yakkety: Fix Committed Status in apport source package in Zesty: Fix Committed Bug description: [Impact] Apport autopkgtests are failing with GPG errors e.g.: SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed. [Test Case] Run the autopkgtests and observe failures regarding GPG. With the test fixed there should be no failures. [Regression Potential] While not a regression its possible fixing these tests will reveal other failures. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 1673557] Please test proposed package
Hello Brian, or anyone else affected, Accepted whoopsie into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/whoopsie/0.2.52.3 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: New Status in whoopsie source package in Trusty: New Status in apport source package in Xenial: New Status in whoopsie source package in Xenial: Fix Committed Status in apport source package in Yakkety: Fix Committed Status in whoopsie source package in Yakkety: Fix Committed Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Re: /proc/cpuinfo should be collected
Hello Brian, or anyone else affected, Accepted apport into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.3 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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: apport (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: whoopsie (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: New Status in whoopsie source package in Trusty: New Status in apport source package in Xenial: New Status in whoopsie source package in Xenial: Fix Committed Status in apport source package in Yakkety: Fix Committed Status in whoopsie source package in Yakkety: Fix Committed Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Please test proposed package
Hello Brian, or anyone else affected, Accepted whoopsie into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/whoopsie/0.2.54.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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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: whoopsie (Ubuntu Xenial) Status: New => Fix Committed -- 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/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: New Status in whoopsie source package in Trusty: New Status in apport source package in Xenial: New Status in whoopsie source package in Xenial: Fix Committed Status in apport source package in Yakkety: Fix Committed Status in whoopsie source package in Yakkety: Fix Committed Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1689585] Re: ntp doesn't unload its apparmor profile on purge
You are technically correct that the still-loaded profile doesn't match a clean uninstall. However, I have a different opinion on this and thing keeping the profile loaded is the better choice. Unloading a profile means removing the confinement from running processes. So if a process is still running and (Hi Murphy!) does something bad after being uninstalled and becoming unconfined, you are screwed up. If the profile stays loaded, still running processes stay confined. The disadvantages are a) you waste some bytes in the RAM and b) if you install a different package shipping a binary with the same path, but without an AppArmor profile, it will suffer from the still-loaded profile. Both ways are not perfect, but I really prefer keeping the profile loaded because it does less harm. For comparison: Does the uninstall script also run "killall -9 ntp"? If so, feel free to unload the profile ;-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1689585 Title: ntp doesn't unload its apparmor profile on purge Status in apparmor package in Ubuntu: New Status in ntp package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) install ntp apt install ntp 2) confirm it has loaded its AA profile aa-status | grep ntpd 3) purge ntp apt purge ntp 4) the profile is left behind but shouldn't aa-status | grep ntpd Additional info: This was found by first install ntp then changing my mind and deciding to go with OpenNTPD. FYI, just installing openntpd while ntp is still there works because openntpd has a kludge to unload ntpd's profile but that only works if the ntp package wasn't purged before. /var/lib/dpkg/info/openntpd.preinst: if [ -f /etc/apparmor.d/usr.sbin.ntpd ] && pathfind apparmor_parser ; then apparmor_parser -R /etc/apparmor.d/usr.sbin.ntpd fi Since a purge deletes /etc/apparmor.d/usr.sbin.ntpd, openntpd.preinst's kludge is ineffective. In any case, having implementation B include workaround for implementation A not cleaning up after itself seems wrong and the issue should be fixed at the source IMHO. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 # apt-cache policy ntp ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.4 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.4 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.4 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.8p4+dfsg-3ubuntu5.3 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1:4.2.8p4+dfsg-3ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 9 15:48:42 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1689585/+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 1651623] Re: adt tests fail on zesty for apport
Hello Dimitri, or anyone else affected, Accepted apport into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.3 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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: apport (Ubuntu Yakkety) Status: In Progress => Fix Committed -- 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/1651623 Title: adt tests fail on zesty for apport Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Yakkety: Fix Committed Status in apport source package in Zesty: Fix Committed Bug description: [Impact] Apport autopkgtests are failing with GPG errors e.g.: SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed. [Test Case] Run the autopkgtests and observe failures regarding GPG. With the test fixed there should be no failures. [Regression Potential] While not a regression its possible fixing these tests will reveal other failures. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 1689344] Re: print of __glib_assert_msg not returning a message
Hello Brian, or anyone else affected, Accepted apport into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.3 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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: apport (Ubuntu Yakkety) Status: In Progress => Fix Committed -- 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/1689344 Title: print of __glib_assert_msg not returning a message Status in apport package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: New Status in apport source package in Yakkety: Fix Committed Status in glib2.0 source package in Yakkety: New Status in apport source package in Zesty: Fix Committed Status in glib2.0 source package in Zesty: New Bug description: [Impact] apport's test, test_add_gdb_info_abort_glib is failing due to a change somewhere in glib2.0, how its built, or gdb. The test shall be disabled while the matter is investigated. [Test Case] Run the autopkgtest and observe the failure. With the version of the package in proposed the test will not be run. [Regression Potential] We are just disabling a broken test so there is none. apport's test test_add_gdb_info_abort_glib has been failing for a bit, since zesty(?), now. Digging into this matter I discovered that using gdb to "print __glib_assert_msg" is resulting in different behavior. With the generated binary, it used to return the following: $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 < 0)" However, now I am seeing: (gdb) print __glib_assert_msg $1 = 1332592064 (gdb) print (char*) __glib_assert_msg $2 = 0x4f6dbdc0 This seems to be a regression in gdb itself, I've added an apport task though to track the disabling of the autopkgtest which utilizes this command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+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
Sorry, that's on a 9560, not 7650. ^ -- 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 alsa-driver 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/ubuntu/+source/alsa-driver/+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 1651623] Re: adt tests fail on zesty for apport
Hello Dimitri, or anyone else affected, Accepted apport into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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: apport (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1651623 Title: adt tests fail on zesty for apport Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Yakkety: In Progress Status in apport source package in Zesty: Fix Committed Bug description: [Impact] Apport autopkgtests are failing with GPG errors e.g.: SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed. [Test Case] Run the autopkgtests and observe failures regarding GPG. With the test fixed there should be no failures. [Regression Potential] While not a regression its possible fixing these tests will reveal other failures. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 1689344] Re: print of __glib_assert_msg not returning a message
Hello Brian, or anyone else affected, Accepted apport into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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: apport (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1689344 Title: print of __glib_assert_msg not returning a message Status in apport package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: New Status in apport source package in Yakkety: In Progress Status in glib2.0 source package in Yakkety: New Status in apport source package in Zesty: Fix Committed Status in glib2.0 source package in Zesty: New Bug description: [Impact] apport's test, test_add_gdb_info_abort_glib is failing due to a change somewhere in glib2.0, how its built, or gdb. The test shall be disabled while the matter is investigated. [Test Case] Run the autopkgtest and observe the failure. With the version of the package in proposed the test will not be run. [Regression Potential] We are just disabling a broken test so there is none. apport's test test_add_gdb_info_abort_glib has been failing for a bit, since zesty(?), now. Digging into this matter I discovered that using gdb to "print __glib_assert_msg" is resulting in different behavior. With the generated binary, it used to return the following: $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 < 0)" However, now I am seeing: (gdb) print __glib_assert_msg $1 = 1332592064 (gdb) print (char*) __glib_assert_msg $2 = 0x4f6dbdc0 This seems to be a regression in gdb itself, I've added an apport task though to track the disabling of the autopkgtest which utilizes this command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+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 1688730] Re: click-apparmor ubuntu-app-launch url-dispatcher
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Package changed: linux (Ubuntu) => click-apparmor (Ubuntu) ** Changed in: click-apparmor (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1688730 Title: click-apparmor ubuntu-app-launch url-dispatcher Status in click-apparmor package in Ubuntu: New Bug description: Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: warning: subprocess old pre-removal script returned error exit status 1 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chanchal 2274 F pulseaudio /dev/snd/controlC0: chanchal 2274 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat May 6 18:58:27 2017 HibernationDevice: RESUME=UUID=459f0094-1f0b-4da8-9fac-1f2e7d6e36bc InstallationDate: Installed on 2016-02-20 (440 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 5537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=b87f269a-0aef-4bb0-93fa-18454ad51275 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-21-generic N/A linux-backports-modules-4.10.0-21-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-06 (0 days ago) dmi.bios.date: 08/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 04NGGW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/19/2013:svnDellInc.:pnInspiron5537:pvrA04:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA04: dmi.product.name: Inspiron 5537 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1688730/+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 1688730] [NEW] click-apparmor ubuntu-app-launch url-dispatcher
You have been subscribed to a public bug: Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: warning: subprocess old pre-removal script returned error exit status 1 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chanchal 2274 F pulseaudio /dev/snd/controlC0: chanchal 2274 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat May 6 18:58:27 2017 HibernationDevice: RESUME=UUID=459f0094-1f0b-4da8-9fac-1f2e7d6e36bc InstallationDate: Installed on 2016-02-20 (440 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 5537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=b87f269a-0aef-4bb0-93fa-18454ad51275 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-21-generic N/A linux-backports-modules-4.10.0-21-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-06 (0 days ago) dmi.bios.date: 08/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 04NGGW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/19/2013:svnDellInc.:pnInspiron5537:pvrA04:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA04: dmi.product.name: Inspiron 5537 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. ** Affects: click-apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed zesty -- click-apparmor ubuntu-app-launch url-dispatcher https://bugs.launchpad.net/bugs/1688730 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. -- 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 1673557] Re: /proc/cpuinfo should be collected
** Description changed: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal - With the version of the package from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. + + With the version of apport from -proposed you will have + ProcCpuinfoMinimal which will contain information about your processor. + + To verify the whoopsie change you'll want to do the following: + 1) sudo service whoopsie stop + 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f + 3) kill -11 a process (but not the whoopsie one!) + 4) confirm sending the report + 5) Find the OOPS ID in the whoopsie output + 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID + 7) Verify ProcCpuinfoMinimal appears in the OOPS + [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: New Status in whoopsie source package in Trusty: New Status in apport source package in Xenial: New Status in whoopsie source package in Xenial: New Status in apport source package in Yakkety: In Progress Status in whoopsie source package in Yakkety: New Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Re: /proc/cpuinfo should be collected
** Description changed: - apport does not currently collect data from /proc/cpuinfo and this would - be useful to determine how many users can only run the i386 version of - Ubuntu. + [Impact] + While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. + + [Test Case] + 1. Run ubuntu-bug 2vcard + 2. Observe there is no report key ProcCpuinfoMinimal + With the version of the package from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. + + [Regression Potential] + This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: New Status in whoopsie source package in Trusty: New Status in apport source package in Xenial: New Status in whoopsie source package in Xenial: New Status in apport source package in Yakkety: In Progress Status in whoopsie source package in Yakkety: New Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of the package from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1689344] Re: print of __glib_assert_msg not returning a message
** Description changed: + [Impact] + apport's test, test_add_gdb_info_abort_glib is failing due to a change somewhere in glib2.0, how its built, or gdb. The test shall be disabled while the matter is investigated. + + [Test Case] + Run the autopkgtest and observe the failure. + With the version of the package in proposed the test will not be run. + + [Regression Potential] + We are just disabling a broken test so there is none. + apport's test test_add_gdb_info_abort_glib has been failing for a bit, since zesty(?), now. Digging into this matter I discovered that using gdb to "print __glib_assert_msg" is resulting in different behavior. With the generated binary, it used to return the following: $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 < 0)" However, now I am seeing: - (gdb) print __glib_assert_msg + (gdb) print __glib_assert_msg $1 = 1332592064 - (gdb) print (char*) __glib_assert_msg + (gdb) print (char*) __glib_assert_msg $2 = 0x4f6dbdc0 This seems to be a regression in gdb itself, I've added an apport task though to track the disabling of the autopkgtest which utilizes this command. -- 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/1689344 Title: print of __glib_assert_msg not returning a message Status in apport package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: New Status in apport source package in Yakkety: In Progress Status in glib2.0 source package in Yakkety: New Status in apport source package in Zesty: In Progress Status in glib2.0 source package in Zesty: New Bug description: [Impact] apport's test, test_add_gdb_info_abort_glib is failing due to a change somewhere in glib2.0, how its built, or gdb. The test shall be disabled while the matter is investigated. [Test Case] Run the autopkgtest and observe the failure. With the version of the package in proposed the test will not be run. [Regression Potential] We are just disabling a broken test so there is none. apport's test test_add_gdb_info_abort_glib has been failing for a bit, since zesty(?), now. Digging into this matter I discovered that using gdb to "print __glib_assert_msg" is resulting in different behavior. With the generated binary, it used to return the following: $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 < 0)" However, now I am seeing: (gdb) print __glib_assert_msg $1 = 1332592064 (gdb) print (char*) __glib_assert_msg $2 = 0x4f6dbdc0 This seems to be a regression in gdb itself, I've added an apport task though to track the disabling of the autopkgtest which utilizes this command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+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
Dell XPS 7560 17.04 Gnome Headphone jack won't work at all until I suspend and wake, then I have no issues. Even the main speaker sometimes has issues now, but with alsactl restore and no headphones in, I can get them to work. -- 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 alsa-driver 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/ubuntu/+source/alsa-driver/+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 1651623] Re: adt tests fail on zesty for apport
** Description changed: - https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac - /autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz + [Impact] + Apport autopkgtests are failing with GPG errors e.g.: + SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed. + + [Test Case] + Run the autopkgtests and observe failures regarding GPG. + With the test fixed there should be no failures. + + [Regression Potential] + While not a regression its possible fixing these tests will reveal other failures. + + + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. -- 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/1651623 Title: adt tests fail on zesty for apport Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Yakkety: In Progress Status in apport source package in Zesty: In Progress Bug description: [Impact] Apport autopkgtests are failing with GPG errors e.g.: SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed. [Test Case] Run the autopkgtests and observe failures regarding GPG. With the test fixed there should be no failures. [Regression Potential] While not a regression its possible fixing these tests will reveal other failures. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 682662] Re: pam-auth-update ignores debconf settings
Same issue in #6 with Xenial. Same chef cookbook that works on 14.04 doesn't work on 16.04 because of the "seen" issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/682662 Title: pam-auth-update ignores debconf settings Status in pam package in Ubuntu: Triaged Status in pam package in Debian: Won't Fix Bug description: pam-auth-update ignores the current debconf-settings. This makes it impossible to do automatically configure pam in noninteractive installations. Demonstration: ~ # debconf-get-selections | grep libpam-runtime libpam-runtimelibpam-runtime/override boolean true libpam-runtimelibpam-runtime/conflictserror libpam-runtimelibpam-runtime/no_profiles_chosen error libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, ldap, tmpdir, gnome-keyring, consolekit libpam-runtimelibpam-runtime/you-had-no-auth error ~ # DEBIAN_FRONTEND=noninteractive pam-auth-update ~ # debconf-get-selections | grep libpam-runtime libpam-runtimelibpam-runtime/override boolean false libpam-runtimelibpam-runtime/conflictserror libpam-runtimelibpam-runtime/no_profiles_chosen error libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, winbind, ldap libpam-runtimelibpam-runtime/you-had-no-auth error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/682662/+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 1690336] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1690336 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in gconf package in Ubuntu: New Bug description: bug ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed May 10 18:56:29 2017 DuplicateSignature: package:gconf2-common:3.2.6-3ubuntu7 Setting up gconf2-common (3.2.6-3ubuntu7) ... dpkg: error processing package gconf2-common (--configure): subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-05-10 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1690336/+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 1690355] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1688721, so 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. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1690355 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: ... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri May 12 14:01:31 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1690355/+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 1690353] Re: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script 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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1690353 Title: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: Setting up openssh-server (1:7.3p1-1ubuntu0.1) ... Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2017-05-12 12:05:21 BST; 7ms ago Process: 21819 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 21819 (code=exited, status=255) May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Starting OpenBSD Secure Shell May 12 12:05:21 chris-XPS-13-9343 sshd[21819]: /etc/ssh/sshd_config line 92:...n May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Main process exit...a May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Failed to start OpenBSD Secure May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Unit entered fail May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Failed with resul Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: openssh-server 1:7.3p1-1ubuntu0.1 Uname: Linux 4.7.6-040706-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Fri May 12 11:25:50 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-07-16 (665 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 92: bad port number in PermitOpen SourcePackage: openssh Title: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-01-24 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690353/+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 1690178] Re: package lib32z1-dev 1:1.2.8.dfsg-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1690178 Title: package lib32z1-dev 1:1.2.8.dfsg-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5 Status in zlib package in Ubuntu: New Bug description: While this error looks very similar to the one in bug #1512992, it happened as a result of the updates that were released today, i.e., it seems like the result of the *fix* for that bug. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: lib32z1-dev 1:1.2.8.dfsg-2ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu May 11 15:49:23 2017 DpkgTerminalLog: Preparing to unpack .../00-lib32z1-dev_1%3a1.2.8.dfsg-2ubuntu5.1_amd64.deb ... Unpacking lib32z1-dev (1:1.2.8.dfsg-2ubuntu5.1) over (1:1.2.8.dfsg-2ubuntu5) ... dpkg: error processing archive /tmp/apt-dpkg-install-SywMFy/00-lib32z1-dev_1%3a1.2.8.dfsg-2ubuntu5.1_amd64.deb (--unpack): trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5 DuplicateSignature: package:lib32z1-dev:1:1.2.8.dfsg-2ubuntu5 Unpacking lib32z1-dev (1:1.2.8.dfsg-2ubuntu5.1) over (1:1.2.8.dfsg-2ubuntu5) ... dpkg: error processing archive /tmp/apt-dpkg-install-SywMFy/00-lib32z1-dev_1%3a1.2.8.dfsg-2ubuntu5.1_amd64.deb (--unpack): trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5 ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5 InstallationDate: Installed on 2015-01-25 (837 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: zlib Title: package lib32z1-dev 1:1.2.8.dfsg-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5 UpgradeStatus: Upgraded to yakkety on 2016-11-30 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1690178/+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 1690247] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1688721, so 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. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1690247 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: Confirmed Bug description: I tried installing 2 things, 1 was teamviewer and 1 was atom (from atom.io) it kept loading and loading then the error came up. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Thu May 11 18:12:26 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1690247/+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 1690382] Re: package passwd 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1690382 Title: package passwd 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device Status in shadow package in Ubuntu: New Bug description: libreoffice 5.3.3 not install ProblemType: Package DistroRelease: Ubuntu 14.04 Package: passwd 1:4.1.5.1-1ubuntu9.2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.23 Architecture: i386 Date: Fri May 12 11:07:07 2017 DuplicateSignature: package:passwd:1:4.1.5.1-1ubuntu9.2:unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device ErrorMessage: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device InstallationDate: Installed on 2014-06-02 (1074 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: shadow Title: package passwd 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1690382/+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 1689495] Re: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' object has no attribute 'write'
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1689495 Title: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' object has no attribute 'write' Status in unattended-upgrades package in Ubuntu: New Bug description: This happened after upgrading it to Artful. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: unattended-upgrades 0.93.1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu6 Architecture: amd64 CrashCounter: 1 Date: Tue May 9 08:20:24 2017 ExecutablePath: /usr/bin/unattended-upgrade InstallationDate: Installed on 2017-05-05 (3 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/unattended-upgrade -d 3 ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) LANG=en_IE.UTF-8 PythonArgs: ['/usr/bin/unattended-upgrade', '-d', '3'] SourcePackage: unattended-upgrades Title: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' object has no attribute 'write' UpgradeStatus: Upgraded to artful on 2017-05-05 (3 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1689495/+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 1666676] Re: Install tracker by default
[Sorry for late reply, I didn't get any notification] >Because nobody provided patches. I will welcome yours at >https://bugzilla.gnome.org/enter_bug.cgi?product=tracker > What are 'vendor' folders at all? vendor: Composer (php librarry manager) dumps libraries into vendor folder in the same directory where `composer update` is called. This is default behavior of composer. One way to think of the vendor directory is as a more generic form of "lib" I filed a bug https://bugzilla.gnome.org/show_bug.cgi?id=782562 >how did you measure the impact of these >modifications? Did you reindex from scratch after every modification? First time I ran tracker never stopped indexing. I monitored tracker- miner-fs.log and also with (/usr/libexec/tracker-extract -v 2). At some point you would expect logging to stop when it becomes idle. But it didn't. Only after tweaking and hard resetting situation improved dramatically. I found similar bugs on bugzilla, I will comment there. >I have the feeling here and other places above that you are >extrapolating personal usecases to entire user bases. Perhaps yes. But my intention is to put indexing at minimal level. In previous version of tracker I used with Ubuntu Gnome, meta.db in ~/.cache used to grow over 1 GB. Again I found the relative bug and will continue discussion over there. Let's not pollute this bug discussing tracker issues. ** Bug watch added: GNOME Bug Tracker #782562 https://bugzilla.gnome.org/show_bug.cgi?id=782562 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Install tracker by default Status in nautilus package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was previously decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch This bug is requesting that patch be dropped and the extra tracker components be allowed into main and installed by default in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 987003] Re: In Pangolin, a new administrator profile was not registred in the sudoer group (Lubuntu /Gnome environment)
Le 10/05/2017 à 08:07, 4tro a écrit : > be advised, Precise Pangolin is EOL. > > As such, maybe close this bug to reduce clutter? > Thanks you to contact me. I suggest to close this bug. I thought first, that at this time, it was certenly due to a successions of installations without update after each one. I didn't mention that I worked first without ability to connect this machine on the net, in a school in French Guyana, near the forest. So I had connected it at home for an new update. The last 14.04 LTs version of Lubuntu din't have these bugs. I think with a lot of friends that every body could constated along his life, that some systems or applications in a beta version could create a few repertory with restrictions of rights on a group user or for an user. In this case I just sugest to remember to verify the part of the bios controller of the hard disk, or hards disks themselves with a fsdisk (in hards situations) . Try to reinstall or last to update frequently as you can. Some of us sometimes reuse unit created with an Ms-dos like system, and after that, put a double boot on it. Don't have any hesitation to replace with sudo 755 rights by hands for home user directory concerned. Rember that, in my case, this old unit can't accept double boot, so I was obliged to work as a light embeded system, just trying to recycle it for my little classroom. Thanks for all. Didalter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/987003 Title: In Pangolin, a new administrator profile was not registred in the sudoer group (Lubuntu /Gnome environment) Status in sudo package in Ubuntu: New Bug description: I recently installed Lubuntu 12.04 cause my old computer wasn't completly accepted by unfinity live-dvd due to its cd limit. So I installed Lubuntu-desktop-cd first quitly fine, with no matter. After that I installed Gnome 3. (perhaps this anomaly was in the lubuntu-sudo first ?) My first administrator was fine accepted as Sudoer. So I installed two new users and an another admin in the Gnome environment . But , when I tried a "sudo aptitude" with this new "adm" profile, I discovered that the new administrator was not registred as sudoer : the message was "you are not a sudoer and I will make a report " and twice in synaptic or any command for admninistrator. So, I came back to verify these news status in the first admin's deskotp. In effect, the new admin was not registred in the "sudoer" group, but was registred in the "adm" group. First I put on the case for this new one in sudo and adm group. At the first try, the new admin sudoer registration "by hand" didn't took effect. I quitted and shutdown (as if in a simple ms boot-on system ;-) . And after reeboot, the new second admin was accepted as sudoer. So I thought I had to report this little anomaly before we have some newbes in trouble the D day. Perhaps wasn't due to succession of my manipulations or not ? So you have a part of answer, if it is. Good luck and long life for the Pangolin ! Alter.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/987003/+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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Also affects: mir (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: New Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1690382] [NEW] package passwd 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/j
Public bug reported: libreoffice 5.3.3 not install ProblemType: Package DistroRelease: Ubuntu 14.04 Package: passwd 1:4.1.5.1-1ubuntu9.2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.23 Architecture: i386 Date: Fri May 12 11:07:07 2017 DuplicateSignature: package:passwd:1:4.1.5.1-1ubuntu9.2:unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device ErrorMessage: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device InstallationDate: Installed on 2014-06-02 (1074 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: shadow Title: package passwd 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1690382 Title: package passwd 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device Status in shadow package in Ubuntu: New Bug description: libreoffice 5.3.3 not install ProblemType: Package DistroRelease: Ubuntu 14.04 Package: passwd 1:4.1.5.1-1ubuntu9.2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.23 Architecture: i386 Date: Fri May 12 11:07:07 2017 DuplicateSignature: package:passwd:1:4.1.5.1-1ubuntu9.2:unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device ErrorMessage: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device InstallationDate: Installed on 2014-06-02 (1074 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: shadow Title: package passwd 1:4.1.5.1-1ubuntu9.2 failed to install/upgrade: unable to create `/usr/share/man/ja/man8/usermod.8.gz.dpkg-new' (while processing `./usr/share/man/ja/man8/usermod.8.gz'): No space left on device UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1690382/+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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Changed in: mir (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection
Having said that, it just happened again. An hour after my previous post. -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 pr500k-9912ec-1 36301ded-0ac5-4a86-9621-87290ef159af /org/freedesktop/NetworkManager/ActiveConnection/5 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.la
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Changed in: mir (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: Fix Committed Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1152137] Re: Pulseaudio won't start when home directory not owned by user
This problem is still present on more recent versions of Ubuntu. We currently locally patch it to allow home directories to be owned by either the relevant user, or root. It would be great if this was patched upstream. -- 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/1152137 Title: Pulseaudio won't start when home directory not owned by user Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have an NFS mounted home directory on a dedicated fileserver which is shared with Windows PCs via SMB. The home directory is not owned by me. ACLs are set on it to allow me full control of the contents but prevent me from changing its permissions. This means any files or directories created in the home directory are owned by me even though the top level is not. Pulseaudio checks the home directory is owned by the user at startup and exits if it isn't. This stops it running on my system. I have recompiled pulseaudio without this check and it works fine. Please either remove or modify the following startup check: pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415: if (st.st_uid != getuid()) { pa_log_error("Home directory %s not ours.", h); errno = EACCES; goto finish; } A better check would be for pulseaudio to try and create the files/folders it needs and fail if it cannot. I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+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 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo
ahasenack, can you please test it? thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1688121 Title: KDC/kadmind explicit wildcard listener addresses do not use pktinfo Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Zesty: Fix Committed Bug description: This is fixed in artful in krb5 1.15-2 - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530 - debian: conflated into https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767 - debian patch in artful's krb5: 0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch [Impact] When the KDC receives a kinit request via UDP on an aliased interface, the response is sent with the wrong source IP and never received by kinit. After a short timeout, kinit tries again with TCP, in which case it works. But if using PREAUTH (the default), that means this first request will correctly fail, with the server demanding PREAUTH, and the client will try again with a changed request. The whole dance starts again: first UDP, ignored, then TCP, and finally we have a ticket. Most clients will just see an increased lag when obtaining tickets. If for some reason 88/TCP is blocked on the KDC and clients are expected to use UDP at all times, then kinit requests will just fail. A workaround is to list the aliased interface's address in kdc_listen besides the wildcard (0.0.0.0) address. The provided patch is applied upstream and in Debian testing. [Test Case] On zesty: a) install krb5-kdc and krb5-admin-server $ sudo apt install krb5-kdc krb5-admin-server when prompted, use EXAMPLE.ORG (all caps) as the default realm when prompted, select your own IP for the KDC and the Admin servers b) configure a new realm called EXAMPLE.ORG $ sudo krb5_newrealm use any password of your liking when prompted c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and with mandatory PREAUTH: $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu d) extract the ubuntu principal keytab and time how long it takes to obtain a ticket: $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu real 0m0.022s $ klist Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: ubu...@example.org Valid starting Expires Service principal 05/03/2017 21:22:08 05/04/2017 07:22:08 krbtgt/example@example.org renew until 05/04/2017 21:22:08 e) add another IP to your network interface. For example, this adds 10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case): $ sudo ip addr add 10.0.5.155/24 dev ens3 f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc and admin server's IP to this new IP you just added in step (e): [realms] EXAMPLE.ORG = { kdc = 10.0.5.155 admin_server = 10.0.5.155 g) Time again how long it takes to obtain a ticket: $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu real 0m2.017s Step (g) shows the bug. On a more technical level, we can see that the server responds to kinit's UDP request using an incorrect source IP, therefore kinit never "sees" it. It quickly times out and switches to TCP, where the server responds using the correct source IP: 1 0.010.0.5.55 → 10.0.5.155 KRB5 216 AS-REQ 2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: KRB5KDC_ERR_PREAUTH_REQUIRED (2) has the incorrect source ip! After roughly 1s, kinit switches to tcp and tries again: 3 1.00323150710.0.5.55 → 10.0.5.155 TCP 76 55588 → 88 [SYN] Seq=0 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128 4 1.003269692 10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 TSecr=3523453804 WS=128 5 1.00330261410.0.5.55 → 10.0.5.155 TCP 68 55588 → 88 [ACK] Seq=1 Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273 6 1.00354520410.0.5.55 → 10.0.5.155 KRB5 244 AS-REQ 7 1.003567693 10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804 8 1.003799664 10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: KRB5KDC_ERR_PREAUTH_REQUIRED (continues) (8) and the whole tcp handshake happens with the correct IP addresses and the exchange happens and we get the ticket, but not before kinit repeats the request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :) h) repeat step (g) with the updated packages. Timing should be similar to the one in step (d), and a traffic capture should show UDP (and not TCP) being used. Alternativaly, you
Re: [Touch-packages] [Bug 1689585] Re: ntp doesn't unload its apparmor profile on purge
On 2017-05-12 01:48 AM, ChristianEhrhardt wrote: > shouldn't dh_apparmor unload it just as it loads it? Exactly, I would have assumed that it was dh_apparmor's job. Curious to hear from the Apparmor folks. Thanks for looking into this. Simon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1689585 Title: ntp doesn't unload its apparmor profile on purge Status in apparmor package in Ubuntu: New Status in ntp package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) install ntp apt install ntp 2) confirm it has loaded its AA profile aa-status | grep ntpd 3) purge ntp apt purge ntp 4) the profile is left behind but shouldn't aa-status | grep ntpd Additional info: This was found by first install ntp then changing my mind and deciding to go with OpenNTPD. FYI, just installing openntpd while ntp is still there works because openntpd has a kludge to unload ntpd's profile but that only works if the ntp package wasn't purged before. /var/lib/dpkg/info/openntpd.preinst: if [ -f /etc/apparmor.d/usr.sbin.ntpd ] && pathfind apparmor_parser ; then apparmor_parser -R /etc/apparmor.d/usr.sbin.ntpd fi Since a purge deletes /etc/apparmor.d/usr.sbin.ntpd, openntpd.preinst's kludge is ineffective. In any case, having implementation B include workaround for implementation A not cleaning up after itself seems wrong and the issue should be fixed at the source IMHO. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 # apt-cache policy ntp ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.4 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.4 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.4 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.8p4+dfsg-3ubuntu5.3 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1:4.2.8p4+dfsg-3ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 9 15:48:42 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1689585/+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 1066488] Re: No sound on Dell XPS after suspend (ALC275)
Hi, Daniel, Appears to be fixed entirely now. I was running Ubuntu 12.04 when I first encountered the bug, and if memory serves it was fixed at least a year or two ago. I'm currently running 16.04. Thanks for responding. -- 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/1066488 Title: No sound on Dell XPS after suspend (ALC275) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Dell XPS One 2710, Ubuntu 12.04, Kernel 3.2.0.31 or 3.2.0.32 or 3.6.2 Sound works out of the box, until machine is supended to RAM. After suspend and resume, no sound at all. A suspend to Disk and resume restores sound! aplay -l: Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC275 Analog [ALC275 Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 lsmod|grep snd: snd_hda_codec_hdmi 32506 1 snd_hda_codec_realtek79668 1 snd_hda_intel 34147 3 snd_hda_codec 135374 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 13668 1 snd_hda_codec snd_pcm97661 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_timer 29989 1 snd_pcm snd79391 13 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 15091 1 snd snd_page_alloc 18572 2 snd_hda_intel,snd_pcm It is NOT possible to unload snd modules. sudo /sbin/alsa force-unload: Unloading ALSA sound driver modules: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device snd-page-alloc (failed: modules still loaded: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-timer snd-page-alloc). All information in the net either is depreciated (using acpi_suspend) or refers to chips that have options (e.g. modprobe snd_hda_intel option=acer). There is NO documentation about options of the ALC275 chip. Anybody has a solution to this? Thanks Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1066488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1689410] Re: nplan with networkd + resolvconf without resolved, results in no DNS resolution
On 9 May 2017 at 19:05, Ryan Harper <1689...@bugs.launchpad.net> wrote: > On Tue, May 9, 2017 at 11:23 AM, Steve Langasek < > steve.langa...@canonical.com> wrote: > > I'm hesitant to say apt-get install nplan implies that you want cloud-init > to > use netplan to rendering things as well. > > So what remains is some unit changes (ensure that network-online.target > depends on systemd-networkd-wait-online.service) > and cloud-config change (cloud-init's network renderer should be netplan > over eni). > > How would those changes get introduced when a user wants to try netplan on > xenial? > My understanding was that cloud-init does not re-initialise the network for initialized instances, and thus an upgrade to cloud-init and/or installation of nplan will not switch one's existing instance to use nplan. The understanding I had was the idea is to have newly provisioned xenial instances to be nplan managed. -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1689410 Title: nplan with networkd + resolvconf without resolved, results in no DNS resolution Status in ifupdown package in Ubuntu: Invalid Status in nplan package in Ubuntu: Invalid Status in resolvconf package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: if nplan yaml specifies nameservers which are passed onto networkd, they will never take effect on systems that do not use systemd- resolved. This is because there is no integration between nplan and resolvconf, either directly; via networkd; via NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1689410/+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 1628287] Re: systemd-resolved crashed with SIGABRT in log_assert_failed()
+1 -- 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/1628287 Title: systemd-resolved crashed with SIGABRT in log_assert_failed() Status in systemd package in Ubuntu: Confirmed Bug description: I don't know ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-6git1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Mon Sep 26 17:02:18 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2015-04-29 (517 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: GOOGLE Samus ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: log_assert_failed () from /lib/systemd/libsystemd-shared-231.so ?? () ?? () ?? () ?? () Title: systemd-resolved crashed with SIGABRT in log_assert_failed() UpgradeStatus: Upgraded to yakkety on 2016-09-26 (0 days ago) UserGroups: dmi.bios.date: 02/25/2015 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd02/25/2015:svnGOOGLE:pnSamus:pvrMP.A:cvnGOOGLE:ct3:cvr: dmi.product.name: Samus dmi.product.version: MP.A dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1628287/+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 1690364] Re: text missing in applications
** Attachment added: "Nautilus example" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1690364/+attachment/4875610/+files/Bildschirmfoto%20vom%202017-05-12%2013-43-57.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1690364 Title: text missing in applications Status in xorg package in Ubuntu: New Bug description: Sometimes when I signup after sleep mode, there's much text missing in several applications. See screenshots: - E.g. Nautilus: directory names and filenames missing, but file symbols are displayed correctly. Also the texts in the left side bar, in the headline, and in the tab header are missing. - When I hover over my email inbox in thunderbird, the email subjects, addresses, timestamps etc. disappear. This problem is occurring maybe in 30% of all cases after sleep mode. I'm using Ubuntu 16.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: /dev/sda6: clean, 856683/22781952 files, 58594296/9424 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 12 13:49:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05be] Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-09-22 (231 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E6540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=6209d39b-1926-4016-8dcf-38037307eed4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0CYT5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd12/22/2016:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 12 13:44:50 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5562 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1690364/+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 1690364] [NEW] text missing in applications
Public bug reported: Sometimes when I signup after sleep mode, there's much text missing in several applications. See screenshots: - E.g. Nautilus: directory names and filenames missing, but file symbols are displayed correctly. Also the texts in the left side bar, in the headline, and in the tab header are missing. - When I hover over my email inbox in thunderbird, the email subjects, addresses, timestamps etc. disappear. This problem is occurring maybe in 30% of all cases after sleep mode. I'm using Ubuntu 16.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: /dev/sda6: clean, 856683/22781952 files, 58594296/9424 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 12 13:49:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05be] Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-09-22 (231 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E6540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=6209d39b-1926-4016-8dcf-38037307eed4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0CYT5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd12/22/2016:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 12 13:44:50 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5562 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial ** Attachment added: "Thunderbird example" https://bugs.launchpad.net/bugs/1690364/+attachment/4875591/+files/Bildschirmfoto%20vom%202017-05-12%2013-43-34.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1690364 Title: text missing in applications Status in xorg package in Ubuntu: New Bug description: Sometimes when I signup after sleep mode, there's much text missing in several applications. See screenshots: - E.g. Nautilus: directory names and filenames missing, but file symbols are displayed correctly. Also the texts in the left side bar, in the headline, and in the tab header are missing. - When I hover over my email inbox in thunderbird, the email subjects, addresses, timestamps etc. disappear. This problem is occurring maybe in 30% of all cases after sleep mode. I'm using Ubuntu 16.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: /dev/sda6: clean, 856683/22781952 files, 58594296/9424 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plu
[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
Must say, since my post of April 24th, the problem has not reoccurred. Settings still as mentioned above. So with these settings it was a one- off incident. -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 pr500k-9912ec-1 36301ded-0ac5-4a86-9621-87290ef159af /org/freedesktop/NetworkManager/ActiveConnection/5 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabl
[Touch-packages] [Bug 1685022] Re: package openssh-server 1:7.2p2-4ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
This bug was fixed in the package openssh - 1:7.5p1-3 --- openssh (1:7.5p1-3) experimental; urgency=medium * Fix debian/adjust-openssl-dependencies to account for preferring libssl1.0-dev. * Adjust OpenSSL dependencies for openssh-client-ssh1 too. * Fix purge failure when /etc/ssh has already somehow been removed (LP: #1682817). * Ensure that /etc/ssh exists before trying to create /etc/ssh/sshd_config (LP: #1685022). -- Colin Watson Tue, 02 May 2017 13:51:27 +0100 ** Changed in: openssh (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1685022 Title: package openssh-server 1:7.2p2-4ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in openssh package in Ubuntu: Fix Released Bug description: I messed up the ssh_config file and I need the stock config files for ssh server. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: openssh-server: Install openssh-server: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Apr 20 14:13:40 2017 DuplicateSignature: package:openssh-server:1:7.2p2-4ubuntu2.1 Setting up openssh-server (1:7.2p2-4ubuntu2.1) ... /var/lib/dpkg/info/openssh-server.postinst: 164: /var/lib/dpkg/info/openssh-server.postinst: cannot create /etc/ssh/sshd_config: Directory nonexistent dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2017-04-03 (17 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1685022/+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 1687129] Re: Needs to allow updates from the ESM archive
This bug was fixed in the package unattended-upgrades - 0.93.1ubuntu4 --- unattended-upgrades (0.93.1ubuntu4) artful; urgency=medium * Add UbuntuESM to the list of sources automatically upgraded from by default. LP: #1687129. -- Steve Langasek Thu, 11 May 2017 18:08:55 -0700 ** Changed in: unattended-upgrades (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1687129 Title: Needs to allow updates from the ESM archive Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Precise: Fix Released Status in unattended-upgrades source package in Trusty: Fix Committed Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Yakkety: Fix Committed Status in unattended-upgrades source package in Zesty: Fix Committed Bug description: [SRU Justification] When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match. [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43 Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both. [Test case] 1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades ca-certificates' 2. run 'sudo ubuntu-advantage enable-esm ' with your private creds to enable the ESM archive 3. run 'sudo apt-get update' 4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 5. run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease' 6. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed. 7. install unattended-upgrades from -proposed. 8. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 9. again run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease' 10. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package. [Regression potential] Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1687129/+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 1682817] Re: package openssh-client 1:6.6p1-2ubuntu2.8 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
This bug was fixed in the package openssh - 1:7.5p1-3 --- openssh (1:7.5p1-3) experimental; urgency=medium * Fix debian/adjust-openssl-dependencies to account for preferring libssl1.0-dev. * Adjust OpenSSL dependencies for openssh-client-ssh1 too. * Fix purge failure when /etc/ssh has already somehow been removed (LP: #1682817). * Ensure that /etc/ssh exists before trying to create /etc/ssh/sshd_config (LP: #1685022). -- Colin Watson Tue, 02 May 2017 13:51:27 +0100 ** Changed in: openssh (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1682817 Title: package openssh-client 1:6.6p1-2ubuntu2.8 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in openssh package in Ubuntu: Fix Released Bug description: /etc/init.d/ssh restart stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.203" (uid=1000 pid=9912 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init") start: Rejected send message, 1 matched rules; type="method_call", sender=":1.204" (uid=1000 pid=9903 comm="start ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init") ProblemType: Package DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2.8 ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Fri Apr 14 18:08:27 2017 DuplicateSignature: package:openssh-client:1:6.6p1-2ubuntu2.8:subprocess installed post-removal script returned error exit status 1 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2016-01-30 (440 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh Title: package openssh-client 1:6.6p1-2ubuntu2.8 failed to install/upgrade: subprocess installed post-removal script 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/openssh/+bug/1682817/+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 1484027] Re: systemd-tmpfiles-clean warns about duplicate /var/log line
Addl comment which could be considered by a future fix... The point and the issue of the problem in fact should address is the following - given the tmpfiles.d behaviour as follows in man -S5 tmpfiles.d: ... Files in /etc/tmpfiles.d override files with the same name in /usr/lib/tmpfiles. and /run/tmpfiles.d. Files in /run/tmpfiles.d override files with the same name in /usr/lib/tmpfiles.d. Packages should install their configuration files in /usr/lib/tmpfiles.d. Files in /etc/tmpfiles.d are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same path, the entry in the file with the lexicographically earliest name will be applied. All other conflicting entries will be logged as errors. ... Considering this, the /usr/lib/tmpfiles.d/00rsyslog.conf file in line 6 (delivered by rsyslog 8.16.0-1ubuntu3 package) to my perception is derived as effective line for /var/log, the /usr/lib/tmpfiles.d/var.conf file line 14 delivered by systemd in the 229-4ubuntu10 package will cause the logging. Since that is an out-of-the-box setting, there should be a discussion of the topic with decision to be taken among systemd and rsyslogd that ONE of the two parties is delivering a tmpfiles config only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1484027 Title: systemd-tmpfiles-clean warns about duplicate /var/log line Status in rsyslog package in Ubuntu: Fix Released Bug description: Triggered by the two /var/log entries that were reported in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1434295, I get daily log messages from systemd-tmpfiles-clean saying: Aug 10 15:04:13 seraph systemd[1]: Starting Cleanup of Temporary Directories... Aug 10 15:04:13 seraph systemd-tmpfiles[5897]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Aug 10 15:04:13 seraph systemd[1]: Started Cleanup of Temporary Directories. I don't know much about systemd, so I have no ideas for how to fix it, sorry. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1484027/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Seumas: It seems that Canonical simply don't care about VPN users. This is opened for more than two months and still not reasonable response :( ... ... right now there is only one workaround: - downgrade network manager: apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 - set it on hold (to prevent updates): apt-mark hold network-manager If necessary then reboot machine. I hope that someone will pick this before they remove 1.2.2. version from repository ... -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Confirmed Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1690355] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri May 12 14:01:31 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1690355 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: ... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri May 12 14:01:31 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1690355/+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 1531622] Re: default config still using a legacy keyword: KLogPermitNonKernelFacility
Ditto What Ivar et. al. said. 16.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1531622 Title: default config still using a legacy keyword: KLogPermitNonKernelFacility Status in rsyslog package in Ubuntu: Fix Released Bug description: /etc/rsyslog.conf contains: $KLogPermitNonKernelFacility on But this no longer supported and trigger this log message: Jan 5 08:56:16 simon-laptop rsyslogd-: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.14.0 try http://www.rsyslog.com/e/ ] Error is described as "legacy parameter no longer permitted". This legacy parameter causes config syntax checks (rsyslogd -N1) to fail. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsyslog 8.14.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 6 15:47:15 2016 SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+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 1690354] [NEW] If default zoom in nautilus set to ≠ 100% icons have different sizes
Public bug reported: Hello, https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1687411 Are there any missing icons in the package ? ( for xml and deb files ) Here is what happens if zoom in nautilus is set to ≠ 100% on my Ubuntu 16.04.2 https://launchpadlibrarian.net/317825735/Capture%20du%202017-05-01.png ** Affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1690354 Title: If default zoom in nautilus set to ≠ 100% icons have different sizes Status in humanity-icon-theme package in Ubuntu: New Bug description: Hello, https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1687411 Are there any missing icons in the package ? ( for xml and deb files ) Here is what happens if zoom in nautilus is set to ≠ 100% on my Ubuntu 16.04.2 https://launchpadlibrarian.net/317825735/Capture%20du%202017-05-01.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1690354/+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 1690353] [NEW] package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Setting up openssh-server (1:7.3p1-1ubuntu0.1) ... Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2017-05-12 12:05:21 BST; 7ms ago Process: 21819 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 21819 (code=exited, status=255) May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Starting OpenBSD Secure Shell May 12 12:05:21 chris-XPS-13-9343 sshd[21819]: /etc/ssh/sshd_config line 92:...n May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Main process exit...a May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Failed to start OpenBSD Secure May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Unit entered fail May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Failed with resul Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: openssh-server 1:7.3p1-1ubuntu0.1 Uname: Linux 4.7.6-040706-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Fri May 12 11:25:50 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-07-16 (665 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 92: bad port number in PermitOpen SourcePackage: openssh Title: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-01-24 (107 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1690353 Title: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: Setting up openssh-server (1:7.3p1-1ubuntu0.1) ... Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2017-05-12 12:05:21 BST; 7ms ago Process: 21819 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 21819 (code=exited, status=255) May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Starting OpenBSD Secure Shell May 12 12:05:21 chris-XPS-13-9343 sshd[21819]: /etc/ssh/sshd_config line 92:...n May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Main process exit...a May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Failed to start OpenBSD Secure May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Unit entered fail May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Failed with resul Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: openssh-server 1:7.3p1-1ubuntu0.1 Uname: Linux 4.7.6-040706-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Fri May 12 11:25:50 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-07-16 (665 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 92: bad port number in PermitOpen SourcePackage: openssh Title: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-01-24 (107 days ago
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Seumas: since Canonical seem to be dragging their feet on this, you might as well downgrade to network-manager 1.2.2, which is a version that works. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Confirmed Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1246929] Re: no audio in KVM virtual machines : cannot select alsa or pa
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete ** Changed in: libvirt (Ubuntu) Status: Confirmed => Incomplete ** Changed in: virt-manager (Ubuntu) Status: Confirmed => 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/1246929 Title: no audio in KVM virtual machines : cannot select alsa or pa Status in libvirt package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in virt-manager package in Ubuntu: Incomplete Bug description: I am on Ubuntu 13.10 desktop 16GB ram asus sabertooth 990fx r2.0 motherboard amd 8346 cpu nvidia gtx650 video card Since upgrading to Ubuntu 13.10 audio no longer works in KVM. Checking SYSLOG I found this error being logged: Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read! Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. brian ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 19:45:53 2013 InstallationDate: Installed on 2013-10-31 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131003) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/09/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1246929/+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 1246587] Re: no audio on Samsung Chromebook unless I edit /etc/pulse/default.pa
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** 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/1246587 Title: no audio on Samsung Chromebook unless I edit /etc/pulse/default.pa Status in pulseaudio package in Ubuntu: Incomplete Bug description: On a Samsung Chromebook 5 running Ubuntu/saucy, the audio does not work at all. I found two things on the Debian wiki that made it work for me: https://wiki.debian.org/InstallingDebianOn/Samsung/ARMChromebook (In Ubuntu, I've mounted the ChromeOS system on /media/root-a.) 1. copy some alsa support files from Chrome: cp /media/root-a/usr/share/alsa/ucm/DAISY-I2S/HiFi.conf /usr/share/alsa/ucm/DAISY-I2S/ 2. edit /etc/pulse/default.pa to add this line: load-module module-alsa-sink device=sysdefault Then I rebooted and I had working audio! It would be great if this could be included by default! This laptop runs XUbuntu quite nicely, and costs US$250! /media/root-a/usr/share/alsa/ucm/DAISY-I2S/HiFi.conf is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1246587/+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 1246478] Re: No playback sound / Cannot un-mute speaker playback
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => 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/1246478 Title: No playback sound / Cannot un-mute speaker playback Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since 12.04 upgrade and continuing with 13.10, gnome-alsamixer, alsamixer, and xfce4-mixer cannot un-mute playback speakers although the apps suggest they have been unmuted. I have an HDA Intel sound card (ALC883). Alsamixergui is the only one that works by clicking the speaker icons at the top to make them green. When I unmute using the other apps, in Alsamixergui the speakers stay white signifying that the playback is not actually unmuted and the sound does not work. This is fairly critical and was reported for 12.04: no sound, no music, not Skype, etc. I hope this is going to be fixed. Not sure if it is actually the apps' fault or pulseaudio's. Please forward as appropriate. This is just another thing that tell people loudly to STAY AWAY FROM UBUNTU! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pch1613 F pulseaudio Date: Wed Oct 30 16:36:56 2013 InstallationDate: Installed on 2011-11-15 (714 days ago) InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-10-19 (11 days ago) dmi.bios.date: 05/03/2007 dmi.bios.vendor: 945GCT-M3 dmi.bios.version: V1.04 dmi.board.name: 945GCT-M3 dmi.board.vendor: ELITEGROUP dmi.board.version: 3.0 dmi.chassis.type: 3 dmi.chassis.vendor: 945G dmi.chassis.version: 945G-M3 dmi.modalias: dmi:bvn945GCT-M3:bvrV1.04:bd05/03/2007:svnGateway:pn945G-M3:pvr3.1:rvnELITEGROUP:rn945GCT-M3:rvr3.0:cvn945G:ct3:cvr945G-M3: dmi.product.name: 945G-M3 dmi.product.version: 3.1 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1246478/+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 1249624] Re: Audio stuttering
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** 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/1249624 Title: Audio stuttering Status in pulseaudio package in Ubuntu: Incomplete Bug description: This issue began after doing updates through the software center. The audio output stutters and skips similarly to how a skipping record sounds. I believe the issue is in ALSA but I can't tell for sure. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nik 12616 F pulseaudio /dev/snd/controlC0: nik 12616 F pulseaudio Date: Sat Nov 9 10:58:18 2013 InstallationDate: Installed on 2013-02-17 (264 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_SpeakerTestPulseStderr: W r i t e e r r o r : - 3 2 , B r o k e n p i p e Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Satellite A665D, Realtek ALC269VB, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to saucy on 2013-10-18 (22 days ago) dmi.bios.date: 08/02/2011 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.50 dmi.board.asset.tag: NULL dmi.board.name: NWQAE dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr1.50:bd08/02/2011:svnTOSHIBA:pnSatelliteA665D:pvrPSAX0U-02Y01P:rvnTOSHIBA:rnNWQAE:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A665D dmi.product.version: PSAX0U-02Y01P dmi.sys.vendor: TOSHIBA modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2013-11-08T22:54:34.114466 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1249624/+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 1247280] Re: [43192RU, Conexant CX20585, Mic, Internal] Crackling sound
Thank you for reporting this bug to Ubuntu. Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** 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/1247280 Title: [43192RU, Conexant CX20585, Mic, Internal] Crackling sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Recording through internal microphone produces crackling noise on playback. This happens regardless of settings for input device using alsamixer. When using the ubuntu-bug wizard I said the first test passed because the audio was remarkably better than the 2nd but there was still minor crackling, so I am not sure how to do some ALSA only tests to verify the culprit really is PulseAudio, please advise. Update: I just discovered arecord and did a test. The crackling is still present with arecord. Update2: I used set options snd-hda-intel position_fix=2 a second time and it appears audio is recording correctly now (and saved correctly). I had it set to 1 for a long time it appears, not sure if I hadn't added that if it would do the same behaviour of set options snd-hda- intel position_fix=2. Tried so far: https://wiki.ubuntu.com/Audio/PositionReporting set options snd-hda-intel position_fix=1 load-module module-udev-detect tsched=0 Related issues: http://askubuntu.com/questions/315282/crackling-sound-from-microphone-recently-in-13-04 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:3.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elijah 2775 F pulseaudio /dev/snd/controlC0: elijah 2775 F pulseaudio elijah11562 F alsamixer Date: Fri Nov 1 17:29:49 2013 InstallationDate: Installed on 2013-06-04 (150 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:MID failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [43192RU, Conexant CX20585, Mic, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET74WW (1.34 ) dmi.board.name: 43192RU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn43192RU:pvrThinkPadW510:rvnLENOVO:rn43192RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 43192RU dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1247280/+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 1246526] Re: Volume of subwoofer on pulseaudio volume control is not working after 13.10 installation..
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Changed in: pavucontrol (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/1246526 Title: Volume of subwoofer on pulseaudio volume control is not working after 13.10 installation.. Status in pavucontrol package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Volume of subwoofer on pulseaudio volume control is not working after I upgrade to 13.10. Subwoofer makes sound and change the loundness with sliding front/left volume slider. Subwoofer slider change nothing. There is no independent control. There are more problems regarding subwoofer controls and You guys never fix this kind of problem but I report here anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1246526/+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 1249216] Re: bluetooth HSP mode broken in pulseaudio
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 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. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => 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/1249216 Title: bluetooth HSP mode broken in pulseaudio Status in pulseaudio package in Ubuntu: Incomplete Bug description: All involved hardware worked in Ubuntu 11.10. HSP-only headsets (like Motorola H300, H700) do not output sound, often cause pulseaudio to hang, and eventually kick out this log message: #v+ E: [pulseaudio] bluetooth-util.c: Failed to acquire transport fd: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. E: [pulseaudio] module.c: Failed to load module "module-bluetooth-device" (argument: "address="00:16:8F:D1:95:36" path="/org/bluez/31385/hci0/dev_00_16_8F_D1_95_36""): initialization failed. #v- After that, the audio sink shows up in pavucontrol, but when selected I cannot play sound through it. Many apps like mplayer will hang, presumably because pulseaudio's input buffer is full. See also https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/972063 $ lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 $ apt-cache policy pulseaudio pulseaudio: Installed: 1:1.1-0ubuntu15.4 Candidate: 1:1.1-0ubuntu15.4 Version table: *** 1:1.1-0ubuntu15.4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:1.1-0ubuntu15 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages $ apt-cache policy bluez bluez: Installed: 4.98-2ubuntu7 Candidate: 4.98-2ubuntu7 Version table: *** 4.98-2ubuntu7 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15.4 ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51 Uname: Linux 3.2.0-55-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bts1045 F pulseaudio /dev/snd/controlC1: bts1045 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,1458a042,0011' Controls : 45 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'CinemaTM'/'Microsoft Microsoft® LifeCam Cinema(TM) at usb-:00:12.2-5, high speed' Mixer name : 'USB Mixer' Components : 'USB045e:075d' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 56 Mono: Capture 53 [95%] [33.00dB] [on] Date: Fri Nov 8 00:34:24 2013 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to precise on 2013-10-13 (26 days ago) dmi.bios.date: 12/25/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-770TA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/25/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-770TA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770TA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-770TA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1249216/+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 1248833] Re: Unable to switch to headset after upgraded to ubuntu 13.10
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete ** Bug watch removed: Linux Kernel Bug Tracker #55541 http://bugzilla.kernel.org/55541 -- 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/1248833 Title: Unable to switch to headset after upgraded to ubuntu 13.10 Status in pulseaudio package in Ubuntu: Incomplete Bug description: There used to be an option in sound control panel that I can switch "play sound through" to headset when using 11.04-13.04, however it's gone in ubuntu 13.10. Currently there are only two options: "Digital output(S/PDIF)" and "Speakers". Tried alsamixer and some other suggestions from askUbuntu.com but with no luck. OS: Ubuntu 13.10 Laptop model: Alienware M14x R2 Related outputs: $ lspci (Removed irrelevant device entries) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev ff) $ amixer -c 0 Simple mixer control 'Master',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 99 Mono: Front Left: Playback 0 [0%] [-90.00dB] [off] Front Right: Playback 0 [0%] [-90.00dB] [off] Simple mixer control 'PCM',0 Capabilities: pvolume Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 0 [0%] [-51.00dB] Front Right: Playback 0 [0%] [-51.00dB] Simple mixer control 'Surround',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'Mic SVM',0 Capabilities: cswitch cswitch-joined Capture channels: Mono Mono: Capture [on] Simple mixer control 'Mic1-Boost (30dB)',0 Capabilities: cswitch cswitch-joined Capture channels: Mono Mono: Capture [off] Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined cswitch cswitch-joined Playback channels: Mono Capture channels: Mono Mono: Playback [off] Capture [on] Simple mixer control 'IEC958 Default PCM',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'IEC958',16 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 99 Front Left: Capture 98 [99%] [8.00dB] [on] Front Right: Capture 98 [99%] [8.00dB] [on] Simple mixer control 'AMic1/DMic',0 Capabilities: cswitch cswitch-joined Capture channels: Mono Mono: Capture [off] Simple mixer control 'AMic1/DMic Auto Detect',0 Capabilities: cswitch cswitch-joined Capture channels: Mono Mono: Capture [off] Simple mixer control 'Analog-Mic2',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 99 Front Left: Capture 90 [91%] [0.00dB] [on] Front Right: Capture 90 [91%] [0.00dB] [on] Simple mixer control 'CrystalVoice',0 Capabilities: cswitch cswitch-joined Capture channels: Mono Mono: Capture [off] Simple mixer control 'Crystalizer',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Dialog Plus',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Digital',0 Capabilities: cvolume Capture channels: Front Left - Front Right Limits: Capture 0 - 120 Front Left: Capture 60 [50%] [0.00dB] Front Right: Capture 60 [50%] [0.00dB] Simple mixer control 'Echo Cancellation',0 Capabilities: cswitch cswitch-joined Capture channels: Mono Mono: Capture [off] Simple mixer control 'Equalizer',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'HP/Speaker',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'HP/Speaker Auto Detect',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'Noise Reduction',0 Capabilities: cswitch cswitch-joined Capture chan
[Touch-packages] [Bug 1248405] Re: [DL-H61MXEL, Realtek ALC888, Green Line Out, Rear] Underruns, dropouts or crackling sound
Thank you for reporting this bug to Ubuntu. Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => 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/1248405 Title: [DL-H61MXEL, Realtek ALC888, Green Line Out, Rear] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: When the output volume is set near 100% and a sound is playing, volume level alternates too fast. Sometimes it goes to mute. I watched System Settings > Sound and found that sound output device is alternating between 'Analog Output -Built-in Audio' and 'Headphones - Built-in Audio'. The switching is too frequent and introduces glitches in output. By default output device is 'Analog Output - Built-in Audio'. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:3.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gokul 2613 F pulseaudio Date: Wed Nov 6 10:36:23 2013 InstallationDate: Installed on 2013-05-22 (167 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [DL-H61MXEL, Realtek ALC888, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A92DLP11 dmi.board.name: DL-H61MXEL dmi.board.vendor: DIGILITE dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA92DLP11:bd12/16/2011:svnDIGILITE:pnDL-H61MXEL:pvrTobefilledbyO.E.M.:rvnDIGILITE:rnDL-H61MXEL:rvr: dmi.product.name: DL-H61MXEL dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: DIGILITE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1248405/+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 1248622] Re: [Inspiron 5323, Cirrus Logic CS4213, Mic, Internal] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 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. ** 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/1248622 Title: [Inspiron 5323, Cirrus Logic CS4213, Mic, Internal] No sound at all Status in pulseaudio package in Ubuntu: Incomplete Bug description: I don't know ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15.4 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-32-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: Cirrus Analog [Cirrus Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cristian 1930 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd061 irq 44' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10134213,1028055b,00100100 HDA:80862806,80860101,0010' Controls : 21 Simple ctrls : 7 Date: Wed Nov 6 18:34:17 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ro_RO.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio intern - HDA Intel PCH Symptom_DevicesInUse: 1930 cristian F pulseaudio PID ACCESS COMMAND Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH failed Symptom_Type: No sound at all Title: [Inspiron 5323, Cirrus Logic CS4213, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J4MPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/16/2012:svnDellInc.:pnInspiron5323:pvr:rvnDellInc.:rn0J4MPR:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 5323 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1248622/+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 1249802] Re: Problem with audio in ubuntu - Failed to create secure directory (/run/user/1000/pulse): Brak dostępu
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** 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/1249802 Title: Problem with audio in ubuntu - Failed to create secure directory (/run/user/1000/pulse): Brak dostępu Status in pulseaudio package in Ubuntu: Incomplete Bug description: Failed to create secure directory (/run/user/1000/pulse): Brak dostępu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1249802/+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 1249705] Re: HDMI output not available in 13.10
** Tags added: trusty ** Summary changed: - HDMI output not available in 13.10 + HDMI output not available in 13.10 or 14.04 -- 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/1249705 Title: HDMI output not available in 13.10 or 14.04 Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hello, My issue here is with the HDMI output, it is non existent. I have had no issues with earlier versions of Ubuntu from 10.x, 12.04 LTS and 13.04. Even the original distro which was originally on this HTPC, Susse. I have researched all avenues for a remedy to my issue including #ALSA, #Pulseaudio and #Ubuntu IRCs. Some have mention it is possibly a kernel issue. I do have audio via S/PDIF which is stereo only. I did not upgrade the existing version; which most would, I have done a clean install of Ubuntu 13.10. Everything is working fine except for my audio issues. HDMI output is not showing in either ALSA or Pavucontrol. On the previous versions of Ubuntu I had many options of Digital 5.1 surround ouputs including HDMI. All that is available now for surround sound is analog options. In the Sound configuration panel I only have Digital Output (S/PDIF)Built-in Audio and Analog Output Built-in Audio which are only Stereo, HDMI is now missing in 13.10 I have tried so many apparent fixes in various forums which included editing confg files, uninstalling and reinstalling Alsa-base and Pulseaudio. I am surprised that I have any sound out of the S/PDIF Coax or Optical now. Thank you for taking the time to look this over. I am not 100% sure this is a bug , but by all the research, suggestions on the IRCs and not having this issue on previous versions, I am leaning towards it being a bug. If you need any further information please let me know and I will respond asap. Here is a link to my system info that was uploaded via alsa-info.sh: HTTP://pastebin.com/Mwhwvwxw This is the original alsa upload link: HTTP://www.alsa-project.org/db/?f=ecbcde4ed5874b18b8c18ea54d85ce7033287134 Here is my system information: Description: Ubuntu 13.10 Release: 13.10 Kernel-release version 3.11.0-13-generic uname -a string Linux HTPC 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux HTPC System Info: Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ × 2 Memory: 4GiB Graphics: GeForce 7050 PV / nForce 630a/integrated/SSE2 OS Type: Ubuntu 13.10 64-bit Disk: 320 GB DVB: AVerTVHD MCE A180 Remote: ATI USB RF wireless remote ( Remote Wonder) Keyboard/Mouse: Wireless System formerly a Captiveworks 3000/4000 ATSC and DVB-S Satellite HTPC, Distro used, Susse --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gee2171 F cairo-dock DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-30 (13 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True NonfreeKernelModules: nvidia Package: pulseaudio 1:4.0-0ubuntu6 [modified: usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf] PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Tags: saucy saucy Uname: Linux 3.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CaptiveWorks CW-3000HD V2.37 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7349 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCaptiveWorksCW-3000HDV2.37:bd03/19/2008:svnMSI:pnMS-7349:pvr1.0:rvnMSI:rnMS-7349:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7349 dmi.product.version: 1.0 dmi.sys.vendor: MSI --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gee1257 F pulseaudio /dev/snd/controlC2: gee1257 F pulseaudio /dev/snd/controlC1: gee1257 F pulseaudio CurrentDmesg: [ 19.643569] init: plymouth-
[Touch-packages] [Bug 1251876] Re: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Underruns, dropouts or crackling sound
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 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. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => 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/1251876 Title: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: no further info ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 1552 F pulseaudio /dev/snd/pcmC0D0p: adam 1552 F...m pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xd83a irq 22' Mixer name : 'Silicon Image SiI1392 HDMI' Components : 'HDA:10ec0269,102802c6,0014 HDA:10951392,,0010' Controls : 27 Simple ctrls : 10 Date: Sat Nov 16 12:09:05 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0R990K dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.asset.tag: ** dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A03 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/27/2009:svnDellInc.:pnInspiron1010:pvrA03:rvnDellInc.:rn0R990K:rvrA03:cvnDellInc.:ct8:cvrA03: dmi.product.name: Inspiron 1010 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1251876/+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 1253488] Re: Sound still coming from speakers when headphones pluged in
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** 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/1253488 Title: Sound still coming from speakers when headphones pluged in Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I plug headphones in my laptop, sound still coming from speakers (I hear this sound in headphones too). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robotex2079 F pulseaudio /dev/snd/pcmC0D0c: robotex2079 F...m pulseaudio /dev/snd/pcmC0D0p: robotex2079 F...m pulseaudio Date: Thu Nov 21 02:52:56 2013 InstallationDate: Installed on 2013-11-18 (2 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 47CN32WW(V2.10) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr47CN32WW(V2.10):bd01/04/2012:svnLENOVO:pn20091:pvrLenovoIdeaPadY570:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: 20091 dmi.product.version: Lenovo IdeaPad Y570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1253488/+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 1253739] Re: [Inspiron 1525, Silicon Image SiI1392 HDMI, Digital Out, HDMI] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** 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/1253739 Title: [Inspiron 1525, Silicon Image SiI1392 HDMI, Digital Out, HDMI] No sound at all Status in pulseaudio package in Ubuntu: Incomplete Bug description: Initially, I had to reset the sound card manually from 'HDMI' to 'analogue' to get sound working, but then the hotkeys no longer managed to control volume. Now, having run the bug report, things work again! I do not understand why. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryn 1428 F pulseaudio Date: Thu Nov 21 18:16:01 2013 InstallationDate: Installed on 2012-10-30 (387 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryn 1428 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 1525, Silicon Image SiI1392 HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to saucy on 2013-11-16 (5 days ago) dmi.bios.date: 03/10/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/10/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1253739/+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 1256128] Re: [Acer Aspire G7711, Realtek ALC888] Underruns, dropouts or crackling sound
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => 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/1256128 Title: [Acer Aspire G7711, Realtek ALC888] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sound on the right channel is cracky. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bartek 2190 F pulseaudio /dev/snd/pcmC0D0p: bartek 2190 F...m pulseaudio /dev/snd/timer: bartek 2190 f pulseaudio Date: Thu Nov 28 23:37:05 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-28 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HDA-Intel - HDA Intel, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A2 dmi.board.name: Aspire G7711 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A2:bd03/31/2010:svnAcer:pnAspireG7711:pvr:rvnAcer:rnAspireG7711:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire G7711 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1256128/+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