[Touch-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang

[jnshey]

I also have the same problem. I am using Ubuntu 16.04 release version
with a Thinkpad X1 Carbon.

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

Title:
  Plugging HDMI screen in causes system hang

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  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)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

-- 
Mailing list: https://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 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used

[msp3k]

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

I reformatted over 14.04 and installed 16.04 as a fresh start.  I use a 
slightly customized server install ISO image that includes my own 
preseed file for automation.  My approach is to start with a bare-bones 
server install on all machines and then install extra packages based on 
the machine's function (ubuntu-desktop on workstations, for instance).  
According to my installation logs, dnsmasq was installed during an 
"apt-get install ubuntu-desktop unity-tweak-tool" on a workstation 
(which of those two packages actually resulted in a dependency on 
dnsmasq I don't know), and on a server it was installed during an 
"apt-get install polipo".

Michael

On 04/28/2016 06:01 AM, Thomas Hood wrote:
> *** This bug is a duplicate of bug 1003842 ***
>  https://bugs.launchpad.net/bugs/1003842
>
> What remains unexplained is why the dnsmasq package was installed on
> your machine at all. Is it the case that dnsmasq was not installed
> before the upgrade and it was installed after the upgrade? In that case,
> please file a new bug report describing that particular misbehavior.
>

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

Title:
  resolvconf doesn't create the correct /etc/resolv.conf file when
  static IP addresses are used

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  By default, when installing ubuntu-desktop (and when installing some
  other packages as well), apt will also install dnsmasq as a
  dependency.  When dnsmasq is installed, and static IP addresses are
  used, resolv.conf creates a nearly empty /etc/resolv.conf file.  The
  file only contains entries for localhost and the search domain.  If
  static IP addresses are defined in /etc/network/interfaces, then
  shouldn't those DNS servers should be included in /etc/resolv.conf
  regardless of the presence of dnsmasq?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed Apr 27 08:34:24 2016
  InstallationDate: Installed on 2016-04-26 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1465814] Re: Apt did the opposite of what I told it to do when it asked me a yes or no question

[Nikita Yerenkov-Scott]

I am now running Ubuntu GNOME 15.10 with GNOME 3.18 and know for a fact
that I did not type anything wrong, I simply executed 'sudo apt-get
dist-upgrade' and this is how it went:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  oracle-java8-installer
1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Need to get 23.1 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Abort.

Is there any way of checking why exactly it aborted or what exact input
it received? Because if you are right about this, then even if it a bug
in something else, there has to be a bug somewhere because I really did
nothing special here and it's not even a remote session or anything...

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

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

Title:
  Apt did the opposite of what I told it to do when it asked me a yes or
  no question

Status in Ubuntu GNOME:
  New
Status in apt package in Ubuntu:
  Invalid

Bug description:
  Today I executed the command:

  sudo apt-get dist-upgrade

  And this was the output:

  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
    aptdaemon aptdaemon-data python-aptdaemon python-aptdaemon.gtk3widgets
    python3-aptdaemon python3-aptdaemon.gtk3widgets 
python3-aptdaemon.pkcompat
    wpasupplicant
  8 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
  Need to get 1,146 kB of archives.
  After this operation, 3,072 B of additional disk space will be used.
  Do you want to continue? [Y/n]

  So I answered 'y' (without the quotes), and this was the output:

  Abort.

  And it seemingly aborted instead of doing what I said, although when I
  ran the command again, it installed the upgrades instead of aborting,
  but I just thought that I should report this as it seemed buggy as
  this is not what it is meant to do.

  ---

  OS Information:

  Description:  Ubuntu 15.04
  Release:  15.04

  Package Information (I got this information after upgrading those
  packages, and the error occurred before the upgrade, so the version it
  occurred on might have been the previous to this):

  apt:
    Installed: 1.0.9.7ubuntu4
    Candidate: 1.0.9.7ubuntu4
    Version table:
   *** 1.0.9.7ubuntu4 0
  500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1465814/+subscriptions

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

[Touch-packages] [Bug 1568439] Re: QtLocation OSM based routing does not work any more

[Timo Jyrinki]

** Changed in: canonical-devices-system-image
   Status: Incomplete => Fix Committed

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

Title:
  QtLocation OSM based routing does not work any more

Status in Canonical System Image:
  Fix Committed
Status in qtlocation-opensource-src package in Ubuntu:
  New
Status in qtlocation-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Apparently OSM changed a status code in their server, so all routing
  operations fail.

  This has been fixed in Qt 5.5. Please consider backporting this patch
  to our Qt 5.4 version:

  
http://code.qt.io/cgit/qt/qtlocation.git/patch/?id=9969179a06c30b56d3d057aba127686b64ccd659

  I have tested it locally and it seems to work fine.

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

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

[Touch-packages] [Bug 1575192] Re: Mir-on-X11 breaks mir_proving_server resize logic

[Alan Griffiths]

The middle button is 2 (correctly mapped to
mir_pointer_button_tertiary).

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

Title:
  Mir-on-X11 breaks mir_proving_server resize logic

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  New

Bug description:
  $ mir_proving_server&
  $ mir_demo_client_egltriangle

  Alt+drag with middle mouse button

  Expect: client is resized
  Actual: Nothing happens

  A bit of investigation shows that the mouse-button-down event isn't
  being received. (The movement event is received.)

  (The problem doesn't occur on other platforms.)

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

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

[Touch-packages] [Bug 1575192] Re: Mir-on-X11 breaks mir_proving_server resize logic

[Cemil Azizoglu]

With https://code.launchpad.net/~cemil-
azizoglu/mir/fix-1575765/+merge/293267, we should have pointer grabbing.
Let's see what you get with that.

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

Title:
  Mir-on-X11 breaks mir_proving_server resize logic

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  $ mir_proving_server&
  $ mir_demo_client_egltriangle

  Alt+drag with middle mouse button

  Expect: client is resized
  Actual: Nothing happens

  A bit of investigation shows that the mouse-button-down event isn't
  being received. (The movement event is received.)

  (The problem doesn't occur on other platforms.)

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

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

[Touch-packages] [Bug 1575192] Re: Mir-on-X11 breaks mir_proving_server resize logic

[Cemil Azizoglu]

Hmm I'm not sure why it works for me then. Perhaps the middle button on
my mouse is nonstandard.

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

Title:
  Mir-on-X11 breaks mir_proving_server resize logic

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  $ mir_proving_server&
  $ mir_demo_client_egltriangle

  Alt+drag with middle mouse button

  Expect: client is resized
  Actual: Nothing happens

  A bit of investigation shows that the mouse-button-down event isn't
  being received. (The movement event is received.)

  (The problem doesn't occur on other platforms.)

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

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

[Touch-packages] [Bug 1576228] [NEW] Black borders around all windows

[John Smith]

Public bug reported:

There seems to be a bug somewhere  in [ kernel OR xorg OR nvidia proprietary 
driver ] in the display stack.
After the laptop ( dell XPS L501X ) resumes from suspend there are wide black 
borders around all windows with close/minimize/maximize buttons blacked out.

[ image attached: black border on all windows ]

It occurs inconsistently, as it doesn't happen every time the computer resumes.
( Slight possibility that it usually occurs after long suspend, i.e. resuming 
after long time ).
=

Also there seems to be certain amount of performance degradation as if
the graphics driver was running at half-strength ( and I don't  mean
software-only rendering, neither do I mean switch over to nouveau open
source driver )

The "nVidia X Server Settings" app suggests its in maximum performance
mode.

==

Adhoc Workaround: switch display layout ( I have an external monitor/TV
attached to HDMI port ) changing anything such as arrangement or
resolution of the displays, etcetera... corrects the black border issue
( and also possibly performance issue )

This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in 16.04
as well. ( It was probably present before that as well )

==

p.s. this is only partial duplicate of black border issue as the black
borders appear on every window, not just windows with new header bars or
client side decoration...

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
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog: [  OK  ] Started LSB: Speech Dispatcher.
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: Thu Apr 28 18:43:37 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e]
InstallationDate: Installed on 2016-04-23 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. XPS L501X
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic 
root=UUID=f657e606-ac2a-49cd-9f3e-fca6a315338d ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/26/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0J1VR3
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn0J1VR3:rvrA08:cvnDellInc.:ct8:cvrA08:
dmi.product.name: XPS L501X
dmi.product.version: A08
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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: Thu Apr 28 17:09:49 

[Touch-packages] [Bug 1388070] Re: [Alarms] Allow snoozing an alarm/silencing a phone call by turning the phone face down.

[John Lea]

** Description changed:

  It'd be great to allow snoozing alarms using the "turnover" gesture as
  described here:
  
  http://qt-project.org/doc/qt-5/sensorgesture-plugins-topics.html
  
  (Same goes for silenting incoming calls)
  
  To be more precise on how the gesture would work:
  
  In order to avoid false positives, the device needs to be turned from
  face up to face down. If the device is already face down when the
  alarm/call starts ringing, it needs first to be turned face up and then
  again face down.
  
   UX comment 
  
- Please refer to the Screen blanking policy doc for further information:
- 
https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0/edit?usp=sharing
+ Great idea, please add ;-)

** Changed in: ubuntu-ux
 Assignee: Andrea Bernabei (faenil) => John Lea (johnlea)

** Changed in: ubuntu-ux
   Status: New => Fix Committed

** Description changed:

  It'd be great to allow snoozing alarms using the "turnover" gesture as
  described here:
  
  http://qt-project.org/doc/qt-5/sensorgesture-plugins-topics.html
  
  (Same goes for silenting incoming calls)
  
  To be more precise on how the gesture would work:
  
  In order to avoid false positives, the device needs to be turned from
  face up to face down. If the device is already face down when the
  alarm/call starts ringing, it needs first to be turned face up and then
  again face down.
  
   UX comment 
  
- Great idea, please add ;-)
+ Great idea, this is a good example of a 'moment of delight' interaction.
+ 
+ Feel free to add this functionality.

** Changed in: unity-system-compositor
   Status: New => Triaged

** Changed in: unity-system-compositor (Ubuntu)
   Status: New => Triaged

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

Title:
  [Alarms] Allow snoozing an alarm/silencing a phone call by turning the
  phone face down.

Status in Ubuntu UX:
  Fix Committed
Status in Unity System Compositor:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  It'd be great to allow snoozing alarms using the "turnover" gesture as
  described here:

  http://qt-project.org/doc/qt-5/sensorgesture-plugins-topics.html

  (Same goes for silenting incoming calls)

  To be more precise on how the gesture would work:

  In order to avoid false positives, the device needs to be turned from
  face up to face down. If the device is already face down when the
  alarm/call starts ringing, it needs first to be turned face up and
  then again face down.

   UX comment 

  Great idea, this is a good example of a 'moment of delight'
  interaction.

  Feel free to add this functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1388070/+subscriptions

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

[Touch-packages] [Bug 1557962] Re: NBS fullscreen overlay benchmark performance is much lower than BufferQueue

[Alberto Aguirre]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  NBS fullscreen overlay benchmark performance is much lower than
  BufferQueue

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  New

Bug description:
  NBS fullscreen benchmark performance is much lower than BufferQueue.

  $ sudo bin/mir_proving_server --nbuffers=0 &
  $ sudo env MIR_CLIENT_PERF_REPORT=log glmark2-mir --fullscreen -b texture
  ===
  glmark2 2014.03+git20150611.fa71af2d
  ===
  OpenGL Information
  GL_VENDOR: Intel Open Source Technology Center
  GL_RENDERER:   Mesa DRI Intel(R) Haswell Desktop
  GL_VERSION:3.0 Mesa 11.1.2
  ===
  [texture] :[2016-03-16 16:47:48.337501] perf: : 1270.00 FPS, render 
time 0.50ms, buffer lag 1.84ms (3 buffers)
  [2016-03-16 16:47:49.337541] perf: : 1284.00 FPS, render time 0.44ms, buffer 
lag 1.88ms (3 buffers)
  [2016-03-16 16:47:50.338014] perf: : 1311.00 FPS, render time 0.45ms, buffer 
lag 1.83ms (3 buffers)
  [2016-03-16 16:47:51.338506] perf: : 1299.00 FPS, render time 0.45ms, buffer 
lag 1.85ms (3 buffers)
  [2016-03-16 16:47:52.338721] perf: : 1309.00 FPS, render time 0.45ms, buffer 
lag 1.84ms (3 buffers)
  [2016-03-16 16:47:53.338970] perf: : 1296.00 FPS, render time 0.44ms, buffer 
lag 1.86ms (3 buffers)
  [2016-03-16 16:47:54.339363] perf: : 1300.00 FPS, render time 0.45ms, buffer 
lag 1.85ms (3 buffers)
  [2016-03-16 16:47:55.339693] perf: : 1299.00 FPS, render time 0.44ms, buffer 
lag 1.86ms (3 buffers)
  [2016-03-16 16:47:56.339954] perf: : 1300.00 FPS, render time 0.44ms, buffer 
lag 1.85ms (3 buffers)
  [2016-03-16 16:47:57.340275] perf: : 1306.00 FPS, render time 0.44ms, buffer 
lag 1.85ms (3 buffers)
   FPS: 1300 FrameTime: 0.769 ms
  ===
    glmark2 Score: 1300
  ===

  $ sudo bin/mir_proving_server &
  $ sudo env MIR_CLIENT_PERF_REPORT=log glmark2-mir --fullscreen -b texture
  ===
  glmark2 2014.03+git20150611.fa71af2d
  ===
  OpenGL Information
  GL_VENDOR: Intel Open Source Technology Center
  GL_RENDERER:   Mesa DRI Intel(R) Haswell Desktop
  GL_VERSION:3.0 Mesa 11.1.2
  ===
  [texture] :[2016-03-16 16:48:06.510089] perf: : 1795.00 FPS, render 
time 14238.16ms, buffer lag 1.68ms (4 buffers)
  [2016-03-16 16:48:07.510343] perf: : 1884.00 FPS, render time 0.44ms, buffer 
lag 1.67ms (4 buffers)
  [2016-03-16 16:48:08.510718] perf: : 1898.00 FPS, render time 0.44ms, buffer 
lag 1.66ms (4 buffers)
  [2016-03-16 16:48:09.511066] perf: : 1894.00 FPS, render time 0.44ms, buffer 
lag 1.66ms (4 buffers)
  [2016-03-16 16:48:10.511537] perf: : 1877.00 FPS, render time 0.44ms, buffer 
lag 1.68ms (4 buffers)
  [2016-03-16 16:48:11.511716] perf: : 1844.00 FPS, render time 0.44ms, buffer 
lag 1.72ms (4 buffers)
  [2016-03-16 16:48:12.511879] perf: : 1862.00 FPS, render time 0.44ms, buffer 
lag 1.69ms (4 buffers)
  [2016-03-16 16:48:13.512307] perf: : 1842.00 FPS, render time 0.45ms, buffer 
lag 1.71ms (4 buffers)
  [2016-03-16 16:48:14.512818] perf: : 1847.00 FPS, render time 0.44ms, buffer 
lag 1.71ms (4 buffers)
  [2016-03-16 16:48:15.513197] perf: : 1854.00 FPS, render time 0.45ms, buffer 
lag 1.70ms (4 buffers)
   FPS: 1863 FrameTime: 0.537 ms
  ===
    glmark2 Score: 1863
  ===

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

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

[Touch-packages] [Bug 1555074] Re: CI failure in NestedServer.display_orientation_changes_are_forwarded_to_host

[Alberto Aguirre]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  CI failure in
  NestedServer.display_orientation_changes_are_forwarded_to_host

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  New

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/385/consoleFull

  Seen on CI on an unrelated branch. Could not reproduce locally.

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

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

[Touch-packages] [Bug 1568439] Re: QtLocation OSM based routing does not work any more

