[Touch-packages] [Bug 1576341] Re: fails in lxd container

[Serge Hallyn]

Seems like just adding

ConditionVirtualization=!container

to debian//open-iscsi.service should fix it.

-- 
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 1656615] [NEW] not been able to boot 16.4

[Nalin Gunawardana]

Public bug reported:

not been able to boot 16.4

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
BootLog:
 * Setting up X socket directories...    
[ OK ]
 Running 0dns-down to make sure resolv.conf is ok...done.
  * Starting uuid generator uuidd    
[ OK ]
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jan 15 11:33:53 2017
DistUpgraded: 2017-01-15 08:11:51,477 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.141+bdcom, 3.13.0-107-generic, x86_64: installed
 bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
 bcmwl, 6.30.223.141+bdcom, 3.13.0-86-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Park [Mobility Radeon HD 5430/5450/5470] 
[103c:1602]
InstallationDate: Installed on 2014-06-22 (937 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP G32 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=50de11f3-961c-4542-8baa-0b01016ee13d ro quiet splash 
init=/sbin/upstart
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-01-15 (0 days ago)
dmi.bios.date: 10/21/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.23
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1602
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 58.27
dmi.chassis.asset.tag: CNU1072M47
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPG32NotebookPC:pvr05991204271000100:rvnHewlett-Packard:rn1602:rvr58.27:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP G32 Notebook PC
dmi.product.version: 05991204271000100
dmi.sys.vendor: Hewlett-Packard
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 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Jan 15 11:29:18 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output  HDMI-0LVDS 
  VGA-0
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1656615

Title:
  not been able to boot 16.4

Status in xorg package in Ubuntu:
  New

Bug description:
  not been able to boot 16.4

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
   Running 0dns-down to make sure resolv.conf is ok...done.
* Starting uuid generator uuidd    
[ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jan 15 11:33:53 2017
  DistUpgraded: 2017-01-15 08:11:51,477 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.141+bdcom, 3.13.0-107-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-86-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller])
 

[Touch-packages] [Bug 1656611] [NEW] [D900T, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card

[Steve Henderson]

Public bug reported:

No sound from internal speakers or from headphone jack after updating to
ubuntu 16.04.1 from ubuntu 13.o .   controller is via search from
terminal,  00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) High Definition Audio Controller (rev 05)  .

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Sun Jan 15 00:36:23 2017
InstallationDate: Installed on 2017-01-15 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel
Symptom_Jack: Line Out, N/A
Title: [D900T, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/13/2005
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: D900T
dmi.board.vendor: CLEVO
dmi.board.version: Revision A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/13/2005:svnalienware:pnD900T:pvrRevisionA:rvnCLEVO:rnD900T:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: D900T
dmi.product.version: Revision A
dmi.sys.vendor: alienware

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1656611

Title:
  [D900T, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound from internal speakers or from headphone jack after updating
  to ubuntu 16.04.1 from ubuntu 13.o .   controller is via search from
  terminal,  00:1b.0 Audio device: Intel Corporation
  82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller
  (rev 05)  .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Jan 15 00:36:23 2017
  InstallationDate: Installed on 2017-01-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel
  Symptom_Jack: Line Out, N/A
  Title: [D900T, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2005
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: D900T
  dmi.board.vendor: CLEVO
  dmi.board.version: Revision A
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/13/2005:svnalienware:pnD900T:pvrRevisionA:rvnCLEVO:rnD900T:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: D900T
  dmi.product.version: Revision A
  dmi.sys.vendor: alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1656611/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1649086] Re: W: Invalid 'Date' entry in Release file /var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apt (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1649086

Title:
  W: Invalid 'Date' entry in Release file
  
/var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  root@ubuntu:/var/lib/apt/lists# apt-get update
  Hit:1 http://ppa.launchpad.net/stefansundin/truecrypt/ubuntu yakkety InRelease
  Hit:3 http://ppa.launchpad.net/unit193/encryption/ubuntu yakkety InRelease
  
  Hit:4 http://es.archive.ubuntu.com/ubuntu yakkety InRelease   
  
  Hit:5 http://repository.spotify.com stable InRelease  
  
  Hit:6 http://ppa.launchpad.net/wine/wine-builds/ubuntu yakkety InRelease  
  
  Get:7 http://es.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB]  
 
  Get:8 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB]   
 
  Get:9 http://es.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 
kB]
  Hit:2 http://screenshots.getdeb.net yakkety-getdeb InRelease  

  Ign:10 
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  
InRelease   
  Hit:11 
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  
Release
  Fetched 306 kB in 1s (242 kB/s)
  Reading package lists... Done
  W: Invalid 'Date' entry in Release file 
/var/lib/apt/lists/developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release
  root@ubuntu:/var/lib/apt/lists# 

  
  The file is as 
'developer.download.nvidia.com_compute_cuda_repos_ubuntu1604_x86%5f64_Release' 
follows:

  Origin: NVIDIA
  Label: NVIDIA CUDA
  Architecture: x86_64
  Date: Fri, 23 Sep 2016 18:52:52 -0700
  MD5Sum:
   3213a453e90b070bc10f329d2fe7f1a384080 Packages
   c1660fe24223ec9b07b04de1dfb3777122493 Packages.gz
  SHA1:
   60f8bd97333efb0bce147702712aab654ba3469b84080 Packages
   04e6ceaf9bcbcd3b36a9cc390b58110da138b7cd22493 Packages.gz
  SHA256:
   44a4473829b9403e7e2d36c43757b4d4ce8334b5804d90d920bd92edaf346241
84080 Packages
   f179e19b7c5b47d5c7247b5d6f37eb2ab2fba168ac70531dd02a0a1cda756038
22493 Packages.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1649086/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645232] Re: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL)

[Theodore Ts'o]

Thanks for the patch; it definitely helps identify the problem.  I don't
think it is a completely correct change, however.

The problem is that it's doing the translation in
write_xattrs_to_buffer(), but it is not making the translation in the
opposite direction in read_xattrs_to_buffer().   This means if some
other program using this library function --- for example, fuse2fs,
reads in an existing xattr block with an ACL, it will read it the on-
disk format, _not_ translate it to a standard acl format, and then
write_xattrs_to_buffer() will take as input an acl encoded in the on-
disk format, and then try to convert it from lgetxattr format to on-disk
format again, and Much Hilarity will result.

I also wonder if write_xattrs_to_buffer() is the right place to make
this conversion, or rather ext2fs_{read,write}_ext_attr3().   Then what
is stored in the handle structure is the on-disk encoding, and we would
do the translation at the higher layer function rather than the low-
level read/write functions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1645232

Title:
  e2fsprogs - could not preserve ACL permissions  : The getxattr()
  returns with (EINVAL)

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  The original installed e2fsprogs did not support mke2fs -d /directory
  " option . So ,  git cloned from e2fsprogs packages from repository
  and installed it and followed below steps to reproduce this :

  1. set the ACL rules as below to one of the binary :

  $ setfacl -m u:vipatil:r-- rootfs/usr/bin/helloworld
  $ getfacl rootfs/usr/bin/helloworld
  # file: rootfs/usr/bin/helloworld
  # owner: shkumar
  # group: hardev
  user::rwx
  user:vipatil:r--
  group::---
  mask::r--
  other::---

  2. $ dd if=/dev/zero of=test.ext4 bs=1M count=60

  3. $ mke2fs -t ext4 test.ext4 -d rootfs/
  mke2fs 1.43.3 (04-Sep-2016)
  Discarding device blocks: done
  Creating filesystem with 61440 1k blocks and 15360 inodes
  Filesystem UUID: 495713b3-5f1f-427a-8359-a736dfb2ece9
  Superblock backups stored on blocks:
  8193, 24577, 40961, 57345

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (4096 blocks): done
  Copying files into the device: done
  Writing superblocks and filesystem accounting information: done

  4. sudo mount -o loop,acl,user_xattr,rw,sync test.ext4 mountpoint

  5.@/mountpoint$ getfacl usr/bin/helloworld
  getfacl: usr/bin/helloworld: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1645232/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1631623] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[Launchpad Bug Tracker]

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/1631623

Title:
  package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  2016-10-07:  During upgrade from 15.10 to 16.04, I got several error
  msgs re: systemd-sysv-229-4ubuntu10 pre-dependency problems; after
  upgrade I noticed error icon in upper in right notification bar;  msg
  there was re: unmet dependencies, with suggestion to run apt-get -f
  install which I did; then I also ran apt-get autoremove; Then I
  rebooted, and got the crash report I am now submitting as a bug:
  package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct  7 15:49:45 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-11-16 (326 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-10-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1631623/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1594715] Re: wifi does not work roughly half of the times

