[Touch-packages] [Bug 1654371] Re: package python-setuptools 20.7.0-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
> Might be important : used > >sudo update-alternatives --install /usr/bin/python python > /usr/bin/python3 20 > > to force system to use python 3.5 by default. what do you expect when you shoot yourself in the foot? ** Changed in: python-setuptools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1654371 Title: package python-setuptools 20.7.0-1 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in python-setuptools package in Ubuntu: Invalid Bug description: Running Ubuntu 16.04.1 MATE (32 bits) on a EeePC (1Gb RAM, HDD 750 Gb, fresh install) Was trying to install THONNY (IDE for beginners in python). (Because I didn't succeed via 'sudo apt-get install thonny', found some "pip" installation hints on the web). Installation succeeded a few days ago on Fujitsu-Siemens Amilo laptop (under Lubuntu 16.04 x64 desktop). I was trying to install PIP to get it done, but system aborted installation on error code. Might be important : used sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 20 to force system to use python 3.5 by default. Accept my apologies for my bad english. I hope you can understand what I wrote ;-) Best regards from Belgium. Claude ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-setuptools 20.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 Date: Thu Jan 5 20:23:34 2017 Dependencies: python-pkg-resources 20.7.0-1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2017-01-05 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: python-setuptools Title: package python-setuptools 20.7.0-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1654371/+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 1606418] Re: PointerConfinement.test_we_update_our_confined_region_on_a_resize
** Changed in: mir Importance: Medium => High ** Changed in: mir (Ubuntu) Status: In Progress => Triaged ** Changed in: mir (Ubuntu) Importance: Medium => High -- 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/1606418 Title: PointerConfinement.test_we_update_our_confined_region_on_a_resize Status in Mir: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: Randomly fails 1/100 times. https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1612/console Looking into it, most likely a race with surface resize... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1606418/+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 1612012] Re: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail
** Changed in: mir Importance: High => Medium -- 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/1612012 Title: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail Status in Mir: Confirmed Status in Mir 0.24 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Tests always fail together: ServerDisconnect, ServerStartup, UnresponsiveClient 17:27:52 9: [ FAILED ] 5 tests, listed below: 17:27:52 9: [ FAILED ] ServerDisconnect.is_detected_by_client 17:27:52 9: [ FAILED ] ServerDisconnect.doesnt_stop_client_calling_API_functions 17:27:52 9: [ FAILED ] ServerStartup.creates_endpoint_on_filesystem 17:27:52 9: [ FAILED ] ServerStartup.after_server_sigkilled_can_start_new_instance 17:27:52 9: [ FAILED ] UnresponsiveClient.does_not_hang_server [https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1772/consoleFull] This is happening regularly in CI. These failures occur together. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1612012/+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 1650634] Re: when installing systemd, it creates /run/nologin preventing all users from logging in.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650634 Title: when installing systemd, it creates /run/nologin preventing all users from logging in. Status in systemd: New Status in systemd package in Ubuntu: Confirmed Status in systemd package in Suse: Unknown Bug description: How to replicate: sudo apt-get install systemd wait for 5 minutes check to see if /run/nologin appears. If it does the bug is present. See https://ubuntuforums.org/showthread.php?t=2327330 I ran this command via ansible on all of my servers. Then I could no longer log into any of them. Pretty big bug in my opinion. Please fix. -Tim ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd 204-5ubuntu20.20 ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 Uname: Linux 3.13.0-105-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: KDE Date: Fri Dec 16 12:03:55 2016 InstallationDate: Installed on 2014-04-21 (970 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1650634/+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 550891] Re: internal speakers do not mute if in dockingstation
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to "New". Thanks again!
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
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/550891
Title:
internal speakers do not mute if in dockingstation
Status in alsa-driver package in Ubuntu:
Invalid
Bug description:
Hello,
I have got a problem with my "Thinkpad T400s" and the "ThinkPad Mini Dock
Series 3" docking station.
Everytime I attach the nookbook to the dock (there are speakers connected)
the internal speakers do not mute.
Currently I do just plugin the speakers to the headphone output. But this is
not what I want to do using a dock.
The operating system is Ubuntu Lucid Beta1 with all updates.
Information about the docking station
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-72871
Further information on the notebook can be found here:
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-72868
In other Bugs I found the hint to put the following into the
/etc/modprobe.d/alsa-base.conf:
options snd-hda-intel model=laptop
But for me this does not work.
Thank you for your help.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mschewe1431 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf262 irq 17'
Mixer name : 'Conexant ID 5069'
Components : 'HDA:14f15069,17aa2132,00100300'
Controls : 6
Simple ctrls : 4
DistroRelease: Ubuntu 10.04
InstallationMedia: Error: [Errno 13] Permission denied:
'/var/log/installer/media-info'
Package: alsa-driver (not installed)
ProcEnviron:
LANG=de_DE.utf8
SHELL=/usr/bin/zsh
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Tags: lucid
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mschewe1488 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf262 irq 17'
Mixer name : 'Conexant ID 5069'
Components : 'HDA:14f15069,17aa2132,00100300'
Controls : 6
Simple ctrls : 4
DistroRelease: Ubuntu 10.04
InstallationMedia: Error: [Errno 13] Permission denied:
'/var/log/installer/media-info'
Package: alsa-driver (not installed)
ProcEnviron:
LANG=de_DE.utf8
SHELL=/usr/bin/zsh
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Tags: lucid
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
---
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on Apr 21 2010 for kernel 2.6.32-21-generic (SMP).
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mschewe1673 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf262 irq 31'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,17aa2132,00100300'
Controls : 12
Simple ctrls : 10
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100317.1)
Package: alsa-driver (not installed)
ProcEnviron:
LANG=de_DE.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-2
[Touch-packages] [Bug 1654490] [NEW] gdm3 won't work on 17.04
Public bug reported: I am not able to log into the display manager using gdm3 and UbuntuGNOME 17.04. I had to install lightdm reconfigure it with dpkg-reconfigure gdm3 and do it again after getting the message that I need to --configure it, which resolved in an error. than I had to sudo service lightdm start and was able to login. weston also won't let me log in. I am using an Nvidia 1050TI which I changed when running this system. Before using the 1050TI I was using a GT210. The Error appeared after changing the cards I think. I am using the 375.26 driver from http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.26 Thu Dec 8 18:36:43 PST 2016 GCC version: gcc version 6.3.0 20161229 (Ubuntu 6.3.0-2ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jan 6 06:40:13 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.9.0-11-generic, x86_64: installed nvidia-375, 375.26, 4.9.0-11-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] [1458:3729] InstallationDate: Installed on 2016-10-15 (82 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic root=UUID=f22a5adb-6406-46d2-98b5-7a3db6e8d489 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1307 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-V LE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1307:bd03/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-VLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.04.20161114.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.74-1 version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Fri Jan 6 06:36:36 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu9 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug has-workaround ubuntu zesty -- 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/1654490 Title: gdm3 won't work on 17.04 Status in xorg package in Ubuntu: New Bug description: I am not able to log into the display manager using gdm3 and UbuntuGNOME 17.04. I had to install lightdm reconfigure it with dpkg- reconfigure gdm3 and do it again after getting the message that I need to --configure it, which resolved in an error. than I had to sudo service lightdm start and was
[Touch-packages] [Bug 387997] Re: can't use sudo after a fresh install (karmic)
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! ** Changed in: sudo (Ubuntu) Status: Incomplete => Invalid -- 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/387997 Title: can't use sudo after a fresh install (karmic) Status in sudo package in Ubuntu: Invalid Bug description: Binary package hint: sudo I just try karmic-server-amd64 (Alpha-2) and I can't run sudo on it. ssh testor@192.168.122.80 testor@192.168.122.80's password: Linux ubuntu 2.6.30-8-server #9-Ubuntu SMP Wed Jun 3 16:37:12 UTC 2009 x86_64 The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. To access official Ubuntu documentation, please visit: http://help.ubuntu.com/ System information as of Tue Jun 16 18:10:01 CEST 2009 System load: 0.03 Memory usage: 7% Processes: 68 Usage of /: 60.1% of 895MB Swap usage: 0% Users logged in: 1 Graph this data and manage this system at https://landscape.canonical.com/ 35 packages can be updated. 0 updates are security updates. Last login: Tue Jun 16 18:09:18 2009 from 192.168.122.1 testor@ubuntu:~$ sudo date [sudo] password for testor: testor is not in the sudoers file. This incident will be reported. testor@ubuntu:~$ id uid=1000(testor) gid=1000(testor) groups=1000(testor) testor@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu karmic (development branch) Release:9.10 Codename: karmic testor@ubuntu:~$ df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 896M 538M 313M 64% / tmpfs 245M 0 245M 0% /lib/init/rw varrun245M 72K 244M 1% /var/run varlock 245M 0 245M 0% /var/lock udev 245M 156K 244M 1% /dev tmpfs 245M 0 245M 0% /dev/shm /home/testor/.Private 896M 538M 313M 64% /home/testor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/387997/+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 309325] Re: sudo segmentation fault [ubuntu 8.10]
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! ** Changed in: sudo (Ubuntu) Status: Incomplete => Invalid -- 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/309325 Title: sudo segmentation fault [ubuntu 8.10] Status in sudo package in Ubuntu: Invalid Bug description: Binary package hint: sudo I'm using ubuntu 8.10 Sudo version 1.6.9p17-1ubuntu2 When using sudo it returns "Segmentation fault" after entering the password. If I don't enter any password it goes to prompt without even saying "Sorry, try again" However, if do I enter a wrong password, it does go "Sorry, try again" It doesn't matter what command I'm entering (i.e even 'sudo ls') gksudo doesn't work, and returns nothing at all. Please help, I'm stuck without rights on my own computer EDIT: It turns out the problem is with pam. After rebooing I couldn't login at all.. purging samba and samba-common solved the problem for now. https://bugs.launchpad.net/ubuntu/+source/pam/+bug/292791/comments/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/309325/+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 885793] Re: .mkv & .flv videos don't play in Totem Ubuntu 11.10
[Expired for gstreamer0.10 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gstreamer0.10 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/885793 Title: .mkv & .flv videos don't play in Totem Ubuntu 11.10 Status in gstreamer0.10 package in Ubuntu: Expired Bug description: In Ubuntu 11.10, I can't play .mkv and some .flv videos in Totem (some other .flv videos do work). I don't get any messages, they just don't play. I see only the first frame of the .mkv or .flv video freezing on Totem where it says "Playing" at the left-bottom, the time stays 0:00 / 0:00 and the audio is automatically muted every time I play any .mkv or .flv video. When I right click in Nautilus to see the properties of these not- playing files I get a popup window saying "Creating Properties window. You can stop this operation by clicking cancel." -- and that is all I get. From the files that do play, I do get a properties window. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libgstreamer0.10-0 0.10.35-1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Thu Nov 3 19:21:35 2011 ExecutablePath: /usr/bin/totem InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/885793/+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 1057276] Re: when playing .flv and .mkv files on totem, the player crashes
[Expired for gstreamer0.10 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gstreamer0.10 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1057276 Title: when playing .flv and .mkv files on totem, the player crashes Status in gstreamer0.10 package in Ubuntu: Expired Bug description: can't play .flv and .mkv videos. the player crashes ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libgstreamer0.10-0 0.10.35-1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Thu Sep 27 09:10:21 2012 ExecutablePath: /usr/bin/totem InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1057276/+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 789379] Re: The following message is shown just after 2 seconds of playing the video :- "Gstreamer encountered a general stream error".
[Expired for gstreamer0.10 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gstreamer0.10 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/789379 Title: The following message is shown just after 2 seconds of playing the video :- "Gstreamer encountered a general stream error". Status in gstreamer0.10 package in Ubuntu: Expired Bug description: This problem occurs only when I am trying to play .mkv files. There is no problem when playing .avi files. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgstreamer0.10-0 0.10.30-1build2 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Fri May 27 18:59:11 2011 ExecutablePath: /usr/bin/totem InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gstreamer0.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/789379/+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 1611078] Re: Support snaps inside of lxd containers
Testing on Xenial with 4.8 Ubuntu kernel. In container, ubuntu@test:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial ubuntu@test:~$ dpkg -l | grep -i 'apparmor\|snap\|squash' ii apparmor 2.10.95-0ubuntu2.5 amd64 user-space parser utility for AppArmor ii libapparmor-perl 2.10.95-0ubuntu2.5 amd64 AppArmor library Perl bindings ii libapparmor1:amd64 2.10.95-0ubuntu2.5 amd64 changehat AppArmor library ii snap-confine 2.20.1ubuntu1 amd64 Support executable to apply confinement for snappy apps ii snapd2.20.1ubuntu1 amd64 Tool to interact with Ubuntu Core Snappy. ii squashfs-tools 1:4.3-3ubuntu2 amd64 Tool to create and append to squashfs filesystems ii squashfuse 0.1.100-0ubuntu1~ubuntu16.04.1 amd64 FUSE filesystem to mount squashfs archives ii ubuntu-core-launcher 2.20.1ubuntu1 amd64 Launcher for ubuntu-core (snappy) apps sudo snap install hello-world error: cannot perform the following tasks: - Setup snap "core" (714) security profiles (cannot setup udev for snap "core": cannot reload udev rules: exit status 2 -- 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/1611078 Title: Support snaps inside of lxd containers Status in Snappy: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in linux source package in Xenial: Fix Released Status in lxd source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in lxd source package in Yakkety: Fix Released Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-
[Touch-packages] [Bug 1653895] Re: package libmount1:armhf 2.27.1-6ubuntu3.1 failed to install/upgrade: libmount1:armhf 패키지는 설정 준비가 되어 있지 않습니다 설정할 수 없습니다. (현재 상태 : `half-installed')
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1653895 Title: package libmount1:armhf 2.27.1-6ubuntu3.1 failed to install/upgrade: libmount1:armhf 패키지는 설정 준비가 되어 있지 않습니다 설정할 수 없습니다. (현재 상태 : `half- installed') Status in util-linux package in Ubuntu: New Bug description: When I ran the commend above, it was freezing. "sudo apt-get upgrade" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmount1:armhf 2.27.1-6ubuntu3.1 Uname: Linux 4.1.19-v7+ armv7l ApportVersion: 2.20.1-0ubuntu2 AptOrdering: libmount1: Configure mysql-client: Install mysql-client: Configure NULL: ConfigurePending Architecture: armhf Date: Wed Jan 4 16:08:14 2017 DpkgTerminalLog: dpkg: error processing package libmount1:armhf (--configure): libmount1:armhf 패키지는 설정 준비가 되어 있지 않습니다 설정할 수 없습니다. (현재 상태 : `half-installed') ErrorMessage: libmount1:armhf 패키지는 설정 준비가 되어 있지 않습니다 설정할 수 없습니다. (현재 상태 : `half-installed') RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: util-linux Title: package libmount1:armhf 2.27.1-6ubuntu3.1 failed to install/upgrade: libmount1:armhf 패키지는 설정 준비가 되어 있지 않습니다 설정할 수 없습니다. (현재 상태 : `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1653895/+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 1654406] Re: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
** Package changed: d-conf (Ubuntu) => tracker (Ubuntu) ** Package changed: tracker (Ubuntu) => dconf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1654406 Title: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Status in dconf package in Ubuntu: New Bug description: chris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 chris@localhost:~$ apt-cache policy tracker-extract tracker-extract: Installed: 1.8.2-0ubuntu1~xenial3 Candidate: 1.8.2-0ubuntu1~xenial3 Version table: *** 1.8.2-0ubuntu1~xenial3 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages Jan 5 15:10:42 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Jan 5 15:12:25 localhost tracker-extract.desktop[3459]: message repeated 2 times: [ (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Jan 5 15:14:27 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. and so on every two minutes +- a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/1654406/+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 1583088] Re: Randomly corrupt font/text/characters in Unity8
Just updating the bug title so that people searching for keywords can find it (Launchpad only finds keywords separated by spaces) ** Summary changed: - Randomly corrupt characters in Unity8 + Randomly corrupt font/text/characters in Unity8 ** Summary changed: - Randomly corrupt font/text/characters in Unity8 + Randomly corrupt font / text / characters in Unity8 -- 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/1583088 Title: Randomly corrupt font / text / characters in Unity8 Status in Canonical System Image: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Corrupted characters in text rendering, mainly in Unity8 window titlebars. I think this is a new issue. It only started happening (on xenial desktop) in the past month or two. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1583092] Re: Focused windows have thin title font and unfocused thick
** Description changed: Focused windows have thin title font and unfocused thick. - It feels backwards. And the think bold text looks much nicer. I think it + It feels backwards. And the thick bold text looks much nicer. I think it should always be bold in the titlebar. -- 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/1583092 Title: Focused windows have thin title font and unfocused thick Status in Canonical System Image: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Incomplete Bug description: Focused windows have thin title font and unfocused thick. It feels backwards. And the thick bold text looks much nicer. I think it should always be bold in the titlebar. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583092/+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 1654308] Re: Logging out of the unity8 session snap takes a long time or sometimes hangs endlessly
AFAIK the long delay on logout is unity8 dumping core (bug 1535297). Can you provide your unity8.log from when the delay occurred? Or reproduce the bug and provide the log here? ** Changed in: unity8 (Ubuntu) Status: New => Incomplete -- 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/1654308 Title: Logging out of the unity8 session snap takes a long time or sometimes hangs endlessly Status in unity8 package in Ubuntu: Incomplete Bug description: Pat "It consistently takes up to a minute to go from a blank screen to displaying the greeter." kg "as of Jan 5, my log out from unity8-session snap on classic is hanging endlessly, i end up having to reboot" kg's snaps kg@kg-MacBookPro:~$ snap list NameVersion Rev Developer Notes address-book-app0.2+17.04.20161124.2-0ubuntu1 19 canonical devmode camera-app 3.0.0.658 8canonical devmode chrome-test 55.0.2883.8719 chadmiller - gallery-app 0.0.67+17.04.20161129-0ubuntu1 10 canonical devmode libreoffice 5.2.3.2 10 canonical - ubuntu-app-platform 1 22 canonical - ubuntu-calculator-app 2.3.1 22 ubuntucoredev devmode ubuntu-calendar-app 0.1.1 22 canonical devmode ubuntu-clock-app3.8.480 22 ubuntucoredev devmode ubuntu-core 16.04.1 423 canonical - ubuntu-device-flash 3 3canonical devmode ubuntu-filemanager-app 0.4 10 canonical devmode ubuntu-image0.5+mvo13 20 canonical devmode ubuntu-terminal-app 0.8 14 canonical devmode unity8-session 1 294 canonical devmode webbrowser-app 20170104-staging4canonical - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1654308/+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 1576341] Re: fails in lxd container
I can confirm this on recently installed system. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial $ lxc launch ubuntu:xenial testct Creating testct Starting testct $ lxc exec testct -- systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● setvtrgb.service loaded failed failed Set console scheme ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 8 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1576341 Title: fails in lxd container Status in lvm2 package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Status in open-iscsi package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: The ubuntu:xenial image shows 'degraded' state in lxd on initial boot. $ lxc launch xenial x1 $ sleep 10 $ lxc file pull x1/etc/cloud/build.info - build_name: server serial: 20160420-145324 $ lxc exc x1 systemctl is-system-running degraded $ lxc exec x1 systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored
** Changed in: oxide/1.20 Milestone: 1.20.0 => 1.20.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1649861 Title: When upgrading to oxide 1.19, tabs from saved session are not restored Status in Oxide: In Progress Status in Oxide 1.19 series: Confirmed Status in Oxide 1.20 series: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: When upgrading to oxide 1.19, tabs from a session saved with oxide 1.18 are not restored. I’m seeing the following in the browser’s log: Failed to read initial state: invalid data It appears sessions::SerializedNavigationEntry::ReadFromPickle() fails, most likely because the format of the serialized entries was changed in chromium 55. Specifically, this commit seems like a good suspect: https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1649861/+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 1651518] Re: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create
The indicated upstream patch, f50582649f8eee73f59aff95fadd9a963ed4ffea, does not apply cleanly against systemd 229. Are there known prerequisites for this patch? ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: New -- 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/1651518 Title: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Bug description: == Comment: #1 - Application Cdeadmin - 2016-12-19 04:15:10 == Configuration: IBM 8001-22C (S822LC), LSI SAS adapters, SMC 4U90 disk drawers, HDD (180) 7.3TB Problem: HTX exercisers stopped on error, with HTX log showing "rc 11, errno 11 from main(): pthread_create" htxubuntu-425 lpar: busybee.aus.stglabs.ibm.com (root/ lab passwd) root@busybee:~# uname -a Linux busybee 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:27:59 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@busybee:~# cat /tmp/htxerr /dev/sdh Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdh Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error No errors logged in syslog after starting HTX: State: Open by: asperez on 16 December 2016 10:28:02 This error recreated on the smaller 1U Open Power system with the same smaller 1-adapter/1-4U90 drawer/90 HDD. There are 2 cables connected to the drawer (one to each ESM) that requires multipath enabled. lpar: yellowbee root@yellowbee:~# cat /tmp/htxerr /dev/sdao Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdak Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdt Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdaz Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdn Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdv Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdaj Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdal Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create State: Open by: cde00 on 19 December 2016 02:48:46 This defect will go to Linux as even after making the below 2 changes in systemd resource limit, errors are seen: root@yellowbee:/etc/systemd/logind.conf.d# cat htxlogindcustom.conf [Login] UserTasksMax=infinity root@yellowbee:/etc/systemd/logind.conf.d# cat ../system.conf.d/htxsystemdcustom.conf [Manager] DefaultTasksAccounting=yes DefaultTasksMax=infinity root@yellowbee:/etc/systemd/logind.conf.d# logind limit for MaxUserTask as well as systemd limit was made infinite. Please look defect SW363655 for more details and the suggestion given earlier by Linux team. errors are still seen. So, would ask Linux team to take a look and see if anything else is causing these errors. == Comment: #3 - Kevin W. Rudd - 2016-12-19 17:34:27 == It appears that the version of logind on this system does not support the value of "infinity", and is reverting to the default of 12288: # cat /sys/fs/cgroup/pids/user.slice/user-0.slice/pids.max 12288 As a workaround until this can be resolved, specify an exact value. You can try using the current system thread-max value: # ca
[Touch-packages] [Bug 1654194] Re: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1654194 Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in url-dispatcher package in Ubuntu: New Bug description: i'm getting this problem fix this ProblemType: Package DistroRelease: Ubuntu 16.10 Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 5 15:04:11 2017 DuplicateSignature: package:url-dispatcher:amd64:0.1+16.10.20160816.1-0ubuntu1 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... 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: error processing package libunity-scopes1.0:amd64 (--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 2016-08-11 (147 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: url-dispatcher Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-01-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1654194/+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 1654191] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1654191 Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unity-scopes-api package in Ubuntu: New Bug description: i'm getting this bug pleaz fix any way ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 5 15:01:23 2017 DuplicateSignature: package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... 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: error processing package libunity-scopes1.0:amd64 (--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 2016-08-11 (146 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-01-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1654191/+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 1654194] Re: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Your problem (from the DpkgTerminalLog) seems to be: 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: error processing package url-dispatcher:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1654194 Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in url-dispatcher package in Ubuntu: New Bug description: i'm getting this problem fix this ProblemType: Package DistroRelease: Ubuntu 16.10 Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 5 15:04:11 2017 DuplicateSignature: package:url-dispatcher:amd64:0.1+16.10.20160816.1-0ubuntu1 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... 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: error processing package libunity-scopes1.0:amd64 (--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 2016-08-11 (147 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: url-dispatcher Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-01-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1654194/+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 1654191] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Similarly to bug 1654194, your problem seems to be: Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... 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: error processing package libunity-scopes1.0:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 -- 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/1654191 Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unity-scopes-api package in Ubuntu: New Bug description: i'm getting this bug pleaz fix any way ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 5 15:01:23 2017 DuplicateSignature: package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... 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: error processing package libunity-scopes1.0:amd64 (--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 2016-08-11 (146 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-01-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1654191/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7
Hello Pat, or anyone else affected, Accepted unity-gtk-module into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity-gtk- module/0.0.0+15.04.20150118-0ubuntu3 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 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: unity-gtk-module (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Fix Committed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Committed Status in unity-gtk-module source package in Xenial: Fix Committed Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1654447] Re: 16.04 NetworkManager dead after hibernation
Bug #1624211 Duplicate of this bug sorry... -- 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/1654447 Title: 16.04 NetworkManager dead after hibernation Status in network-manager package in Ubuntu: New Bug description: 16.04 all updates. Toshiba Satalite L675 4G ram. Lots of disk space. Intel I3 Recently the return from hibernation has issues with Network Manager not running. I can open a terminal and do "sudo service NetworkManager restart" and it comes right back up and works fine again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1654447/+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 1654447] [NEW] 16.04 NetworkManager dead after hibernation
Public bug reported: 16.04 all updates. Toshiba Satalite L675 4G ram. Lots of disk space. Intel I3 Recently the return from hibernation has issues with Network Manager not running. I can open a terminal and do "sudo service NetworkManager restart" and it comes right back up and works fine again. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1654447 Title: 16.04 NetworkManager dead after hibernation Status in network-manager package in Ubuntu: New Bug description: 16.04 all updates. Toshiba Satalite L675 4G ram. Lots of disk space. Intel I3 Recently the return from hibernation has issues with Network Manager not running. I can open a terminal and do "sudo service NetworkManager restart" and it comes right back up and works fine again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1654447/+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 1654448] [NEW] XPS 13 9360, Realtek ALC3246, Headphone audio hiss
Public bug reported: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: New Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1641954] Re: Output switches from HDMI speakers to internal speakers on DPMS off
Hello Cristian, or anyone else affected, Accepted pulseaudio into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.2 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 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: pulseaudio (Ubuntu) Status: New => Fix Released ** Changed in: pulseaudio (Ubuntu Xenial) 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1641954 Title: Output switches from HDMI speakers to internal speakers on DPMS off Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Bug description: Impact: This bug affects users of audio via HDMI to their monitor or another HDMI device like an audio receiver. Regression potential: The regression potential should be low to non-existant. Test case: (1) Play some music through speakers connected through an HDMI display. (2) type `xset dpms force off` (3) Move mouse to bring screen back up. With the version of PulseAudio in Xenial now, music plays in internal speakers, even after display wakes up Once the version of PulseAudio from xenial-proposed is installed, music plays in HDMI speaker after display wakes up Original bug report PulseAudio 8.0 includes a well-known user-experience regression: Its new auto-routing algorithm tries to switch to another output, as soon as the active output gets disconnected. This leads to the following bad user experience: (1) Alice listens to music on her speakers, which are connected to the screen, which is connected through HDMI to the computer. (2) Alice leaves the computer, the screen gets suspended (DPMS off). (3) PulseAudio sees that the HDMI output got disconnected (although only for a short interval) and switches to internal speaker. (4) Alice returns to the computer but finds that the music is now playing through the internal speakers. (5) Alice can switch the output to the HDMI speakers manually, but the above user experience bug will reoccur when she leaves the computer again. This is a well-known upstream bug that was fixed in PulseAudio 9.0. Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is desirable to backport this fix to PulseAudio 8.0, so that all LTS users have better experience. Upstream said they would not do this and that I should report this to Ubuntu directly. Other information: * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946 * Fix 1: https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09 * Fix 2: https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1641954/+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 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target
I accepted systemd into xenial-proposed but I received an LP timeout when the script was trying to add a comment. I image you can figure out what to do from the resolvconf comment though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1649931 Title: systemd-networkd needs to ensure DNS is up before network- online.target Status in resolvconf package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in resolvconf source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in resolvconf source package in Yakkety: Fix Committed Status in resolvconf package in Debian: Fix Committed Bug description: Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached. This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug. [SRU] Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target. Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial. Test Case: lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash # make sure you're on systemd-229-4ubuntu13 apt update && apt install -y systemd # enable networkd and netplan apt install -y nplan cat < /etc/netplan/nplan.yaml network: version: 2 ethernets: eth0: dhcp4: true EOF sed -i.orig -e 's/^source/# source/' /etc/network/interfaces netplan generate # make sure cloud-init.service uses networkd sed -i.orig -e '/After=networking.service/a After=systemd-network-wait-online.service' /lib/systemd/system/cloud-init.service reboot # check that the order of execution with: journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service # the order should be: 1. resolvconf: systemd[1]: Started Nameserver information manager. 2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured... 3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS. 4. network-online.target: systemd[1]: Reached target Network is Online. === BAD OUTPUT === On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output: Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager. Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured... Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS... Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured. Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online. Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS. === GOOD OUTPUT === On a passing system, Reached target Network is Online occurs after 1, 2, and 3. Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager. Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured... Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured. Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS... Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS. Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+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 1649213] Re: Support rootfs on xhci-plat-hcd attached storage
On Thu, Jan 5, 2017 at 2:46 PM, Brian Murray wrote: > Is the Trusty task valid? I don't see an upload in its SRU queue. It is - I think Ike maybe waiting for the current trusty-proposed version to migrate before rebasing. -dann -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1649213 Title: Support rootfs on xhci-plat-hcd attached storage Status in initramfs-tools package in Ubuntu: Invalid Status in initramfs-tools source package in Trusty: New Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Zesty: Invalid Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires xhci-plat-hcd, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1649213/+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 1652486] Re: mesa gpu lockup
** Bug watch added: freedesktop.org Bugzilla #93649 https://bugs.freedesktop.org/show_bug.cgi?id=93649 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=93649 Importance: Unknown Status: Unknown ** Changed in: mesa (Ubuntu) Importance: Undecided => 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/1652486 Title: mesa gpu lockup Status in Mesa: Unknown Status in mesa package in Ubuntu: New Bug description: package: mesa version: 11.2.0-1ubuntu2.2 release: 16.04.1 / "Xenial" references: * https://bugs.freedesktop.org/show_bug.cgi?id=93649 * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3 symptoms: 1. kernel reports "GPU lockup" 2. kernel reports "GPU softreset" 3. immediately frozen display 4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 seconds." 5. computer hanging on system reboot requiring a forced power off Symptoms occur when playing Team Fortress 2. Attachments: 1. mesa source package patch 2. lspci output for video card (ie Radeon HD 7750) 3. kernel log To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1652486/+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 1450642] Please test proposed package
Hello Jamie, or anyone else affected, Accepted libseccomp into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libseccomp/2.1.1-1ubuntu1~trusty3 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 libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls Status in Snappy: Fix Released Status in Snappy 15.04 series: Fix Released Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Trusty: Fix Committed Status in libseccomp source package in Vivid: Fix Released Status in libseccomp source package in Wily: Fix Released Bug description: [Impact] Several syscalls were discovered to be missing when using the launcher on snappy. These should be added so we may properly support seccomp filtering. [Test Case] seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log. Eg: Regression Test Summary tests run: 6494 tests skipped: 52 tests passed: 6494 tests failed: 0 tests errored: 0 Furthermore, on a snappy system, perform: # Note, for the 14.04 SRU, you'll have to install snapd from trusty-proposed and reboot into the lts kernel that it installs $ sudo snap install hello-world $ hello-world.env It should show the environment. On an arm system with 2.1.1-1 from the archive, this will fail due to a seccomp denial: audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 compat=0 ip=0xb6fb0bd6 code=0x0 (note, snappy images have a ppa fix for this, see notes below). To test the segfault fix, do: $ scmp_sys_resolver 1024 Segmentation fault It should return: $ scmp_sys_resolver 1024 UNKNOWN For the new 3.19 syscalls: $ scmp_sys_resolver getrandom -1 it should return something like (actual number depends on arch, this is on armhf): $ scmp_sys_resolver getrandom 384 For the 14.04 SRU, test the following syscalls (expected results on amd64 are shown): $ scmp_sys_resolver getrandom 318 $ scmp_sys_resolver membarrier 324 $ scmp_sys_resolver userfaultfd 323 $ scmp_sys_resolver mlock2 325 autopkgtests for libseccomp have been added as part of this update to verify that the library recognizes all the syscalls from 3.19 and the private syscalls. These tests can be run like so (assuming you are in the unpacked source and the binaries are in ../binary): $ export REL=vivid $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED" Alternatively, if you don't have autopkgtest setup, you can do: $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter ... PASS $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-scmp_sys_resolver ... PASS Lastly, seccomp is used by lxc. lxc can be tested by using the test case as outlined in step 4 of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only. [Regression Potential] If the above tests, regression potential is considered low. Unknown syscalls will continue to be handled as before. Description of changes: add finit_module: https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15 sync the syscall table entries - 3.16 https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75 https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4 https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718 https://github
[Touch-packages] [Bug 1653487] Re: seccomp argument filtering not working on trusty amd64
Hello Michael, or anyone else affected, Accepted libseccomp into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libseccomp/2.1.1-1ubuntu1~trusty3 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: libseccomp (Ubuntu Trusty) 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 libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1653487 Title: seccomp argument filtering not working on trusty amd64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Trusty: Fix Committed Bug description: [Impact] A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we (currently) only use seccomp arg filtering in one interface which is why Tyler's testing of 2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. [Test Case] A test case is included in the build in debian/patches/bpf-accumulator-check.patch (19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log to verify no failures. You can also run the snapd testsuite: 0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp 1. enable deb-src trusty-proposed to get snapd 2.20 2. apt-get source snapd 3. cd ./snapd-2.20* 4. apt-get build-dep snapd 5. install libseccomp2 libseccomp-dev from trusty release (to demonstrate the problem) 6. debian/rules build # this should fail on amd64 ... FAIL: test_restrictions_working_args ... 7. install libseccomp2 libseccomp-dev from trusty-proposed 8. debian/rules clean ; debian/rules build # this should pass In addition, follow the testing procedures as outlined in bug #1450642 [Regression Potential] The patch to fix this issue required several other supporting patches. This patches applied cleanly to trusty and the patches themselves are well tested under upstream and 16.04+. The regression potential should be relatively low since the testsuite during the build shows no errors or failures and snapd has a big testsuite. Manually testing with snaps and lxc (the biggest consumers of libseccomp) and running the libseccomp autopkgtests also shows no issues. = Original description = The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not
[Touch-packages] [Bug 1653487] Re: seccomp argument filtering not working on trusty amd64
** Also affects: libseccomp (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: libseccomp (Ubuntu Trusty) Status: New => In Progress ** Changed in: libseccomp (Ubuntu Trusty) Importance: Undecided => High ** Changed in: libseccomp (Ubuntu Trusty) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: libseccomp (Ubuntu) Assignee: Jamie Strandboge (jdstrand) => (unassigned) ** Changed in: libseccomp (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1653487 Title: seccomp argument filtering not working on trusty amd64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Trusty: Fix Committed Bug description: [Impact] A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we (currently) only use seccomp arg filtering in one interface which is why Tyler's testing of 2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. [Test Case] A test case is included in the build in debian/patches/bpf-accumulator-check.patch (19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log to verify no failures. You can also run the snapd testsuite: 0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp 1. enable deb-src trusty-proposed to get snapd 2.20 2. apt-get source snapd 3. cd ./snapd-2.20* 4. apt-get build-dep snapd 5. install libseccomp2 libseccomp-dev from trusty release (to demonstrate the problem) 6. debian/rules build # this should fail on amd64 ... FAIL: test_restrictions_working_args ... 7. install libseccomp2 libseccomp-dev from trusty-proposed 8. debian/rules clean ; debian/rules build # this should pass In addition, follow the testing procedures as outlined in bug #1450642 [Regression Potential] The patch to fix this issue required several other supporting patches. This patches applied cleanly to trusty and the patches themselves are well tested under upstream and 16.04+. The regression potential should be relatively low since the testsuite during the build shows no errors or failures and snapd has a big testsuite. Manually testing with snaps and lxc (the biggest consumers of libseccomp) and running the libseccomp autopkgtests also shows no issues. = Original description = The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not run the integration tests of snap-confine in anything else beside the package build (until https://github.com/snapcore/snapd/pull/2433/files is merged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1653487/+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 1653487] Re: seccomp argument filtering not working on trusty amd64
I uploaded 2.1.1-1ubuntu1~trusty3 to fix this issue to trusty-proposed. ** Description changed: [Impact] A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we only use seccomp arg filtering in one interface which is why Tyler's testing of 2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. [Test Case] A test case is included in the build in debian/patches/bpf-accumulator-check.patch (19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log to verify no failures. You can also run the snapd testsuite: 0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp 1. enable deb-src trusty-proposed to get snapd 2.20 2. apt-get source snapd 3. cd ./snapd-2.20* 4. apt-get build-dep snapd 5. install libseccomp2 libseccomp-dev from trusty release (to demonstrate the problem) 6. debian/rules build # this should fail on amd64 ... FAIL: test_restrictions_working_args ... 7. install libseccomp2 libseccomp-dev from trusty-proposed 8. debian/rules clean ; debian/rules build # this should pass In addition, follow the testing procedures as outlined in bug #1450642 [Regression Potential] The patch to fix this issue required several other supporting patches. - This patches applied cleanly to trusty and the patches themselves are + These patches applied cleanly to trusty and the patches themselves are well tested under upstream and 16.04+. The regression potential should be relatively low since the testsuite during the build shows no errors or failures and snapd has a big testsuite. Manually testing with snaps and lxc (the biggest consumers of libseccomp) and running the libseccomp autopkgtests also shows no issues. = Original description = The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not run the integration tests of snap-confine in anything else beside the package build (until https://github.com/snapcore/snapd/pull/2433/files is merged). ** Description changed: [Impact] - A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we only use seccomp arg filtering in one interface which is why Tyler's testing of 2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. + A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument f
[Touch-packages] [Bug 1654422] [NEW] package libdbus-1-3:i386 1.10.6-1ubuntu3.1 failed to install/upgrade: A(z) libdbus-1-3:i386 csomag már települt és be van állítva
Public bug reported: package libdbus-1-3:i386 1.10.6-1ubuntu3.1 failed to install/upgrade: A(z) libdbus-1-3:i386 csomag már települt és be van állítva ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdbus-1-3:i386 1.10.6-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Thu Jan 5 23:44:16 2017 ErrorMessage: A(z) libdbus-1-3:i386 csomag már települt és be van állítva InstallationDate: Installed on 2017-01-05 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: dbus Title: package libdbus-1-3:i386 1.10.6-1ubuntu3.1 failed to install/upgrade: A(z) libdbus-1-3:i386 csomag már települt és be van állítva UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1654422 Title: package libdbus-1-3:i386 1.10.6-1ubuntu3.1 failed to install/upgrade: A(z) libdbus-1-3:i386 csomag már települt és be van állítva Status in dbus package in Ubuntu: New Bug description: package libdbus-1-3:i386 1.10.6-1ubuntu3.1 failed to install/upgrade: A(z) libdbus-1-3:i386 csomag már települt és be van állítva ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdbus-1-3:i386 1.10.6-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Thu Jan 5 23:44:16 2017 ErrorMessage: A(z) libdbus-1-3:i386 csomag már települt és be van állítva InstallationDate: Installed on 2017-01-05 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: dbus Title: package libdbus-1-3:i386 1.10.6-1ubuntu3.1 failed to install/upgrade: A(z) libdbus-1-3:i386 csomag már települt és be van állítva UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1654422/+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 1654421] [NEW] package libsystemd0:i386 229-4ubuntu13 failed to install/upgrade: A(z) libsystemd0:i386 csomag már települt és be van állítva
Public bug reported: package libsystemd0:i386 229-4ubuntu13 failed to install/upgrade: A(z) libsystemd0:i386 csomag már települt és be van állítva ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsystemd0:i386 229-4ubuntu13 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Thu Jan 5 23:44:16 2017 ErrorMessage: A(z) libsystemd0:i386 csomag már települt és be van állítva InstallationDate: Installed on 2017-01-05 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: systemd Title: package libsystemd0:i386 229-4ubuntu13 failed to install/upgrade: A(z) libsystemd0:i386 csomag már települt és be van állítva UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1654421 Title: package libsystemd0:i386 229-4ubuntu13 failed to install/upgrade: A(z) libsystemd0:i386 csomag már települt és be van állítva Status in systemd package in Ubuntu: New Bug description: package libsystemd0:i386 229-4ubuntu13 failed to install/upgrade: A(z) libsystemd0:i386 csomag már települt és be van állítva ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsystemd0:i386 229-4ubuntu13 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Thu Jan 5 23:44:16 2017 ErrorMessage: A(z) libsystemd0:i386 csomag már települt és be van állítva InstallationDate: Installed on 2017-01-05 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: systemd Title: package libsystemd0:i386 229-4ubuntu13 failed to install/upgrade: A(z) libsystemd0:i386 csomag már települt és be van állítva UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1654421/+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 1654416] [NEW] Requesting 2.4.44 build which includes fix for ITS#8185
Public bug reported: I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release. There have been no OpenLDAP releases since 2.4.44 in February 2016, so it looks like things have been stable for a while. I'd like to request a refreshed slapd package for 2.4.44 (the most recent slapd package available on Ubuntu is 2.4.42 which dates back to August 2015). This would help me remove a manual workaround for the ITS#8185 issue, and users would also benefit from the number of fixes in 2.4.43 and 2.4.44. http://www.openldap.org/software/release/changes.html purging stale pwdFailureTime attributes: http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185 ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1654416 Title: Requesting 2.4.44 build which includes fix for ITS#8185 Status in openldap package in Ubuntu: New Bug description: I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release. There have been no OpenLDAP releases since 2.4.44 in February 2016, so it looks like things have been stable for a while. I'd like to request a refreshed slapd package for 2.4.44 (the most recent slapd package available on Ubuntu is 2.4.42 which dates back to August 2015). This would help me remove a manual workaround for the ITS#8185 issue, and users would also benefit from the number of fixes in 2.4.43 and 2.4.44. http://www.openldap.org/software/release/changes.html purging stale pwdFailureTime attributes: http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1654416/+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 1598300] Re: CUPS web interface stops responding after a while
Please note that the delay of publishing the SRU for this bug is cause by bug 1642966. We either need to put out the SRU for that bug first (as it blocks any installation of the CUPS packages) or put out a joint SRU for both bugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1653487] Re: seccomp argument filtering not working on trusty amd64
** Summary changed: - seccomp argument filtering not working on trusty + seccomp argument filtering not working on trusty amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1653487 Title: seccomp argument filtering not working on trusty amd64 Status in libseccomp package in Ubuntu: In Progress Bug description: [Impact] A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we only use seccomp arg filtering in one interface which is why Tyler's testing of 2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. [Test Case] A test case is included in the build in debian/patches/bpf-accumulator-check.patch (19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log to verify no failures. You can also run the snapd testsuite: 0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp 1. enable deb-src trusty-proposed to get snapd 2.20 2. apt-get source snapd 3. cd ./snapd-2.20* 4. apt-get build-dep snapd 5. install libseccomp2 libseccomp-dev from trusty release (to demonstrate the problem) 6. debian/rules build # this should fail on amd64 ... FAIL: test_restrictions_working_args ... 7. install libseccomp2 libseccomp-dev from trusty-proposed 8. debian/rules clean ; debian/rules build # this should pass In addition, follow the testing procedures as outlined in bug #1450642 [Regression Potential] The patch to fix this issue required several other supporting patches. This patches applied cleanly to trusty and the patches themselves are well tested under upstream and 16.04+. The regression potential should be relatively low since the testsuite during the build shows no errors or failures and snapd has a big testsuite. Manually testing with snaps and lxc (the biggest consumers of libseccomp) and running the libseccomp autopkgtests also shows no issues. = Original description = The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not run the integration tests of snap-confine in anything else beside the package build (until https://github.com/snapcore/snapd/pull/2433/files is merged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1653487/+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 1653487] Re: seccomp argument filtering not working on trusty
** Summary changed: - seccomp argument filtering not working on trusty(?) + seccomp argument filtering not working on trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1653487 Title: seccomp argument filtering not working on trusty amd64 Status in libseccomp package in Ubuntu: In Progress Bug description: [Impact] A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we only use seccomp arg filtering in one interface which is why Tyler's testing of 2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. [Test Case] A test case is included in the build in debian/patches/bpf-accumulator-check.patch (19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log to verify no failures. You can also run the snapd testsuite: 0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp 1. enable deb-src trusty-proposed to get snapd 2.20 2. apt-get source snapd 3. cd ./snapd-2.20* 4. apt-get build-dep snapd 5. install libseccomp2 libseccomp-dev from trusty release (to demonstrate the problem) 6. debian/rules build # this should fail on amd64 ... FAIL: test_restrictions_working_args ... 7. install libseccomp2 libseccomp-dev from trusty-proposed 8. debian/rules clean ; debian/rules build # this should pass In addition, follow the testing procedures as outlined in bug #1450642 [Regression Potential] The patch to fix this issue required several other supporting patches. This patches applied cleanly to trusty and the patches themselves are well tested under upstream and 16.04+. The regression potential should be relatively low since the testsuite during the build shows no errors or failures and snapd has a big testsuite. Manually testing with snaps and lxc (the biggest consumers of libseccomp) and running the libseccomp autopkgtests also shows no issues. = Original description = The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not run the integration tests of snap-confine in anything else beside the package build (until https://github.com/snapcore/snapd/pull/2433/files is merged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1653487/+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 1653487] Re: seccomp argument filtering not working on trusty(?)
** Description changed: - [Impact] - A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we only use seccomp arg filtering in one interface which is why Tyler's of 2.1.1-1ubuntu1~trusty1 testing didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. + [Impact] + A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we only use seccomp arg filtering in one interface which is why Tyler's testing of 2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. [Test Case] - A test case is included in the build in debian/patches/bpf-accumulator-check.patch. You can check the amd64 and verify no failures. + A test case is included in the build in debian/patches/bpf-accumulator-check.patch (19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log to verify no failures. You can also run the snapd testsuite: 0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp 1. enable deb-src trusty-proposed to get snapd 2.20 2. apt-get source snapd 3. cd ./snapd-2.20* - 4. debian/rules build # this should fail on amd64 - 5. install libseccomp2 from trusty-proposed - 6. debian/rules clean ; debian/rules build # this should pass + 4. apt-get build-dep snapd + 5. install libseccomp2 libseccomp-dev from trusty release (to demonstrate the problem) + 6. debian/rules build # this should fail on amd64 + ... + FAIL: test_restrictions_working_args + ... + 7. install libseccomp2 libseccomp-dev from trusty-proposed + 8. debian/rules clean ; debian/rules build # this should pass In addition, follow the testing procedures as outlined in bug #1450642 [Regression Potential] The patch to fix this issue required several other supporting patches. This patches applied cleanly to trusty and the patches themselves are well tested under upstream and 16.04+. The regression potential should be relatively low since the testsuite during the build shows no errors or failures and snapd has a big testsuite. Manually testing with snaps and lxc (the biggest consumers of libseccomp) and running the libseccomp autopkgtests also shows no issues. - = Original description = The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not run the integration tests of snap-confine in anything else beside the package build (until https://github.com/snapcore/snapd/pull/2433/files is merged). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which
[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
xnox, if you make an SRU for this bug, can you merge it with the SRU for bug 1598300. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Triaged Status in cups source package in Xenial: Triaged Status in cups source package in Yakkety: Triaged Status in cups source package in Zesty: Triaged Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 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/cups/+bug/1642966/+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 1650389] Re: Installing snapd on 14.04.5 desktop downgrades xorg et al.
** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1650389 Title: Installing snapd on 14.04.5 desktop downgrades xorg et al. Status in Snappy: Confirmed Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Trusty: New Bug description: When trying to install the latest snapd on a 14.04.5 desktop image, the installation of systemd (as a dependency of snapd) triggers a whole bunch of downgrades as systemd-shim is removed and replaced with systemd. We have to adjust the packaging such that installation of systemd does not trigger such behavior for packages depending on systemd-shim in trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1650389/+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 1654406] [NEW] Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
Public bug reported: chris@localhost:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 chris@localhost:~$ apt-cache policy tracker-extract tracker-extract: Installed: 1.8.2-0ubuntu1~xenial3 Candidate: 1.8.2-0ubuntu1~xenial3 Version table: *** 1.8.2-0ubuntu1~xenial3 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages Jan 5 15:10:42 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Jan 5 15:12:25 localhost tracker-extract.desktop[3459]: message repeated 2 times: [ (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Jan 5 15:14:27 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. and so on every two minutes +- a few seconds. ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1654406 Title: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Status in d-conf package in Ubuntu: New Bug description: chris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 chris@localhost:~$ apt-cache policy tracker-extract tracker-extract: Installed: 1.8.2-0ubuntu1~xenial3 Candidate: 1.8.2-0ubuntu1~xenial3 Version table: *** 1.8.2-0ubuntu1~xenial3 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages Jan 5 15:10:42 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Jan 5 15:12:25 localhost tracker-extract.desktop[3459]: message repeated 2 times: [ (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Jan 5 15:14:27 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. and so on every two minutes +- a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1654406/+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 1653487] Re: seccomp argument filtering not working on trusty(?)
** Description changed: + [Impact] + A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we only use seccomp arg filtering in one interface which is why Tyler's of 2.1.1-1ubuntu1~trusty1 testing didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. + + [Test Case] + A test case is included in the build in debian/patches/bpf-accumulator-check.patch. You can check the amd64 and verify no failures. + + You can also run the snapd testsuite: + 0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp + 1. enable deb-src trusty-proposed to get snapd 2.20 + 2. apt-get source snapd + 3. cd ./snapd-2.20* + 4. debian/rules build # this should fail on amd64 + 5. install libseccomp2 from trusty-proposed + 6. debian/rules clean ; debian/rules build # this should pass + + In addition, follow the testing procedures as outlined in bug #1450642 + + [Regression Potential] + + The patch to fix this issue required several other supporting patches. + This patches applied cleanly to trusty and the patches themselves are + well tested under upstream and 16.04+. The regression potential should + be relatively low since the testsuite during the build shows no errors + or failures and snapd has a big testsuite. Manually testing with snaps + and lxc (the biggest consumers of libseccomp) and running the libseccomp + autopkgtests also shows no issues. + + + = Original description = The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not run the integration tests of snap-confine in anything else beside the package build (until https://github.com/snapcore/snapd/pull/2433/files is merged). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1653487 Title: seccomp argument filtering not working on trusty Status in libseccomp package in Ubuntu: In Progress Bug description: [Impact] A latent bug in libseccomp 2.1.0 and the proposed 2.1.1-1ubuntu1~trusty1 was exposed in the snapd build testsuite when run on amd64. It has to do with libseccomp's state machine not always working correctly when using argument filtering and there were no tests for this particular failure in 2.1. Once 19e6c4aeca9818c4b288b09911dfa4be9a831236 (the upstream test for this issue) is applied to 2.1, you see the failures. Simple seccomp filters that just use the syscall name are not affected by the bug and we only use seccomp arg filtering in one interface which is why Tyler's testing of 2.1.1-1ubuntu1~trusty1 didn't show it either. The snap-confine tests do exercise it, but seccomp argument filtering wasn't added until series 16 and seccomp 2.2.3 had all the fixes already. Porting series 16 snapd/snap-confine and all of snap-confine's arg filtering tests to trusty revealed the bug in seccomp 2.1. [Test Case] A test case is included in the build in debian/patches/bpf-accumulator-check.patch (19e6c4aeca9818c4b288b09911dfa4be9a831236). You can check the amd64 build log to verify no failures. You can also run the snapd testsuite: 0. apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev se
[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while
Thank you Robie for pointing to the fix in comment 21 and for the comment that the final fix should be exactly as that one. Any estimate about when will we see the final fix in updates? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1649213] Re: Support rootfs on xhci-plat-hcd attached storage
Is the Trusty task valid? I don't see an upload in its SRU queue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1649213 Title: Support rootfs on xhci-plat-hcd attached storage Status in initramfs-tools package in Ubuntu: Invalid Status in initramfs-tools source package in Trusty: New Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Zesty: Invalid Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires xhci-plat-hcd, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1649213/+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 1649213] Re: Support rootfs on xhci-plat-hcd attached storage
Hello Ike, or anyone else affected, Accepted initramfs-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.122ubuntu8.8 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 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: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1649213 Title: Support rootfs on xhci-plat-hcd attached storage Status in initramfs-tools package in Ubuntu: Invalid Status in initramfs-tools source package in Trusty: New Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Zesty: Invalid Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires xhci-plat-hcd, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1649213/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records
I've uploaded a version with the reverts to my PPA:
https://launchpad.net/~barry/+archive/ubuntu/experimental
A local build looks promising, but I want to test it more before I
upload it for real. Please do test the PPA version once it builds.
--
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/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
Status in systemd:
New
Status in network-manager package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Triaged
Bug description:
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping www.freedesktop.org
ping: www.freedesktop.org: Name or service not known
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
$ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
;www.freedesktop.org. IN A
www.freedesktop.org. 7146IN CNAME annarchy.freedesktop.org.
$ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
;www.freedesktop.org. IN A
www.freedesktop.org. 14399 IN CNAME annarchy.freedesktop.org.
annarchy.freedesktop.org. 14399 IN A 131.252.210.176
I trust it needn’t be explained why this makes the internet almost
completely useless in zesty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+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 1450642] Re: seccomp missing many new syscalls
@Tyler, the problem in bug #1653487 was due to a latent bug in libseccomp 2.1 that is only exposed via snap-confine's use of argument filtering. I'm uploading 2.1.1-1ubuntu1~trusty3 now and will do the verification. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls Status in Snappy: Fix Released Status in Snappy 15.04 series: Fix Released Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Trusty: Fix Committed Status in libseccomp source package in Vivid: Fix Released Status in libseccomp source package in Wily: Fix Released Bug description: [Impact] Several syscalls were discovered to be missing when using the launcher on snappy. These should be added so we may properly support seccomp filtering. [Test Case] seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log. Eg: Regression Test Summary tests run: 6494 tests skipped: 52 tests passed: 6494 tests failed: 0 tests errored: 0 Furthermore, on a snappy system, perform: # Note, for the 14.04 SRU, you'll have to install snapd from trusty-proposed and reboot into the lts kernel that it installs $ sudo snap install hello-world $ hello-world.env It should show the environment. On an arm system with 2.1.1-1 from the archive, this will fail due to a seccomp denial: audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 compat=0 ip=0xb6fb0bd6 code=0x0 (note, snappy images have a ppa fix for this, see notes below). To test the segfault fix, do: $ scmp_sys_resolver 1024 Segmentation fault It should return: $ scmp_sys_resolver 1024 UNKNOWN For the new 3.19 syscalls: $ scmp_sys_resolver getrandom -1 it should return something like (actual number depends on arch, this is on armhf): $ scmp_sys_resolver getrandom 384 For the 14.04 SRU, test the following syscalls (expected results on amd64 are shown): $ scmp_sys_resolver getrandom 318 $ scmp_sys_resolver membarrier 324 $ scmp_sys_resolver userfaultfd 323 $ scmp_sys_resolver mlock2 325 autopkgtests for libseccomp have been added as part of this update to verify that the library recognizes all the syscalls from 3.19 and the private syscalls. These tests can be run like so (assuming you are in the unpacked source and the binaries are in ../binary): $ export REL=vivid $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED" Alternatively, if you don't have autopkgtest setup, you can do: $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter ... PASS $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-scmp_sys_resolver ... PASS Lastly, seccomp is used by lxc. lxc can be tested by using the test case as outlined in step 4 of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only. [Regression Potential] If the above tests, regression potential is considered low. Unknown syscalls will continue to be handled as before. Description of changes: add finit_module: https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15 sync the syscall table entries - 3.16 https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75 https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4 https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718 https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a sync the syscall table entries - 3.17 https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9 sync the syscall table entries - 3.19 https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3 This should also be applied (fix a segfault for invalid syscall numbers): https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3 For the 14.04 SRU so that libseccomp can handle all of the syscalls in the 4.4 based linux-lts-xenial kernel: - membarrier and userfaultfd syscalls: https://github.com/seccomp/libseccomp/commit/d2ca11b7cdddbba3782b1e306ceacf19e898faee - x86 direct socket syscalls https://github.c
[Touch-packages] [Bug 1450642] Re: seccomp missing many new syscalls
** Description changed: [Impact] Several syscalls were discovered to be missing when using the launcher on snappy. These should be added so we may properly support seccomp filtering. [Test Case] seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log. Eg: Regression Test Summary tests run: 6494 tests skipped: 52 tests passed: 6494 tests failed: 0 tests errored: 0 Furthermore, on a snappy system, perform: - # Note, for the 14.04 SRU, you'll have to install snapd from trusty-proposed - $ sudo snappy install hello-world + # Note, for the 14.04 SRU, you'll have to install snapd from trusty-proposed and reboot into the lts kernel that it installs + $ sudo snap install hello-world $ hello-world.env It should show the environment. On an arm system with 2.1.1-1 from the archive, this will fail due to a seccomp denial: audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 compat=0 ip=0xb6fb0bd6 code=0x0 (note, snappy images have a ppa fix for this, see notes below). To test the segfault fix, do: $ scmp_sys_resolver 1024 Segmentation fault It should return: $ scmp_sys_resolver 1024 UNKNOWN For the new 3.19 syscalls: $ scmp_sys_resolver getrandom -1 it should return something like (actual number depends on arch, this is on armhf): $ scmp_sys_resolver getrandom 384 For the 14.04 SRU, test the following syscalls (expected results on amd64 are shown): $ scmp_sys_resolver getrandom 318 $ scmp_sys_resolver membarrier 324 $ scmp_sys_resolver userfaultfd 323 $ scmp_sys_resolver mlock2 325 - autopkgtests for libseccomp have been added as part of this update to verify that the library recognizes all the syscalls from 3.19 and the private syscalls. These tests can be run like so (assuming you are in the unpacked source and the binaries are in ../binary): $ export REL=vivid $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED" Alternatively, if you don't have autopkgtest setup, you can do: $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter ... PASS $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-scmp_sys_resolver ... PASS Lastly, seccomp is used by lxc. lxc can be tested by using the test case as outlined in step 4 of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only. [Regression Potential] If the above tests, regression potential is considered low. Unknown syscalls will continue to be handled as before. Description of changes: add finit_module: https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15 sync the syscall table entries - 3.16 https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75 https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4 https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718 https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a sync the syscall table entries - 3.17 https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9 sync the syscall table entries - 3.19 https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3 This should also be applied (fix a segfault for invalid syscall numbers): https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3 For the 14.04 SRU so that libseccomp can handle all of the syscalls in the 4.4 based linux-lts-xenial kernel: - membarrier and userfaultfd syscalls: https://github.com/seccomp/libseccomp/commit/d2ca11b7cdddbba3782b1e306ceacf19e898faee - x86 direct socket syscalls https://github.com/seccomp/libseccomp/commit/24114ca6703036f76be1920a7ba387d6835dd764 - mlock2 syscall https://github.com/seccomp/libseccomp/commit/173b96ba8d36a4b1954e99570e82f2f932fe056a In addition, add-missing-arm-private-syscalls.patch is add to add 5 private ARM syscalls. These are absolutely required on snappy. This portion of the patch has been well tested and is included by default in stable snappy images via the snappy image PPA. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https:
[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records
As per pitti's email in #12, added network-manager bugtask and
subscribed pitti.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: network-manager (Ubuntu)
Milestone: None => ubuntu-17.04
--
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/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
Status in systemd:
New
Status in network-manager package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Triaged
Bug description:
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping www.freedesktop.org
ping: www.freedesktop.org: Name or service not known
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
$ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
;www.freedesktop.org. IN A
www.freedesktop.org. 7146IN CNAME annarchy.freedesktop.org.
$ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
;www.freedesktop.org. IN A
www.freedesktop.org. 14399 IN CNAME annarchy.freedesktop.org.
annarchy.freedesktop.org. 14399 IN A 131.252.210.176
I trust it needn’t be explained why this makes the internet almost
completely useless in zesty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+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 1654308] Re: Logging out of the unity8 session snap takes a long time or sometimes hangs endlessly
I believe @mterry and I were looking at this in The Hague (but put it on the back burner since). I don't think its specific to snaps and may be an issue with LightDM. Stay tuned... ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Josh Arenson (josharenson) -- 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/1654308 Title: Logging out of the unity8 session snap takes a long time or sometimes hangs endlessly Status in unity8 package in Ubuntu: New Bug description: Pat "It consistently takes up to a minute to go from a blank screen to displaying the greeter." kg "as of Jan 5, my log out from unity8-session snap on classic is hanging endlessly, i end up having to reboot" kg's snaps kg@kg-MacBookPro:~$ snap list NameVersion Rev Developer Notes address-book-app0.2+17.04.20161124.2-0ubuntu1 19 canonical devmode camera-app 3.0.0.658 8canonical devmode chrome-test 55.0.2883.8719 chadmiller - gallery-app 0.0.67+17.04.20161129-0ubuntu1 10 canonical devmode libreoffice 5.2.3.2 10 canonical - ubuntu-app-platform 1 22 canonical - ubuntu-calculator-app 2.3.1 22 ubuntucoredev devmode ubuntu-calendar-app 0.1.1 22 canonical devmode ubuntu-clock-app3.8.480 22 ubuntucoredev devmode ubuntu-core 16.04.1 423 canonical - ubuntu-device-flash 3 3canonical devmode ubuntu-filemanager-app 0.4 10 canonical devmode ubuntu-image0.5+mvo13 20 canonical devmode ubuntu-terminal-app 0.8 14 canonical devmode unity8-session 1 294 canonical devmode webbrowser-app 20170104-staging4canonical - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1654308/+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 1640326] Re: FTBFS on zesty
Marking as fixed released according tot he feedback here. ** Changed in: leveldb (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1640326 Title: FTBFS on zesty Status in leveldb package in Ubuntu: Fix Released Status in taglib package in Ubuntu: Invalid Status in thumbnailer package in Ubuntu: Fix Released Bug description: Hello, A no change rebuild on zesty FTBFS, is "zesty" not encoded somehow in the test suite exclusions? Could you please take a look and fix? This is blocking boost1.62 transition. The following tests FAILED: 1 - art_extractor (Failed) 3 - dbus (Failed) 9 - qml (Failed) 10 - libthumbnailer-qt (Failed) 14 - thumbnailer (SEGFAULT) 15 - thumbnailer-admin (Failed) Errors while running CTest Makefile:130: recipe for target 'test' failed make[2]: *** [test] Error 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/leveldb/+bug/1640326/+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 1654365] Re: Session dbus lauched by /etc/X11/Xsession.d/75dbus_dbus-launch dies immediately
** Description changed: We've been troubleshooting an issue with dbus on: $ system-image-cli -i current build number: 115 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2017-01-05 18:30:16 version version: 115 version ubuntu: 20170105.1 version device: 20161014.0 version custom: 20170105.1 I've come to the conclusion as follows: The session dbus daemon is launched by lightdm through Xsession.d /75dbus_dbus-launch (pstree): systemd,1 fixrtc - `-lightdm,2384 - `-lightdm,2439 --session-child 11 16 - `-dbus-launch,2692 --exit-with-session ubuntu-touch-session - `-dbus-launch,2747 --exit-with-session ubuntu-touch-session - `-dbus-daemon,2748 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session + `-lightdm,2384 + `-lightdm,2439 --session-child 11 16 + `-dbus-launch,2692 --exit-with-session ubuntu-touch-session + `-dbus-launch,2747 --exit-with-session ubuntu-touch-session + `-dbus-daemon,2748 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session Due to how the touch session is set up, dbus-launch subsequently kills the daemon because of the --exit-with-session option. Not sure exactly how/why this happens yet. The dbus-launch PID is replaced with upstart: phablet 2692 13.6 0.1 45948 3688 ?Ss 19:25 0:21 upstart --user It was fine so far because the session upstart dbus job launched a session dbus regardless. With the change in https://launchpad.net/ubuntu/+source/dbus/1.10.6-1ubuntu3.2 however, it won't launch one if DBUS_SESSION_BUS_ADDRESS is set already. The environment is left with the address of the dead session dbus and so we're left with a bogus environment variable... + + === Workaround === + + It's possible to disable the Xsessions-dbus script by editing + /etc/X11/Xsession.options and commenting out the following entry: + + use-session-dbus + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-touch-session 0.108+16.04.20161206-0ubuntu1 Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: arm64 Date: Thu Jan 5 19:06:28 2017 PackageArchitecture: all SourcePackage: ubuntu-touch-session UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.ubuntu-touch-session.d.android.conf: - GRID_UNIT_PX=13 - QTWEBKIT_DPR=1.0 - NATIVE_ORIENTATION=landscape - FORM_FACTOR=tablet + GRID_UNIT_PX=13 + QTWEBKIT_DPR=1.0 + NATIVE_ORIENTATION=landscape + FORM_FACTOR=tablet mtime.conffile..etc.ubuntu-touch-session.d.android.conf: 2016-10-14T08:44:51 upstart.bluez-mpris-proxy.log: - Can't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busorg.bluez appeared - Bluetooth Adapter /org/bluez/hci0 found - player core.ubuntu.media.Service at :1.1746 found + Can't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busorg.bluez appeared + Bluetooth Adapter /org/bluez/hci0 found + player core.ubuntu.media.Service at :1.1746 found upstart.obexd.log: - Failed to connect to socket /tmp/dbus-lf2wBKftE7: Connection refused - Failed to connect to socket /tmp/dbus-ej3pH8DVYy: Connection refused + Failed to connect to socket /tmp/dbus-lf2wBKftE7: Connection refused + Failed to connect to socket /tmp/dbus-ej3pH8DVYy: Connection refused upstart.plymouth-log.override: manual upstart.plymouth-shutdown.override: manual upstart.plymouth.override: manual ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1654365 Title: Session dbus lauched by /etc/X11/Xsession.d/75dbus_dbus-launch dies immediately Status in lightdm package in Ubuntu: New Status in ubuntu-touch-session package in Ubuntu: New Bug description: We've been troub
[Touch-packages] [Bug 1654371] [NEW] package python-setuptools 20.7.0-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: Running Ubuntu 16.04.1 MATE (32 bits) on a EeePC (1Gb RAM, HDD 750 Gb, fresh install) Was trying to install THONNY (IDE for beginners in python). (Because I didn't succeed via 'sudo apt-get install thonny', found some "pip" installation hints on the web). Installation succeeded a few days ago on Fujitsu-Siemens Amilo laptop (under Lubuntu 16.04 x64 desktop). I was trying to install PIP to get it done, but system aborted installation on error code. Might be important : used sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 20 to force system to use python 3.5 by default. Accept my apologies for my bad english. I hope you can understand what I wrote ;-) Best regards from Belgium. Claude ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-setuptools 20.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 Date: Thu Jan 5 20:23:34 2017 Dependencies: python-pkg-resources 20.7.0-1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2017-01-05 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: python-setuptools Title: package python-setuptools 20.7.0-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-setuptools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1654371 Title: package python-setuptools 20.7.0-1 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in python-setuptools package in Ubuntu: New Bug description: Running Ubuntu 16.04.1 MATE (32 bits) on a EeePC (1Gb RAM, HDD 750 Gb, fresh install) Was trying to install THONNY (IDE for beginners in python). (Because I didn't succeed via 'sudo apt-get install thonny', found some "pip" installation hints on the web). Installation succeeded a few days ago on Fujitsu-Siemens Amilo laptop (under Lubuntu 16.04 x64 desktop). I was trying to install PIP to get it done, but system aborted installation on error code. Might be important : used sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 20 to force system to use python 3.5 by default. Accept my apologies for my bad english. I hope you can understand what I wrote ;-) Best regards from Belgium. Claude ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-setuptools 20.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 Date: Thu Jan 5 20:23:34 2017 Dependencies: python-pkg-resources 20.7.0-1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2017-01-05 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: python-setuptools Title: package python-setuptools 20.7.0-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1654371/+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 1654365] [NEW] Session dbus lauched by /etc/X11/Xsession.d/75dbus_dbus-launch dies immediately
Public bug reported: We've been troubleshooting an issue with dbus on: $ system-image-cli -i current build number: 115 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2017-01-05 18:30:16 version version: 115 version ubuntu: 20170105.1 version device: 20161014.0 version custom: 20170105.1 I've come to the conclusion as follows: The session dbus daemon is launched by lightdm through Xsession.d /75dbus_dbus-launch (pstree): systemd,1 fixrtc `-lightdm,2384 `-lightdm,2439 --session-child 11 16 `-dbus-launch,2692 --exit-with-session ubuntu-touch-session `-dbus-launch,2747 --exit-with-session ubuntu-touch-session `-dbus-daemon,2748 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session Due to how the touch session is set up, dbus-launch subsequently kills the daemon because of the --exit-with-session option. Not sure exactly how/why this happens yet. The dbus-launch PID is replaced with upstart: phablet 2692 13.6 0.1 45948 3688 ?Ss 19:25 0:21 upstart --user It was fine so far because the session upstart dbus job launched a session dbus regardless. With the change in https://launchpad.net/ubuntu/+source/dbus/1.10.6-1ubuntu3.2 however, it won't launch one if DBUS_SESSION_BUS_ADDRESS is set already. The environment is left with the address of the dead session dbus and so we're left with a bogus environment variable... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-touch-session 0.108+16.04.20161206-0ubuntu1 Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: arm64 Date: Thu Jan 5 19:06:28 2017 PackageArchitecture: all SourcePackage: ubuntu-touch-session UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.ubuntu-touch-session.d.android.conf: GRID_UNIT_PX=13 QTWEBKIT_DPR=1.0 NATIVE_ORIENTATION=landscape FORM_FACTOR=tablet mtime.conffile..etc.ubuntu-touch-session.d.android.conf: 2016-10-14T08:44:51 upstart.bluez-mpris-proxy.log: Can't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busorg.bluez appeared Bluetooth Adapter /org/bluez/hci0 found player core.ubuntu.media.Service at :1.1746 found upstart.obexd.log: Failed to connect to socket /tmp/dbus-lf2wBKftE7: Connection refused Failed to connect to socket /tmp/dbus-ej3pH8DVYy: Connection refused upstart.plymouth-log.override: manual upstart.plymouth-shutdown.override: manual upstart.plymouth.override: manual ** Affects: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1654365 Title: Session dbus lauched by /etc/X11/Xsession.d/75dbus_dbus-launch dies immediately Status in ubuntu-touch-session package in Ubuntu: New Bug description: We've been troubleshooting an issue with dbus on: $ system-image-cli -i current build number: 115 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2017-01-05 18:30:16 version version: 115 version ubuntu: 20170105.1 version device: 20161014.0 version custom: 20170105.1 I've come to the conclusion as follows: The session dbus daemon is launched by lightdm through Xsession.d /75dbus_dbus-launch (pstree): systemd,1 fixrtc `-lightdm,2384 `-lightdm,2439 --session-child 11 16 `-dbus-launch,2692 --exit-with-session ubuntu-touch-session `-dbus-launch,2747 --exit-with-session ubuntu-touch-session `-dbus-daemon,2748 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session Due to how the touch session is set up, dbus-launch subsequently kills the daemon because of the --exit-with-session option. Not sure exactly how/why this happens yet. The dbus-launch PID is replaced with upstart: phablet 2692 13.6 0.1 45948 3688 ?Ss 19:25 0:21 upstart --user It was fine so far because the session upstart dbus job launched a session dbus regardless. With the change in https://launchpad.net/ubuntu/+source/dbus/1.10.6-1ubuntu3.2 however, it won't launch one if DBUS_SESSION_BUS_ADDRESS is set already. The environment is left with the address of the dead session dbus and so we're left with a bogus environment variable... ProblemType: Bug DistroRelease: Ubuntu 16.04 Pac
[Touch-packages] [Bug 1577460] Re: mkinitramfs --help > Core dumped
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1577460 Title: mkinitramfs --help > Core dumped Status in Ubuntu on IBM z Systems: Fix Committed Status in glibc package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Fix Released Status in glibc source package in Xenial: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in glibc source package in Yakkety: Fix Released Status in util-linux source package in Yakkety: Fix Committed Bug description: [Testcase] * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help Expected result: /usr/sbin/mkinitramfs: unrecognized option '--help' -- Exit code 1 Current result: Segmentation fault Exit code 139. There are two bugs in play here. glibc bug was fixed, and util-linux bug needs an upload still. Problem Description == root@zlin060:~# mkinitramfs --help Segmentation fault (core dumped) W: non-GNU getopt root@zlin060:~# == Comment: #9 - Heinz-Werner Seeck - 2016-05-02 10:09:34 == With Ubuntu 14.40 login via ssh: Following cmd : 'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help' Following call-stack occured (creates coredump): #0 __strncmp_c (s1=0x2e6575634a500a6d , s1@entry=0x2e6575634a500a6a , s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at ../string/strncmp.c:44 #1 0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40, optstring=0x20030 , longopts=, longind=, long_only=0, d=0x3ff7ea8c330 , posixly_correct=0) at getopt.c:546 #2 0x03ff7e9d51f2 in _getopt_internal (argc=, argv=, optstring=, longopts=, longind=0x3fff7ffe674, long_only=0, posixly_correct=0) at getopt.c:1175 #3 0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65 #4 0x02aa236821d8 in ?? () #5 0x02aa23681c22 in main () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1577460/+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 1086811] Re: Add test suite
** Changed in: account-plugins (Ubuntu) Assignee: Robert Bruce Park (robru) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1086811 Title: Add test suite Status in Online Accounts: Account plugins: Confirmed Status in account-plugins package in Ubuntu: Triaged Bug description: account-plugins currently has no tests. We need automated test coverage to ensure quality and utilize autolanding of packages. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1086811/+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 1168943] Re: Friends does not present RT in official way: missing original avatar and pseudo, messages truncated
** Changed in: friends Assignee: Robert Bruce Park (robru) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1168943 Title: Friends does not present RT in official way: missing original avatar and pseudo, messages truncated Status in Friends: Triaged Status in friends-app package in Ubuntu: Triaged Bug description: Hello, When someone I follow on Twitter or Identica RT a tweet from the official way (ie not makes manually a citation with "RT @...") by using "Retweet" option, I expect to see the message in my Timeline as it appears on Twitter website. It means : avatar and pseudo of original author of message retweeted, and below a row which says "Shared" or "RT by @..." and name of user who made the RT. Because RT are a way to make your followers discover new interesting users and be able to follow them. I guess Friends will have soon an option to directly follow an user from a menu coming after click on his avatar or name, so for that we need the original ones, not those of the person who did the RT (see screenshot). Another problem : when you RT a message which is already 140 characters, the way Friends presents : it adds on the beginning of the message "RT @" and name of author, which reduces number of characters available. So often the end of message is truncated : we miss end of sentance, or sometimes URL links are no more correct and can not be visited from the RT. I hope it will be possible to make it like official Twitter behavior :) To manage notifications about this bug go to: https://bugs.launchpad.net/friends/+bug/1168943/+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 1248302] Re: facebook msgid parsing fails
** Changed in: friends
Assignee: Robert Bruce Park (robru) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to friends in Ubuntu.
https://bugs.launchpad.net/bugs/1248302
Title:
facebook msgid parsing fails
Status in Friends:
Confirmed
Status in friends package in Ubuntu:
Fix Released
Bug description:
ERROR Thread-22013-10-30 00:33:35,425 friends.utils.base list index
out of range
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/friends/utils/base.py", line 159, in
run
super().run()
File "/usr/lib/python3.3/threading.py", line 594, in run
self._target(*self._args, **self._kwargs)
File "/usr/lib/python3/dist-packages/friends/utils/base.py", line 153, in
_retval_catcher
self._success_callback(str(func(*args, **kwargs)))
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line
197, in receive
self.home()
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line
185, in home
self._get(ME_URL + '/home', 'messages')
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line
180, in _get
self._publish_entry(entry, stream=stream)
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line
124, in _publish_entry
entry=comment)
File "/usr/lib/python3/dist-packages/friends/protocols/facebook.py", line
92, in _publish_entry
post_id = message_id.split('_')[1]
IndexError: list index out of range
This is clearly caused by the fix from
https://bugs.launchpad.net/friends/+bug/1185684 so we need a more
robust way of parsing that string.
To manage notifications about this bug go to:
https://bugs.launchpad.net/friends/+bug/1248302/+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 1161546] Re: Disabled accounts data appears in timeline
** Changed in: friends Assignee: Robert Bruce Park (robru) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1161546 Title: Disabled accounts data appears in timeline Status in Friends: Incomplete Status in Gwibber: Invalid Status in friends-app package in Ubuntu: Incomplete Bug description: If you toggle off an online account, it doesn't remove posts from timeline To repeat: Add an online account, eg facebook Start gwibber --Timeline fills up with facebook posts Close gwibber Toggle account off in online accounts (both setting 'gwibber' to off, or turning off the entire account) gwibber still contains the previous data from the account EDIT: It appears that if I completely remove the account from online accounts the data is removed from gwibber.. Is this intended? If I disable an account I simply get no new data from the data source, and I must remove the account completely to remove the data? (If so, what about the other account integration points I may want to keep?) To manage notifications about this bug go to: https://bugs.launchpad.net/friends/+bug/1161546/+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 1171670] Re: [indicators] Provide Ability To Post via Message Icon in Global Menu Bar
** Changed in: friends Assignee: Robert Bruce Park (robru) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1171670 Title: [indicators] Provide Ability To Post via Message Icon in Global Menu Bar Status in Friends: Confirmed Status in friends-app: New Status in Ubuntu UX: Triaged Status in friends-app package in Ubuntu: Confirmed Bug description: Using friends in 13.04, installed via `sudo apt-get install friends` In recent versions of Ubuntu (prior to writing this) I was able to click the message icon (currently a snail mail icon) and update my status on Identi.ca (and others) from the menu. Now, i cannot. Please bring that feature back. Thank you for your consideration. To manage notifications about this bug go to: https://bugs.launchpad.net/friends/+bug/1171670/+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 1035039] Re: Mock keyring tests
** Changed in: gnome-control-center-signon (Ubuntu) Assignee: Robert Bruce Park (robru) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1035039 Title: Mock keyring tests Status in Online Accounts: GNOME Control Center: Triaged Status in gnome-control-center-signon package in Ubuntu: Triaged Bug description: We really need the tests run in the package build, but using the keyring and signon-ui during the build is really problematic. The keyring and signon-ui access should be mocked. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center-signon/+bug/1035039/+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 1266787] Re: Autopilot tests pass in emulator, please consider automating their execution with emulator
** Changed in: friends-app (Ubuntu) Assignee: Robert Bruce Park (robru) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1266787 Title: Autopilot tests pass in emulator, please consider automating their execution with emulator Status in friends-app package in Ubuntu: New Bug description: I can execute autopilot address book app testsuite like so: $ bzr branch lp:~xnox/ubuntu-test-cases/touch-emulator $ cd touch-emulator $ ./scripts/provision-emulator.sh $ ./scripts/run-test.sh deb friends-app-autopilot friends_app On the desktop, on a headless server, on a cloud VM. Please consider automating test execution with emulator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1266787/+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 1262296] Re: qtorganizer5-eds: bugfixes, tests, saving multiple items, support for recurrence
** Changed in: landing-plan Status: In Progress => New ** Changed in: landing-plan Assignee: Robert Bruce Park (robru) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1262296 Title: qtorganizer5-eds: bugfixes, tests, saving multiple items, support for recurrence Status in Touch Landing Plan: New Status in qtorganizer5-eds package in Ubuntu: Fix Released Bug description: Run calendar-app click package AP tests and unity8 tests. Do some general dogfooding in the datetime area I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/landing-plan/+bug/1262296/+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 1654349] [NEW] computer stopped for a while..
Public bug reported: the computer "stopped" for a while and them continue working ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jan 5 18:07:55 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96M [GeForce 9700M GT] [10de:064a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96M [GeForce 9700M GT] [1043:19a2] InstallationDate: Installed on 2016-09-06 (120 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK Computer Inc. G71V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=1794e97f-a724-4f55-b96f-7de8f8e07ec2 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G71V 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.:bvr207:bd09/22/2008:svnASUSTeKComputerInc.:pnG71V:pvr1.0:rvnASUSTeKComputerInc.:rnG71V:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: G71V dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Thu Jan 5 18:05:06 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu yakkety -- 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/1654349 Title: computer stopped for a while.. Status in xorg package in Ubuntu: New Bug description: the computer "stopped" for a while and them continue working ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jan 5 18:07:55 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96M [GeForce 9700M GT] [10de:064a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96M [GeForce 9700M GT] [1043:19a2] InstallationDate: Installed on 2016-09-06 (120 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK Computer Inc. G71V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=1794e97f-a724-4f55-b96f-7de8f8e07ec2 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G71V 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.:bvr207:bd09/22/2008:svnASUSTeKComputerInc.:pnG71V:pvr1.
[Touch-packages] [Bug 1653295] Re: [Acer Chromebook 11 C730] Chromium and Chrome flickering
Jacob Doherty, given this is also reproducible with ChromeOS, is there a more direct recourse for you to submit a bug to Google directly? The only public bug reporting method I know of is via: http://dev.chromium.org/for-testers/bug-reporting-guidelines It would be helpful if you reported a public bug report upstream so that the ChromeOS/ChromiumOS developers can provide additional assistance. Once done, could you please advise to the bug report URL? ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1653295 Title: [Acer Chromebook 11 C730] Chromium and Chrome flickering Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Chromium and Chrome 55.0.2883.87 flickering. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 3.10.18 x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 31 11:19:59 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 04f2:b490 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashtree=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=5fb151de5f21d1172e6c0f68e3f1f582c083a5cd salt=4ce7adaeb24ff98d94fb9bff36a65ac39b743a9ecca5390ad010972810c5697a" noinitrd vt.global_cursor_default=0 kern_guid=f32d8bfa-395b-d240-bbf7-eb409533babd add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.bios.version: Google_Gnawty.5216.239.34 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrGoogle_Gnawty.5216.239.34:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 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 N/A 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 N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1653295/+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 1653295] Re: [Acer Chromebook 11 C730] Chromium and Chrome flickering
** Summary changed: - Chromium and Chrome flickering + [Acer Chromebook 11 C730] Chromium and Chrome flickering -- 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/1653295 Title: [Acer Chromebook 11 C730] Chromium and Chrome flickering Status in xorg package in Ubuntu: Incomplete Bug description: Chromium and Chrome 55.0.2883.87 flickering. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 3.10.18 x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 31 11:19:59 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 04f2:b490 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashtree=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=5fb151de5f21d1172e6c0f68e3f1f582c083a5cd salt=4ce7adaeb24ff98d94fb9bff36a65ac39b743a9ecca5390ad010972810c5697a" noinitrd vt.global_cursor_default=0 kern_guid=f32d8bfa-395b-d240-bbf7-eb409533babd add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.bios.version: Google_Gnawty.5216.239.34 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrGoogle_Gnawty.5216.239.34:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 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 N/A 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 N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653295/+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 1654075] Re: multiarch support broken in yakkety
** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1654075 Title: multiarch support broken in yakkety Status in heimdal package in Ubuntu: New Bug description: In Ubuntu 16.10 amd64 system the 32-bit heimdal libraries packages cannot be installed together with 64-bit packages, i.e.: $ sudo apt install libroken18-heimdal libroken18-heimdal:i386 Reading package lists... Done Building dependency tree Reading state information... Done libroken18-heimdal is already the newest version (1.7~git20160703+dfsg-1). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libroken18-heimdal : Breaks: libroken18-heimdal:i386 (!= 1.7~git20160703+dfsg-1) but 1.7~git20150920+dfsg-4ubuntu1 is to be installed libroken18-heimdal:i386 : Breaks: libroken18-heimdal (!= 1.7~git20150920+dfsg-4ubuntu1) but 1.7~git20160703+dfsg-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1654075/+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 1407640] Re: Preview generation should not rely on glReadPixels
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtvideo-node (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtvideo-node in Ubuntu. https://bugs.launchpad.net/bugs/1407640 Title: Preview generation should not rely on glReadPixels Status in Canonical System Image: Confirmed Status in qtvideo-node package in Ubuntu: Confirmed Bug description: Right now, snapshot/preview generation relies on a call to QGlFramebufferObject::toImage to obtain a QImage in http://bazaar.launchpad.net/~phablet-team/qtvideo- node/trunk/view/head:/src/snapshotgenerator.cpp#L118. Ultimately, this results in a very expensive call to glReadPixels, blocking the buffer processing of the camera app. Instead, we should avoid mapping the pixels to main memory and just copy the texture. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407640/+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 1645793] Re: Logout delayed by a minute because of url-dispatcher
** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1645793 Title: Logout delayed by a minute because of url-dispatcher Status in Canonical System Image: Fix Committed Status in url-dispatcher package in Ubuntu: Fix Released Bug description: If you try to log out during the first minute of a session, you may not be able to, because upstart is waiting for the url-dispatcher- refresh job to finish. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645793/+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 1651518] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2017-01-05 12:13 EDT--- State: Assigned by: cde00 on 05 January 2017 11:13:34 -- 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/1651518 Title: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create Status in systemd package in Ubuntu: New Bug description: == Comment: #1 - Application Cdeadmin - 2016-12-19 04:15:10 == Configuration: IBM 8001-22C (S822LC), LSI SAS adapters, SMC 4U90 disk drawers, HDD (180) 7.3TB Problem: HTX exercisers stopped on error, with HTX log showing "rc 11, errno 11 from main(): pthread_create" htxubuntu-425 lpar: busybee.aus.stglabs.ibm.com (root/ lab passwd) root@busybee:~# uname -a Linux busybee 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:27:59 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@busybee:~# cat /tmp/htxerr /dev/sdh Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdh Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error No errors logged in syslog after starting HTX: State: Open by: asperez on 16 December 2016 10:28:02 This error recreated on the smaller 1U Open Power system with the same smaller 1-adapter/1-4U90 drawer/90 HDD. There are 2 cables connected to the drawer (one to each ESM) that requires multipath enabled. lpar: yellowbee root@yellowbee:~# cat /tmp/htxerr /dev/sdao Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdak Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdt Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdaz Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdn Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdv Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdaj Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdal Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create State: Open by: cde00 on 19 December 2016 02:48:46 This defect will go to Linux as even after making the below 2 changes in systemd resource limit, errors are seen: root@yellowbee:/etc/systemd/logind.conf.d# cat htxlogindcustom.conf [Login] UserTasksMax=infinity root@yellowbee:/etc/systemd/logind.conf.d# cat ../system.conf.d/htxsystemdcustom.conf [Manager] DefaultTasksAccounting=yes DefaultTasksMax=infinity root@yellowbee:/etc/systemd/logind.conf.d# logind limit for MaxUserTask as well as systemd limit was made infinite. Please look defect SW363655 for more details and the suggestion given earlier by Linux team. errors are still seen. So, would ask Linux team to take a look and see if anything else is causing these errors. == Comment: #3 - Kevin W. Rudd - 2016-12-19 17:34:27 == It appears that the version of logind on this system does not support the value of "infinity", and is reverting to the default of 12288: # cat /sys/fs/cgroup/pids/user.slice/user-0.slice/pids.max 12288 As a workaround until this can be resolved, specify an exact value. You can try using the current system thread-max value: # cat /proc/sys/kernel/threads-max 3974272 /etc/systemd/logind.conf.d/htxlogindcustom.conf: [Login] UserTasksMax=3974272 == Comment: #4 - Kevin W. Rudd - 2016-12-20 10:25:09 == Canonical, This issue appears to map to the following systemd bug and patch: https://github.com/systemd/system
[Touch-packages] [Bug 1631763] Re: Ubuntu needs a GPU accelerated browser
Can we confirm there is no progress on this ? ** Description changed: We all know the Web support of an operating system is becoming more and more important for users. The situation right now in terms of browser Performance and power consumption of GNU/Linux is not really in a good shape compared to the 2 other competitors : Windows and Mac OSX. Windows 10 : Microsoft has shown how its integrated browser is more efficient and less hungry on power consumption than other browsers. Mac OSX: Safari is also showing a great power consumption and integrated features. + SO this bug is to track progress for an integrated browser for Ubuntu ( + can be firefox, chromium, something else ) that would out of the box : - SO this bug is to track progress for an integrated browser for Ubuntu ( can be firefox, chromium, something else ) that would out of the box : - - - - Use GPU for video decoding + - Use GPU for video decoding - Use GPU for Web 3D rendering like webGL - integrate as much as possible EME HTML5 for DRM support (like firefox 49 for netflix) + Please suggest other features in the comments - Please suggest other features in the comments + + For chromium we track progress on lp:#1424201 -- 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/1631763 Title: Ubuntu needs a GPU accelerated browser Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: We all know the Web support of an operating system is becoming more and more important for users. The situation right now in terms of browser Performance and power consumption of GNU/Linux is not really in a good shape compared to the 2 other competitors : Windows and Mac OSX. Windows 10 : Microsoft has shown how its integrated browser is more efficient and less hungry on power consumption than other browsers. Mac OSX: Safari is also showing a great power consumption and integrated features. SO this bug is to track progress for an integrated browser for Ubuntu ( can be firefox, chromium, something else ) that would out of the box : - Use GPU for video decoding - Use GPU for Web 3D rendering like webGL - integrate as much as possible EME HTML5 for DRM support (like firefox 49 for netflix) Please suggest other features in the comments For chromium we track progress on lp:#1424201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631763/+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 1651518] Re: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create
** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Taco Screen team (taco-screen-team) -- 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/1651518 Title: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create Status in systemd package in Ubuntu: New Bug description: == Comment: #1 - Application Cdeadmin - 2016-12-19 04:15:10 == Configuration: IBM 8001-22C (S822LC), LSI SAS adapters, SMC 4U90 disk drawers, HDD (180) 7.3TB Problem: HTX exercisers stopped on error, with HTX log showing "rc 11, errno 11 from main(): pthread_create" htxubuntu-425 lpar: busybee.aus.stglabs.ibm.com (root/ lab passwd) root@busybee:~# uname -a Linux busybee 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:27:59 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@busybee:~# cat /tmp/htxerr /dev/sdh Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdh Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage Hardware Exerciser stopped on an error No errors logged in syslog after starting HTX: State: Open by: asperez on 16 December 2016 10:28:02 This error recreated on the smaller 1U Open Power system with the same smaller 1-adapter/1-4U90 drawer/90 HDD. There are 2 cables connected to the drawer (one to each ESM) that requires multipath enabled. lpar: yellowbee root@yellowbee:~# cat /tmp/htxerr /dev/sdao Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdak Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdt Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdaz Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdn Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdv Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdaj Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create /dev/sdal Dec 16 01:14:44 2016 err=000b sev=1 hxestorage rc 11, errno 11 from main(): pthread_create State: Open by: cde00 on 19 December 2016 02:48:46 This defect will go to Linux as even after making the below 2 changes in systemd resource limit, errors are seen: root@yellowbee:/etc/systemd/logind.conf.d# cat htxlogindcustom.conf [Login] UserTasksMax=infinity root@yellowbee:/etc/systemd/logind.conf.d# cat ../system.conf.d/htxsystemdcustom.conf [Manager] DefaultTasksAccounting=yes DefaultTasksMax=infinity root@yellowbee:/etc/systemd/logind.conf.d# logind limit for MaxUserTask as well as systemd limit was made infinite. Please look defect SW363655 for more details and the suggestion given earlier by Linux team. errors are still seen. So, would ask Linux team to take a look and see if anything else is causing these errors. == Comment: #3 - Kevin W. Rudd - 2016-12-19 17:34:27 == It appears that the version of logind on this system does not support the value of "infinity", and is reverting to the default of 12288: # cat /sys/fs/cgroup/pids/user.slice/user-0.slice/pids.max 12288 As a workaround until this can be resolved, specify an exact value. You can try using the current system thread-max value: # cat /proc/sys/kernel/threads-max 3974272 /etc/systemd/logind.conf.d/htxlogindcustom.conf: [Login] UserTasksMax=3974272 == Comment: #4 - Kevin W. Rudd - 2016-12-20 10:25:09 == Canonical, This issue appears to map to the following systemd bug and patch: https://github.com/systemd/systemd/issues/3833 https://github.c
[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records
I will test the revert of this change until upstream fixes their bug.
** Changed in: systemd (Ubuntu)
Importance: Low => High
--
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/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
Status in systemd:
New
Status in systemd package in Ubuntu:
Triaged
Bug description:
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping www.freedesktop.org
ping: www.freedesktop.org: Name or service not known
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
$ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
;www.freedesktop.org. IN A
www.freedesktop.org. 7146IN CNAME annarchy.freedesktop.org.
$ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
;www.freedesktop.org. IN A
www.freedesktop.org. 14399 IN CNAME annarchy.freedesktop.org.
annarchy.freedesktop.org. 14399 IN A 131.252.210.176
I trust it needn’t be explained why this makes the internet almost
completely useless in zesty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+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 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
I was able to test this on a m10 tablet. The fix seems to have gone through to the cooler image I was trying to test - r13 in ubuntu- touch/staging/bq-aquaris-pd.en, and now no longer hangs on install. -- 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/1653725 Title: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Triaged Status in lxc source package in Xenial: Fix Committed Status in lxc source package in Yakkety: Fix Committed Status in lxc source package in Zesty: Fix Released Bug description: # SRU ## Rationale LXC 2.0.6 introduced a writability test for /var/lib/lxc which breaks the corner case of partly-writable systems like the Ubuntu phone. This upload fixes this by changing the test to a simple readability one. ## Test case 1) Attempt to run lxc-start with /var/lib/lxc on a read-only filesystem but /var/lib/lxc/ on a writable one. 2) Confirm that the container now starts. ## Regression potential This upload only changes the check from read/write to read so the only consequence of this should be more cases now being allowed. In the case where a writable /var/lib/lxc is in fact absolutely required for the requested operation, the operation will still fail, just a bit later and with a slightly less clear error message (as was the case pre-2.0.6). # Original report As in topic. Since the 20161217 rootfs, after upgrade of lxc from 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc-android-config service does not start - making the devices unbootable. The syslog only states this: Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and Container Initialization... Jan 3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN = 0x1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager... Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate persistent MAC address for ifb0: No such file or directory Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate persistent MAC address for ifb1: No such file or directory Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to /var/lib/lxc Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Control process exited, code=exited status=1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config and Container Initialization. Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for force-mtp.service. Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job force-mtp.service/start failed with result 'dependency'. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit entered failed state. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed with result 'exit-code'. This makes all of our frieza and cooler devices useless for testing purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+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 1654308] Re: Logging out of the unity8 session snap takes a long time or sometimes hangs endlessly
** Summary changed: - Logging out of the unity8 session snap takes a long time + Logging out of the unity8 session snap takes a long time or sometimes hangs endlessly ** Description changed: - It consistently takes up to a minute to go from a blank screen to - displaying the greeter. + Pat "It consistently takes up to a minute to go from a blank screen to displaying the greeter." + kg "as of Jan 5, my log out is hanging endlessly" + kg's snaps + + kg@kg-MacBookPro:~$ snap list + NameVersion Rev Developer Notes + address-book-app0.2+17.04.20161124.2-0ubuntu1 19 canonical devmode + camera-app 3.0.0.658 8canonical devmode + chrome-test 55.0.2883.8719 chadmiller - + gallery-app 0.0.67+17.04.20161129-0ubuntu1 10 canonical devmode + libreoffice 5.2.3.2 10 canonical - + ubuntu-app-platform 1 22 canonical - + ubuntu-calculator-app 2.3.1 22 ubuntucoredev devmode + ubuntu-calendar-app 0.1.1 22 canonical devmode + ubuntu-clock-app3.8.480 22 ubuntucoredev devmode + ubuntu-core 16.04.1 423 canonical - + ubuntu-device-flash 3 3canonical devmode + ubuntu-filemanager-app 0.4 10 canonical devmode + ubuntu-image0.5+mvo13 20 canonical devmode + ubuntu-terminal-app 0.8 14 canonical devmode + unity8-session 1 294 canonical devmode + webbrowser-app 20170104-staging4canonical - ** Description changed: - Pat "It consistently takes up to a minute to go from a blank screen to displaying the greeter." + Pat "It consistently takes up to a minute to go from a blank screen to + displaying the greeter." + + kg "as of Jan 5, my log out is hanging endlessly" kg's snaps kg@kg-MacBookPro:~$ snap list NameVersion Rev Developer Notes address-book-app0.2+17.04.20161124.2-0ubuntu1 19 canonical devmode camera-app 3.0.0.658 8canonical devmode chrome-test 55.0.2883.8719 chadmiller - gallery-app 0.0.67+17.04.20161129-0ubuntu1 10 canonical devmode libreoffice 5.2.3.2 10 canonical - ubuntu-app-platform 1 22 canonical - ubuntu-calculator-app 2.3.1 22 ubuntucoredev devmode ubuntu-calendar-app 0.1.1 22 canonical devmode ubuntu-clock-app3.8.480 22 ubuntucoredev devmode ubuntu-core 16.04.1 423 canonical - ubuntu-device-flash 3 3canonical devmode ubuntu-filemanager-app 0.4 10 canonical devmode ubuntu-image0.5+mvo13 20 canonical devmode ubuntu-terminal-app 0.8 14 canonical devmode unity8-session 1 294 canonical devmode webbrowser-app 20170104-staging4canonical - ** Description changed: Pat "It consistently takes up to a minute to go from a blank screen to displaying the greeter." - - kg "as of Jan 5, my log out is hanging endlessly" + kg "as of Jan 5, my log out from unity8-session snap on classic is hanging endlessly, i end up having to reboot" kg's snaps kg@kg-MacBookPro:~$ snap list NameVersion Rev Developer Notes address-book-app0.2+17.04.20161124.2-0ubuntu1 19 canonical devmode camera-app 3.0.0.658 8canonical devmode chrome-test 55.0.2883.8719 chadmiller - gallery-app 0.0.67+17.04.20161129-0ubuntu1 10 canonical devmode libreoffice 5.2.3.2 10 canonical - ubuntu-app-platform 1 22 canonical - ubuntu-calculator-app 2.3.1 22 ubuntucoredev devmode ubuntu-calendar-app 0.1.1 22 canonical devmode ubuntu-clock-app3.8.480 22 ubuntucoredev devmode ubuntu-core 16.04.1 423 canonical - ubuntu-device-flash
[Touch-packages] [Bug 1291373] Re: wget. memory leaks
** Changed in: wget (Ubuntu) Status: New => Triaged ** Changed in: wget (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1291373 Title: wget. memory leaks Status in wget package in Ubuntu: Triaged Bug description: Wget eats RAM when downloading big website. To reproduce run these on slow internet connection: bash$ wget -r -k -p -l inf -U 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)' 'http://bigwebsite.com/' 2> stderr.txt After one ~6 hours wget eats 1.5 GiB of RAM. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: wget 1.13.4-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-36.52~precise1-generic 3.8.13.14 Uname: Linux 3.8.0-36-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Mar 12 15:29:05 2014 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1291373/+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 1654307] Re: Font rendering in titlebars and indicators is glitchy
*** This bug is a duplicate of bug 1583088 *** https://bugs.launchpad.net/bugs/1583088 Yup, most likely a dupe of lp:1583088 ** This bug has been marked a duplicate of bug 1583088 Randomly corrupt characters in Unity8 -- 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/1654307 Title: Font rendering in titlebars and indicators is glitchy Status in unity8 package in Ubuntu: New Bug description: I'm running unity8 installed from debs with the stable-phone-overlay PPA on 16.04, in a qemu/kvm instance. Recently, some font rendering issues have started showing up in window title bars and in the indicators menus. Attached is a screenshot of the printing indicator that I've been working on, which shows the issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1654307/+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 1654313] [NEW] The greeter is not shown correctly when locking the screen
Public bug reported: This is not consistent, when switching between two user sessions (one unity8 and one unity7) I sometimes get presented with a screen that only provides the current session as an option. The screen itself is also sometimes different from the normal greeter (will add a pic next time) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1654313 Title: The greeter is not shown correctly when locking the screen Status in unity8 package in Ubuntu: New Bug description: This is not consistent, when switching between two user sessions (one unity8 and one unity7) I sometimes get presented with a screen that only provides the current session as an option. The screen itself is also sometimes different from the normal greeter (will add a pic next time) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1654313/+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 1654308] [NEW] Logging out of the unity8 session snap takes a long time
Public bug reported: It consistently takes up to a minute to go from a blank screen to displaying the greeter. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1654308 Title: Logging out of the unity8 session snap takes a long time Status in unity8 package in Ubuntu: New Bug description: It consistently takes up to a minute to go from a blank screen to displaying the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1654308/+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 1654310] [NEW] lxcfs: update the 'btime' field in /proc/stat to reflect guest boot time not host
Public bug reported: The 'btime' field in /proc/stat reflects the host boot time and not the time that the guest container has started. ** Affects: make-dfsg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1654310 Title: lxcfs: update the 'btime' field in /proc/stat to reflect guest boot time not host Status in make-dfsg package in Ubuntu: New Bug description: The 'btime' field in /proc/stat reflects the host boot time and not the time that the guest container has started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1654310/+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 1654306] [NEW] Unity8 is not in desktop mode inside the snap session
Public bug reported: On occasion when I enter the user session running unity8-session, the shell comes up in staged mode and the desktop mode toggle is disabled. Enabling it does not dynamically change the state. Logging out and in again seems to then start in desktop mode. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1654306 Title: Unity8 is not in desktop mode inside the snap session Status in unity8 package in Ubuntu: New Bug description: On occasion when I enter the user session running unity8-session, the shell comes up in staged mode and the desktop mode toggle is disabled. Enabling it does not dynamically change the state. Logging out and in again seems to then start in desktop mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1654306/+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 1654307] [NEW] Font rendering in titlebars and indicators is glitchy
Public bug reported: I'm running unity8 installed from debs with the stable-phone-overlay PPA on 16.04, in a qemu/kvm instance. Recently, some font rendering issues have started showing up in window title bars and in the indicators menus. Attached is a screenshot of the printing indicator that I've been working on, which shows the issues. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Weird font rendering in unity 8" https://bugs.launchpad.net/bugs/1654307/+attachment/4800382/+files/u8-printers.png -- 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/1654307 Title: Font rendering in titlebars and indicators is glitchy Status in unity8 package in Ubuntu: New Bug description: I'm running unity8 installed from debs with the stable-phone-overlay PPA on 16.04, in a qemu/kvm instance. Recently, some font rendering issues have started showing up in window title bars and in the indicators menus. Attached is a screenshot of the printing indicator that I've been working on, which shows the issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1654307/+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 1654298] Re: google maps scope cannot find position OTA 14 nexus 4
by the way: unav is working so gps works! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1654298 Title: google maps scope cannot find position OTA 14 nexus 4 Status in location-service package in Ubuntu: New Bug description: Install google maps scope or open maps.google.com in browser. wait and you see error "google cannot find your current location" browser & google maps both have location access in security settings. OTA14 phablet@ubuntu-phablet:~$ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1654298/+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 1654298] [NEW] google maps scope cannot find position OTA 14 nexus 4
Public bug reported: Install google maps scope or open maps.google.com in browser. wait and you see error "google cannot find your current location" browser & google maps both have location access in security settings. OTA14 phablet@ubuntu-phablet:~$ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 ** Affects: location-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1654298 Title: google maps scope cannot find position OTA 14 nexus 4 Status in location-service package in Ubuntu: New Bug description: Install google maps scope or open maps.google.com in browser. wait and you see error "google cannot find your current location" browser & google maps both have location access in security settings. OTA14 phablet@ubuntu-phablet:~$ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1654298/+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 1653529] Re: qtwebkit 5.7.1 fails to build on armhf
Looks like workaroundable by not using gold on armhf either for Qt (already disabled on powerpc and now newly i386 in Debian). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1653529 Title: qtwebkit 5.7.1 fails to build on armhf Status in gcc-6 package in Ubuntu: Confirmed Status in qtwebkit-opensource-src package in Ubuntu: Confirmed Bug description: Build log: https://launchpadlibrarian.net/300952415/buildlog_ubuntu- zesty-armhf.qtwebkit-opensource-src_5.7.1+dfsg- 1build1~1_BUILDING.txt.gz --- g++ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined -Wl,--no-undefined -fdebug-types-section -Wl,-O1 -Wl,--enable-new-dtags -Wl,--no-keep-memory -shared -Wl,-soname,libQt5WebKit.so.5 -o libQt5WebKit.so.5.7.1 -lQt5Gui -lQt5Core -lpthread -lQt5Network -lQt5Core -lpthread -lQt5Core -lpthread -lpthread -Wl,-whole-archive -lWebKit1 -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit/ -Wl,-whole-archive -lWebKit2 -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit2/ -lrt -Wl,-whole-archive -lWebCore -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebCore/ -lz -lXrender -ljpeg -lpng -lwebp -Wl,-whole-archive -lANGLE -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/ThirdParty/ANGLE/ -Wl,-whole-archive -lleveldb -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/ThirdParty/leveldb/ -Wl,-whole-archive -lJa vaScriptCore -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/JavaScriptCore/ -Wl,-whole-archive -lWTF -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WTF/ -lpthread -lEGL -lXext -lX11 -lm -lX11 -lxslt -lxml2 -lxml2 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstapp-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstpbutils-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstvideo-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstaudio-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lsqlite3 -licui18n -licuuc -licudata -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lpthread -lQt5Qml -lQt5Network -lQt5Core -lpthread -lQt5Network -lQt5Core -lpthread -lQt5Gui -lQt5Core -lpthread -lQt5Sql -lQt5Core -lpthread -lQt5Core -lpthread -lGLESv2 /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0): multiple definition of `__bss_start' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0): multiple definition of `_edata' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0): multiple definition of `_end' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0): multiple definition of `_edata' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0): multiple definition of `__bss_start' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0): multiple definition of `_end' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `__bss_start' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `__bss_start' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `_edata' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `_edata' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `_end' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `_end' collect2: error: ld returned 1 exit status --- This has built fine on Debian. https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1653529/+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 1603815] Re: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks
sorry, I gave up and I gave the laptop to a family member who is going to reinstall an OS. Miguel On 3 January 2017 at 11:42, Michael Mess <1603...@bugs.launchpad.net> wrote: > Can you check the password in network-manager view and edit it there? > > I think that the "wrong password - enter new"-dialog does not save the > entered password and thus a reconnect with the old wrong password always > fails. > See also Bug #1542733 which I have experienced together with this one. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1603815 > > Title: > after updating to ubuntu 16.04 the network manager is unable to > connect me to the wifi network. I can see the network, but once I > introduce the password, it asks me for the password after a few > seconds and never connects. > > Status in network-manager package in Ubuntu: > Confirmed > > Bug description: > after updating to ubuntu 16.04 the network manager is unable to > connect me to the wifi network. I can see the network, but once I > introduce the password, it asks me for the password after a few > seconds and never connects. I use different devices connected to the > same wifi so it is not a problem of writting the wrong password. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: network-manager 1.1.93-0ubuntu4 > ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 > Uname: Linux 4.4.0-31-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.1 > Architecture: amd64 > CurrentDesktop: Unity > Date: Sun Jul 17 16:58:17 2016 > IfupdownConfig: ># interfaces(5) file used by ifup(8) and ifdown(8) >auto lo >iface lo inet loopback > InstallationDate: Installed on 2016-07-16 (1 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > IpRoute: >default via 192.168.2.1 dev enp2s0 proto static metric 100 >169.254.0.0/16 dev enp2s0 scope link metric 1000 >192.168.2.0/24 dev enp2s0 proto kernel scope link src > 192.168.2.242 metric 100 > NetworkManager.state: >[main] >NetworkingEnabled=true >WirelessEnabled=true >WWANEnabled=true > SourcePackage: network-manager > UpgradeStatus: No upgrade log present (probably fresh install) > nmcli-con: >NAME UUID TYPE > TIMESTAMP TIMESTAMP-REALAUTOCONNECT > AUTOCONNECT-PRIORITY READONLY DBUS-PATH > ACTIVE DEVICE STATE ACTIVE-PATH >Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 > 802-3-ethernet 1468789026 dom 17 jul 2016 16:57:06 CDT yes > 4294966297no/org/freedesktop/NetworkManager/Settings/2 > yes enp2s0 activated /org/freedesktop/NetworkManager/ > ActiveConnection/1 >BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6 > 802-11-wireless 0 never yes 0 >no/org/freedesktop/NetworkManager/Settings/1 > no -- -- -- > nmcli-dev: >DEVICETYPE STATE DBUS-PATH > CONNECTION CON-UUID CON-PATH >enp2s0ethernet connected /org/freedesktop/NetworkManager/Devices/1 > Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 > /org/freedesktop/NetworkManager/ActiveConnection/1 >wlp3s0b1 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 > -- ---- >loloopback unmanaged /org/freedesktop/NetworkManager/Devices/2 > -- ---- > nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit > code 2: Error: Object 'nm' is unknown, try 'nmcli help'. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1603815/+ > subscriptions > -- 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/1603815 Title: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. Status in network-manager package in Ubuntu: Confirmed Bug description: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. I use different devices connected to the same wifi so it is not a problem of writting the wrong password. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0
[Touch-packages] [Bug 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts
** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1565772 Title: [SRU] Allow plugins to decide which username to set on new accounts Status in Online Accounts: Account plugins: Fix Released Status in Canonical System Image: Fix Released Status in Online Accounts: GNOME Control Center: Fix Released Status in webapps-sprint: Fix Committed Status in account-plugins package in Ubuntu: Fix Released Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in account-plugins source package in Xenial: Fix Committed Status in gnome-control-center-signon source package in Xenial: Fix Committed Status in account-plugins source package in Yakkety: Fix Released Status in gnome-control-center-signon source package in Yakkety: Fix Released Bug description: This bug is related to bug 1547647, even though it makes sense in any case. Currently, the ApOAuthPlugin class in libaccount-plugin gets the username from the SignonIdentity, which in turn gets it from signon- ui, which in the current WebKit1 implementation gets it from the DOM of the login webpage. This is a hack, it's fragile, not trivial to port to the Oxide web engine, and possibly against some providers' guidelines. We should retrieve the username using some REST API provided by the service, and in order to do so we need to extend libaccounts-plugin with some hooks which subclasses can use to get the username. Once we fix this we can also get rid of the files /etc/signon-ui /webkit-options.d/, which are conflicting with those installed by the KDE account plugins packages. SRU information === [Impact] The same file /etc/signon-ui/webkit- options.d/www.facebook.com.conf is installed by the account-plugin- facebook package (used by Unity) and by kaccount-providers (used by KDE). See this bug's duplicates to see actual bug reports. [Test Case] Install both account-plugin-facebook and kaccount- providers and you'll get the conflict. [Regression Potential] Users running KDE will be completely unaffected by this. Users running Unity might see a change when creating accounts in System Settings->Online Accounts: with this bugfix, the account's display name is obtained by making a REST API call to the remote service, rather than by scrapping the DOM of the server webpages (which is a hack, and prone to errors if the providers' webpage changes). The new way of retrieving the username is the proper one, and it's been tested to work reliably. In any case, the worst thing that might happen is that accounts get created with an empty display name, which is mostly an aesthetic problem (the display name is used only for UI purposes). To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1565772/+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 1653345] Re: Cura crashes on start probably caused by Qt5+DBus
removing unity8 as I don't see how anything in unity8 could influence this. ** No longer affects: unity8 (Ubuntu) -- 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/1653345 Title: Cura crashes on start probably caused by Qt5+DBus Status in Qt: New Status in unity package in Ubuntu: Confirmed Bug description: I installed Cura from the PPA (https://launchpad.net/~thopiekar/+archive/ubuntu/cura) When starting it it crashes. According to the issue on GitHub (https://github.com/Ultimaker/Cura/issues/1094) this is caused by a certain Qt version. To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1653345/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
Comment #8 worked for me too. Thank you! I'm on an Asus E402S with internal soundcard model Realtek ALC256. I'm running elementaryOS Loki. -- 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/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA 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.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings
Note: the workaround patch from comment 17 *will not* conflict with
whatever fix is implemented upstream. The patch changes *only* the NVMe
rules to force whitespace replacement. If upstream changes the default
behavior, to replace whitespace, then this workaround patch becomes
redundant/unneeded, but it will not conflict.
The issue is the behavior of udev for SYMLINK values, depending on the
"string_escape" option setting for each SYMLINK rule. There are 3
possible settings, 1) unset (the default), 2) "none", and 3) "replace".
As expected, when set to "none", udev does not replace any characters
(neither whitespace nor any other characters) in the SYMLINK value; and
when set to "replace", udev replaces all whitespace, as well as invalid
characters, with underscores. The default behavior (when unset) is what
may change upstream - currently, it replaces all invalid characters but
*does not* replace whitespace. This is a problem for SYMLINK values,
since the SYMLINK string is a whitespace-separated list of strings. No
rules that are included with udev currently want this behavior, but
there may be some custom udev rules that expect it. The NVMe rules do
not expect or want it. For reference, the NVMe udev rules are:
SYMLINK+="disk/by-id/nvme-$env{ID_SERIAL}"
SYMLINK+="disk/by-id/nvme-$env{ID_SERIAL}-part%n"
these rules expect one, and only one, symlink to be created for each new
NVMe drive (or NVMe partition) that is detected. Under no circumstances
do these rules ever want multiple symlinks created for a single
execution of the rule. So this workaround, to set
"string_escape=replace" only for these 2 NVMe rules, is appropriate. If
the default behavior upstream is changed later, so that any whitespace
in the ID_SERIAL string is replaced when "string_escape" is unset, then
the behavior of udev for these specific rules will be identical whether
"string_escape" is unset or set to "replace", and so at that point this
workaround patch can be left or reverted, as the udev behavior will be
identical either way. Until then, this workaround patch is needed for
the correct behavior.
--
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/1647485
Title:
NVMe symlinks broken by devices with spaces in model or serial strings
Status in systemd:
New
Status in systemd package in Ubuntu:
New
Bug description:
[Impact]
After including the patch from bug 1642903, NVMe devices that include spaces
in their model or serial strings result in incorrect symlinks, e.g. if the
model string is "XYZ Corp NVMe drive" then instead of creating:
/dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
it creates:
/dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
/dev/Corp -> nvme0n1
/dev/NVMe -> nvme0n1
/dev/drive_SERIAL -> nvme0n1
This is because of the way udev handles the SYMLINK value strings; by
default, it does not do any whitespace replacement. To enable
whitespace replacement of a symlink value, the rule must also include
OPTIONS+="string_escape=replace". This is done for 'md' and 'dm'
devices in their rules. However, there are no rules that actually
want to specify multiple symlinks, and defaulting to not replacing
whitespace makes no sense; instead, the default should be to replace
all whitespace in each symlink value, unless the rule explicitly
specifies OPTIONS+="string_escape=none".
[Test Case]
This assumes using udev with the patch from bug 1642903.
Without this patch, when using a NVMe drive that contains spaces in
its model and/or serial strings, check the /dev/disk/by-id/ directory.
It should contain a partially-correct symlink to the NVMe drive, with
the name up to the first space. All following space-separated parts
of the mode/serial string should have symlinks in the /dev/ directory.
This is the incorrect behavior.
With this patch, check the /dev/disk/by-id/ directory. It should
contain a fully-correct symlink to the NVMe drive, and no part of the
drive's model/serial number string should be a link in the /dev
directory.
An example of the correct/incorrect naming is in the Impact section.
There should be no other changes to any of the symlinks under /dev
before and after this patch. Typical locations for symlinks are
/dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
/dev/disk/by-label/
[Regression Potential]
Errors in udev rules can lead to an unbootable or otherwise completely
broken system if they unintentionally break or clobber existing
/dev/disks/ symlinks.
[Other Info]
This is also tracked with upstream systemd (udev) bug 4833:
https://github.com/systemd/systemd/issues/4833
Also note, this can be worked around in individual rules ONLY (i.e.
not fixed for all rules) by appending OPTIONS+="string_escape=replace"
to each of the NVMe rules with SYMLINK+="..." a
[Touch-packages] [Bug 1654244] [NEW] popups take up to 15 seconds to show
Public bug reported: Both the main popup of `indicator-network` and the popup listing OpenVPN connections take between 5 and 15 seconds to show. The number list of available ethernet connections is 1, of available WiFi connections 20 and of configured OpenVPN connections 2. There's been no changes to list, except maybe WiFi. An unknown time before (approx. weeks) the popups showed within parts of seconds. There's been no change to the system which could explain this recent behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 5 12:51:36 2017 InstallationDate: Installed on 2015-12-12 (389 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: indicator-network UpgradeStatus: Upgraded to yakkety on 2016-10-17 (80 days ago) ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1654244 Title: popups take up to 15 seconds to show Status in indicator-network package in Ubuntu: New Bug description: Both the main popup of `indicator-network` and the popup listing OpenVPN connections take between 5 and 15 seconds to show. The number list of available ethernet connections is 1, of available WiFi connections 20 and of configured OpenVPN connections 2. There's been no changes to list, except maybe WiFi. An unknown time before (approx. weeks) the popups showed within parts of seconds. There's been no change to the system which could explain this recent behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 5 12:51:36 2017 InstallationDate: Installed on 2015-12-12 (389 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: indicator-network UpgradeStatus: Upgraded to yakkety on 2016-10-17 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1654244/+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 1653345] Re: Cura crashes on start probably caused by Qt5+DBus
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1653345 Title: Cura crashes on start probably caused by Qt5+DBus Status in Qt: New Status in unity package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: I installed Cura from the PPA (https://launchpad.net/~thopiekar/+archive/ubuntu/cura) When starting it it crashes. According to the issue on GitHub (https://github.com/Ultimaker/Cura/issues/1094) this is caused by a certain Qt version. To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1653345/+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 1591833] Re: [Featue] Upgrade Openssl for Intel QAT (quickassist-technology)
Whilst debian is transitioning to openssl1.1, it is only partial transition at the moment with many projects explicitly not supporting openssl1.1 and forcing compilation against openssl1.0. In Ubuntu main, the big ones are apache2, erlang, openssh, ruby, pam. Providing security support for both openssl1.1 and openssl1.0 in main would increases attack surface and result in mixed features (some components have ability to use new crypto, whilst others don't). Thus we would like to only have one openssl in main, and we have reverted the openssl1.1 transition in Ubuntu. Making openssl1.1 available, without making it the default openssl is of limited benefit as none of the server packages will use it and/or benefit from it. Please note, 1.0.2 is LTS with upstream support until end of 2019. Whilst 1.1.0 has a shorter cycle until end of August 2018. Please help upstreams (apache2, openssh, erlang, ruby, pam-p11, etc.) porting to openssl1.1. ** Also affects: openssl (Ubuntu) Importance: Undecided Status: New ** Changed in: openssl (Ubuntu) Milestone: None => later ** Changed in: openssl (Ubuntu) Status: New => Confirmed ** Changed in: openssl (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1591833 Title: [Featue] Upgrade Openssl for Intel QAT (quickassist-technology) Status in intel: New Status in openssl package in Ubuntu: Confirmed Status in openssl package in Debian: Confirmed Bug description: In order to support Intel QAT, please upgrade Openssl package from 1.0.2 to 1.1.0 HW: Purley-4s Upstream schedule: Openssl: 1.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591833/+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 1577460] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted util-linux into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util- linux/2.27.1-6ubuntu3.2 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 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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1577460 Title: mkinitramfs --help > Core dumped Status in Ubuntu on IBM z Systems: In Progress Status in glibc package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Fix Released Status in glibc source package in Xenial: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in glibc source package in Yakkety: Fix Released Status in util-linux source package in Yakkety: Fix Committed Bug description: [Testcase] * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help Expected result: /usr/sbin/mkinitramfs: unrecognized option '--help' -- Exit code 1 Current result: Segmentation fault Exit code 139. There are two bugs in play here. glibc bug was fixed, and util-linux bug needs an upload still. Problem Description == root@zlin060:~# mkinitramfs --help Segmentation fault (core dumped) W: non-GNU getopt root@zlin060:~# == Comment: #9 - Heinz-Werner Seeck - 2016-05-02 10:09:34 == With Ubuntu 14.40 login via ssh: Following cmd : 'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help' Following call-stack occured (creates coredump): #0 __strncmp_c (s1=0x2e6575634a500a6d , s1@entry=0x2e6575634a500a6a , s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at ../string/strncmp.c:44 #1 0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40, optstring=0x20030 , longopts=, longind=, long_only=0, d=0x3ff7ea8c330 , posixly_correct=0) at getopt.c:546 #2 0x03ff7e9d51f2 in _getopt_internal (argc=, argv=, optstring=, longopts=, longind=0x3fff7ffe674, long_only=0, posixly_correct=0) at getopt.c:1175 #3 0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65 #4 0x02aa236821d8 in ?? () #5 0x02aa23681c22 in main () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1577460/+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 1577460] Re: mkinitramfs --help > Core dumped
Hello bugproxy, or anyone else affected, Accepted util-linux into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util- linux/2.28.2-1ubuntu1.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 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: util-linux (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Changed in: util-linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1577460 Title: mkinitramfs --help > Core dumped Status in Ubuntu on IBM z Systems: In Progress Status in glibc package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Fix Released Status in glibc source package in Xenial: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in glibc source package in Yakkety: Fix Released Status in util-linux source package in Yakkety: Fix Committed Bug description: [Testcase] * $ LC_ALL=fo_FOO.UTF-8 getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help Expected result: /usr/sbin/mkinitramfs: unrecognized option '--help' -- Exit code 1 Current result: Segmentation fault Exit code 139. There are two bugs in play here. glibc bug was fixed, and util-linux bug needs an upload still. Problem Description == root@zlin060:~# mkinitramfs --help Segmentation fault (core dumped) W: non-GNU getopt root@zlin060:~# == Comment: #9 - Heinz-Werner Seeck - 2016-05-02 10:09:34 == With Ubuntu 14.40 login via ssh: Following cmd : 'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help' Following call-stack occured (creates coredump): #0 __strncmp_c (s1=0x2e6575634a500a6d , s1@entry=0x2e6575634a500a6a , s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at ../string/strncmp.c:44 #1 0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40, optstring=0x20030 , longopts=, longind=, long_only=0, d=0x3ff7ea8c330 , posixly_correct=0) at getopt.c:546 #2 0x03ff7e9d51f2 in _getopt_internal (argc=, argv=, optstring=, longopts=, longind=0x3fff7ffe674, long_only=0, posixly_correct=0) at getopt.c:1175 #3 0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65 #4 0x02aa236821d8 in ?? () #5 0x02aa23681c22 in main () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1577460/+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