[Timo Jyrinki]

** Changed in: canonical-devices-system-image
Milestone: None => 11

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

Title:
  QtLocation OSM based routing does not work any more

Status in Canonical System Image:
  Incomplete
Status in qtlocation-opensource-src package in Ubuntu:
  New
Status in qtlocation-opensource-src package in Ubuntu RTM:
  New

Bug description:
  Apparently OSM changed a status code in their server, so all routing
  operations fail.

  This has been fixed in Qt 5.5. Please consider backporting this patch
  to our Qt 5.4 version:

  
http://code.qt.io/cgit/qt/qtlocation.git/patch/?id=9969179a06c30b56d3d057aba127686b64ccd659

  I have tested it locally and it seems to work fine.

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

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

[Touch-packages] [Bug 1568439] Re: QtLocation OSM based routing does not work any more

[Łukasz Zemczak]

This bug was fixed in the package qtlocation-opensource-src
5.4.1-1ubuntu2~overlay1 in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay

---

qtlocation-opensource-src (5.4.1-1ubuntu2~overlay1) vivid;
urgency=medium

  * debian/patches/Add-center-function-to-QGeoShape.patch
debian/patches/Allow-HTML-based-copyright-notices.patch
debian/patches/backport_qt_56_osm_backend.patch
(the last one include CycleMap support adding)
- Backport OpenStreetMap backend changes from Qt 5.6. (LP: #1568439)
  * Update symbols for the copyrightsChanged symbols.

 -- Timo Jyrinki   Mon, 25 Apr 2016 11:32:12
+


** Changed in: qtlocation-opensource-src (Ubuntu RTM)
   Status: New => Fix Released

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

Title:
  QtLocation OSM based routing does not work any more

Status in Canonical System Image:
  Incomplete
Status in qtlocation-opensource-src package in Ubuntu:
  New
Status in qtlocation-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Apparently OSM changed a status code in their server, so all routing
  operations fail.

  This has been fixed in Qt 5.5. Please consider backporting this patch
  to our Qt 5.4 version:

  
http://code.qt.io/cgit/qt/qtlocation.git/patch/?id=9969179a06c30b56d3d057aba127686b64ccd659

  I have tested it locally and it seems to work fine.

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

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

[Touch-packages] [Bug 1536662] Re: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random

[Alberto Aguirre]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Black screen: Mir hangs and then crashes on startup/login
  due to reading from /dev/random

Status in Mir:
  Fix Released
Status in Mir 0.19 series:
  Won't Fix
Status in Mir 0.20 series:
  Won't Fix
Status in Mir 0.21 series:
  Triaged
Status in Unity System Compositor:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Fix Released

Bug description:
  cookie_factory attempts to read data from /dev/random at boot, and
  blocks until it has enough random data or timesout after 30 seconds.

  How I can reproduce
  1. Run the Unity8 greeter as a mir server
  2. Reboot

  Expected behavior: Greeter is displayed as mir && USC run happily
  Actual behavior: Mir throws an exception after 30 seconds

  Work-around:
  Before logging in, move the mouse around lots, for at least 20 seconds. And 
after logging in, while you're looking at a black screen, move the mouse around 
furiously. This will populate the kernel entropy pool sufficiently to avoid the 
hang and crash.

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

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

[Touch-packages] [Bug 1528109] Re: [regression] Cursor mostly does not move at all in response to slow mouse movement, but then sometimes jumps

[Alberto Aguirre]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Cursor mostly does not move at all in response to slow
  mouse movement, but then sometimes jumps

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Won't Fix
Status in Mir 0.20 series:
  Triaged
Status in Mir 0.21 series:
  Fix Committed
Status in libinput package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Starting in Mir 0.18 I've noticed with a Microsoft Intellimouse
  Explorer 3.0 that moving it slowly does not move the cursor. That is
  unless I move it slowly for a while, and then the cursor jumps.

  Xorg and Mir 0.17 do not have this problem.

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

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

[Touch-packages] [Bug 1499229] Re: [regression] [testsfail] failure in CI on ThreadedDispatcherSignalTest.keeps_dispatching_after_signal_interruption under Valgrind

[Alberto Aguirre]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] [testsfail] failure in CI on
  ThreadedDispatcherSignalTest.keeps_dispatching_after_signal_interruption
  under Valgrind

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  New

Bug description:
  Opening a new bug, rather than recycling lp:1441620

  9: [ RUN ] 
ThreadedDispatcherSignalTest.keeps_dispatching_after_signal_interruption
  9: ==26614==
  9: ==26614== FILE DESCRIPTORS: 2 open at exit.
  9: ==26614== Open file descriptor 2:
  9: ==26614== 
  9: ==26614==
  9: ==26614== Open file descriptor 1:
  9: ==26614== 
  9: ==26614==
  9: ==26614==
  9: ==26614== HEAP SUMMARY:
  9: ==26614== in use at exit: 95,523 bytes in 757 blocks
  9: ==26614== total heap usage: 843,952 allocs, 843,195 frees, 135,376,735 
bytes allocated
  9: ==26614==
  9: ==26614== LEAK SUMMARY:
  9: ==26614== definitely lost: 0 bytes in 0 blocks
  9: ==26614== indirectly lost: 0 bytes in 0 blocks
  9: ==26614== possibly lost: 852 bytes in 22 blocks
  9: ==26614== still reachable: 94,179 bytes in 729 blocks
  9: ==26614== of which reachable via heuristic:
  9: ==26614== newarray : 1,244 bytes in 39 blocks
  9: ==26614== suppressed: 0 bytes in 0 blocks
  9: ==26614== Reachable blocks (those to which a pointer was found) are not 
shown.
  9: ==26614== To see them, rerun with: --leak-check=full --show-leak-kinds=all
  9: ==26614==
  9: ==26614== For counts of detected and suppressed errors, rerun with: -v
  9: ==26614== Use --track-origins=yes to see where uninitialised values come 
from
  9: ==26614== ERROR SUMMARY: 2443 errors from 8 contexts (suppressed: 129883 
from 41)
  9: 
/tmp/buildd/mir-0.18.0bzr3187pkg0xenial129+autopilot0/tests/unit-tests/dispatch/test_threaded_dispatcher.cpp:382:
 Failure
  9: Value of: result.succeeded()
  9: Actual: false
  9: Expected: true
  9: [ FAILED ] 
ThreadedDispatcherSignalTest.keeps_dispatching_after_signal_interruption (2710 
ms)

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

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

[Touch-packages] [Bug 1388070] Re: [Alarms] Allow snoozing an alarm by turning the phone.

[Michael Zanetti]

Reopening this after discussing with design on the Shell sprint

** Description changed:

  It'd be great to allow snoozing alarms using the "turnover" gesture as
  described here:
  
  http://qt-project.org/doc/qt-5/sensorgesture-plugins-topics.html
  
  (Same goes for silenting incoming calls)
  
+ To be more precise on how the gesture would work:
+ 
+ In order to avoid false positives, the device needs to be turned from
+ face up to face down. If the device is already face down when the
+ alarm/call starts ringing, it needs first to be turned face up and then
+ again face down.
+ 
   UX comment 
  
  Please refer to the Screen blanking policy doc for further information:
  
https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0/edit?usp=sharing

** Changed in: ubuntu-ux
   Status: Fix Committed => New

** Summary changed:

- [Alarms] Allow snoozing an alarm by turning the phone.
+ [Alarms] Allow snoozing an alarm/silencing a phone call by turning the phone 
face down.

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

Title:
  [Alarms] Allow snoozing an alarm/silencing a phone call by turning the
  phone face down.

Status in Ubuntu UX:
  Fix Committed
Status in Unity System Compositor:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  It'd be great to allow snoozing alarms using the "turnover" gesture as
  described here:

  http://qt-project.org/doc/qt-5/sensorgesture-plugins-topics.html

  (Same goes for silenting incoming calls)

  To be more precise on how the gesture would work:

  In order to avoid false positives, the device needs to be turned from
  face up to face down. If the device is already face down when the
  alarm/call starts ringing, it needs first to be turned face up and
  then again face down.

   UX comment 

  Great idea, this is a good example of a 'moment of delight'
  interaction.

  Feel free to add this functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1388070/+subscriptions

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

[Touch-packages] [Bug 1575604] Re: Fast repeated scrolling with a finger changes direction of the scrolling

[Joachim Tuchel]

Also available on an aquaris e5 hd near you ;-)

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

Title:
  Fast repeated scrolling with a finger changes direction of the
  scrolling

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When scrolling on a page with repeated gestures with the finger on the
  screen, it often changes the direction of the scrolling and scrolls
  super fast.  So if I am far down on a page and scrolls a few times
  with  the finger, it suddenly start to scroll upwards super fast to
  the top.

  It seems like it happens if it lags while scrolling and it misses part
  of the gesture.

  Experienced on an M10 with OTA-10.1

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

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

[Touch-packages] [Bug 1576058] Re: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in packag

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/accounts/providers/google.provider', which is also in
  package kaccounts-providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 16:53:29 2016
  DpkgTerminalLog:
   Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  DuplicateSignature:
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2014-02-25 (793 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1576058/+subscriptions

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

[Touch-packages] [Bug 1576058] [NEW] package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in pack

[Chih-Hung Li]

Public bug reported:

Errors were encountered while processing:
 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-google (not installed)
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu Apr 28 16:53:29 2016
DpkgTerminalLog:
 Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
 Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite '/usr/share/accounts/providers/google.provider', which is 
also in package kaccounts-providers 4:15.12.3-0ubuntu1
DuplicateSignature:
 Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite '/usr/share/accounts/providers/google.provider', which is 
also in package kaccounts-providers 4:15.12.3-0ubuntu1
ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2014-02-25 (793 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac 
(20131016.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: account-plugins
Title: package account-plugin-google (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/accounts/providers/google.provider', which is 
also in package kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: Upgraded to xenial on 2016-04-28 (0 days ago)

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


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/accounts/providers/google.provider', which is also in
  package kaccounts-providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 16:53:29 2016
  DpkgTerminalLog:
   Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  DuplicateSignature:
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2014-02-25 (793 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1576058/+subscriptions

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

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

[Martin Pitt]

> systemd-sysctl.service loaded failed failed Apply Kernel Variables

I filed this as https://github.com/lxc/lxcfs/issues/111 . I'll stop
treating this here now, as there are already too many unrelated issues
here for one bug report.

-- 
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 1576235] Re: FTBFS - ubuntu-keyboard - xenial arm64

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => In Progress

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-keyboard (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

** Changed in: canonical-devices-system-image
Milestone: None => xenial

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

Title:
  FTBFS - ubuntu-keyboard - xenial arm64

Status in Canonical System Image:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  In Progress

Bug description:
  ubuntu-keyboard fails to build on xenial arm64

  https://launchpad.net/ubuntu/+source/ubuntu-
  keyboard/0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1/+build/9278079

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

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

[Touch-packages] [Bug 1547466] Re: grep switches into binary mode while processing a text file

[teo1978]

@Brian Murray, I resubscribed you because you marked this issue as
duplicate of #1535458, I asked you if you could confirm because that
seems doubtful and you didn't reply, and now at 1535458 they say it only
affects xenial, while this one I am observing on wily.

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

Title:
  grep switches into binary mode while processing a text file

Status in grep package in Ubuntu:
  Fix Released
Status in grep source package in Xenial:
  In Progress
Status in grep source package in Yakkety:
  Fix Released
Status in grep package in Debian:
  Fix Released

Bug description:
  I noticed this staring to happen in Xenial about two days ago. When
  running sbuild (or now the buildd, too), the build breaks when trying
  to compile a generated file. I traced the problem down to grep
  suddenly acting weird. When not having any language set (or a non-UTF8
  mode) it will start printing some lines of a source file and then
  suddenly end that by printing "Binary file ... matches".

  With the attached file, the difference can be observed (running
  Xenial):

  LANG=C grep -v xxx grant_table.h

  and

  LANG=C.UTF-8 grep -v xxx grant_table.h

  SRU INFORMATION
  ===
  Upstream fixes:
   - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but 
depends on previous patches and is not sufficient by itself)
   - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc)

  Test case:

  Call grep on a file or a string with non-ASCII characters in the C locale:
  $ echo 'héll☺ ≥x' | LC_ALL=C grep .
  In xenial this just shows "Binary file (standard input) matches", with the 
fix it should show the actual input string (with some garbled output of course 
as the UTF-8 chars cannot be displayed in C)

  Regression potential: grep is being used in tons of places; during
  xenial we had to fix/put a "use grep -a" workaround into a lot of
  packages to fix the fallout from grep 2.23 which introduced this. That
  said, as a result of "Binary file matches" does not give any more
  information than the actual string match, and scripts which get along
  with this answer most likely just check the exit code anyway (which
  does not change), the risk is bearable.

  We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25,
  and will sift through the results to identify new FTBFS that are due
  to grep 2.25. This SRU should not be released until this happens.

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

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

[Touch-packages] [Bug 1547466] Re: grep switches into binary mode while processing a text file

[teo1978]

Sorry, meant to post this on the other bug

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

Title:
  grep switches into binary mode while processing a text file

Status in grep package in Ubuntu:
  Fix Released
Status in grep source package in Xenial:
  In Progress
Status in grep source package in Yakkety:
  Fix Released
Status in grep package in Debian:
  Fix Released

Bug description:
  I noticed this staring to happen in Xenial about two days ago. When
  running sbuild (or now the buildd, too), the build breaks when trying
  to compile a generated file. I traced the problem down to grep
  suddenly acting weird. When not having any language set (or a non-UTF8
  mode) it will start printing some lines of a source file and then
  suddenly end that by printing "Binary file ... matches".

  With the attached file, the difference can be observed (running
  Xenial):

  LANG=C grep -v xxx grant_table.h

  and

  LANG=C.UTF-8 grep -v xxx grant_table.h

  SRU INFORMATION
  ===
  Upstream fixes:
   - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but 
depends on previous patches and is not sufficient by itself)
   - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc)

  Test case:

  Call grep on a file or a string with non-ASCII characters in the C locale:
  $ echo 'héll☺ ≥x' | LC_ALL=C grep .
  In xenial this just shows "Binary file (standard input) matches", with the 
fix it should show the actual input string (with some garbled output of course 
as the UTF-8 chars cannot be displayed in C)

  Regression potential: grep is being used in tons of places; during
  xenial we had to fix/put a "use grep -a" workaround into a lot of
  packages to fix the fallout from grep 2.23 which introduced this. That
  said, as a result of "Binary file matches" does not give any more
  information than the actual string match, and scripts which get along
  with this answer most likely just check the exit code anyway (which
  does not change), the risk is bearable.

  We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25,
  and will sift through the results to identify new FTBFS that are due
  to grep 2.25. This SRU should not be released until this happens.

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

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

[Touch-packages] [Bug 1576345] Re: cannot view available wifi networks after enabling wifi

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  cannot view available wifi networks after enabling wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  cannot view available wifi networks after enabling wifi, although it
  get connected to the wifi. but if i want to switch to other wifi i
  cannot as i cant see any available wifi. and the icon is also changed
  to up-down arror(which is for ethernet connection) instead of wifi
  icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 28 20:34:57 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-11-13 (167 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.8.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.8.0/24 dev wlan0  proto kernel  scope link  src 192.168.8.104  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-11-16T16:09:56.538140
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
Ooredoo-B315-9088 1  c9230ff1-5ce5-4c9b-bbaf-a064901a20b6  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----  
   
   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/1576345/+subscriptions

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

[Touch-packages] [Bug 1547466] Re: grep switches into binary mode while processing a text file

[teo1978]

Well, I have wily and I am observing this bug all the time (starting
from a few months ago), or at least I was told that what I'm observing
was a duplicate of this bug.

What I see is that when I grep text files, randomly (but the same files will 
consistently produce the same results) text files are processed like binary 
files, meaning that the output is
  Binary file .txt matches 
rather than the line of text with the match.

Most of the times, text files that are incorrectly processed as binary
are ISO-8859-whatever encoded while files that are matched like text as
expected are utf8-encoded (my locale is utf8). However, I tried with two
files I created from scratch, one utf-8 and the other iso-8859, and I
couldn't reproduce the issue at will.

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

Title:
  grep switches into binary mode while processing a text file

Status in grep package in Ubuntu:
  Fix Released
Status in grep source package in Xenial:
  In Progress
Status in grep source package in Yakkety:
  Fix Released
Status in grep package in Debian:
  Fix Released

Bug description:
  I noticed this staring to happen in Xenial about two days ago. When
  running sbuild (or now the buildd, too), the build breaks when trying
  to compile a generated file. I traced the problem down to grep
  suddenly acting weird. When not having any language set (or a non-UTF8
  mode) it will start printing some lines of a source file and then
  suddenly end that by printing "Binary file ... matches".

  With the attached file, the difference can be observed (running
  Xenial):

  LANG=C grep -v xxx grant_table.h

  and

  LANG=C.UTF-8 grep -v xxx grant_table.h

  SRU INFORMATION
  ===
  Upstream fixes:
   - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but 
depends on previous patches and is not sufficient by itself)
   - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc)

  Test case:

  Call grep on a file or a string with non-ASCII characters in the C locale:
  $ echo 'héll☺ ≥x' | LC_ALL=C grep .
  In xenial this just shows "Binary file (standard input) matches", with the 