[Joel]

@alberto: just tried what you suggested. Returns that dnsmasq is not
installed in the first place.

-- 
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/1594715

Title:
  wifi does not work roughly half of the times

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After booting, roughly half of the times, wifi doesn't work: The nm-
  applet menu looks as if no wifi would exist. Instead, it lists the a
  non-existing cable network device called "Marvell 88W8897 [AVASTAR]
  802.11ac Wireless". (The network manager seems to be trying to connect
  to that device, but fails.)

  After doing
/etc/init.d/network-manager restart
  the wifi device is always recognized properly, so I guess it's something 
happening in the wrong order during booting. (Alternatively, unloading and 
reloading the kernel module mwifiex_pcie also always helps.)

  The problem did not exist in ubuntu 15.10.

  
  Some more information:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04


  When the bug is there:

  $ nmcli d show wlp1s0
  GENERAL.DEVICE: wlp1s0
  GENERAL.TYPE:   ethernet
  GENERAL.HWADDR: 50:1A:C5:E8:2F:09
  GENERAL.MTU:1500
  GENERAL.STATE:  70 (connecting (getting IP 
configuration))
  GENERAL.CONNECTION: Kabelnetzwerkverbindung 2
  GENERAL.CON-PATH:   
/org/freedesktop/NetworkManager/ActiveConnection/7
  WIRED-PROPERTIES.CARRIER:   on

  $ ifconfig -a
  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:3380 errors:0 dropped:0 overruns:0 frame:0
TX packets:3380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1 
RX bytes:251184 (251.1 KB)  TX bytes:251184 (251.1 KB)

  wlp1s0Link encap:Ethernet  HWaddr 50:1a:c5:e8:2f:09  
UP BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  
  After restarting the network manager:

  immi@flunder:~$ nmcli d show wlp1s0
  GENERAL.DEVICE: wlp1s0
  GENERAL.TYPE:   wifi
  GENERAL.HWADDR: 50:1A:C5:E8:2F:09
  GENERAL.MTU:0
  GENERAL.STATE:  100 (connected)
  GENERAL.CONNECTION: virginmedia4709476
  GENERAL.CON-PATH:   
/org/freedesktop/NetworkManager/ActiveConnection/8
  IP4.ADDRESS[1]: 192.168.0.3/24
  IP4.GATEWAY:192.168.0.1
  IP4.ROUTE[1]:   dst = 169.254.0.0/16, nh = 0.0.0.0, 
mt = 1000
  IP4.DNS[1]: 194.168.4.100
  IP4.DNS[2]: 194.168.8.100
  IP6.ADDRESS[1]: fe80::521a:c5ff:fee8:2f09/64
  IP6.GATEWAY:

  (...)

  wlp1s0Link encap:Ethernet  HWaddr 50:1a:c5:e8:2f:09  
inet6 addr: fe80::521a:c5ff:fee8:2f09/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:304 (304.0 B)  TX bytes:680 (680.0 B)

  
  $ dmesg
  (...)
  [7.850180] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.850263] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.859773] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.869408] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  (...)

  
  I'm happy to try to fix the bug myself, but I could need some help: I don't 
know how to change booting order or something like that.

  I could also temporarily insert some commands into /etc/init.d
  /network-manager printing some status information about the wifi, but
  I don't know how to get such status information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 21 09:35:14 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-11-19 (579 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - 

[Touch-packages] [Bug 1574415] Re: [16.04] ssh : Bad protocol spec '1'

[Colin Watson]

I certainly won't grep user configuration files from package maintainer
scripts - that sort of thing causes serious problems in some
environments, particularly those with lots of users or home directories
mounted over NFS.

There's something to be said for doing a better job of the error message
in this case (e.g. pointing people to the openssh-client-ssh1 package),
although I'm wary of ending up maintaining yet another long-lived and
necessarily-Debian-specific patch.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1574415

Title:
  [16.04] ssh : Bad protocol spec '1'

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 16.04 ssh client will not connect to any host,
  reporting

  /home/tj/.ssh/config line 109: Bad protocol spec '1'.

  The entry is:

  Host ups-01
  Hostname 10.254.0.1
  User hostmaster
  IdentityFile ~/.ssh/id_hostmaster
  IdentitiesOnly yes
  Protocol 1

  If this were an entry in /etc/ssh/ssh_config and the user had no
  privileges to edit that file it could create a denial of service to
  the ssh client (if the user doesn't know how to over-ride the config).

  It would be helpful if the openssh-client postinst script were to grep
  the standard config files (including for users) and add a warning to
  the motd and syslog if any invalidated configuration statements are
  found.

  This will especially affect connections to embedded devices - in this
  case it is an ssh server on a management VLAN in one of several
  network-attached Uninterruptable Power Supplies that cannot be
  upgraded, and only support Protocol 1.

  According to the 16.04 Release Notes protocol 1 requires the openssh-
  client-ssh1 package with the ssh1 binary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1574415/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1039470] Re: 'man sftp' shows a wrong creation date

[Colin Watson]

This was in fact fixed in groff 1.22.3, which is in Ubuntu 15.04 and
newer:

  https://savannah.gnu.org/bugs/?42968
  
http://git.savannah.gnu.org/cgit/groff.git/commit/?id=19f60d9e88208633350987f148396fe1376b76bf

** Bug watch added: GNU Savannah Bug Tracker #42968
   http://savannah.gnu.org/bugs/?42968

** Package changed: openssh (Ubuntu) => groff (Ubuntu)

** Changed in: groff (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1039470

Title:
  'man sftp' shows a wrong creation date

Status in groff package in Ubuntu:
  Fix Released

Bug description:
  'man sftp' shows in the last row "August 21, 2012".
  I expect that 'man sftp' will show the creation date of this manual page and 
not the current date.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: openssh-client 1:5.9p1-5ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Tue Aug 21 07:36:55 2012
  InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 
(20110426)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  2.7.1-1
   ssh-askpass-gnome 1:5.9p1-5ubuntu1
  SSHClientVersion: OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
  SourcePackage: openssh
  UpgradeStatus: Upgraded to precise on 2012-05-15 (97 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1039470/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1389167] Re: HostbasedAuthentication produces spurious warnings

[Colin Watson]

This was fixed upstream in OpenSSH 6.8, which is in Ubuntu 15.10 and
newer:

https://anongit.mindrot.org/openssh.git/commit/?id=1195f4cb07ef4b0405c839293c38600b3e9bdb46

** Changed in: openssh (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1389167

Title:
  HostbasedAuthentication produces spurious warnings

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 14.04.1 LTS
  openssh-client 1:6.6p1-2ubuntu2

  We have HostbasedAuthentication set up in our environment so that
  users can ssh between equivalent hosts without a password.

  ssh_config contains (relevantly)

  HostbasedAuthentication yes
  PreferredAuthentications publickey,hostbased,password,keyboard-interactive
  EnableSSHKeysign yes

  sshd_config contains (relevantly)

  HostbasedAuthentication yes

  This works:

  ocelot:~$ ssh othermc
  othermc:~$

  However, ssh-ing as an alternative user produces additional warning
  messages before the expected password prompt:

  ocelot:~$ ssh otheruser@othermc
  no matching hostkey found
  ssh_keysign: no reply
  key_sign failed
  otheruser@othermc's password:

  If instead of relying on EnableSSHKeysign in ssh_config I make the ssh
  binary setuid:

  chmod u+s /usr/bin/ssh

  ...the extra warnings go away and I get what I expect:

  ocelot:~$ ssh otheruser@othermc
  otheruser@othermc's password:

  This makes me suspect that there may be a problem with ssh-keysign.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1389167/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656557] Re: sshd boolean option parsing is excessively case-sensitive

[Colin Watson]

** Changed in: openssh (Ubuntu)
   Status: New => Triaged

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1656557

Title:
  sshd boolean option parsing is excessively case-sensitive

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged

Bug description:
  
  Dear People,

  The field 'PasswordAuthentication' unlike all the others requires no
  capitalization in order for the ssh daemon to start properly!

  While this works:

  PasswordAuthentication yes

  
  The following doesn't work for this field (though works for other fields):

  PasswordAuthentication Yes

  This is most likely an issue to bring up to upstream project. Could we
  have a fix so that configuration can be done in a consistent way and
  the daemon doesn't break because of capitalization of a given
  parameter (it works on the other fields using [Yy] or [Nn]).

  This is a reality in 14.04 and 16.04.

  Thanks for your time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1656557/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656557] Re: sshd_config issue crashes sshd daemon