fix it should show the actual input string (with some garbled output of course 
as the UTF-8 chars cannot be displayed in C)

  Regression potential: grep is being used in tons of places; during
  xenial we had to fix/put a "use grep -a" workaround into a lot of
  packages to fix the fallout from grep 2.23 which introduced this. That
  said, as a result of "Binary file matches" does not give any more
  information than the actual string match, and scripts which get along
  with this answer most likely just check the exit code anyway (which
  does not change), the risk is bearable.

  We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25,
  and will sift through the results to identify new FTBFS that are due
  to grep 2.25. This SRU should not be released until this happens.

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

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

[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary

[teo1978]

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

(btw sorry for subscribing you to the other bug by mistake)

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

Title:
  [15.10 REGRESSION] Randomly wrongly detects files as binary

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  I have a folder with a bunch of subfolder and several hundred or
  thousands files, most of them PHP files (obviously text).

  I often use grep recursively, like this:
$ grep -R somepattern *

  Since the upgrade from 15.04 to 15.10, it often happens that a lot of text 
files are wrongly treated as binary. That means that, when a match is found, 
instead of getting the normal output which would show the file name and the 
matching line (with the matching substring highlighted), I get the bogus 
message:
binary file whatever.php matches

  Just to be clear: in one invocation of grep -R, I get mixed output
  with a lot of matches shown in the expected way and quit e a few
  matches shown in the wrong way, even though ALL matching files are
  text files.

  
  This worked as expected before the upgrade from 15.04 and 15.10.

  
  This is a HUGE issue that makes it impossible to do everyday developing work.

  
  Until you fix it, please f***ing roll back grep to the previous version, 
because this sh** is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: grep 2.21-2
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 22:43:51 2016
  InstallationDate: Installed on 2013-10-11 (829 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: grep
  UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago)

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

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

[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary

[teo1978]

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

@Brian Murray, I resubscribed you because you marked this issue as
duplicate of #1547466, I asked you if you could confirm because that
seems doubtful and you didn't reply, and now at 1535458 they say it only
affects xenial, while this one I am observing on wily.

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

Title:
  [15.10 REGRESSION] Randomly wrongly detects files as binary

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  I have a folder with a bunch of subfolder and several hundred or
  thousands files, most of them PHP files (obviously text).

  I often use grep recursively, like this:
$ grep -R somepattern *

  Since the upgrade from 15.04 to 15.10, it often happens that a lot of text 
files are wrongly treated as binary. That means that, when a match is found, 
instead of getting the normal output which would show the file name and the 
matching line (with the matching substring highlighted), I get the bogus 
message:
binary file whatever.php matches

  Just to be clear: in one invocation of grep -R, I get mixed output
  with a lot of matches shown in the expected way and quit e a few
  matches shown in the wrong way, even though ALL matching files are
  text files.

  
  This worked as expected before the upgrade from 15.04 and 15.10.

  
  This is a HUGE issue that makes it impossible to do everyday developing work.

  
  Until you fix it, please f***ing roll back grep to the previous version, 
because this sh** is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: grep 2.21-2
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 22:43:51 2016
  InstallationDate: Installed on 2013-10-11 (829 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: grep
  UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago)

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

-- 
Mailing list: https://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 1547466] Re: grep switches into binary mode while processing a text file

[Martin Pitt]

teo1978 [2016-04-28 20:26 -]:
> And what about wily??

This bug does not affect wily at all. It was introduced in grep 2.23
and still present in 2.24, earlier/later versions are not affected.
Wily has 2.21.

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

Title:
  grep switches into binary mode while processing a text file

Status in grep package in Ubuntu:
  Fix Released
Status in grep source package in Xenial:
  In Progress
Status in grep source package in Yakkety:
  Fix Released
Status in grep package in Debian:
  Fix Released

Bug description:
  I noticed this staring to happen in Xenial about two days ago. When
  running sbuild (or now the buildd, too), the build breaks when trying
  to compile a generated file. I traced the problem down to grep
  suddenly acting weird. When not having any language set (or a non-UTF8
  mode) it will start printing some lines of a source file and then
  suddenly end that by printing "Binary file ... matches".

  With the attached file, the difference can be observed (running
  Xenial):

  LANG=C grep -v xxx grant_table.h

  and

  LANG=C.UTF-8 grep -v xxx grant_table.h

  SRU INFORMATION
  ===
  Upstream fixes:
   - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but 
depends on previous patches and is not sufficient by itself)
   - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc)

  Test case:

  Call grep on a file or a string with non-ASCII characters in the C locale:
  $ echo 'héll☺ ≥x' | LC_ALL=C grep .
  In xenial this just shows "Binary file (standard input) matches", with the 
fix it should show the actual input string (with some garbled output of course 
as the UTF-8 chars cannot be displayed in C)

  Regression potential: grep is being used in tons of places; during
  xenial we had to fix/put a "use grep -a" workaround into a lot of
  packages to fix the fallout from grep 2.23 which introduced this. That
  said, as a result of "Binary file matches" does not give any more
  information than the actual string match, and scripts which get along
  with this answer most likely just check the exit code anyway (which
  does not change), the risk is bearable.

  We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25,
  and will sift through the results to identify new FTBFS that are due
  to grep 2.25. This SRU should not be released until this happens.

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

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

[Touch-packages] [Bug 1420914] Re: secret-tool does not run on headless system

[Quanah]

It is trivial to fix this by adding the following to ~/.bashrc:

if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
  eval `dbus-launch --sh-syntax`
fi

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

Title:
  secret-tool does not run on headless system

Status in libsecret package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  libsecret-tools:
Installed: 0.16-0ubuntu1
Candidate: 0.16-0ubuntu1
Version table:
   *** 0.16-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  I expected to be able to run secret-tool on a headless sytem, but got
  this message after running it.

  secret-tool store ...

  (secret-tool:26626): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY

  # didn't expect thisto work, but thought I'd give it a try.
  export DISPLAY=:0
  secret-tool store ...

  (secret-tool:26639): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  secret-tool: Error spawning command line 'dbus-launch 
--autolaunch=0feb8b37e7d1bdde6782aa3e537cfda6 --binary-syntax --close-stderr': 
Child process exited with code 1

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

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

[Touch-packages] [Bug 1574792] Re: sound devices disappear from sound settings

[Launchpad Bug Tracker]

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

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

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

Title:
  sound devices disappear from sound settings

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sound devices disappear from the sound settings however sound is still 
working.
  pulseaudio --kill pulse audio --start restore them back to the sound 
settings. In rear cases, it cannot be started "daemon startup failed".
  This can happen at any time without a reason, also sometimes happen when 
plugging headphones or connecting bluetooth speaker.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 01:02:04 2016
  InstallationDate: Installed on 2016-04-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.0-6588-g4acd8ea-dirty
  dmi.board.name: Peppy
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr4.0-6588-g4acd8ea-dirty:bd09/04/2014:svnGOOGLE:pnPeppy:pvr1.0:rvnGOOGLE:rnPeppy:rvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Martin Pitt]

So would a namespace aware check for CAP_SYS_AUDIT say "no" then? (The
audit subsystem isn't namespace aware right now). How would such a check
look like in userspace?

CAP_SYS_ADMIN is a different beast, as this contains a lot of different
and unrelated  issues. It's also not fine-grained enough anyway for the
above purpose of "can we mount", as this can't/doesn't consider MACs. So
with the statement above (keeping all caps in a container) this means
that the failing dev-hugepages.mount is not easily fixable. It's also
mostly cosmetical, so not urgent for now. I guess the same goes for
iscsi/lvm2 etc.

-- 
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 1574792] Re: sound devices disappear from sound settings

[Bruno Nova]

I'm seeing the same thing.

Every once in a while, the sound devices disappear from the sound settings.
However, for me the sound usually stops working, and then when I open VLC, it 
throws sound errors.

This bug seems to be important.

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

Title:
  sound devices disappear from sound settings

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sound devices disappear from the sound settings however sound is still 
working.
  pulseaudio --kill pulse audio --start restore them back to the sound 
settings. In rear cases, it cannot be started "daemon startup failed".
  This can happen at any time without a reason, also sometimes happen when 
plugging headphones or connecting bluetooth speaker.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 01:02:04 2016
  InstallationDate: Installed on 2016-04-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.0-6588-g4acd8ea-dirty
  dmi.board.name: Peppy
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr4.0-6588-g4acd8ea-dirty:bd09/04/2014:svnGOOGLE:pnPeppy:pvr1.0:rvnGOOGLE:rnPeppy:rvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Stéphane Graber]

I closed the lxd task as our current behavior wrt capabilities is
correct. But I also subscribed the ubuntu-lxc team to this bug so we can
keep an eye on 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 1573168] Re: [Frieza] Location service fails to start cleanly, entering restart loop

[Stefan Kamps]

Hi,

I have the Ubuntu M10 (updated to 10.1 after arrival) for a week now and 
successfully
used GPS with uNav, SensorStatus and Here Maps.

Since yesterday I encounter the above-mentioned bug. I would like to add
the following observations:

After reboot everything is fine, but when I start one of the GPS apps the GPS 
symbol in the indicator menu
starts blinking (frequency: once per second). When I check the app
permissions I see that the list with apps which have requested GPS
access is empty.
When I reboot the M10 again the blinking stops and the list with apps which
requested GPS access is there again.
When the GPS indicator symbol is blinking (because I launched
SensorStatus) and then I start uNav, uNav gives the following error message:
"GPS Denied"
"Error reading the GPS status"
"Please review your device settings"
When I go to device settings I see the following:
- Location Settings: GPS and anoymised Wi-Fi (HERE)
- Battery Settings: GPS enabled
- Secury & privacy -> Apps Permissions -> Location:0

The only way to make the GPS indicator symbol stop blinking is to switch
off GPS location detection.

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

Title:
  [Frieza] Location service fails to start cleanly, entering restart
  loop

Status in location-service package in Ubuntu:
  In Progress

Bug description:
  See http://makeagif.com/i/QlHXU7 for further details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1573168/+subscriptions

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

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

[Stéphane Graber]

LXC doesn't drop many capabilities, we only really drop mac_admin,
mac_override, sys_time, sys_module and sys_rawio.

That's because we do run workloads which do need the other capabilities,
including cap_sys_admin.


Now in an unprivileged container, having those capabilities will only do you 
good against resources owned by the container and will (obviously) not let you 
gain any more rights than you had as the owning uid prior to entering the 
container.

So you absolutely do have cap_sys_admin and it will let you do a bunch
of things against the network devices owned by your container or mount
entries owned by the container, ... but it will not let you mess with
things that aren't namespaced and that you wouldn't be allowed to touch
as a normal unprivileged user.

The kernel has a nice ns_capable(ns, CAP) function which lets you check
whether you do have the named capability against a given resource, I'm
not aware of a userspace equivalent though.

Having us drop a bunch of capabilities is the wrong answer though and we
won't be doing that.

** Changed in: lxd (Ubuntu)
   Status: New => Invalid

-- 
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 1528228] Re: [ADT test failure] linux-lts-utopic: ubuntu_qrt_apparmor.test-apparmor.py -- FAIL: test_aa_unconfined (__main__.ApparmorTest)

[Steve Beattie]

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

Title:
  [ADT test failure] linux-lts-utopic: ubuntu_qrt_apparmor.test-
  apparmor.py --   FAIL: test_aa_unconfined (__main__.ApparmorTest)

Status in QA Regression Testing:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  New ADT test failure in linux-lts-utopic in Trusty:

    FAIL: test_aa_unconfined (__main__.ApparmorTest)
    Test aa-unconfined
    --
    Traceback (most recent call last):
  File "./test-apparmor.py", line 815, in test_aa_unconfined
    self.assertTrue(re.search('[1-9][0-9]* /bin/nc(.openbsd|.traditional)( 
\(/bin/nc\))? not confined', report), result + report)
    AssertionError: Could not find /bin/nc* in report
    609 /sbin/dhclient confined by '/sbin/dhclient (enforce)'
    894 /usr/sbin/sshd not confined
    5326 /usr/sbin/exim4 not confined

  Full log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/linux-lts-utopic/20151218_194502@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1528228/+subscriptions

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

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

[arthurcamargo]

in my terminal apt-get update answered:

W: http://archive.getdeb.net/ubuntu/dists/xenial-getdeb/InRelease:
Signature by key 1958A549614CE21CFC27F4BAA8A515F046D7E7CF uses weak
digest algorithm (SHA1)

W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg:
Signature by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak
digest algorithm (SHA1)

W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg:
Signature by key 3B068FB4789ABE4AEFA3BB491397BC53640DB551 uses weak
digest algorithm (SHA1)

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

Title:
  message "The repository is insufficiently signed by key  (weak
  digest)" is poorly worded

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The title pretty much says it all.

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

-- 
Mailing list: https://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 1576341] Re: fails in lxd container

[Serge Hallyn]

Quoting Martin Pitt (martin.p...@ubuntu.com):
> So would a namespace aware check for CAP_SYS_AUDIT say "no" then? (The
> audit subsystem isn't namespace aware right now). How would such a check
> look like in userspace?

I suppose a namespace aware check for CAP_SYS_AUDIT would look like an
fcntl or something funky against an nsfs inode for a user namespace.
Going from an instantiated or abstract object (like an fd, a pathname,
a process id) to the relevant nsfs inode would be interesting.  I.e.
if one day we allow unpriv users to mknod /dev/null, then a check
for CAP_MKNOD against /dev/null might return true, while a check for
CAP_MKNOD against /dev/sda might return false.

This is interesting, but not likely to be ever implemented :)

-- 
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 1576341] Re: fails in lxd container

[Serge Hallyn]

Right you can check whether you have CAP_X targeted at your own user ns,
and you can check whether you are in an init_user_ns (by checking
/proc/self/uid_map).  The manpages currently are rarely clear, when they
say you need CAP_X, about which namespace that must be targeted against.
(I just corrected one instance in a branch).  And as you can see, if the
manpages were, they woudl be quickly out of date, since the process of
(a) deducing which capability checks can be namespaced, (b) converting
those, or (c) improving the target's namespaces so that the checks can
be namespaced (if possible) is ongoing, and will be for a long time.

-- 
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 1576403] [NEW] graphic drivers

[Arman]

Public bug reported:

Hi I bought Dell inspiron 15 with ubuntu on it. Then I did something
wrong which is spoiled  my system. So I had to reinstall it through usb
stick. Now I cant install dissent drivers.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
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: Thu Apr 28 21:31:29 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:06ac]
InstallationDate: Installed on 2016-04-28 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Dell Inc. Inspiron 15-3552
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=9993039e-0164-4e50-82fc-02800e26ac3d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 4.0.4
dmi.board.name: 01M0MH
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.4:bd01/05/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.4:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 15-3552
dmi.product.version: 4.0.4
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Apr 28 11:26:28 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1557 
 vendor BOE
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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


** Tags: amd64 apport-bug compiz-0.9 trusty 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/1576403

Title:
  graphic drivers

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi I bought Dell inspiron 15 with ubuntu on it. Then I did something
  wrong which is spoiled  my system. So I had to reinstall it through
  usb stick. Now I cant install dissent drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Thu Apr 28 21:31:29 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06ac]
  InstallationDate: Installed on 2016-04-28 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=9993039e-0164-4e50-82fc-02800e26ac3d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.4
  dmi.board.name: 01M0MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.4:bd01/05/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.4:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 

[Touch-packages] [Bug 1512327] Re: [dialer-app] Can't hang up phone calls

[Pat McGowan]

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

** This bug has been marked a duplicate of bug 1528668
   [regression] Qt.application.active not working correctly

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

Title:
  [dialer-app] Can't hang up phone calls

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Recently I had a problem with hanging up. I don't think it was just
  with incoming calls but in that case I was able to reproduce it. I
  have all the recent updates installed and I think the problem only
  occurred after the update to OTA-7.

  - Somebody calls me
  - Name appears in the dialog and I take off
  - The dialer app opens but doesn't show the name nor number nor the calling 
time but the call works
  - It is not possible to hang up the call by pressing the red button
  - I close the dialer app, the green bar at the top appears
  - I reopen it, at this point I might be able to hang up the call otherwise I 
have to redo the closing

  I couldn't find the combination which led to this issue.

  Could be related to bug #1377996.


  - UX comment ---

  The dialer should always show the contact who is calling. Also, it
  should always be possible to hang up the call.

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

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

[Touch-packages] [Bug 1408760] Re: Streaming video does not work

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  Streaming video does not work

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

Bug description:
  Try going to a https://twitch.tv and open any live stream. Hopefully
  you should be redirected to https://twitch.tv/:streamer-slug/mobile,
  where there's a video being streamed over HLS. Clicking on the play
  button makes the video look like it's initializing for a second, and
  then nothing happens. Just in case there was something funky with that
  particular implementation, I also tried it at https://hitbox.tv, but
  had the same thing happen.

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

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

[Touch-packages] [Bug 1572880] Re: Cannot call emergency number from sim lock screen if phone screen is unlocked before

[Gustavo Pichorim Boiko]

** Changed in: dialer-app (Ubuntu)
   Status: New => Triaged

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

Title:
  Cannot call emergency number from sim lock screen if phone screen is
  unlocked before

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in dialer-app package in Ubuntu:
  Triaged

Bug description:
  current build number: 4
  device name: turbo
  channel: ubuntu-touch/rc/meizu.en
  last update: 2016-04-19 10:38:50
  version version: 4
  version ubuntu: 20160418
  version device: 20160412-d272a77,

  Steps:
  1.Turn on sim pin
  2.Reboot the device
  3.Don't unlock the SIM but unlock phone screen
  4.Swipe down the indicator and select network section
  5.Tap on "Unlock sim" to bring up sim lock screen
  6.Tap on "Emergency Call" button
  7.Enter an emergency number and call

  Actual result:
  At step6, it shows regular dial pad with SIM locked header
  At step7, "SIM card is locked" dialog appears

  Expected result:
  At step6, it shows emergency dial pad with emergency header
  At step7, be able to make an emergency call

  Error also can be reproduced with krillin and arale.

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

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

[Touch-packages] [Bug 1537913] Re: Active APN is not selected

[Bill Filler]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => Bill Filler (bfiller)

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

Title:
  Active APN is not selected

Status in Canonical System Image:
  In Progress
Status in network-manager package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  The APN panel shows 3 APNs but the active APN is not selected in the UI
  MX4 running rc-proposed 230

  A krillin running ota 8.5 shows a selected APN

  The settings log contains this when viewing the page
  2016-01-25 16:06:34,484 - WARNING - 
file:///usr/share/ubuntu/settings/system/qml-plugins/cellular/apn_manager.js:50:
 Error: Unknown context type

  You can see ATT Phone should be selected

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_0 ]
  [ /ril_0/context1 ]
  Password =
  IPv6.Settings = { }
  Settings = { }
  Protocol = ip
  AccessPointName = nxtgenphone
  Type = internet
  AuthenticationMethod = chap
  MessageProxy = proxy.mobile.att.net:80
  Name = ATT Nextgenphone
  Username =
  Active = 0
  Preferred = 0
  MessageCenter = http://mmsc.mobile.att.net

  [ /ril_0/context2 ]
  Password =
  IPv6.Settings = { }
  Settings = { Gateway=10.244.204.71 Method=static 
Address=10.244.204.71 Proxy=172.26.39.1 Interface=ccmni0 ProxyPort=80 
DomainNameServers=172.26.38.1,172.26.38.2, Netmask=255.255.255.0 }
  Protocol = ip
  AccessPointName = phone
  Type = internet
  AuthenticationMethod = chap
  MessageProxy = proxy.mobile.att.net:80
  Name = ATT Phone
  Username =
  Active = 1
  Preferred = 0
  MessageCenter = http://mmsc.mobile.att.net

  [ /ril_0/context3 ]
  Password =
  IPv6.Settings = { }
  Settings = { }
  Protocol = ip
  AccessPointName = wap.cingular
  Type = internet
  AuthenticationMethod = chap
  MessageProxy = wireless.cingular.com
  Name = ATT WAP
  Username =
  Active = 0
  Preferred = 0
  MessageCenter = http://mmsc.cingular.com/

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

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

[Touch-packages] [Bug 1576409] Re: calling init.d script with "status" invokes pager

[Martin Pitt]

http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=e308302dc