[Colin Watson]

This is true of all the purely yes/no flags; I agree that there are some
multi-state options that behave differently.

I've raised this upstream, and linked the bug here.  Thanks for your
report.  I should warn you in advance that a backport to 14.04/16.04 is
rather unlikely, but if fixed upstream then it'll make its way into
later Ubuntu releases.

** Bug watch added: OpenSSH Portable Bugzilla #2664
   https://bugzilla.mindrot.org/show_bug.cgi?id=2664

** Also affects: openssh via
   https://bugzilla.mindrot.org/show_bug.cgi?id=2664
   Importance: Unknown
   Status: Unknown

** Summary changed:

- sshd_config issue crashes sshd daemon
+ sshd boolean option parsing is excessively case-sensitive

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1656557

Title:
  sshd boolean option parsing is excessively case-sensitive

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged

Bug description:
  
  Dear People,

  The field 'PasswordAuthentication' unlike all the others requires no
  capitalization in order for the ssh daemon to start properly!

  While this works:

  PasswordAuthentication yes

  
  The following doesn't work for this field (though works for other fields):

  PasswordAuthentication Yes

  This is most likely an issue to bring up to upstream project. Could we
  have a fix so that configuration can be done in a consistent way and
  the daemon doesn't break because of capitalization of a given
  parameter (it works on the other fields using [Yy] or [Nn]).

  This is a reality in 14.04 and 16.04.

  Thanks for your time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1656557/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1451808] Re: apport-collect error: No module named PyQt5.QtCore

[Sergio Callegari]

Yes, but shouldn't this be a dependency of python-apport?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1451808

Title:
  apport-collect error: No module named PyQt5.QtCore

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  In kubuntu vivid, apport reacts as follows:

  apport-collect 1451277
  ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  5 14:35:33 2015
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1451808/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656599] [NEW] Package sane-backends not installed and no hook available, ignoring

[Christopher M. Penalver]

Public bug reported:

What happens is that when folks run apport-collect against a report with 
sane-backends, this fails as per below:
apport-collect 1643544
Package sane-backends not installed and no hook available, ignoring

This is despite folks having the constituent packages of sane-backends
installed.

Example bug report:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1643544

While this isn't a show stopper, it would be nice if this was resolved
to prevent problems of problems, and avoid confusing folks.

** Affects: apport (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: yakkety zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1656599

Title:
  Package sane-backends not installed and no hook available, ignoring

Status in apport package in Ubuntu:
  Triaged

Bug description:
  What happens is that when folks run apport-collect against a report with 
sane-backends, this fails as per below:
  apport-collect 1643544
  Package sane-backends not installed and no hook available, ignoring

  This is despite folks having the constituent packages of sane-backends
  installed.

  Example bug report:
  https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1643544

  While this isn't a show stopper, it would be nice if this was resolved
  to prevent problems of problems, and avoid confusing folks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1656599/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1572807] Re: /bin/nano:*** Error in `nano': double free or corruption (!prev): ADDR ***

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nano (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/1572807

Title:
  /bin/nano:*** Error in `nano': double free or corruption (!prev): ADDR
  ***

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nano.  This problem was most recently seen with version
  2.5.3-2, the problem page at
  https://errors.ubuntu.com/problem/7dd7f74a72fca06513544d8af66b623efa15b26c
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1572807/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Éric Piel]

As a side-note, as it seems it's been triggered for my laptop by the update to 
network-manger 1.2.4, one of the few fixes included in 1.2.6 is the following:
* Fixed a bug that caused devices to stay unmanaged after resume from sleep.

So quite probably, updating network-manager to the latest stable version
will help

-- 
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/1585863

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Éric Piel]

One more thing: contrarily to the title of this bug report, here "sudo
wpa_cli scan" doesn't help to get the list of network again. However,
"sudo wpa_cli resume" works.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585863

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1547647] Re: [SRU] please remove libqt5webkit dependency

[Amr Ibrahim]

Ping!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1547647

Title:
  [SRU] please remove libqt5webkit dependency

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  In Progress
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  This is an SRU request, based on the process documented at
  https://wiki.ubuntu.com/StableReleaseUpdates

  
  [Impact]

   * When declaring online accounts for use by Ubuntu, the system uses a
  webview to authenticate to online services like Facebook or Google.

   * On X11 desktops, that webview currently uses an old qt5webkit
  component that is now unmaintained

   * Backporting this fix will simplify the maintenance work, by
  removing the need for that old component, and will improve the
  coherence of the system by using a supported Oxide webview

  [Test Case]

  To verify the change:

   * Go to system settings > Online Accounts
   * Add account of type Google, Facebook or Twitter (which uses webview for 
authentication)
   * Verify that a webview opens to log onto the online service
   * Verify that the account is listed in the account list at the end of this 
process
   * Verify that the related apps and services can use the online account as 
before (ie Shotwell photo uploads, Photos scope, etc.)

  [Regression Potential]

   * On architectures not supported by Oxide, namely ppc64el and s390x,
  the change will trigger a runtime error when trying to use that part
  of signon-ui.

   * The problem affects users of Ubuntu desktop systems based on X11.
  The change is already in effect on Unity8/Mir devices for a few
  months.

  [Other Info]

   * signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11)
  depends on libqt5webkit5

   * See also: https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-
  security-updates/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1547647/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Éric Piel]

Same as comment #52 and #53, while it used to be just once in a while,
since a few weeks, it's now _every_ single time that my laptop resumes.

There are many similar bugs but with probably different causes. So to be
clear here is the symptoms I see much more recently since a few weeks
(on 16.04): after resume, only a couple of wifi networks will be listed
at most, and never the one I use.

This workaround does work (to get nm-applet list all the networks again):
sudo service network-manager restart

These things do _not_ work:
 * restarting nm-applet
 * disabling/enabling the wifi from the hardware key
 * trying to unblock the wifi in software (via rfkill), it's not even marked as 
disabled anyway.

-- 
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/1585863

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected

[Christopher M. Penalver]

Mauricio Maluff Masi:

>" The label is pretty faded, so I'm not positive on this. But I think
it's: Make: DisplayLink Model: E364109"

AFAIK, DisplayLink doesn't sell adapters as a manufacturer. Other
hardware manufacturers integrate DisplayLink technology in their
products and then brand it differently. Hence, the device you have
wouldn't have DisplayLink as either the manufacturer or the make.

Also, I wasn't able to find any device from any manufacturer with model
E364109. Would this device have any other sticker, markings, or logos?
Would you have a receipt for this device to reference?

Also, have you tried testing earlier versions of the DisplayLink driver
to see if this is a regression of it via
http://www.displaylink.com/downloads/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/1655828

Title:
  Mouse flickers and disappears on primary monitor when additional
  monitor is connected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Any time I connect my Acer G236HL LCD monitor with VGA via my
  Displaylink adapter (DisplayLink driver version 1.2.65), the mouse
  flickers and disappears in the primary monitor. It displays perfectly
  on the additional monitor. It also displays perfectly after the
  additional monitor is disconnected.

  I see that there are a number of similar bug reports:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001

  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
  NonfreeKernelModules: wl
  .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
  CurrentDesktop: Unity
  Date: Tue Jan 10 22:34:58 2017
  DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could 
not locate dkms.conf file.
   File:  does not exist.

   bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2016-01-26 (350 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=485e1110-0879-413f-b537-6b5b97353478 ro quiet splash 
usbcore.autosuspend=-1 "acpi_osi=Windows 2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (79 days ago)
  XorgLogOld:

  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell 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: Tue Jan 10 20:18:19 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   

[Touch-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Dirk F]

Christian, thanks for looking at this.

I'd definitely encourage someone with a relevant Debian installation to
reportbug this, and indeed any of the bugs that I've reported in pm-
utils but remain ignored upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1548486

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656504] Re: Permission denied when running apport-collect

[Christopher M. Penalver]

nico, thank you for reporting this and helping make Ubuntu better.

To advise, you shouldn't be running apport-collect to a report on
Launchpad you aren't the original reporter of. Launchpad typically
blocks this type of action, so this may be intended behavior.

Despite this, can you please advise what happens when you run:
ubuntu-bug linux