** Changed in: systemd (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: systemd (Ubuntu)
 Assignee: Martin Pitt (pitti) => (unassigned)

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

Title:
  calling init.d script with "status" invokes pager

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd package in Debian:
  Unknown

Bug description:
  Running e. g. "/etc/init.d/networking status" runs a pager (less by
  default). This is unexpected from an init.d script, and potentially
  breaks scripts or CLI programs that do this operation, as this then
  hangs eternally in the interactive pager process until the user quits
  it. This reportedly happens with "vagrant up" (see original Debian bug
  https://bugs.debian.org/765175).

  SRU INFORMATION:
  Test case:
   Run "/etc/init.d/networking status". In current xenial this invokes less 
which you need to quit. With the proposed fix this should return to the shell 
immediately without a pager.

  Regression potential:  very low. The main visible change is the
  interactive usage of "/etc/init.d/foo status", but nothing in Ubuntu
  (nor hopefully anywhere else) *relies* on the fact that systemctl
  invokes a pager, particularly as this is not always done (it depends
  on whether stdout is a terminal and how many lines are written).

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

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

[Touch-packages] [Bug 1576367] Re: Aquaris M10 tablet can't connect to bluetooth version 4.0 devices

[Tomas Öqvist]

Interestingly I managed to pair the Designer Mouse through bluetoothctl
in the terminal. It is still not recognized by the bluetooth system
settings though, which shows only my connected keyboard!!

My trick seems to survive a reboot, but I have to turn bluetooth off and
then on again for the mouse to become reenabled. Remains to be seen if
this trick will work with the foldable keyboard as well.

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

Title:
  Aquaris M10 tablet can't connect to bluetooth version 4.0 devices

Status in bluez package in Ubuntu:
  New

Bug description:
  I have tried to pair my Bq Aquaris M10 running Ubuntu 15.05 (OTA-10.1)
  to Microsofts Universal Foldable Keyboard and Designer Moust, both
  equipped with bluetooth version 4.0 through the bluetooth settings on
  the tablet.

  Expected behaviour:
  Search and discover device
  Click on device and choose "pair"

  What happens:
  Nothing
  None of the devices above are being discovered in the bluetooth settings.

  The command

  dpkg --status bluez | grep '^Version:'

  on the tablet gives me:

  Version: 5.37-0ubuntu5-overlay1

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

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

[Touch-packages] [Bug 1488364] Re: [Qt 5.5] OxideQSslCertificate::issuer doesn't work in Qml

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: New => In Progress

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

Title:
  [Qt 5.5] OxideQSslCertificate::issuer doesn't work in Qml

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Triaged
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  New

Bug description:
  With older Qt versions, we use private APIs (QQmlValueType and
  friends) for exposing value types. However, with the built-in gadget
  support in Qt5.5, OxideQSslCertificate::issuer() is no longer working
  correctly.

  - When OxideQSecurityStatus::certificate() returns a null QVariant, the value 
gets converted to null in Qml. When it returns a QVariant containing 
OxideQSslCertificate, this gets correctly converted to a value type in Qml.
  - The QVariant returned from OxideQSslCertificate::issuer() gets converted to 
an object in Qml (verified with typeof), and calling toString() on the object 
gives "QVariant(QVariant): undefined".

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

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

[Touch-packages] [Bug 1576409] [NEW] calling init.d script with "status" invokes pager

[Martin Pitt]

Public bug reported:

Running e. g. "/etc/init.d/networking status" runs a pager (less by
default). This is unexpected from an init.d script, and potentially
breaks scripts or CLI programs that do this operation, as this then
hangs eternally in the interactive pager process until the user quits
it. This reportedly happens with "vagrant up" (see original Debian bug
https://bugs.debian.org/765175).

SRU INFORMATION:
Test case:
 Run "/etc/init.d/networking status". In current xenial this invokes less which 
you need to quit. With the proposed fix this should return to the shell 
immediately without a pager.

Regression potential:  very low. The main visible change is the
interactive usage of "/etc/init.d/foo status", but nothing in Ubuntu
(nor hopefully anywhere else) *relies* on the fact that systemctl
invokes a pager, particularly as this is not always done (it depends on
whether stdout is a terminal and how many lines are written).

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: systemd (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: systemd (Debian)
 Importance: Unknown
 Status: Unknown

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Bug watch added: Debian Bug tracker #765175
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765175

** Also affects: systemd (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765175
   Importance: Unknown
   Status: Unknown

** Changed in: systemd (Ubuntu)
   Status: New => In Progress

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  calling init.d script with "status" invokes pager

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd package in Debian:
  Unknown

Bug description:
  Running e. g. "/etc/init.d/networking status" runs a pager (less by
  default). This is unexpected from an init.d script, and potentially
  breaks scripts or CLI programs that do this operation, as this then
  hangs eternally in the interactive pager process until the user quits
  it. This reportedly happens with "vagrant up" (see original Debian bug
  https://bugs.debian.org/765175).

  SRU INFORMATION:
  Test case:
   Run "/etc/init.d/networking status". In current xenial this invokes less 
which you need to quit. With the proposed fix this should return to the shell 
immediately without a pager.

  Regression potential:  very low. The main visible change is the
  interactive usage of "/etc/init.d/foo status", but nothing in Ubuntu
  (nor hopefully anywhere else) *relies* on the fact that systemctl
  invokes a pager, particularly as this is not always done (it depends
  on whether stdout is a terminal and how many lines are written).

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

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

[Touch-packages] [Bug 1437485] Re: No video on youtube when on GSM/3g

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  No video on youtube when on GSM/3g

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

Bug description:
  Using my ubuntu phone, When I'm on wifi everything is fine I go to
  m.youtube.com in the browser navigate to a video hit play and
  everything is fine picture and sound work as expected. I turn off wifi
  reopen the browser and do the same thing and I get audio but no
  picture.

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

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

[Touch-packages] [Bug 1576420] [NEW] [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts or crackling sound

[Maceatron]

Public bug reported:

crackling and noisy audio out of only LH speaker.  Only recently started
on upgrade to 16.04.  Previous versions worked correctly with no
changes.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tron   1912 F pulseaudio
 /dev/snd/controlC0:  tron   1912 F pulseaudio
CurrentDesktop: Unity
Date: Fri Apr 29 07:17:59 2016
InstallationDate: Installed on 2016-04-24 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts or 
crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/04/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: H55M-D2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd05/04/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-D2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H55M-D2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: apport-bug i386 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/1576420

Title:
  [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts
  or crackling sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  crackling and noisy audio out of only LH speaker.  Only recently
  started on upgrade to 16.04.  Previous versions worked correctly with
  no changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tron   1912 F pulseaudio
   /dev/snd/controlC0:  tron   1912 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr 29 07:17:59 2016
  InstallationDate: Installed on 2016-04-24 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts 
or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: H55M-D2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd05/04/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-D2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H55M-D2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1576235] Re: FTBFS - ubuntu-keyboard - xenial arm64

[Launchpad Bug Tracker]

** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-1576235

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

Title:
  FTBFS - ubuntu-keyboard - xenial arm64

Status in Canonical System Image:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  ubuntu-keyboard fails to build on xenial arm64

  https://launchpad.net/ubuntu/+source/ubuntu-
  keyboard/0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1/+build/9278079

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

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

[Touch-packages] [Bug 1569292] Re: Can't join to AD domain

[Alex Morris]

I'm a total noob to all of this stuff. But I've been struggling and
struggling with this for a week.

Adding the PPA and updating the package got this fixed.

Thanks so much! I was so excited when I found this.

Let me know if I can help going forward!

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

Title:
  Can't join to AD domain

Status in realmd:
  New
Status in packagekit package in Ubuntu:
  In Progress
Status in packagekit source package in Xenial:
  In Progress

Bug description:
  [Impact]

  When trying to join AD domain via realm command, it hangs.
  after researching, packagekit got segfault.

  [Testcase]

  realm -v join int.domainname.com --user login

   * Resolving: _ldap._tcp.int.domanname.com
   * Performing LDAP DSE lookup on: 192.168.xx.xx
   * Performing LDAP DSE lookup on: 192.168.xx.xx
   * Successfully discovered: int.domainname.com
  Password for login:
   * Unconditionally checking packages
   * Resolving required packages

  From here nothing happens. It doesn't go any further.

  journalctl -b realmd shows:
  [...]
  Apr 12 13:02:49 ls-mysql57 realmd[946]: Sending TCP Netlogon request
  Apr 12 13:02:49 ls-mysql57 realmd[946]: Searching  for (objectClass=*)
  Apr 12 13:02:49 ls-mysql57 realmd[946]: Received TCP Netlogon response
  Apr 12 13:02:49 ls-mysql57 realmd[946]:  * Successfully discovered: 
int.domainname.com
  Apr 12 13:02:49 ls-mysql57 realmd[946]:  * Successfully discovered: 
int.domainame.com
  Apr 12 13:02:53 ls-mysql57 realmd[946]: Using 'r209.955' operation for method 
'Join' invocation on 'org.freedesktop.realmd.KerberosMembership' interface
  Apr 12 13:02:53 ls-mysql57 realmd[946]: Registered cancellable for operation 
'r209.955'
  Apr 12 13:02:53 ls-mysql57 realmd[946]: holding daemon: current-invocation
  Apr 12 13:02:53 ls-mysql57 realmd[946]: ** (realmd:946): CRITICAL **: 
realm_invocation_get_cancellable: assertion 'invocation != NULL' failed
  Apr 12 13:02:53 ls-mysql57 realmd[946]: (realmd:946): GLib-GObject-CRITICAL 
**: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  Apr 12 13:02:53 ls-mysql57 realmd[946]:  * Unconditionally checking packages
  Apr 12 13:02:53 ls-mysql57 realmd[946]:  * Unconditionally checking packages
  Apr 12 13:02:53 ls-mysql57 realmd[946]:  * Resolving required packages
  Apr 12 13:02:53 ls-mysql57 realmd[946]:  * Resolving required packages
  Apr 12 13:02:53 ls-mysql57 realmd[946]: realm_invocation_get_cancellable: 
assertion 'invocation != NULL' failed
  Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: CreateTransaction call
  Apr 12 13:02:53 ls-mysql57 realmd[946]: GLib-GObject: g_object_unref: 
assertion 'G_IS_OBJECT (object)' failed
  Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: SetHints call
  Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: call Resolve (262144, 
['sssd-tools', 'sssd', 'libnss-sss', 'libpam-sss', 'adcli'])
  Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed ()
  Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: call Resolve completed
  Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed ()
  Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed ()
  Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed ()

  It works in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: realmd 0.16.2-2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Tue Apr 12 13:08:33 2016
  SourcePackage: realmd
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Regression Potential]

  [Other Info]
  Upstream Patch
  
https://github.com/hughsie/PackageKit/commit/97161e231b2ab406e77977a2a693d7935e33df0f
  
https://github.com/hughsie/PackageKit/commit/06fae067c909db93bb5b1e1d04aa7a987208eda2
  
https://github.com/hughsie/PackageKit/commit/c64c16c2d1ad9142ec8e74473044874bb6398728
  
https://github.com/hughsie/PackageKit/commit/e94b80f90179db18221b2eff93b4561b5418fbfb

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

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

[Touch-packages] [Bug 1576311] [NEW] Cancel search executes run() twice

[Kyle Nitzsche]

Public bug reported:

OTA10:

I find that on tapping Cancel after entering a search query, the scope's
run() method executes twice.

For example: calls-scope always prints "CALLS starting" on entering
run().

While watching scope-registry.log:
(launch or refresh calls-scope)
CAllS starting
(enter query string)
CALLS starting
(tap Cancel)
CALLS starting
CALLS starting

There should not be two entries after tapping cancel.

** Affects: canonical-scopes-project
 Importance: Undecided
 Status: Triaged

** Affects: unity-scopes-shell (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: canonical-scopes-project
   Importance: Undecided
   Status: New

** Changed in: canonical-scopes-project
   Status: New => Triaged

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

Title:
  Cancel search executes run() twice

Status in canonical-scopes-project:
  Triaged
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  OTA10:

  I find that on tapping Cancel after entering a search query, the
  scope's run() method executes twice.

  For example: calls-scope always prints "CALLS starting" on entering
  run().

  While watching scope-registry.log:
  (launch or refresh calls-scope)
  CAllS starting
  (enter query string)
  CALLS starting
  (tap Cancel)
  CALLS starting
  CALLS starting

  There should not be two entries after tapping cancel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-scopes-project/+bug/1576311/+subscriptions

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

[Touch-packages] [Bug 1575319] [NEW] [Ubuntu Touch] Manage Scopes doesn't scroll up/down when modifying position

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When managing the order of available scopes, if the list of scopes is
longer than what can be shown on the screen, dragging scope to top or
bottom of screen doesn't automatically begin to scroll screen.  Scope
would have to be dropped near then top, then scroll screen, then move
scope into final position.

** Affects: canonical-devices-system-image
 Importance: Medium
 Status: Confirmed

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

-- 
[Ubuntu Touch] Manage Scopes doesn't scroll up/down when modifying position
https://bugs.launchpad.net/bugs/1575319
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity8 in Ubuntu.

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

[Touch-packages] [Bug 1576316] [NEW] User cannot change Input source

[Jonas G. Drange]

Public bug reported:

Log:
http://pastebin.ubuntu.com/16097735/

Could be related to bug 1512002?

What happens:
User tries to change input source on own user and is asked to authenticate:

phablet@ubuntu-phablet:~$  gdbus call -y -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User32011 -m 
org.freedesktop.Accounts.User.SetInputSources "[{'xkb': 'en'}]"
Error: GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: 
Authentication is required
(According to introspection data, you need to pass 'aa{ss}')

What should happen:
Not sure if this is a regression or what? We call this from System Settings—do 
we have to change it?

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Affects: ubuntu-system-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  User cannot change Input source

Status in Canonical System Image:
  New
Status in accountsservice package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Log:
  http://pastebin.ubuntu.com/16097735/

  Could be related to bug 1512002?

  What happens:
  User tries to change input source on own user and is asked to authenticate:

  phablet@ubuntu-phablet:~$  gdbus call -y -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User32011 -m 
org.freedesktop.Accounts.User.SetInputSources "[{'xkb': 'en'}]"
  Error: GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: 
Authentication is required
  (According to introspection data, you need to pass 'aa{ss}')

  What should happen:
  Not sure if this is a regression or what? We call this from System 
Settings—do we have to change it?

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

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

[Touch-packages] [Bug 1576316] Re: User cannot change Input source

[Jonas G. Drange]

Could this [1] explain it?

[1]
http://launchpadlibrarian.net/254485305/accountsservice_0.6.40-2ubuntu9_0.6.40-2ubuntu10.diff.gz

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

Title:
  User cannot change Input source

Status in Canonical System Image:
  New
Status in accountsservice package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Log:
  http://pastebin.ubuntu.com/16097735/

  Could be related to bug 1512002?

  What happens:
  User tries to change input source on own user and is asked to authenticate:

  phablet@ubuntu-phablet:~$  gdbus call -y -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User32011 -m 
org.freedesktop.Accounts.User.SetInputSources "[{'xkb': 'en'}]"
  Error: GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: 
Authentication is required
  (According to introspection data, you need to pass 'aa{ss}')

  What should happen:
  Not sure if this is a regression or what? We call this from System 
Settings—do we have to change it?

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

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

[Touch-packages] [Bug 1576327] [NEW] I keep getting your computer has a problem dialog.

[Herbert Smith]

Public bug reported:

I can't download and install some programs.  My computer  sometimes just
stall and will not continue.  Sorry I'm a newbe on linux but I thank you
for trying to help me.

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:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Apr 28 12:39:52 2016
DistUpgraded: 2016-04-21 22:29:31,752 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-04-21 (7 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Gigabyte Technology Co., Ltd. G1.Sniper H6
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=8bf2503e-6ed8-4199-979b-790339fd484f ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-22 (6 days ago)
dmi.bios.date: 04/21/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: G1.Sniper H6
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperH6:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperH6:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: G1.Sniper H6
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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: Thu Apr 28 12:31:28 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1179 
 vendor SAM
xserver.version: 2:1.18.3-1ubuntu2

** 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/1576327

Title:
  I keep getting your computer has a problem dialog.

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't download and install some programs.  My computer  sometimes
  just stall and will not continue.  Sorry I'm a newbe on linux but I
  thank you for trying to help me.

  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:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Apr 28 12:39:52 2016
  DistUpgraded: 2016-04-21 22:29:31,752 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 

[Touch-packages] [Bug 1576298] [NEW] PageHeader tutorial as UITK doc

[Tim Peeters]

Public bug reported:

Add this tutorial https://developer.ubuntu.com/en/blog/2016/02/24
/pageheader-tutorial/ as documentation in the UITK.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Medium
 Assignee: Tim Peeters (tpeeters)
 Status: Confirmed

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

Title:
  PageHeader tutorial as UITK doc

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Add this tutorial https://developer.ubuntu.com/en/blog/2016/02/24
  /pageheader-tutorial/ as documentation in the UITK.

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

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

[Touch-packages] [Bug 1575301] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

[Titus]

I am having the same problem if I open a protected Libreoffice Writer
document. The system goes back to the login screen as soon as I enter a
password.

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

Title:
  GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice
  dialog boxes (regression)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.

  Dialog boxes in LibreOffice (including the automated recovery dialog
  on LO start) started displaying garbled text and garbled or missing
  button icons. Interacting with them -- or often even their appearance
  at all -- causes a rapid crash of the whole graphical session and a
  free trip back to the login screen.  Syslog shows a GPU hang (stuck on
  render ring).

  This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
  Controller (HP Envy x360 convertible laptop).

  Before the upgrade from 15.10 to 16.04, I had the xorg-edgers
  repository enabled and then had used the installation tool from 01.org
  to install the Intel graphics stack.  As part of troubleshooting this,
  I have removed/purged the 01.org sources/packages/modules as best I
  could (16.04 not supported) and also disabled the edgers repository.
  This has not affected the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:04:07 2016
  DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
  InstallationDate: Installed on 2014-08-10 (625 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard
  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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 14:02:01 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "intel" (module does not exist, 0)
   Failed to load module "intel" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Touch-packages] [Bug 1566741] Re: Tabs and Page with PageHeader shows two headers

[Tim Peeters]

We do not support using Tabs in combination with PageHeader. We need to
document that, see this bug https://bugs.launchpad.net/ubuntu/+source
/ubuntu-ui-toolkit/+bug/1566735

There will be new tab designs though, and we need to evaluate those to
see if we will update the current Tabs component for those patterns
(then we have to make it work with PageHeader), or we completely
deprecated the old Tabs and we don't fix this bug.

I will try to get the new designs so we can make a more-informed
decision.

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

Title:
  Tabs and Page with PageHeader shows two headers

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  If I use a Tabs component, and place a Page in one of the Tabs, and
  that Page has a new-style PageHeader, then my app shows two separate
  headers.

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  width: units.gu(70)
  height: units.gu(80)
  Tabs {
  Tab {
  page:Page {
  header: PageHeader {
  id: pageHeader
  title: i18n.tr("MyApp")
  }
  }
  }
  Tab {
  title: i18n.tr("Simple page")
  page: Page {
  Label {
  id: label
  anchors.centerIn: parent
  text: "A centered label"
  }
  }
  }
  }
  }

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

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

[Touch-packages] [Bug 1566735] Re: Tabs documentation does not mention that Tabs are deprecated

[Tim Peeters]

Question for design: The current Tabs pattern is completely deprecated,
right? We will have a new pattern for that to be used with the new
PageHeader and AdaptivePageLayout. For that, we'll need new API as well
so we deprecate the old Tabs in UITK 1.3.

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Tabs documentation does not mention that Tabs are deprecated

Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  The Tabs documentation at
  https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.Tabs/
  does not mention that the Tabs component and navigation pattern are
  apparently deprecated, according to
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1539759.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1566735/+subscriptions

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

[Touch-packages] [Bug 1576066] Re: 32bit glibc calls old socketcall() syscall, causing seccomp problems

[Jamie Strandboge]

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

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

Title:
  32bit glibc calls old socketcall() syscall, causing seccomp problems

Status in glibc package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New

Bug description:
  Back in the day when Linux was created for i386, for who knows what
  reason, all socket calls were multiplexed through a single syscall
  API, socketcall().  This was a strange thing to do, but it probably
  made sense from the standpoint of the same part of the kernel handling
  all of those calls.

  It was realised a long time ago that this was a strange and suboptimal
  arrangement.

  By the time they got around to doing amd64 and other architectures,
  they fixed this arrangement and gave each socket call a separate
  syscall entry point.  32bit systems continued to do it this old way,
  however, multiplexing all calls through socketcall().

  This is a problem for seccomp.  If we want to allow a program to make
  casual use of the network, but not bind a listener socket, we cannot
  currently do that.  On 64bits we just filter out the bind() and
  listen() calls, but on 32bit, it's all the same syscall.

  The kernel people fixed this problem up last summer by introducing
  new, separate, syscall entries for each separate call.

http://patchwork.sourceware.org/patch/7679/

  The problem is that glibc in Y is still using the old socketcall()
  interface on i386.  It needs to be updated to use the new calls.

  A possible caveat is that this might create problems for running newer
  binaries on older kernels on i386 (as we sometimes do with builders)
  because they won't have the new syscalls.  A solution could involve
  checking for ENOSYS and trying again via the old route.

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

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

[Touch-packages] [Bug 1575319] Re: [Ubuntu Touch] Manage Scopes doesn't scroll up/down when modifying position

[Rodney Dawes]

** Package changed: unity-scope-click (Ubuntu) => unity8 (Ubuntu)

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

Title:
  [Ubuntu Touch] Manage Scopes doesn't scroll up/down when modifying
  position

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  When managing the order of available scopes, if the list of scopes is
  longer than what can be shown on the screen, dragging scope to top or
  bottom of screen doesn't automatically begin to scroll screen.  Scope
  would have to be dropped near then top, then scroll screen, then move
  scope into final position.

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

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

[Touch-packages] [Bug 1576294] [NEW] slow pc

[Javier]

Public bug reported:

my pc is slower and  display resolution is low.

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.1:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog:
 [  OK  ] Started Detect the available GPUs and deal with any system 
changes.
  Starting Light Display Manager...
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Apr 28 08:23:53 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates-core, 15.201, 4.2.0-35-generic, x86_64: installed
 virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
 virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 
6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-04-05 (22 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. OptiPlex 320
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=5e7fc8e4-1af7-4a07-8eac-46decfa65538 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.12
dmi.board.name: 0CU395
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.12:bd06/17/2009:svnDellInc.:pnOptiPlex320:pvr:rvnDellInc.:rn0CU395:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: OptiPlex 320
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: Thu Apr 28 07:31:59 2016
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2

** 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/1576294

Title:
  slow pc

Status in xorg package in Ubuntu:
  New

Bug description:
  my pc is slower and  display resolution is low.

  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.1:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   [  OK  ] Started Detect the available GPUs and deal with any system 
changes.
Starting Light Display Manager...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Apr 28 08:23:53 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates-core, 15.201, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 
6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-04-05 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. OptiPlex 320
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=5e7fc8e4-1af7-4a07-8eac-46decfa65538 ro quiet 

[Touch-packages] [Bug 1576260] Re: Can't VT switch from mir_demo_server

[Alan Griffiths]

I've not encountered this problem - VT switching works for me (on
desktop and a couple of Thinkpad laptops).

Is this specific to certain devices?

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

Title:
  Can't VT switch from mir_demo_server

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in mir source package in Xenial:
  New

Bug description:
  I can't VT switch from mir_demo_server. This turns out to be an issue
  that occurred in 16.04 where /dev/console no longer works with VT
  switching. Using /dev/tty0 work. See bug 1566073 for associated change
  in LightDM.

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

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

[Touch-packages] [Bug 1576260] Re: Can't VT switch from mir_demo_server

[Alan Griffiths]

I've not encountered this problem - VT switching works for me (on
desktop and a couple of Thinkpad laptops).

Is this specific to certain devices?

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

Title:
  Can't VT switch from mir_demo_server

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in mir source package in Xenial:
  New

Bug description:
  I can't VT switch from mir_demo_server. This turns out to be an issue
  that occurred in 16.04 where /dev/console no longer works with VT
  switching. Using /dev/tty0 work. See bug 1566073 for associated change
  in LightDM.

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

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

[Touch-packages] [Bug 1576066] Re: 32bit glibc calls old socketcall() syscall, causing seccomp problems

[Jamie Strandboge]

I'll take a look at this. I'll try an updated libseccomp with xenial's
glibc and a > 4.2 kernel and if this works, I'll pursue an SRU. Is there
a simple test case or snap that I can use to verify it is broken with
old seccomp and working with new?

** Changed in: libseccomp (Ubuntu)
   Importance: Undecided => High

** Changed in: libseccomp (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

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

Title:
  32bit glibc calls old socketcall() syscall, causing seccomp problems

Status in glibc package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  Incomplete

Bug description:
  Back in the day when Linux was created for i386, for who knows what
  reason, all socket calls were multiplexed through a single syscall
  API, socketcall().  This was a strange thing to do, but it probably
  made sense from the standpoint of the same part of the kernel handling
  all of those calls.

  It was realised a long time ago that this was a strange and suboptimal
  arrangement.

  By the time they got around to doing amd64 and other architectures,
  they fixed this arrangement and gave each socket call a separate
  syscall entry point.  32bit systems continued to do it this old way,
  however, multiplexing all calls through socketcall().

  This is a problem for seccomp.  If we want to allow a program to make
  casual use of the network, but not bind a listener socket, we cannot
  currently do that.  On 64bits we just filter out the bind() and
  listen() calls, but on 32bit, it's all the same syscall.

  The kernel people fixed this problem up last summer by introducing
  new, separate, syscall entries for each separate call.

http://patchwork.sourceware.org/patch/7679/

  The problem is that glibc in Y is still using the old socketcall()
  interface on i386.  It needs to be updated to use the new calls.

  A possible caveat is that this might create problems for running newer
  binaries on older kernels on i386 (as we sometimes do with builders)
  because they won't have the new syscalls.  A solution could involve
  checking for ENOSYS and trying again via the old route.

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

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

[Touch-packages] [Bug 1575301] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

[Launchpad Bug Tracker]

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

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

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

Title:
  GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice
  dialog boxes (regression)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.

  Dialog boxes in LibreOffice (including the automated recovery dialog
  on LO start) started displaying garbled text and garbled or missing
  button icons. Interacting with them -- or often even their appearance
  at all -- causes a rapid crash of the whole graphical session and a
  free trip back to the login screen.  Syslog shows a GPU hang (stuck on
  render ring).

  This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
  Controller (HP Envy x360 convertible laptop).

  Before the upgrade from 15.10 to 16.04, I had the xorg-edgers
  repository enabled and then had used the installation tool from 01.org
  to install the Intel graphics stack.  As part of troubleshooting this,
  I have removed/purged the 01.org sources/packages/modules as best I
  could (16.04 not supported) and also disabled the edgers repository.
  This has not affected the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:04:07 2016
  DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
  InstallationDate: Installed on 2014-08-10 (625 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard
  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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 14:02:01 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "intel" (module does not exist, 0)
   Failed to load module "intel" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Touch-packages] [Bug 1576302] [NEW] Cannot use keyboard to navigate the UITK gallery in single-column mode

[Tim Peeters]

Public bug reported:

Start the UITK gallery, and resize the window to have a single column.

Now, with TAB you can navigate between the actions in the header, and
the ListView with that list the different Pages with components. But it
is not possible to use the arrow keys to select a ListItem, and then
press ENTER/SPACE to open that page, because pressing the arrow
(up/down) key automatically triggers the ListItem (onClicked?) and opens
the Page. So only the first Page (ActionBar) can be opened using
keyboard navigation when you have only one column.

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Description changed:

  Start the UITK gallery, and resize the window to have a single column.
  
  Now, with TAB you can navigate between the actions in the header, and
- the ListItems in the listview that list the different Pages with
- components. But it is not possible to use the arrow keys to select a
- ListItem, and then press ENTER/SPACE to open that page, because pressing
- the arrow (up/down) key automatically triggers the ListItem (onClicked?)
- and opens the Page. So only the first Page (ActionBar) can be opened
- using keyboard navigation when you have only one column.
+ the ListView with that list the different Pages with components. But it
+ is not possible to use the arrow keys to select a ListItem, and then
+ press ENTER/SPACE to open that page, because pressing the arrow
+ (up/down) key automatically triggers the ListItem (onClicked?) and opens
+ the Page. So only the first Page (ActionBar) can be opened using
+ keyboard navigation when you have only one column.

** Summary changed:

- Cannot use keyboard focus to navigate the UITK gallery
+ Cannot use keyboard focus to navigate the UITK gallery in single-column mode

** Summary changed:

- Cannot use keyboard focus to navigate the UITK gallery in single-column mode
+ Cannot use keyboard to navigate the UITK gallery in single-column mode

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

Title:
  Cannot use keyboard to navigate the UITK gallery in single-column mode

Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Start the UITK gallery, and resize the window to have a single column.

  Now, with TAB you can navigate between the actions in the header, and
  the ListView with that list the different Pages with components. But
  it is not possible to use the arrow keys to select a ListItem, and
  then press ENTER/SPACE to open that page, because pressing the arrow
  (up/down) key automatically triggers the ListItem (onClicked?) and
  opens the Page. So only the first Page (ActionBar) can be opened using
  keyboard navigation when you have only one column.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1576302/+subscriptions

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

[Touch-packages] [Bug 1576314] [NEW] Wifi fails to resume from standby

[Alex]

Public bug reported:

System fails to detect any Wifi network SSID's on resume from standby 
sudo service network-manager restart brings the list of wireless network back 
in operation and you can continue as normal until next standby. Or a full 
system restart. Wireless card replaced with another working model. System fully 
patched as of 28.04.2016

 description: Wireless interface
   product: Wireless 7260
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:02:00.0
   logical name: wlp2s0
   version: 73
   serial: 0c:8b:fd:b5:7c:0f
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-21-generic firmware=16.242414.0 ip=10.10.10.239 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
   resources: irq:47 memory:f7a0-f7a01fff

Description:Ubuntu 16.04 LTS
Release:16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 28 17:17:33 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-04-15 (13 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
IpRoute:
 default via 10.10.10.1 dev wlp2s0  proto static  metric 600 
 10.10.10.0/23 dev wlp2s0  proto kernel  scope link  src 10.10.10.239  metric 
600 
 169.254.0.0/16 dev wlp2s0  scope link  metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1576314

Title:
  Wifi fails to resume from standby

Status in network-manager package in Ubuntu:
  New

Bug description:
  System fails to detect any Wifi network SSID's on resume from standby 
  sudo service network-manager restart brings the list of wireless network back 
in operation and you can continue as normal until next standby. Or a full 
system restart. Wireless card replaced with another working model. System fully 
patched as of 28.04.2016

   description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 73
 serial: 0c:8b:fd:b5:7c:0f
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-21-generic firmware=16.242414.0 ip=10.10.10.239 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
 resources: irq:47 memory:f7a0-f7a01fff

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 28 17:17:33 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-15 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 10.10.10.1 dev wlp2s0  proto static  metric 600 
   10.10.10.0/23 dev wlp2s0  proto kernel  scope link  src 10.10.10.239  metric 
600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1576314/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1576254] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[Martin Pitt]

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

** This bug has been marked a duplicate of bug 1560797
   apt does not configure Pre-Depends: before depending package

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

Title:
  package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  New

Bug description:
  trying to use dist upgrade to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 08:35:45 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2016-04-27 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576260] Re: Can't VT switch from mir_demo_server

[Robert Ancell]

My guess it that it is video driver / hardware dependent, but I wasn't
able to exactly pinpoint where the issue is. I couldn't find any
documentation as to which device is the correct one to use, but
/dev/tty0 seems to be used by larger projects (logind, GDM) and thus is
probably better tested.

I'm using a Toshiba P50W with Intel Haswell-ULT graphics and running
16.04 LTS.

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

Title:
  Can't VT switch from mir_demo_server

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in mir source package in Xenial:
  New

Bug description:
  I can't VT switch from mir_demo_server. This turns out to be an issue
  that occurred in 16.04 where /dev/console no longer works with VT
  switching. Using /dev/tty0 work. See bug 1566073 for associated change
  in LightDM.

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

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

[Touch-packages] [Bug 1576066] Re: 32bit glibc calls old socketcall() syscall, causing seccomp problems

[Sebastien Bacher]

@Jamie, the gnome-calculator one on i386 with confinment enabled hits a
system call error, I'm happy to test candidate debs if that's useful

** Tags added: snap-desktop-issue

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

Title:
  32bit glibc calls old socketcall() syscall, causing seccomp problems

Status in glibc package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New

Bug description:
  Back in the day when Linux was created for i386, for who knows what
  reason, all socket calls were multiplexed through a single syscall
  API, socketcall().  This was a strange thing to do, but it probably
  made sense from the standpoint of the same part of the kernel handling
  all of those calls.

  It was realised a long time ago that this was a strange and suboptimal
  arrangement.

  By the time they got around to doing amd64 and other architectures,
  they fixed this arrangement and gave each socket call a separate
  syscall entry point.  32bit systems continued to do it this old way,
  however, multiplexing all calls through socketcall().

  This is a problem for seccomp.  If we want to allow a program to make
  casual use of the network, but not bind a listener socket, we cannot
  currently do that.  On 64bits we just filter out the bind() and
  listen() calls, but on 32bit, it's all the same syscall.

  The kernel people fixed this problem up last summer by introducing
  new, separate, syscall entries for each separate call.

http://patchwork.sourceware.org/patch/7679/

  The problem is that glibc in Y is still using the old socketcall()
  interface on i386.  It needs to be updated to use the new calls.

  A possible caveat is that this might create problems for running newer
  binaries on older kernels on i386 (as we sometimes do with builders)
  because they won't have the new syscalls.  A solution could involve
  checking for ENOSYS and trying again via the old route.

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

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

[Touch-packages] [Bug 1576314] Re: Wifi fails to resume from standby

[Alex]

Dell Latitude E5540 tested
system76 bonobo extreme (will submit wifi card info once home)

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

Title:
  Wifi fails to resume from standby

Status in network-manager package in Ubuntu:
  New

Bug description:
  System fails to detect any Wifi network SSID's on resume from standby 
  sudo service network-manager restart brings the list of wireless network back 
in operation and you can continue as normal until next standby. Or a full 
system restart. Wireless card replaced with another working model. System fully 
patched as of 28.04.2016

   description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 73
 serial: 0c:8b:fd:b5:7c:0f
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-21-generic firmware=16.242414.0 ip=10.10.10.239 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
 resources: irq:47 memory:f7a0-f7a01fff

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 28 17:17:33 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-15 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 10.10.10.1 dev wlp2s0  proto static  metric 600 
   10.10.10.0/23 dev wlp2s0  proto kernel  scope link  src 10.10.10.239  metric 
600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1576314/+subscriptions

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

[Touch-packages] [Bug 1576327] Re: I keep getting your computer has a problem dialog.

[Herbert Smith]

WOW I'm amazed at what it the bug finder does1

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

Title:
  I keep getting your computer has a problem dialog.

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't download and install some programs.  My computer  sometimes
  just stall and will not continue.  Sorry I'm a newbe on linux but I
  thank you for trying to help me.

  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:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Apr 28 12:39:52 2016
  DistUpgraded: 2016-04-21 22:29:31,752 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2016-04-21 (7 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. G1.Sniper H6
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=8bf2503e-6ed8-4199-979b-790339fd484f ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (6 days ago)
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G1.Sniper H6
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperH6:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperH6:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: G1.Sniper H6
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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: Thu Apr 28 12:31:28 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1179 
   vendor SAM
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1576350] [NEW] wget crashes when terminal becomes too small

[fish]

Public bug reported:

If started in a terminal which is too small, it crashes right away.
If started in a bigger terminal which then gets resized, it crashes on resize:

```
ft {0, 947927})
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\\0\0\0\0\0\0\0\0\0"..., 8192) 
= 4344
write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\00\0\0\0\0\0\0\0\0\0"..., 
4096) = 4096
write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\00\0\0\0\0\0\0\0\0\0"..., 248) 
= 248
select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3ft {0, 949783})
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\\0\0\0\0\0\0\0\0\0"..., 8192) 
= 2896
write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\00\0\0\0\0\0\0\0\0\0"..., 
2896) = 2896
select(4, [3], NULL, NULL, {0, 95}) = ? ERESTARTNOHAND (To be restarted if 
no handler)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
rt_sigaction(SIGWINCH, {0x55fd9fdccb50, [WINCH], SA_RESTORER|SA_RESTART, 
0x7fc6eb3844a0}, {0x55fd9fdccb50, [WINCH], SA_RESTORER|SA_RESTART, 
0x7fc6eb3844a0}, 8) = 0
rt_sigreturn({mask=[]}) = -1 EINTR (Interrupted system call)
select(4, [3], NULL, NULL, {0, 923204}) = 1 (in [3], left {0, 916417})
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
8192) = 2896
write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
2896) = 2896
ioctl(2, TIOCGWINSZ, {ws_row=49, ws_col=50, ws_xpixel=819, ws_ypixel=1542}) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x55fda0a43000} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
```

Here is a little screencast demoing it: http://5pi.de/wget-crash.gif

- Ubuntu 16.04 LTS
- wget 1.17.1-1ubuntu1

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

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

Title:
  wget crashes when terminal becomes too small

Status in wget package in Ubuntu:
  New

Bug description:
  If started in a terminal which is too small, it crashes right away.
  If started in a bigger terminal which then gets resized, it crashes on resize:

  ```
  ft {0, 947927})
  read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\\0\0\0\0\0\0\0\0\0"..., 
8192) = 4344
  write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\00\0\0\0\0\0\0\0\0\0"..., 
4096) = 4096
  write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\00\0\0\0\0\0\0\0\0\0"..., 
248) = 248
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3ft {0, 949783})
  read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\\0\0\0\0\0\0\0\0\0"..., 
8192) = 2896
  write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\00\0\0\0\0\0\0\0\0\0"..., 
2896) = 2896
  select(4, [3], NULL, NULL, {0, 95}) = ? ERESTARTNOHAND (To be restarted 
if no handler)
  --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
  rt_sigaction(SIGWINCH, {0x55fd9fdccb50, [WINCH], SA_RESTORER|SA_RESTART, 
0x7fc6eb3844a0}, {0x55fd9fdccb50, [WINCH], SA_RESTORER|SA_RESTART, 
0x7fc6eb3844a0}, 8) = 0
  rt_sigreturn({mask=[]}) = -1 EINTR (Interrupted system call)
  select(4, [3], NULL, NULL, {0, 923204}) = 1 (in [3], left {0, 916417})
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 
2896
  write(4, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2896) = 
2896
  ioctl(2, TIOCGWINSZ, {ws_row=49, ws_col=50, ws_xpixel=819, ws_ypixel=1542}) = 0
  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x55fda0a43000} 
---
  +++ killed by SIGSEGV (core dumped) +++
  Segmentation fault (core dumped)
  ```

  Here is a little screencast demoing it: http://5pi.de/wget-crash.gif

  - Ubuntu 16.04 LTS
  - wget 1.17.1-1ubuntu1

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

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

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

[Ryan Harper]

iscsid.service: Failed to read PID from file /run/iscsid.pid: Invalid
argument

When runnig iscsid -f -d7, we see the issue:

root@x1:~# iscsid -f -d 7 
iscsid: sysfs_init: sysfs_path='/sys'

iscsid: InitiatorName=iqn.1993-08.org.debian:01:32a765bb043
iscsid: InitiatorName=iqn.1993-08.org.debian:01:32a765bb043
iscsid: InitiatorAlias=x1
iscsid: Max file limits 65536 65536

iscsid: Could not increase process priority: Operation not permitted
iscsid: Could not set oom score to -16: Permission denied
iscsid: Could not set oom score to -17: Permission denied
iscsid: failed to mlockall, exiting...

It doesn't handle non-root usernamespace; expects to be able to write to
oom_adjst.  similar to tgtd.

-- 
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 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 1559308] Re: Plugging HDMI screen in causes system hang

[Jonathan Hartley]

It crosses my mind that as well as the HDMI output, my laptop also has a
mini display port. Does anyone have a feel for whether it's worth buying
an mini display port adaptor or cable to test whether that behaves the
same?

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

Title:
  Plugging HDMI screen in causes system hang

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  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)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

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

[Touch-packages] [Bug 1576092] ProcEnviron.txt

[mathojojo]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1576092/+attachment/4650441/+files/ProcEnviron.txt

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

Title:
  libgl1-mesa-dri

Status in mesa package in Ubuntu:
  New

Bug description:
  Everytime I try to start Sweethome 3D, the interface appear and then
  directly crashes !

  When I launch it in Terminal, I get this :

  Java 3D: implicit antialiasing enabled
  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f70066de823, pid=1667, tid=140119133419264
  #
  # JRE version: OpenJDK Runtime Environment (8.0_03-b03) (build 
1.8.0_03-Ubuntu-8u77-b03-3ubuntu3-b03)
  # Java VM: OpenJDK 64-Bit Server VM (25.03-b03 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [radeonsi_dri.so+0x256823]
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
  #
  # An error report file with more information is saved as:
  # /tmp/hs_err_pid1667.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.java.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #
  Aborted (core dumped)

  As mentionned, radeonsi-dri.so may have a problem. It's an important
  bug, as we can't install the proprietary fglrx drivers on ubuntu
  16.04.

  my system : kubuntu 16.04 64bit / AMD Phenom(tm) II X6 1090T Processor / 8Go 
RAM / RADEON HD 7750 (no propretary drivers installed, as they are not 
available anymore in 16.04)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE 16.04
  InstallationDate: Installed on 2016-04-25 (3 days ago)
  InstallationMedia: neon 16.04 "Xenial" - Build amd64 LIVE Binary 
20160419-23:13
  Package: sweethome3d 4.5+dfsg-3 [origin: Ubuntu]
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags: xenial third-party-packages
  Uname: Linux 4.4.0-21-generic x86_64
  UnreportableReason: This is not an official KDE package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1576092] Re: libgl1-mesa-dri

[mathojojo]

apport information

** Tags added: apport-collected third-party-packages xenial

** Description changed:

  Everytime I try to start Sweethome 3D, the interface appear and then
  directly crashes !
  
  When I launch it in Terminal, I get this :
  
  Java 3D: implicit antialiasing enabled
  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f70066de823, pid=1667, tid=140119133419264
  #
  # JRE version: OpenJDK Runtime Environment (8.0_03-b03) (build 
1.8.0_03-Ubuntu-8u77-b03-3ubuntu3-b03)
  # Java VM: OpenJDK 64-Bit Server VM (25.03-b03 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [radeonsi_dri.so+0x256823]
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
  #
  # An error report file with more information is saved as:
  # /tmp/hs_err_pid1667.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.java.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #
  Aborted (core dumped)
  
  As mentionned, radeonsi-dri.so may have a problem. It's an important
  bug, as we can't install the proprietary fglrx drivers on ubuntu 16.04.
  
- my system : kubuntu 16.04 64bit / AMD Phenom(tm) II X6 1090T Processor /
- 8Go RAM / RADEON HD 7750 (no propretary drivers installed, as they are
- not available anymore in 16.04)
+ my system : kubuntu 16.04 64bit / AMD Phenom(tm) II X6 1090T Processor / 8Go 
RAM / RADEON HD 7750 (no propretary drivers installed, as they are not 
available anymore in 16.04)
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DistroRelease: KDE 16.04
+ InstallationDate: Installed on 2016-04-25 (3 days ago)
+ InstallationMedia: neon 16.04 "Xenial" - Build amd64 LIVE Binary 
20160419-23:13
+ Package: sweethome3d 4.5+dfsg-3 [origin: Ubuntu]
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
+ Tags: xenial third-party-packages
+ Uname: Linux 4.4.0-21-generic x86_64
+ UnreportableReason: This is not an official KDE package. Please remove any 
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1576092/+attachment/4650439/+files/Dependencies.txt

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

Title:
  libgl1-mesa-dri

Status in mesa package in Ubuntu:
  New

Bug description:
  Everytime I try to start Sweethome 3D, the interface appear and then
  directly crashes !

  When I launch it in Terminal, I get this :

  Java 3D: implicit antialiasing enabled
  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f70066de823, pid=1667, tid=140119133419264
  #
  # JRE version: OpenJDK Runtime Environment (8.0_03-b03) (build 
1.8.0_03-Ubuntu-8u77-b03-3ubuntu3-b03)
  # Java VM: OpenJDK 64-Bit Server VM (25.03-b03 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [radeonsi_dri.so+0x256823]
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
  #
  # An error report file with more information is saved as:
  # /tmp/hs_err_pid1667.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.java.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #
  Aborted (core dumped)

  As mentionned, radeonsi-dri.so may have a problem. It's an important
  bug, as we can't install the proprietary fglrx drivers on ubuntu
  16.04.

  my system : kubuntu 16.04 64bit / AMD Phenom(tm) II X6 1090T Processor / 8Go 
RAM / RADEON HD 7750 (no propretary drivers installed, as they are not 
available anymore in 16.04)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE 16.04
  InstallationDate: Installed on 2016-04-25 (3 days ago)
  InstallationMedia: neon 16.04 "Xenial" - Build amd64 LIVE Binary 
20160419-23:13
  Package: sweethome3d 4.5+dfsg-3 [origin: Ubuntu]
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags: xenial third-party-packages
  Uname: Linux 4.4.0-21-generic x86_64
  UnreportableReason: This is not an official KDE package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To 

[Touch-packages] [Bug 1576092] JournalErrors.txt

[mathojojo]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1576092/+attachment/4650440/+files/JournalErrors.txt

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

Title:
  libgl1-mesa-dri

Status in mesa package in Ubuntu:
  New

Bug description:
  Everytime I try to start Sweethome 3D, the interface appear and then
  directly crashes !

  When I launch it in Terminal, I get this :

  Java 3D: implicit antialiasing enabled
  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f70066de823, pid=1667, tid=140119133419264
  #
  # JRE version: OpenJDK Runtime Environment (8.0_03-b03) (build 
1.8.0_03-Ubuntu-8u77-b03-3ubuntu3-b03)
  # Java VM: OpenJDK 64-Bit Server VM (25.03-b03 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [radeonsi_dri.so+0x256823]
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
  #
  # An error report file with more information is saved as:
  # /tmp/hs_err_pid1667.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.java.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #
  Aborted (core dumped)

  As mentionned, radeonsi-dri.so may have a problem. It's an important
  bug, as we can't install the proprietary fglrx drivers on ubuntu
  16.04.

  my system : kubuntu 16.04 64bit / AMD Phenom(tm) II X6 1090T Processor / 8Go 