** Changed in: apport (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1656504

Title:
  Permission denied when running apport-collect

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  I tried several times to launch apport-collect 1651520 but it failed
  everytime:

  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=Xp4CFWJ01GvW7QPhMfq8_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Waiting to hear from Launchpad about your decision...
  ERROR: connecting to Launchpad failed: [Errno 13] Permission denied: 
'/home/nicolas/.cache/apport/launchpad.credentials'
  You can reset the credentials by removing the file 
"/home/nicolas/.cache/apport/launchpad.credentials"

  I've tried successively to "Allow nicolas-MS-7808 to access my
  Launchpad account:" "for an hour", "for a week", "until I disable it",
  apport-collect failed everytime with the same message.

  Note that running:
  rm /home/nicolas/.cache/apport/launchpad.credentials
  return:
  rm: impossible de supprimer 
'/home/nicolas/.cache/apport/launchpad.credentials': Aucun fichier ou dossier 
de ce type

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 14 08:53:31 2017
  InstallationDate: Installed on 2014-06-14 (945 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to xenial on 2016-08-25 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1656504/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645232] Re: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL)

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-mke2fs-handle-ACL-in-xattrs-correctly.patch" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1645232

Title:
  e2fsprogs - could not preserve ACL permissions  : The getxattr()
  returns with (EINVAL)

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  The original installed e2fsprogs did not support mke2fs -d /directory
  " option . So ,  git cloned from e2fsprogs packages from repository
  and installed it and followed below steps to reproduce this :

  1. set the ACL rules as below to one of the binary :

  $ setfacl -m u:vipatil:r-- rootfs/usr/bin/helloworld
  $ getfacl rootfs/usr/bin/helloworld
  # file: rootfs/usr/bin/helloworld
  # owner: shkumar
  # group: hardev
  user::rwx
  user:vipatil:r--
  group::---
  mask::r--
  other::---

  2. $ dd if=/dev/zero of=test.ext4 bs=1M count=60

  3. $ mke2fs -t ext4 test.ext4 -d rootfs/
  mke2fs 1.43.3 (04-Sep-2016)
  Discarding device blocks: done
  Creating filesystem with 61440 1k blocks and 15360 inodes
  Filesystem UUID: 495713b3-5f1f-427a-8359-a736dfb2ece9
  Superblock backups stored on blocks:
  8193, 24577, 40961, 57345

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (4096 blocks): done
  Copying files into the device: done
  Writing superblocks and filesystem accounting information: done

  4. sudo mount -o loop,acl,user_xattr,rw,sync test.ext4 mountpoint

  5.@/mountpoint$ getfacl usr/bin/helloworld
  getfacl: usr/bin/helloworld: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1645232/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[laurent]

I am also interested in any news about the sound.

-- 
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/1563110

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1451808] Re: apport-collect error: No module named PyQt5.QtCore

[Ray-Ven]

sudo apt-get install python-pyqt5

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1451808

Title:
  apport-collect error: No module named PyQt5.QtCore

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  In kubuntu vivid, apport reacts as follows:

  apport-collect 1451277
  ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  5 14:35:33 2015
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1451808/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638909] Re: Calc : /build/glib2.0-D_MnHF/glib2.0-2.50.1/./gobject/gsignal.c:3492: signal name 'selection_changed' is invalid for instance '0x564cca142c50' of type 'OOoAtkObjComp

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libreoffice (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1638909

Title:
  Calc :  /build/glib2.0-D_MnHF/glib2.0-2.50.1/./gobject/gsignal.c:3492:
  signal name 'selection_changed' is invalid for instance
  '0x564cca142c50' of type 'OOoAtkObjCompTxt'

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Often get such problem when using calc, either the 5.2.2 or 5.2.3 version, 
mainly when i click on the top right arrow to expand the formula bar.
  This is not happening every time but quite half time. Looks like glib2.0 is 
linked with the issue: first the app freeze due to the click failure, the cpu 
goes to 100% for a while; at that point, either it finally succeed to expand 
the formula bar or it crash.

  soffice.bin[29680]: 
/build/glib2.0-D_MnHF/glib2.0-2.50.1/./gobject/gsignal.c:3492: signal name 
'selection_changed' is invalid for instance '0x564cca142c50' of type 
'OOoAtkObjCompTxt'
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: libreoffice 1:5.2.3~rc2-0ubuntu1~yakkety1 [origin: 
LP-PPA-libreoffice-libreoffice-5-2]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags: zesty third-party-packages
  Uname: Linux 4.8.0-27-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638909/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638909] Re: Calc : /build/glib2.0-D_MnHF/glib2.0-2.50.1/./gobject/gsignal.c:3492: signal name 'selection_changed' is invalid for instance '0x564cca142c50' of type 'OOoAtkObjComp

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1638909

Title:
  Calc :  /build/glib2.0-D_MnHF/glib2.0-2.50.1/./gobject/gsignal.c:3492:
  signal name 'selection_changed' is invalid for instance
  '0x564cca142c50' of type 'OOoAtkObjCompTxt'

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Often get such problem when using calc, either the 5.2.2 or 5.2.3 version, 
mainly when i click on the top right arrow to expand the formula bar.
  This is not happening every time but quite half time. Looks like glib2.0 is 
linked with the issue: first the app freeze due to the click failure, the cpu 
goes to 100% for a while; at that point, either it finally succeed to expand 
the formula bar or it crash.

  soffice.bin[29680]: 
/build/glib2.0-D_MnHF/glib2.0-2.50.1/./gobject/gsignal.c:3492: signal name 
'selection_changed' is invalid for instance '0x564cca142c50' of type 
'OOoAtkObjCompTxt'
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: libreoffice 1:5.2.3~rc2-0ubuntu1~yakkety1 [origin: 
LP-PPA-libreoffice-libreoffice-5-2]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags: zesty third-party-packages
  Uname: Linux 4.8.0-27-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638909/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645232] Re: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL)

[Sojan James]

Hello,

I have a fix for this and the patch is attached. I couldn't find the
right mailing list for e2fsprogs. Until I find that, this is a good
place to upload the patch.

mke2fs was copying the ACL in the POSIX extended attribute format. The
attached patch converts it to for format expected by the file-system.

Regards,
Sojan

** Patch added: "0001-mke2fs-handle-ACL-in-xattrs-correctly.patch"
   
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1645232/+attachment/4804387/+files/0001-mke2fs-handle-ACL-in-xattrs-correctly.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1645232

Title:
  e2fsprogs - could not preserve ACL permissions  : The getxattr()
  returns with (EINVAL)

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  The original installed e2fsprogs did not support mke2fs -d /directory
  " option . So ,  git cloned from e2fsprogs packages from repository
  and installed it and followed below steps to reproduce this :

  1. set the ACL rules as below to one of the binary :

  $ setfacl -m u:vipatil:r-- rootfs/usr/bin/helloworld
  $ getfacl rootfs/usr/bin/helloworld
  # file: rootfs/usr/bin/helloworld
  # owner: shkumar
  # group: hardev
  user::rwx
  user:vipatil:r--
  group::---
  mask::r--
  other::---

  2. $ dd if=/dev/zero of=test.ext4 bs=1M count=60

  3. $ mke2fs -t ext4 test.ext4 -d rootfs/
  mke2fs 1.43.3 (04-Sep-2016)
  Discarding device blocks: done
  Creating filesystem with 61440 1k blocks and 15360 inodes
  Filesystem UUID: 495713b3-5f1f-427a-8359-a736dfb2ece9
  Superblock backups stored on blocks:
  8193, 24577, 40961, 57345

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (4096 blocks): done
  Copying files into the device: done
  Writing superblocks and filesystem accounting information: done

  4. sudo mount -o loop,acl,user_xattr,rw,sync test.ext4 mountpoint

  5.@/mountpoint$ getfacl usr/bin/helloworld
  getfacl: usr/bin/helloworld: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1645232/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1397663] Re: sudo does not properly initialize libgcrypt

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 869166 ***
https://bugs.launchpad.net/bugs/869166

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: sudo (Ubuntu)
   Status: New => Confirmed

-- 
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/1397663

Title:
  sudo does not properly initialize libgcrypt

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  The following warnings can be found in syslog:

  pieter-local@test-02:~$ grep "please fix the application" /var/log/syslog 
|grep sudo
  Nov 30 12:20:20 test-02 sudo: Libgcrypt warning: missing initialization - 
please fix the application
  Nov 30 12:25:15 test-02 sudo: Libgcrypt warning: missing initialization - 
please fix the application
  Nov 30 12:46:27 test-02 sudo: Libgcrypt warning: missing initialization - 
please fix the application
  Nov 30 13:15:02 test-02 sudo: Libgcrypt warning: missing initialization - 
please fix the application
  Nov 30 13:16:57 test-02 sudo: Libgcrypt warning: missing initialization - 