RAM / RADEON HD 7750 (no propretary drivers installed, as they are not 
available anymore in 16.04)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE 16.04
  InstallationDate: Installed on 2016-04-25 (3 days ago)
  InstallationMedia: neon 16.04 "Xenial" - Build amd64 LIVE Binary 
20160419-23:13
  Package: sweethome3d 4.5+dfsg-3 [origin: Ubuntu]
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags: xenial third-party-packages
  Uname: Linux 4.4.0-21-generic x86_64
  UnreportableReason: This is not an official KDE package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1576345] [NEW] cannot view available wifi networks after enabling wifi

[hussain]

Public bug reported:

cannot view available wifi networks after enabling wifi, although it get
connected to the wifi. but if i want to switch to other wifi i cannot as
i cant see any available wifi. and the icon is also changed to up-down
arror(which is for ethernet connection) instead of wifi icon.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 28 20:34:57 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-11-13 (167 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IpRoute:
 default via 192.168.8.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.8.0/24 dev wlan0  proto kernel  scope link  src 192.168.8.104  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-11-16T16:09:56.538140
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
 wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
Ooredoo-B315-9088 1  c9230ff1-5ce5-4c9b-bbaf-a064901a20b6  
/org/freedesktop/NetworkManager/ActiveConnection/5 
 eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
----
 
 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'.

** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1576345

Title:
  cannot view available wifi networks after enabling wifi

Status in network-manager package in Ubuntu:
  New

Bug description:
  cannot view available wifi networks after enabling wifi, although it
  get connected to the wifi. but if i want to switch to other wifi i
  cannot as i cant see any available wifi. and the icon is also changed
  to up-down arror(which is for ethernet connection) instead of wifi
  icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 28 20:34:57 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-11-13 (167 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.8.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.8.0/24 dev wlan0  proto kernel  scope link  src 192.168.8.104  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-11-16T16:09:56.538140
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
Ooredoo-B315-9088 1  c9230ff1-5ce5-4c9b-bbaf-a064901a20b6  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----  
   
   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:

[Touch-packages] [Bug 1404824] Re: [Scopes] There is no way to uninstall a scope on ubuntu phone

[Pat McGowan]

** No longer affects: canonical-devices-system-image

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

Title:
  [Scopes] There is no way to uninstall a scope on ubuntu phone

Status in The Savilerow project:
  Won't Fix
Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Currently, I only know that "click unregister" may help to remove an
  installed scope. May I know how I can remove an installed scope on the
  phone if a user does not like to have it in the phone?

  -- UX Comment --

  There are two possibilities for "removing" a scope from the phone:

  1 - Unfavourite a scope: 
  If we access the 'Manage Dash' screen (via bottom edge gesture), you can tap 
on the star icon to remove any scope from the Dash (except the Apps Scope). 
After doing this, that scope will not be shonw as part of the Dash pagination. 
You can reverse the action by tapping on the star again.

  2 - Uninstall a scope:
  If we go to the Ubunut Store (accessible from the Apps Scope or by tapping on 
the Store icon on the Manage Dash header) and we search for a specific scope 
(e.g.: Today Scope), we can tap on the 'Uninstall' button to uninstall it from 
the system. A confirmation dialog will prompt you and if you confirm, the scope 
will be uninstalled and therefore removed permantly from the Dash (pagination) 
and the Manage Dash screen. You can reverse this action by installing the scope 
again (same steps as any other app in the store).

  However, we are working towards a entire redesign of Scopes and Dash,
  therefore this is subject to change in the near future. The desired
  solution and specs will be updated as soon as they are available.

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

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

[Touch-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang

[shinyblue]

Mine has a usb3.1 with an adaptor providing another HDMI and a VGA port.
They all work the same, ie hardly!, so if say don't rush out and spend
cash!

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

Title:
  Plugging HDMI screen in causes system hang

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  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)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

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

[Touch-packages] [Bug 1576341] [NEW] fails in lxd container

[Scott Moser]

Public bug reported:

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)

** Affects: lvm2 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: open-iscsi (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug uec-images xenial

** Description changed:

- 
  $ lxc launch xenial x1
  $ sleep 10
- $ lxc file pull x5/etc/cloud/build.info -
+ $ 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
+   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)
+  TERM=xterm-256color
+  PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

+ 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 

[Touch-packages] [Bug 1576302] Re: Cannot use keyboard to navigate the UITK gallery in single-column mode

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

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

Title:
  Cannot use keyboard to navigate the UITK gallery in single-column mode

Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Start the UITK gallery, and resize the window to have a single column.

  Now, with TAB you can navigate between the actions in the header, and
  the ListView with that list the different Pages with components. But
  it is not possible to use the arrow keys to select a ListItem, and
  then press ENTER/SPACE to open that page, because pressing the arrow
  (up/down) key automatically triggers the ListItem (onClicked?) and
  opens the Page. So only the first Page (ActionBar) can be opened using
  keyboard navigation when you have only one column.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1576302/+subscriptions

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

[Touch-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang

[Scott Vrooman]

I have a Asus Zenbook UX305CA-EHM1 M3-6Y30. It's a pretty sweetly
designed machine and Ubuntu looks and works awesome  on it EXCEPT for
this external monitor issue.

I've got the Intel HD Graphics 515 using the i915_bpo driver and a micro
HDMI display port.

I've got a few days left to return this machine but I've wisely deleted
the Asus Windows 10 recovery partition and I'm having a hell of a time
getting Windows 10 reinstalled. It's so sad, I was really looking
forward to having a dedicated Linux laptop to code on.

I know this is not the place to vent, I couldn't help myself!

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

Title:
  Plugging HDMI screen in causes system hang

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  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)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

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

[Touch-packages] [Bug 1574566] Re: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[jean-christophe manciot]

There is an issue, although it is not directly related to the title of
this thread.

It used to be possible to install libvirt 1.3.3 over 1.2.16 on Ubuntu 15.10 
***without any issue.***
Now, on Ubuntu 16.10, trying to install libvirt 1.3.3 from the ***same 
sources*** triggers the error already depicted above:
systemctl status libvirt-bin
● libvirt-bin.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Thu 2016-04-28 19:10:19 
CEST; 1min 3s ago
 Docs: man:libvirtd(8)
   http://libvirt.org
  Process: 11398 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, 
status=1/FAILURE)
 Main PID: 11398 (code=exited, status=1/FAILURE)

Apr 28 19:10:19 samsung-ubuntu systemd[1]: Failed to start Virtualization 
daemon.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: libvirt-bin.service: Unit entered 
failed state.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: libvirt-bin.service: Failed with 
result 'exit-code'.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: libvirt-bin.service: Service 
hold-off time over, scheduling restart.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: Stopped Virtualization daemon.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: libvirt-bin.service: Start request 
repeated too quickly.
Apr 28 19:10:19 samsung-ubuntu systemd[1]: Failed to start Virtualization 
daemon.

What has changed?
I finally figured it out.
On Ubuntu 15.10, we had the shared libraries in /usr/lib as expected:
dpkg --contents libvirt0_1.2.16-2ubuntu11_amd64.deb | grep so
-rw-r--r-- root/root   3607776 2015-09-29 03:02 ./usr/lib/libvirt.so.0.1002.16
-rw-r--r-- root/root 10168 2015-09-29 03:02 
./usr/lib/libvirt-lxc.so.0.1002.16
-rw-r--r-- root/root 14264 2015-09-29 03:02 
./usr/lib/libvirt-qemu.so.0.1002.16
lrwxrwxrwx root/root 0 2015-09-29 03:02 ./usr/lib/libvirt-qemu.so.0 -> 
libvirt-qemu.so.0.1002.16
lrwxrwxrwx root/root 0 2015-09-29 03:02 ./usr/lib/libvirt.so.0 -> 
libvirt.so.0.1002.16
lrwxrwxrwx root/root 0 2015-09-29 03:02 ./usr/lib/libvirt-lxc.so.0 -> 
libvirt-lxc.so.0.1002.16

Since libvirt 1.3.3 installs its libraries over the previous ones in the same 
folder, everything worked fine:
dpkg --contents libvirt_1.3.3-14_amd64.deb | grep so
...
-rwxr-xr-x root/root   3718272 2016-04-28 19:09 ./usr/lib/libvirt.so.0.1003.3
-rwxr-xr-x root/root 34952 2016-04-28 19:09 
./usr/lib/libvirt-admin.so.0.1003.3
-rwxr-xr-x root/root 14272 2016-04-28 19:09 
./usr/lib/libvirt-qemu.so.0.1003.3
-rwxr-xr-x root/root 14272 2016-04-28 19:09 
./usr/lib/libvirt-lxc.so.0.1003.3
-rwxr-xr-x root/root264496 2016-04-28 19:09 ./usr/lib/libnss_libvirt.so.2
lrwxrwxrwx root/root 0 2016-04-28 19:09 ./usr/lib/libvirt.so -> 
libvirt.so.0.1003.3
lrwxrwxrwx root/root 0 2016-04-28 19:09 ./usr/lib/libvirt-qemu.so.0 -> 
libvirt-qemu.so.0.1003.3
lrwxrwxrwx root/root 0 2016-04-28 19:09 ./usr/lib/libvirt-admin.so.0 -> 
libvirt-admin.so.0.1003.3
lrwxrwxrwx root/root 0 2016-04-28 19:09 ./usr/lib/libvirt-lxc.so.0 -> 
libvirt-lxc.so.0.1003.3
lrwxrwxrwx root/root 0 2016-04-28 19:09 ./usr/lib/libvirt.so.0 -> 
libvirt.so.0.1003.3
lrwxrwxrwx root/root 0 2016-04-28 19:09 ./usr/lib/libvirt-admin.so -> 
libvirt-admin.so.0.1003.3
lrwxrwxrwx root/root 0 2016-04-28 19:09 ./usr/lib/libvirt-qemu.so -> 
libvirt-qemu.so.0.1003.3
lrwxrwxrwx root/root 0 2016-04-28 19:09 ./usr/lib/libvirt-lxc.so -> 
libvirt-lxc.so.0.1003.3

Alas! Someone in Canonical decided to change that and now the libraries have 
moved to a different folder:
dpkg --contents libvirt0_1.3.1-1ubuntu10_amd64.deb | grep so
-rw-r--r-- root/root 10168 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-lxc.so.0.1003.1
-rw-r--r-- root/root 14264 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-qemu.so.0.1003.1
-rw-r--r-- root/root 30680 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-admin.so.0.1003.1
-rw-r--r-- root/root   3689792 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt.so.0.1003.1
lrwxrwxrwx root/root 0 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-admin.so.0 -> libvirt-admin.so.0.1003.1
lrwxrwxrwx root/root 0 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-qemu.so.0 -> libvirt-qemu.so.0.1003.1
lrwxrwxrwx root/root 0 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt.so.0 -> libvirt.so.0.1003.1
lrwxrwxrwx root/root 0 2016-04-15 09:15 
./usr/lib/x86_64-linux-gnu/libvirt-lxc.so.0 -> libvirt-lxc.so.0.1003.1

That explains the confusion:
Apr 28 19:18:45 samsung-ubuntu systemd[1]: Stopped Virtualization daemon.
Apr 28 19:18:45 samsung-ubuntu systemd[1]: Starting Virtualization daemon...
Apr 28 19:18:45 samsung-ubuntu libvirtd[12918]: /usr/sbin/libvirtd: 
/usr/lib/x86_64-linux-gnu/libvirt-admin.so.0: version 
`LIBVIRT_ADMIN_PRIVATE_1.3.3' not found (required by /usr/sbin/libvirtd)
Apr 28 19:18:45 samsung-ubuntu 

[Touch-packages] [Bug 1574566] Re: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[jean-christophe manciot]

Do I need to open a new "bug report"?

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

Title:
  package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  upgrade 15.10 -> 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libvirt-bin 1.3.1-1ubuntu10
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon Apr 25 12:44:51 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-06 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: libvirt
  Title: package libvirt-bin 1.3.1-1ubuntu10 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (0 days ago)
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2016-04-14T14:20:45.067249

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

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

[Touch-packages] [Bug 1574568] Re: Missing dual monitor support

[Michał Sawicz]

** Summary changed:

- dual monitor feature for M10 FHD/HD
+ Missing dual monitor support

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtmir (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Missing dual monitor support

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  A wish list suggestion to use the tablet along with the monitor or TV
  like if we were using 2 monitors. Duplicate screens, share screens
  etc... to use them as two different work desktops

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

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

[Touch-packages] [Bug 1576011] Re: Sometimes wifi is unusable and detected as wired network

[Chih-Hsyuan Ho]

** Also affects: network-manager
   Importance: Undecided
   Status: New

** Package changed: network-manager (Ubuntu) => oem-priority

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

Title:
  Sometimes wifi is unusable and detected as wired network

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New

Bug description:
  * Steps to reproduce:
  1. Boot into Ubuntu
  2. Check wifi connection in network-manager applet drop-down list

  * Expected result:
  A list of available APs should be listed and connection can be established 
after selecting one AP

  * Actual result:
  Sometimes the wifi device is listed as a "Ethernet network", and system will 
unsuccessfully try to connect to this non-existing ethernet network.

  * Issue can be resolved by:
  1. Warm boot
  2. Cold boot
  3. sudo service network-manager restart

  * Wireless module: 
  Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38]

  * Network-manager:
  1.1.93-0ubuntu3
  (Please note that an older network-manager version 1.0.4-0ubuntu10 does not 
have this issue)

  * Ubuntu: Xenial

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

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

[Touch-packages] [Bug 1573229] Re: Greeter does not rotate

[Michał Sawicz]

** Summary changed:

- no rotation of start screen on M10
+ Greeter does not rotate

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

Title:
  Greeter does not rotate

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Touch start/welcome screen (with the big wheel) does not
  rotate following the tablet orientation.

  Device: Aquaris M10
  Ubuntu version: Ubuntu touch OTA 10.1

  This bug can be very tedious for convergence, when you are in desktop
  mode, with the tablet on the table upside-down and using a bluetooth
  mouse tryng to start the desktop (with no security configuration)
  because the cursor movements follow an opposite direction to mouse
  movements.

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

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

[Touch-packages] [Bug 1297234] Re: Live session set wrong keyboard layout and time zone

[Mathew Hodson]

** Changed in: ubiquity (Ubuntu Trusty)
   Status: Invalid => Confirmed

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

Title:
  Live session set wrong keyboard layout and time zone

Status in console-setup package in Ubuntu:
  Expired
Status in ibus package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Confirmed
Status in console-setup source package in Trusty:
  Invalid
Status in ibus source package in Trusty:
  Invalid
Status in ubiquity source package in Trusty:
  Confirmed

Bug description:
  When I boot the Ubuntu Studio 14.04 beta 2 testing it will start with
  keyboard set to English US and time zone as UTC. Usually I believe
  this would be localized to my Swedish keyboard and CET.

  ubuntu-studio@ubuntu-studio:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  ubuntu-studio@ubuntu-studio:~$ apt-cache policy keyboard-configuration
  keyboard-configuration:
Installed: 1.70ubuntu8
Candidate: 1.70ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-19.40-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CurrentDesktop: XFCE
  Date: Tue Mar 25 11:33:44 2014
  LiveMediaBuild: Ubuntu-Studio 14.04 LTS "Trusty Tahr" - Beta i386 (20140325)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1297234/+subscriptions

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

[Touch-packages] [Bug 1573385] Re: Video Audio Desync

[Launchpad Bug Tracker]

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

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Video Audio Desync

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  On youtube the video lags behind the audio of the video

  Device Information: BQ Aquarius M10
  OS Version Ubuntu 15.04 OTA10.1

  Steps to reproduce:
  1. Go to youtube
  2. Play a video preferably one with a distinct matching between audio and 
video like somebody talking.
  3. Notice that the audio is heard roughly 1 second before seeing that which 
caused the sound. For instance someone's mouth still moving after they stopped 
talking in the video.

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

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

[Touch-packages] [Bug 1427216] Re: Error while loading 50dictionaries-common: Symbol's value as variable is void: debian-aspell-only-dictionary-alist

[aaron thomas]

This problem has returned for us as well. What was the solution last
time?

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

Title:
  Error while loading 50dictionaries-common: Symbol's value as variable
  is void: debian-aspell-only-dictionary-alist

Status in dictionaries-common package in Ubuntu:
  Confirmed

Bug description:
  When starting Emacs I get this error message in *Messages* buffer

  Error while loading 50dictionaries-common: Symbol's value as variable
  is void: debian-aspell-only-dictionary-alist

  This is due to a fault in dictionaries-common 1.20.5 and it is corrected in 
1.22.6
  (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741706)

  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1427216/+subscriptions

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

[Touch-packages] [Bug 1571686] Re: "Ask me each time" for SMS does not work

[Tiago Salem Herrmann]

** Branch linked: lp:~tiagosh/messaging-app/fix-sections-dualsim

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

Title:
  "Ask me each time" for SMS does not work

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  New

Bug description:
  BQ Aquaris E4.5 with OTA 10.1
  Settings "Ask me each time" in "For messages, use" in "Cellular" in "Settings"

  I am using 2 SIM cards and since the beginning of my usage (started
  with release21 this settings was working as expected -> when I wanted
  to send SMS and did not select SIM card by myself (so no SIM card was
  highlighted in the Messages app), I was asked to select one.

  Since some time (OTA-9?) there is always (first one) SIM card selected
  despite the above mentioned settings. And, by whatever reason
  sometimes the SMS is send from other then selected SIM card. Because
  it is now happening much more often and I see that "nice" info: "You
  switched to XXX XX" (PS: no I did not!), it becomes really annoying (I
  have one SIM card in roaming mode) and people are receiving my
  messages from different number and therefore I decided to open this
  bug report.

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

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

[Touch-packages] [Bug 1576446] [NEW] desktop shortcut names just print the file name ("*.desktop") and a generic icon

[David M. Karr]

Public bug reported:

I have VMs for 14.04, 15.10, and now 16.04.  I've had no particular
trouble creating desktop shortcuts in the first two.  I typically create
a new desktop entry by copying the "*.desktop" file in ~/Desktop to a
new file and editing the contents, changing the Name, Icon, and Exec
properties.  This has worked perfectly fine in the first two.

In 16.04, although "executing" the shortcut (double-clicking, for
instance) works fine, executing the application I want, the display of
it is somewhat defective in two ways.  First, all of the shortcuts I
create this way are using the same generic icon (looks like a document
editor, with "Aa" in text with some little colored boxes).  My "Icon"
property is a fully-qualified path to the icon file.  I've double-
checked that the path I specify there exists.  Second, the label
underneath the icon isn't the "Name" value, it's just displaying the
name of the ".desktop" file, including the ".desktop" extension.

I then tried the "recommended" way of creating shortcuts for "provided"
applications by searching for the app in the "appstore" (don't remember
what that's called) and then dragging the icon I found onto the desktop.
I thought I tried this yesterday, and it resulted in the same symptom,
but when I tried it today it worked fine.

So I then looked closer at the generated ".desktop" file and compared it
to my "hand-coded" ".desktop" files.  The generated one had quite a few
more properties, but I didn't see anything obvious that indicated why
mine was not working properly.  However, I still looked at the
differences and decided to try removing some differences to see if it
would fix my hand-coded file.  The first thing I noted was that in my
hand-coded file, the "Name" property was not the first property setting
in the "Desktop Entry" group, but in the generated one, it was.  I read
the "Desktop Entry Specification", and I didn't see any indication that
the order of those properties was relevant, but just in case, I tried
making that change.

In fact, that appeared to be the problem.  When I just moved the "Name"
property to the first position in the group, the icon and name displayed
correctly.

I'd call this a bug.  This ordering constraint was not required in 14.04
or 15.10, and again, the "Desktop Entry Specification" says nothing
about any required ordering of these properties.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-desktop 1.361
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 28 14:16:15 2016
InstallationDate: Installed on 2016-04-26 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (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 ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1576446

Title:
  desktop shortcut names just print the file name ("*.desktop") and a
  generic icon

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I have VMs for 14.04, 15.10, and now 16.04.  I've had no particular
  trouble creating desktop shortcuts in the first two.  I typically
  create a new desktop entry by copying the "*.desktop" file in
  ~/Desktop to a new file and editing the contents, changing the Name,
  Icon, and Exec properties.  This has worked perfectly fine in the
  first two.

  In 16.04, although "executing" the shortcut (double-clicking, for
  instance) works fine, executing the application I want, the display of
  it is somewhat defective in two ways.  First, all of the shortcuts I
  create this way are using the same generic icon (looks like a document
  editor, with "Aa" in text with some little colored boxes).  My "Icon"
  property is a fully-qualified path to the icon file.  I've double-
  checked that the path I specify there exists.  Second, the label
  underneath the icon isn't the "Name" value, it's just displaying the
  name of the ".desktop" file, including the ".desktop" extension.

  I then tried the "recommended" way of creating shortcuts for
  "provided" applications by searching for the app in the "appstore"
  (don't remember what that's called) and then dragging the icon I found
  onto the desktop.  I thought I tried this yesterday, and it resulted
  in the same symptom, but when I tried it today it worked fine.

  So I then looked closer at the generated ".desktop" file and compared
  it to my "hand-coded" ".desktop" files.  The generated one had quite a
  few more properties, but I didn't see anything obvious that indicated
  why mine was not working properly.  However, I still looked at the
  differences and decided to try removing 

[Touch-packages] [Bug 1576446] Re: desktop shortcut names just print the file name ("*.desktop") and a generic icon

[David M. Karr]

Unfortunately, now since I did something to "fix" the desktop entry,
even if I change it back so the "Name" property isn't first, it won't
display the problem anymore.  I even tried copying one of them to a new
file with a different name, with the "Name" property not first, and that
works also.

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

Title:
  desktop shortcut names just print the file name ("*.desktop") and a
  generic icon

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I have VMs for 14.04, 15.10, and now 16.04.  I've had no particular
  trouble creating desktop shortcuts in the first two.  I typically
  create a new desktop entry by copying the "*.desktop" file in
  ~/Desktop to a new file and editing the contents, changing the Name,
  Icon, and Exec properties.  This has worked perfectly fine in the
  first two.

  In 16.04, although "executing" the shortcut (double-clicking, for
  instance) works fine, executing the application I want, the display of
  it is somewhat defective in two ways.  First, all of the shortcuts I
  create this way are using the same generic icon (looks like a document
  editor, with "Aa" in text with some little colored boxes).  My "Icon"
  property is a fully-qualified path to the icon file.  I've double-
  checked that the path I specify there exists.  Second, the label
  underneath the icon isn't the "Name" value, it's just displaying the
  name of the ".desktop" file, including the ".desktop" extension.

  I then tried the "recommended" way of creating shortcuts for
  "provided" applications by searching for the app in the "appstore"
  (don't remember what that's called) and then dragging the icon I found
  onto the desktop.  I thought I tried this yesterday, and it resulted
  in the same symptom, but when I tried it today it worked fine.

  So I then looked closer at the generated ".desktop" file and compared
  it to my "hand-coded" ".desktop" files.  The generated one had quite a
  few more properties, but I didn't see anything obvious that indicated
  why mine was not working properly.  However, I still looked at the
  differences and decided to try removing some differences to see if it
  would fix my hand-coded file.  The first thing I noted was that in my
  hand-coded file, the "Name" property was not the first property
  setting in the "Desktop Entry" group, but in the generated one, it
  was.  I read the "Desktop Entry Specification", and I didn't see any
  indication that the order of those properties was relevant, but just
  in case, I tried making that change.

  In fact, that appeared to be the problem.  When I just moved the
  "Name" property to the first position in the group, the icon and name
  displayed correctly.

  I'd call this a bug.  This ordering constraint was not required in
  14.04 or 15.10, and again, the "Desktop Entry Specification" says
  nothing about any required ordering of these properties.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-desktop 1.361
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 28 14:16:15 2016
  InstallationDate: Installed on 2016-04-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576454] [NEW] Superfluous Xsession.d script: 60x11-common_localhost

[Forest]

Public bug reported:

Both of these scripts do the same thing, and both are installed by
x11-common:

/etc/X11/Xsession.d/35x11-common_xhost-local
/etc/X11/Xsession.d/60x11-common_localhost

35x11-common_xhost-local is present in debian, while
60x11-common_localhost is not. I suspect the latter should be removed.

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

** Summary changed:

- Duplicate Xsession.d script: 60x11-common_localhost
+ Superfluous Xsession.d script: 60x11-common_localhost

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

Title:
  Superfluous Xsession.d script: 60x11-common_localhost

Status in xorg package in Ubuntu:
  New

Bug description:
  Both of these scripts do the same thing, and both are installed by
  x11-common:

  /etc/X11/Xsession.d/35x11-common_xhost-local
  /etc/X11/Xsession.d/60x11-common_localhost

  35x11-common_xhost-local is present in debian, while
  60x11-common_localhost is not. I suspect the latter should be removed.

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

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