please fix the application

  These seem to be related to the following change:

  http://git.gnupg.org/cgi-
  
bin/gitweb.cgi?p=libgcrypt.git;a=commitdiff_plain;h=7627f9646701e88c827bbadd1231221d5f0c89a6

  It looks like that sudo does not properly initialize libgcrypt. From
  looking at the above patch, it does not seem to do any harm, since the
  lib will then initialize itself. When trying to find issues on a
  system, warnings like this will make things a bit more cloudy then
  needed. A proper implementation for this would be beneficial to the
  system in general.

  These warnings are present in 14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1397663/+subscriptions

-- 
Mailing list: https://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 1656431] Re: Some KDE applications 16.10 FTbFS with Qt 5.7.1 on arm64 and ppc64el

[Rik Mills]

On 14/01/17 17:32, Timo Jyrinki wrote:
> Let's tackle this as soon as the first transition is over so that we
> don't relaunch the currently passed autopkgtests.
> 
> Meanwhile there have been two binutils uploads too, and once
> https://launchpad.net/ubuntu/+source/binutils/2.27.90.20170114-1ubuntu1
> is in release pocket this would be worth retrying.

Well, I am ppa building against proposed, as this is staging for archive
uploads, and this still fails with that in place.

Yes, I was just recording this with the bug. Definitely one to tackle
once Qt has migrated the 1st time.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1656431

Title:
  Some KDE applications 16.10 FTbFS with Qt 5.7.1 on arm64 and ppc64el

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  libkf5kipi https://userbase.kde.org/KIPI
  parley
  kidentitymanagement
  libkeduvocdocument

  FTBFS with errors similar to the one shown at the bottom of this

  As is the case with LP Bug #1654820, it seems likely that

  kmail
  kdepim-addons

  would also fail in the same fashion, but the build depends are not yet
  in place to confirm that absolutely.

  Again, this seems to be a case of qtbase using the gold linker, and I
  would surmise that as with amd64 etc, setting no gold linker for
  arm64 and ppc64el would resolve this.

  no gold linker is already set in qtbase for amd64, i386, powerpc &
  armhf.

  
  --- log extract --

  [ 56%] Linking CXX executable plaintexteditortest
  cd 
/<>/obj-aarch64-linux-gnu/src/texteditor/plaintexteditor/autotests 
&& /usr/bin/cmake -E cmake_link_script 
CMakeFiles/plaintexteditortest.dir/link.txt --verbose=1
  /usr/bin/c++   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-exceptions 
-Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -pedantic  -Wl,--enable-new-dtags -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/plaintexteditortest.dir/plaintexteditortest.cpp.o 
CMakeFiles/plaintexteditortest.dir/plaintexteditortest_automoc.cpp.o  -o 
plaintexteditortest -Wl,-rpath,/<>/obj-aarch64-linux-gnu/src 
-rdynamic ../../../libKF5PimTextEdit.so.5.4.0.abi1 
/usr/lib/aarch64-linux-gnu/libQt5Test.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1 
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_edata'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `__bss_start'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_end'
  collect2: error: ld returned 1 exit status
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_edata'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `__bss_start'
  

[Touch-packages] [Bug 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

[John Rodriguez]

Have not updated Ubuntu 12.04 since 12-24-16.  Has the bug been fixed?
If I upgrade to 14.04 will I encounter the same problem?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1643467

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/libav/+bug/1643467/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638909] Re: Calc : /build/glib2.0-D_MnHF/glib2.0-2.50.1/./gobject/gsignal.c:3492: signal name 'selection_changed' is invalid for instance '0x564cca142c50' of type 'OOoAtkObjComp

[Julien]

Same type of message with Writer "LibreOffice 5.1.4.2 10m0(Build:2)" under 
Ubuntu 16.04 LTS :
(soffice:14460): GLib-GObject-WARNING **: 
/build/glib2.0-prJhLS/glib2.0-2.48.2/./gobject/gsignal.c:3486: signal name 
'selection_changed' is invalid for instance '0x1ced110' of type 
'OOoAtkObjCompTxt'

Window become randomly (?) gray and crash with this message.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1638909

Title:
  Calc :  /build/glib2.0-D_MnHF/glib2.0-2.50.1/./gobject/gsignal.c:3492:
  signal name 'selection_changed' is invalid for instance
  '0x564cca142c50' of type 'OOoAtkObjCompTxt'

Status in glib2.0 package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New

Bug description:
  Often get such problem when using calc, either the 5.2.2 or 5.2.3 version, 
mainly when i click on the top right arrow to expand the formula bar.
  This is not happening every time but quite half time. Looks like glib2.0 is 
linked with the issue: first the app freeze due to the click failure, the cpu 
goes to 100% for a while; at that point, either it finally succeed to expand 
the formula bar or it crash.

  soffice.bin[29680]: 
/build/glib2.0-D_MnHF/glib2.0-2.50.1/./gobject/gsignal.c:3492: signal name 
'selection_changed' is invalid for instance '0x564cca142c50' of type 
'OOoAtkObjCompTxt'
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: libreoffice 1:5.2.3~rc2-0ubuntu1~yakkety1 [origin: 
LP-PPA-libreoffice-libreoffice-5-2]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags: zesty third-party-packages
  Uname: Linux 4.8.0-27-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638909/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656431] Re: Some KDE applications 16.10 FTbFS with Qt 5.7.1 on arm64 and ppc64el

[Timo Jyrinki]

Let's tackle this as soon as the first transition is over so that we
don't relaunch the currently passed autopkgtests.

Meanwhile there have been two binutils uploads too, and once
https://launchpad.net/ubuntu/+source/binutils/2.27.90.20170114-1ubuntu1
is in release pocket this would be worth retrying.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1656431

Title:
  Some KDE applications 16.10 FTbFS with Qt 5.7.1 on arm64 and ppc64el

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  libkf5kipi https://userbase.kde.org/KIPI
  parley
  kidentitymanagement
  libkeduvocdocument

  FTBFS with errors similar to the one shown at the bottom of this

  As is the case with LP Bug #1654820, it seems likely that

  kmail
  kdepim-addons

  would also fail in the same fashion, but the build depends are not yet
  in place to confirm that absolutely.

  Again, this seems to be a case of qtbase using the gold linker, and I
  would surmise that as with amd64 etc, setting no gold linker for
  arm64 and ppc64el would resolve this.

  no gold linker is already set in qtbase for amd64, i386, powerpc &
  armhf.

  
  --- log extract --

  [ 56%] Linking CXX executable plaintexteditortest
  cd 
/<>/obj-aarch64-linux-gnu/src/texteditor/plaintexteditor/autotests 
&& /usr/bin/cmake -E cmake_link_script 
CMakeFiles/plaintexteditortest.dir/link.txt --verbose=1
  /usr/bin/c++   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-exceptions 
-Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -pedantic  -Wl,--enable-new-dtags -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/plaintexteditortest.dir/plaintexteditortest.cpp.o 
CMakeFiles/plaintexteditortest.dir/plaintexteditortest_automoc.cpp.o  -o 
plaintexteditortest -Wl,-rpath,/<>/obj-aarch64-linux-gnu/src 
-rdynamic ../../../libKF5PimTextEdit.so.5.4.0.abi1 
/usr/lib/aarch64-linux-gnu/libQt5Test.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1 
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_edata'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `__bss_start'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_end'
  collect2: error: ld returned 1 exit status
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `__bss_start'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_edata'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  /usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple 
definition of `_end'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_edata'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `__bss_start'
  //usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple 
definition of `_end'
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1656431/+subscriptions

-- 

[Touch-packages] [Bug 1656557] [NEW] sshd_config issue crashes sshd daemon

[nmarques]

Public bug reported:


Dear People,

The field 'PasswordAuthentication' unlike all the others requires no
capitalization in order for the ssh daemon to start properly!

While this works:

PasswordAuthentication yes


The following doesn't work for this field (though works for other fields):

PasswordAuthentication Yes

This is most likely an issue to bring up to upstream project. Could we
have a fix so that configuration can be done in a consistent way and the
daemon doesn't break because of capitalization of a given parameter (it
works on the other fields using [Yy] or [Nn]).

This is a reality in 14.04 and 16.04.

Thanks for your time.

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1656557

Title:
  sshd_config issue crashes sshd daemon

Status in openssh package in Ubuntu:
  New

Bug description:
  
  Dear People,

  The field 'PasswordAuthentication' unlike all the others requires no
  capitalization in order for the ssh daemon to start properly!

  While this works:

  PasswordAuthentication yes

  
  The following doesn't work for this field (though works for other fields):

  PasswordAuthentication Yes

  This is most likely an issue to bring up to upstream project. Could we
  have a fix so that configuration can be done in a consistent way and
  the daemon doesn't break because of capitalization of a given
  parameter (it works on the other fields using [Yy] or [Nn]).

  This is a reality in 14.04 and 16.04.

  Thanks for your time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1656557/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1574347] Re: WiFi networks list disappears (device type not reloaded)

[stavros daliakopoulos]

The "HOW TO TEST A FIX" is meaningless.

nmcli dev

DEVICE  TYPE  STATECONNECTION  
wlp2s0  wifi  connectedThomson_etc 


but the applet still doesn't list any wireless network.

-- 
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/1574347

Title:
  WiFi networks list disappears (device type not reloaded)

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  
   WARNING 
  
  If you are still experiencing this bug please don't comment here, but look at 
these: (https://goo.gl/LdPpYG)

  **
   HOW TO REPRODUCE
  **
  Boot the system.

  
   RESULT
  
  From time to time, some of these happen:
  - The applet doesn't list any wireless network.
  - The applet doesn't show the name of the current network.
  - The icon shows the wired connection symbol, instead of the wifi one.

  *
   WORK AROUND
  *
  (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)

  *
   FIX
  *
  The applet needs to re-read the DEVTYPE after the device name changed.

  ***
   HOW TO TEST A FIX
  ***
  In the Terminal application enter:
  nmcli dev

  If it works, in the line for the wireless device, the TYPE column
  should be "wifi". If it doesn't it will be "ethernet".

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

[Alberto Salvia Novella]

Please:

1. In the Terminal application enter "sudo apt purge dnsmasq".
2. Reboot the system.
3. If that fixes this bug, please mark it as duplicate of bug #1534501.

Thank you.

-- 
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/1434986

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  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/network-manager/+bug/1434986/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1589005] Re: After update DNS work unstable

[Alberto Salvia Novella]

Please:

1. In the Terminal application enter "sudo apt purge dnsmasq".
2. Reboot the system.
3. If that fixes this bug, please mark it as duplicate of bug #1534501.

Thank you.

-- 
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/1589005

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   lo  loopback  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/1589005/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1594715] Re: wifi does not work roughly half of the times

[Alberto Salvia Novella]

Please:

1. In the Terminal application enter "sudo apt purge dnsmasq".
2. Reboot the system.
3. If that fixes this bug, please mark it as duplicate of bug #1534501.

Thank you.

-- 
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/1594715

Title:
  wifi does not work roughly half of the times

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After booting, roughly half of the times, wifi doesn't work: The nm-
  applet menu looks as if no wifi would exist. Instead, it lists the a
  non-existing cable network device called "Marvell 88W8897 [AVASTAR]
  802.11ac Wireless". (The network manager seems to be trying to connect
  to that device, but fails.)

  After doing
/etc/init.d/network-manager restart
  the wifi device is always recognized properly, so I guess it's something 
happening in the wrong order during booting. (Alternatively, unloading and 
reloading the kernel module mwifiex_pcie also always helps.)

  The problem did not exist in ubuntu 15.10.

  
  Some more information:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04


  When the bug is there:

  $ nmcli d show wlp1s0
  GENERAL.DEVICE: wlp1s0
  GENERAL.TYPE:   ethernet
  GENERAL.HWADDR: 50:1A:C5:E8:2F:09
  GENERAL.MTU:1500
  GENERAL.STATE:  70 (connecting (getting IP 
configuration))
  GENERAL.CONNECTION: Kabelnetzwerkverbindung 2
  GENERAL.CON-PATH:   
/org/freedesktop/NetworkManager/ActiveConnection/7
  WIRED-PROPERTIES.CARRIER:   on

  $ ifconfig -a
  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:3380 errors:0 dropped:0 overruns:0 frame:0
TX packets:3380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1 
RX bytes:251184 (251.1 KB)  TX bytes:251184 (251.1 KB)

  wlp1s0Link encap:Ethernet  HWaddr 50:1a:c5:e8:2f:09  
UP BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  
  After restarting the network manager:

  immi@flunder:~$ nmcli d show wlp1s0
  GENERAL.DEVICE: wlp1s0
  GENERAL.TYPE:   wifi
  GENERAL.HWADDR: 50:1A:C5:E8:2F:09
  GENERAL.MTU:0
  GENERAL.STATE:  100 (connected)
  GENERAL.CONNECTION: virginmedia4709476
  GENERAL.CON-PATH:   
/org/freedesktop/NetworkManager/ActiveConnection/8
  IP4.ADDRESS[1]: 192.168.0.3/24
  IP4.GATEWAY:192.168.0.1
  IP4.ROUTE[1]:   dst = 169.254.0.0/16, nh = 0.0.0.0, 
mt = 1000
  IP4.DNS[1]: 194.168.4.100
  IP4.DNS[2]: 194.168.8.100
  IP6.ADDRESS[1]: fe80::521a:c5ff:fee8:2f09/64
  IP6.GATEWAY:

  (...)

  wlp1s0Link encap:Ethernet  HWaddr 50:1a:c5:e8:2f:09  
inet6 addr: fe80::521a:c5ff:fee8:2f09/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:304 (304.0 B)  TX bytes:680 (680.0 B)

  
  $ dmesg
  (...)
  [7.850180] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.850263] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.859773] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.869408] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  (...)

  
  I'm happy to try to fix the bug myself, but I could need some help: I don't 
know how to change booting order or something like that.

  I could also temporarily insert some commands into /etc/init.d
  /network-manager printing some status information about the wifi, but
  I don't know how to get such status information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 21 09:35:14 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 

[Touch-packages] [Bug 1656553] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Rafal Idzikowski]

Public bug reported:

Error during partial update from 16.04 LTS to 16.10.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: gconf2 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic i686
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
Date: Sat Jan 14 15:46:26 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2016-12-14 (31 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.3
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gconf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1656553

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Error during partial update from 16.04 LTS to 16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  Date: Sat Jan 14 15:46:26 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-12-14 (31 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1656553/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1574347] Re: WiFi networks list disappears (device type not reloaded)

[Alberto Salvia Novella]

** Summary changed:

- WiFi networks list disappears
+ WiFi networks list disappears (device type not reloaded)

** Description changed:

  
   WARNING 
  
- If you are still experiencing this bug please don't comment here, but create 
a new report: (https://goo.gl/teQ0XV)
+ If you are still experiencing this bug please don't comment here, but look at 
these: (https://goo.gl/LdPpYG)
  
  **
-  HOW TO REPRODUCE 
+  HOW TO REPRODUCE
  **
  Boot the system.
  
  
-  RESULT 
+  RESULT
  
  From time to time, some of these happen:
  - The applet doesn't list any wireless network.
  - The applet doesn't show the name of the current network.
  - The icon shows the wired connection symbol, instead of the wifi one.
  
  *
-  WORK AROUND 
+  WORK AROUND
  *
  (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)
  
  *
-  FIX 
+  FIX
  *
  The applet needs to re-read the DEVTYPE after the device name changed.
  
  ***
-  HOW TO TEST A FIX 
+  HOW TO TEST A FIX
  ***
  In the Terminal application enter:
  nmcli dev
  
  If it works, in the line for the wireless device, the TYPE column should
  be "wifi". If it doesn't it will be "ethernet".

-- 
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/1574347

Title:
  WiFi networks list disappears (device type not reloaded)

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  
   WARNING 
  
  If you are still experiencing this bug please don't comment here, but look at 
these: (https://goo.gl/LdPpYG)

  **
   HOW TO REPRODUCE
  **
  Boot the system.

  
   RESULT
  
  From time to time, some of these happen:
  - The applet doesn't list any wireless network.
  - The applet doesn't show the name of the current network.
  - The icon shows the wired connection symbol, instead of the wifi one.

  *
   WORK AROUND
  *
  (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)

  *
   FIX
  *
  The applet needs to re-read the DEVTYPE after the device name changed.

  ***
   HOW TO TEST A FIX
  ***
  In the Terminal application enter:
  nmcli dev

  If it works, in the line for the wireless device, the TYPE column
  should be "wifi". If it doesn't it will be "ethernet".

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

[Alberto Salvia Novella]

** Description changed:

  
   WARNING 
  
  If you are still experiencing this bug please don't comment here, but create 
a new report: (https://goo.gl/teQ0XV)
  
- [Impact]
- NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet
+ **
+  HOW TO REPRODUCE 
+ **
+ Boot the system.
  
- [Testcase]
- 1. Boot the system. It should include a wireless device.
- 2. In a terminal, run 'nmcli dev'.
- 3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".
+ 
+  RESULT 
+ 
+ From time to time, some of these happen:
+ - The applet doesn't list any wireless network.
+ - The applet doesn't show the name of the current network.
+ - The icon shows the wired connection symbol, instead of the wifi one.
  
- After upgrading to the new version, the repeating the above steps should
- give expected behavior.
+ *
+  WORK AROUND 
+ *
+ (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)
  
- [Regression Potential]
- Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.
+ *
+  FIX 
+ *
+ The applet needs to re-read the DEVTYPE after the device name changed.
  
- ---
+ ***
+  HOW TO TEST A FIX 
+ ***
+ In the Terminal application enter:
+ nmcli dev
  
- Problems:-
- 
- 1. The network manager applet does not show the list of WiFI APs it can find.
- 2. The network manager applet does not the name of the AP to which it is 
connected
- 3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.
- 
- Temporary Workaround:-
- Log out and again log back in.
+ If it works, in the line for the wireless device, the TYPE column should
+ be "wifi". If it doesn't it will be "ethernet".

** Summary changed:

- [SRU] Re-read the link type if the name changed
+ WiFi network list disappears

** Summary changed:

- WiFi network list disappears
+ WiFi networks list disappears

-- 
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/1574347

Title:
  WiFi networks list disappears (device type not reloaded)

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  
   WARNING 
  
  If you are still experiencing this bug please don't comment here, but create 
a new report: (https://goo.gl/teQ0XV)

  **
   HOW TO REPRODUCE 
  **
  Boot the system.

  
   RESULT 
  
  From time to time, some of these happen:
  - The applet doesn't list any wireless network.
  - The applet doesn't show the name of the current network.
  - The icon shows the wired connection symbol, instead of the wifi one.

  *
   WORK AROUND 
  *
  (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)

  *
   FIX 
  *
  The applet needs to re-read the DEVTYPE after the device name changed.

  ***
   HOW TO TEST A FIX 
  ***
  In the Terminal application enter:
  nmcli dev

  If it works, in the line for the wireless device, the TYPE column
  should be "wifi". If it doesn't it will be "ethernet".

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656551] [NEW] webbrowser only partially loads https sites with self-signed certificate

[Rüdiger Kupper]

Public bug reported:

The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open self-signed 
https-secured sites correctly. The browser presents the option to go back to a 
safe site or continue anyway. If I choose continue anyway, it starts to load 
the site, but never completes. After some time it stops loading and displays a 
rather incomplete version of the site. It is clearly composed of only some of 
the pages' elements and incomplete.The amount of the page that is displayed 
varies from time to time.
It appears that transmission times out while loading the page.
One common usecase of self-signed certificates is webinterfaces of DSL or cable 
routers, such as the popular fritz box.
Test case:
1) Try loading the web interface of my router: https://rkupper.no-ip.org/
   You should see the login page of a fritz box router.
2) Try loading the web interface of my nextcloud 
instance:https://rkupper.no-ip.org:444/
   You should see the login page of nextcloud
Observe that the appearance of the pages varies every time, depending on how 
much of the site was loaded. Observe that pressing the login button does 
nothing – probably because the scripts have not been loaded.
I have tried other self-signed sites, and am confident that it is not a problem 
of my server.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1656551

Title:
  webbrowser only partially loads https sites with self-signed
  certificate

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open self-signed 
https-secured sites correctly. The browser presents the option to go back to a 
safe site or continue anyway. If I choose continue anyway, it starts to load 
the site, but never completes. After some time it stops loading and displays a 
rather incomplete version of the site. It is clearly composed of only some of 
the pages' elements and incomplete.The amount of the page that is displayed 
varies from time to time.
  It appears that transmission times out while loading the page.
  One common usecase of self-signed certificates is webinterfaces of DSL or 
cable routers, such as the popular fritz box.
  Test case:
  1) Try loading the web interface of my router: https://rkupper.no-ip.org/
 You should see the login page of a fritz box router.
  2) Try loading the web interface of my nextcloud 
instance:https://rkupper.no-ip.org:444/
 You should see the login page of nextcloud
  Observe that the appearance of the pages varies every time, depending on how 
much of the site was loaded. Observe that pressing the login button does 
nothing – probably because the scripts have not been loaded.
  I have tried other self-signed sites, and am confident that it is not a 
problem of my server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1656551/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

[taiebot65]

with the silo removed twitter looks like that

** Attachment added: "twitter"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+attachment/4804311/+files/screenshot20170114_170006579.png

-- 
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/1656310

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

[Alberto Salvia Novella]

** Description changed:

+ 
+  WARNING 
+ 
+ If you are still experiencing this bug please don't comment here, but create 
a new report: (https://goo.gl/teQ0XV)
+ 
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet
  
  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".
  
  After upgrading to the new version, the repeating the above steps should
  give expected behavior.
  
  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.
  
  ---
  
  Problems:-
  
  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.
  
  Temporary Workaround:-
  Log out and again log back in.

-- 
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/1574347

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  
   WARNING 
  
  If you are still experiencing this bug please don't comment here, but create 
a new report: (https://goo.gl/teQ0XV)

  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

[taiebot65]

I am on rc proposed with the silo installed and now twitter website
looks like that

** Attachment added: "twitter"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+attachment/4804310/+files/screenshot20170114_145423332.png

-- 
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/1656310

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1326954] Re: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate

[Michael]

This problem is also happening in debian Stretch (using kernel 4.8).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1326954

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Confirmed
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin: 'Generic'
 |   primary port: 'cdc-wdm0'
 |  ports: 'cdc-wdm0 (mbim), wwan0 (net)'
-
Numbers  |   own : 'unknown'

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Juan Hernández]

For me replacing xserver-xorg-input-synaptics with xserver-xorg-input-
libinput made the clickpad (a touchpad without fisical buttons) very
usable and without cursor jumps.

By default libinput enables multitouch gestures for scrolling, 2-finger
clicks (right button) and 3-finger clicks (middle button) but I think
you can adapt the configuration file to enable right button clicks on
the clickpad instead of the 2-finger option.

All I had to do was:
sudo apt-get install xserver-xorg-input-libinput
sudo apt-get remove --purge xserver-xorg-input-synaptics

..and reboot

-- 
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/1574667

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1607666] Re: sudo fails with host netgroup returned from freeipa

[Launchpad Bug Tracker]

This bug was fixed in the package sudo - 1.8.19p1-1ubuntu1

---
sudo (1.8.19p1-1ubuntu1) zesty; urgency=low

  * Merge from Debian unstable. (LP: #1607666)
Remaining changes:
- Use tmpfs location to store timestamp files
  + debian/rules: change --with-rundir to /var/run/sudo
  + debian/rules, debian/sudo.service, debian/sudo.sudo.init: stop
shipping init script and service file, as they are no longer
necessary.
  + debian/*.preinst, debian/*.postinst, debian/*.postrm: remove old
init script with dpkg-maintscript-helper.
  + debian/*.postinst: remove old /var/run/sudo to /var/lib/sudo
transition code, remove old /var/lib/sudo/ts timestamp directory.
- debian/rules:
  + compile with --without-lecture --with-tty-tickets --enable-admin-flag
  + install man/man8/sudo_root.8 in both flavours
  + install apport hooks
- debian/source_sudo.py, debian/sudo-ldap.dirs, debian/sudo.dirs:
  + add usr/share/apport/package-hooks
- debian/sudo.pam:
  + Use pam_env to read /etc/environment and /etc/default/locale
environment files. Reading ~/.pam_environment is not permitted due to
security reasons.
- debian/sudoers:
  + also grant admin group sudo access
  + include /snap/bin in the secure_path
- debian/control, debian/rules:
  + use dh-autoreconf
- Remaining patches:
  + keep_home_by_default.patch: Keep HOME in the default environment
- Dropped patches no longer needed:
  + debian/patches/lp1565567.patch: upstream.
  + debian/patches/also_check_sudo_group.diff: upstream.

 -- Timo Aaltonen   Sat, 14 Jan 2017 01:41:17 +0200

** Changed in: sudo (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1607666

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Confirmed
Status in sudo source package in Yakkety:
  New

Bug description:
  Sudo currently fails to validate netgroups against host netgroups
  returned from the sss plugin, see
  https://fedorahosted.org/freeipa/ticket/6139 for the glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1607666/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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

[Steve Langasek]

the fix for zesty is in -proposed, currently only held up by autopkgtest
flakiness.

** Changed in: systemd (Ubuntu Zesty)
   Status: Confirmed => Fix Committed

-- 
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:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  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+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647485/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] Re: Unity8 is not in desktop mode inside the snap session

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gsettings-qt (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-qt in Ubuntu.
https://bugs.launchpad.net/bugs/1654306

Title:
  Unity8 is not in desktop mode inside the snap session

Status in Canonical System Image:
  Triaged
Status in gsettings-qt package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

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.

  unity8-session snap on classic

  gsettings get com.canonical.Unity8 usage-mode
  says Windowed"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+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 1656518] [NEW] computer blocked

[costa]

Public bug reported:

the computer stays blocked (I need to start with the xterminal). It's
the graphic motehrboard?? my computer is old...2008

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: Sat Jan 14 11:34:20 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus: nvidia-304, 304.132, 4.8.0-34-generic, x86_64: installed
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 (129 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 plymouth:debug drm.debug=0xe
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: Sat Jan 14 11:10:52 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/1656518

Title:
  computer blocked

Status in xorg package in Ubuntu:
  New

Bug description:
  the computer stays blocked (I need to start with the xterminal). It's
  the graphic motehrboard?? my computer is old...2008

  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: Sat Jan 14 11:34:20 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus: nvidia-304, 304.132, 4.8.0-34-generic, x86_64: installed
  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 (129 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 plymouth:debug drm.debug=0xe
  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.
  

[Touch-packages] [Bug 1656517] [NEW] can't login with unity 8

[Samvel Malintsyan]

Public bug reported:

After upgrading from ubuntu 16.04 to 16.10 I can't login with unity8

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unity8 8.14+16.10.20160922-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jan 14 15:32:32 2017
InstallationDate: Installed on 2016-11-05 (69 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: unity8
UpgradeStatus: Upgraded to yakkety on 2017-01-08 (5 days ago)

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages yakkety

** Attachment added: "VzMVO.jpg"
   https://bugs.launchpad.net/bugs/1656517/+attachment/4804198/+files/VzMVO.jpg

-- 
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/1656517

Title:
   can't login with unity 8

Status in unity8 package in Ubuntu:
  New

Bug description:
  After upgrading from ubuntu 16.04 to 16.10 I can't login with unity8

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 14 15:32:32 2017
  InstallationDate: Installed on 2016-11-05 (69 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to yakkety on 2017-01-08 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1656517/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1607666] Re: sudo fails with host netgroup returned from freeipa

[Florian Apolloner]

Can confirm that this seems to work for us.

-- 
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/1607666

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Confirmed
Status in sudo source package in Xenial:
  Confirmed
Status in sudo source package in Yakkety:
  New

Bug description:
  Sudo currently fails to validate netgroups against host netgroups
  returned from the sss plugin, see
  https://fedorahosted.org/freeipa/ticket/6139 for the glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1607666/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1655429] Re: Noise and poor audio quality over SPDIF

[Olli Lupton]

** Changed in: alsa-driver (Ubuntu)
   Status: New => 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/1655429

Title:
  Noise and poor audio quality over SPDIF

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I recently updated a system to Ubuntu 16.04.1 LTS from 14.04.5 LTS.

  After the upgrade, the sound quality I get over the SPDIF output is
  terrible -- I hear crackling/noise when no sound is being played, and
  when I play a sound it is heavily distorted. The situation was much
  better (if not quite perfect) in 14.04.5.

  The system runs on an ASROCK N3150DC-ITX board with a coaxial SPDIF
  cable connected to the headers on the board.

  $ cat /proc/asound/version
  Advanced Linux Sound Architecture Driver Version k4.4.0-59-generic.

  $ cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC892
  Codec: Intel Braswell HDMI

  in alsamixer it shows:

  Card: HDA Intel PCH
  Chip: Realtek ALC892

  I can't confirm this, but I believe that in 14.04.5 this showed the
  'Chip' as 'Intel Braswell HDMI'

  The alsamixer control for my SPDIF output is called 'SPDIF 16'
  muting/unmuting this works, and no other combination of controls I
  have tried changing has any effect. 'SPDIF 1' and 'SPDIF 2' are also
  present in alsamixer

  I tried the position_fix suggestion here
  https://wiki.ubuntu.com/Audio/PositionReporting, but it didn't make
  any difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oliver 2174 F lxpanel
  Date: Tue Jan 10 18:40:24 2017
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to xenial on 2017-01-08 (2 days ago)
  dmi.bios.date: 06/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: N3150DC-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd06/22/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150DC-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-01-10T18:34:19.982437

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1655429/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622499] Re: kaccounts-providers packagepackage kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.googl

[Hans Joachim Desserud]

** Also affects: account-plugins (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: account-plugins (Ubuntu)
   Status: New => Confirmed

-- 
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/1622499

Title:
  kaccounts-providers packagepackage kaccounts-providers (not installed)
  failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/accounts.google.com.conf', which is also in package account-
  plugin-google 0.13+16.04.20160719-0ubuntu1

Status in One Hundred Papercuts:
  Confirmed
Status in account-plugins package in Ubuntu:
  Confirmed
Status in kaccounts-providers package in Ubuntu:
  Confirmed

Bug description:
  
  kaccounts-providers packagepackage kaccounts-providers (not installed) failed 
to install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package account-plugin-google 0.13+16.04.20160719-0ubuntu1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Sep 12 08:14:14 2016
  DuplicateSignature:
   package:kaccounts-providers:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package account-plugin-google 0.13+16.04.20160719-0ubuntu1
  InstallationDate: Installed on 2016-09-08 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.14
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', 
which is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1622499/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

[Olivier Tilloy]

@taiebot65: thanks for testing! Indeed silo 2366 has an incomplete fix,
I’m aware of it and will update it on Monday. Regarding twitter, I’m
assuming you’re on the stable channel (i.e. OTA-14) ? I’m not seeing the
issue on rc-proposed.

-- 
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/1656310

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1629632

Title:
  Sap driver initialization failed, sap-server: Operation not permitted

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here are are messages from the bluetooth daemon:

  $ journalctl -b | grep bluetoothd
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for 
"Service Changed" characteristic
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
  Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted 
(1)

  There are at least 2 errors concerning:
   - handles
   - Sap driver/server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 09:59:43 2016
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX bytes:6033 acl:0 sco:0 commands:132 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656504] [NEW] Permission denied when running apport-collect

[nico]

Public bug reported:

I tried several times to launch apport-collect 1651520 but it failed
everytime:

The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=Xp4CFWJ01GvW7QPhMfq8_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
ERROR: connecting to Launchpad failed: [Errno 13] Permission denied: 
'/home/nicolas/.cache/apport/launchpad.credentials'
You can reset the credentials by removing the file 
"/home/nicolas/.cache/apport/launchpad.credentials"

I've tried successively to "Allow nicolas-MS-7808 to access my Launchpad
account:" "for an hour", "for a week", "until I disable it", apport-
collect failed everytime with the same message.

Note that running:
rm /home/nicolas/.cache/apport/launchpad.credentials
return:
rm: impossible de supprimer 
'/home/nicolas/.cache/apport/launchpad.credentials': Aucun fichier ou dossier 
de ce type

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.4
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jan 14 08:53:31 2017
InstallationDate: Installed on 2014-06-14 (945 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to xenial on 2016-08-25 (142 days ago)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1656504

Title:
  Permission denied when running apport-collect

Status in apport package in Ubuntu:
  New

Bug description:
  I tried several times to launch apport-collect 1651520 but it failed
  everytime:

  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=Xp4CFWJ01GvW7QPhMfq8_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Waiting to hear from Launchpad about your decision...
  ERROR: connecting to Launchpad failed: [Errno 13] Permission denied: 
'/home/nicolas/.cache/apport/launchpad.credentials'
  You can reset the credentials by removing the file 
"/home/nicolas/.cache/apport/launchpad.credentials"

  I've tried successively to "Allow nicolas-MS-7808 to access my
  Launchpad account:" "for an hour", "for a week", "until I disable it",
  apport-collect failed everytime with the same message.

  Note that running:
  rm /home/nicolas/.cache/apport/launchpad.credentials
  return:
  rm: impossible de supprimer 
'/home/nicolas/.cache/apport/launchpad.credentials': Aucun fichier ou dossier 
de ce type

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 14 08:53:31 2017
  InstallationDate: Installed on 2014-06-14 (945 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to xenial on 2016-08-25 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1656504/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp