date:20160531

This bug was fixed in the package pulseaudio - 1:8.0-2ubuntu2

---
pulseaudio (1:8.0-2ubuntu2) yakkety; urgency=medium

  [ Simon Fels ]
  * debian/patches/0700-modules-add-snappy-policy-module.patch:
- Add initial support for a snappy specific policy manager
  which will deny all audio recording from snaps for now
  until real integration with the trust-store is available. (LP: #1583057)
  * debian/rules:
- Build with snappy support
  * debian/pulseaudio.install:
- Include new snappy policy module

 -- Luke Yelavich   Wed, 01 Jun 2016 12:04:14 +1000

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

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1560398] Re: Proximity sensor during call doesn't allow dialing options

2016-05-31 Thread Lorn Potter

It seems that most of our proximity drivers have only close/far and not the 
full ir reflectance value that would be needed for obtaining a better distance 
indication.
That said, the driver could possibly be changed to toggle at a closer or 
greater distance.

But to me, this seems like it is some undefined behavior related to
#1543948

Sadly, I do not have an arale to test.

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

Title:
  Proximity sensor during call doesn't allow dialing options

Status in Canonical System Image:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  I'm not sure if this is a duplicate of any of the proximity bugs
  already reported (https://bugs.launchpad.net/canonical-devices-system-
  image/+bug/1512100,  https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1493574, https://bugs.launchpad.net/canonical-
  devices-system-image/+bug/1524648,  https://bugs.launchpad.net
  /canonical-devices-system-image/+bug/1523308 to name a few).

  On arale, rc-proposed I made a call, but at a certain point I needed
  to choose an option on an IVR. When I took the phone off my ear, the
  screen would indeed wake up, but when I wanted to press a key number
  (after some trouble to bring up the keyboard altogether) I wouldn't be
  able because the screen would turn off. Eventually I managed to
  "trick" the phone being quick, but it took me some time. Hanging up
  was somehow less painful.

  Maybe a matter of adjusting the distance from which the screen turns
  off during calls?

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

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

[Touch-packages] [Bug 1572493] Re: pulseaudio 8.0 drops connections after playing audio in a firejail

@ Michael Hudson-Doyle

If you are about to invalidate this report, please provide a reason for
doing so.

** Tags added: xenail

** Tags removed: xenail
** Tags added: xenial

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

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

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

Title:
  pulseaudio 8.0 drops connections after playing audio in a firejail

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 15.10 to 16.04 (pulseaudio 6 -> 8), I
  notice that my audio output stops working every few hours.  When this
  happens, if I run pavucontrol, it seems to wait forever trying to
  connect to pulseaudio.  Killing pulseaudio and starting it again fixes
  the problem for a little while.

  I don't think anything fancy is needed to cause a hang; usually, I'm
  just using Chrome.

  This never happened with pulseaudio 6 over hundreds of hours of use.

  I am using the default pulseaudio config files on an HP EliteBook
  8460p, which has this audio sink:

  1 sink(s) available.
* index: 0
name: 
driver: 
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
DYNAMIC_LATENCY
state: IDLE
suspend cause: 
priority: 9959
volume: front-left: 61870 /  94% / -1.50 dB,   front-right: 61870 /  
94% / -1.50 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 38.86 ms
max request: 6 KiB
max rewind: 64 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 1
configured latency: 40.00 ms; range is 0.50 .. 371.52 ms
card: 1 
module: 7
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "92HD81B1X5 Analog"
alsa.id = "92HD81B1X5 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xd452 irq 40"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1c20"
device.product.name = "6 Series/C200 Series Chipset Family High 
Definition Audio Controller"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "IDT 92HD81B1X5"
alsa.components = "HDA:111d7605,103c3588,00100105 
HDA:11c11040,103c3066,00100200"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-output-lineout: Line Out (priority 9900, latency offset 
0 usec, available: no)
properties:

analog-output-speaker: Speakers (priority 1, latency offset 
0 usec, available: unknown)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9000, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "audio-headphones"
active port: 



  # dpkg -l | grep pulse
  ii  libpulse-mainloop-glib0:amd64   1:8.0-0ubuntu3   amd64
PulseAudio client libraries (glib support)
  ii  libpulse0:amd64 1:8.0-0ubuntu3   amd64
PulseAudio client libraries
  ii  libpulse0:i386  1:8.0-0ubuntu3   i386 
PulseAudio client libraries
  ii  libpulsedsp:amd64   1:8.0-0ubuntu3   amd64
PulseAudio OSS pre-load library
  ii  pulseaudio  1:8.0-0ubuntu3   amd64

[Touch-packages] [Bug 1587730] [NEW] graphic system freezes after a while, can still ssh into machine

2016-05-31 Thread James

Public bug reported:

Ubuntu 16.04 desktop with all updates up to date
Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 SSD, 
Gigabyte GEForce GT710 graphics (nvidia chipset)

Very light load. A few terminal windows, a few Firefox pages,
Thunderbird, and VirtualBox (with the extension pack loaded) running one
small Linux VM with 512Mb memory (very lightly loaded as it's only
running bind9). I think (but don't have perfect certainty on this) that
some of the crashes have happened without VirtualBox running. Also
running rsync so that backuppc on a separate machine can back it up over
the network (backuppc has been a real lifesaver with all the
reinstallations!)

After booting the system runs happily for a while then the GUI freezes.
This can take a few hours or up to a day or two. You can still ssh into
the system, and if you do "top" it typically shows 100% CPU load on
systemd-timesync.

The same happens whether I use nouveau or the proprietary nvidia driver (361)
I have tried a complete reinstallation (4 times already, starting to get quite 
frustrating) using the proprietary drivers and NOT using the proprietary 
drivers and the same still happens. The most recent time was with nouveau, and 
Xorg.log has a number of entries like this:
(EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
(EE) 
(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
(EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
(EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
[0x7f31f98621f3]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
[0x7f31f9862a5d]
(EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
(EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
(EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
(EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
(EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
(EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
(EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
(EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
(EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
(EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f3202d0f830]
(EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
(EE) 
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
(EE) [mi] mieq is *NOT* the cause.  It is a victim.
(EE) [mi] EQ overflow continuing.  100 events have been dropped.
 
Then at the end the last few are:

[  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
[  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
[  6265.543] [mi] This may be caused by a misbehaving driver monopolizing the 
server's resources.

What cna the problem possibly be, especially as 16.04 is meant to be a
stable release and an Nvidia GT710 card is hardly bleeding-edge? Help
greatly appreciated!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jun  1 13:22:13 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:36ec]
InstallationDate: Installed on 2016-06-01 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. Z170-D3H
ProcEnviron:
 LANGUAGE=en_HK:en
 PATH=(custom, no user)
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=79d1ab40-4431-445f-87bb-6a8d44370cee ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170-D3H-CF
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: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:

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

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

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Medium

** Changed in: pulseaudio (Ubuntu)
   Importance: Medium => High

** This bug has been marked a duplicate of bug 1572493
   pulseaudio 8.0 drops connections after playing audio in a firejail

-- 
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 1584853] Re: Shotwell crashes on startup / Crash in exiv2 due to assertion when setting rating on jpg with a Casio makernote

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

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

Title:
  Shotwell crashes on startup / Crash in exiv2 due to assertion when
  setting rating on jpg with a Casio makernote

Status in exiv2 package in Ubuntu:
  Confirmed
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  Starting from the command line, this can be seen:

  shotwell: tiffcomposite.cpp:749: virtual Exiv2::Internal::TiffComponent* 
Exiv2::Internal::TiffMnEntry::doAddPath(uint16_t, Exiv2::Internal::TiffPath&, 
Exiv2::Internal::TiffComponent*, Exiv2::Internal::TiffComponent::AutoPtr): 
Assertion `mn_' failed.
  Aborted (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 23 08:48:32 2016
  InstallationDate: Installed on 2015-09-20 (245 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: shotwell
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (31 days ago)
  shotwell.log:
   L 24280 2016-05-23 08:46:56 [MSG] main.vala:385: Shotwell Photo Manager 
0.22.0
   L 24280 2016-05-23 08:46:56 [MSG] main.vala:43: Verifying database ...

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

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

[Touch-packages] [Bug 1584072] Re: package lib32z1-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:

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

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => High

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

Title:
  package lib32z1-dev (not installed) failed to install/upgrade: trying
  to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in
  package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4

Status in One Hundred Papercuts:
  Confirmed
Status in zlib package in Ubuntu:
  Confirmed

Bug description:
  Just trying to install the tools to build the Android Open Source
  Project. Nothing special to note, I just ran the command that is
  recommended on the AOSP website.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lib32z1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri May 20 10:05:35 2016
  ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', 
which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: zlib
  Title: package lib32z1-dev (not installed) failed to install/upgrade: trying 
to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package 
zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583666] Re: laggy PC

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

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

Title:
  laggy PC

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have an HP envy 13 (6th gen core i5) that runs smoothly on windows.
  I really try using ubuntu as my main OS but lagginess doesn't help
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-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: Thu May 19 10:34:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80df]
  InstallationDate: Installed on 2016-05-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=54673ec1-b654-4c3e-b021-29dcd078a702 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DF
  dmi.board.vendor: HP
  dmi.board.version: 87.59
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd02/18/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.59:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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 May 19 06:48:29 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16730 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"

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

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

Title:
  Swap Failed, Indefinite hang on reboot/shutdown "Reached target
  Shutdown"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This bug has been affecting me since 15.04
  Prior to shutdown I activate debug-shell 'systemctl start debug-shell'
  I have followed bug #1464917 and installed Xenial-proposed with systemd 
229-4ubuntu5 package.  
  I have finally collected shutdown info using vt9.  
  Issues collecting info due to what I believe is a timeout where vt9 is not 
activated when ctl+alt+F9 is pressed.  I was able to collect info in vt9 to 
file "shutdown.text" I appended outputs to file "shutdown.text" the following 
commands in this order:
  systemctl list-jobs >>shutdown.text
  systemctl --failed >>shutdown.text
  uname -a >>shutdown.text
  systemd --version >>shutdown.text
  lsblk >>shutdown.text
  blkid >>shutdown.text
  journalctl -b >>shutdown.text
  systemctl -all >>shutdown.text
  journalctl -xe >>shutdown.text

  After gaining these data I was only able to finish the reboot with the 
alt+Sysrq and REISUB which forces a reboot even when I just want to shutdown
  Each output I separated upon next boot by hand with a line 
# for easier perusing.

  As a workaround for shutdown/reboot I turn swap off, 'sudo swapoff -a
  && systemctl poweroff' or 'sudo swapoff -a && reboot'  which
  occasionally fails if SWAP has more data than available RAM.  In that
  latter case I am left waiting for the hang and then using
  alt+Sysrq+REISUB to reboot then shutdown again immediately upon boot
  before SWAP has a chance to gain data, then I can use any form of
  halt, poweroff or menu to shutdown.

  I have been unable to get answers from AskUbuntu or the above listed
  bug #1464917 "Reached target Shutdown"  I am filing this bug per
  instructions requested in that bug.  Other systemd bugs I have
  researched #788303 Debian bug reports, #2930 Github and #3087 Github.

  Thanks for your time and efforts to help with this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May 15 12:08:34 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2015-06-29 (321 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Sony Corporation VGN-FW250J
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=b010e611-6efb-49a9-bff0-59b9533d659b ro 
resume=UUID=8bcb4169-f5ab-4ab6-b644-23e528088d41 usbcore.autosuspend=-1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (18 days ago)
  dmi.bios.date: 07/25/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1090Y0
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1090Y0:bd07/25/2008:svnSonyCorporation:pnVGN-FW250J:pvrC6011MLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-FW250J
  dmi.product.version: C6011MLK
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1579012] Re: Remote LUKS Root Filesystem Problem After Upgrading 14.04 to 16.04

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Remote LUKS Root Filesystem Problem After Upgrading 14.04 to 16.04

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  enclosed script /etc/initramfs-tools/hooks/mount_cryptroot is used to
  unlock LUKS root filesystem. Until 14.04 it was no problem to depend
  on existence of ${DESTDIR}/root for writing files, e.g. ssh public
  keys, scripts etc. From 16.04 a random home dir for root is used.
  Enclosed script contains an ugly workaround.

  Feature request: Please provide a variable for hooks which contains
  path to root home dir.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  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: Fri May  6 12:48:05 2016
  InstallationDate: Installed on 2014-08-23 (621 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-06 (0 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1579012/+subscriptions

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

[Touch-packages] [Bug 1580917] Re: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  All was working fine, then one day it goes silent when plugging in my
  speakers to the headphone socket, and forever after with something
  plugged in (internal speakers still work fine).

  Looking at pavucontrol and/or "Sound settings" under Gnome it shows
  that the sound should be playing on the Headphones output port - the
  VU meter is bouncing up and down ok, but it's silent. Pull out the
  wire (or select internal speakers for the Output) and the sound
  switches to the internal speakers OK.

  Last time this happened I fiddled for ages and then got distorted
  sound (sounds like some sort of cross-channel thing) and this only
  went a away with a complete re-install of Ubuntu (which I did to try
  to fix a separate bug but am not willing to do again!).

  I ran alsa-info.sh from the command line and uploaded the info. Here's
  the URL it gave me to share: http://www.alsa-
  project.org/db/?f=06...3f7ebb379442a7

  It's now happened again, having spent all Friday enjoying music,
  Monday morning turn on and silence! I've not done any upgrades since.

  
  I have tried completely reinstalling pulseaudio (based on suggestions found 
on the ubuntu wiki) to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.4.8-040408-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rich   7826 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 12 09:31:00 2016
  InstallationDate: Installed on 2016-04-22 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rich   7826 F...m pulseaudio
   /dev/snd/controlC0:  rich   7826 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 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.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-05-09T13:36:55.718771

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

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

[Touch-packages] [Bug 1577247] Re: webbrowser-app

Please:

1. Edit the bug description, so it explains the perceptible consequences of the 
issue.
2. Set status back to "confirmed".

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  webbrowser-app

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  (webbrowser-app:4034): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4034): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4034): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
  QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
  file:///usr/share/webbrowser-app/webbrowser/ContentPickerDialog.qml:22:1: 
module "Ubuntu.Content" is not installed
  file:///usr/share/webbrowser-app/webbrowser/ContentDownloadDialog.qml:22:1: 
module "Ubuntu.Content" is not installed
  file:///usr/share/webbrowser-app/ContentHandler.qml:20:1: module 
"Ubuntu.Content" is not installed
  file:///usr/share/webbrowser-app/webbrowser/DownloadHandler.qml:20:1: module 
"Ubuntu.DownloadManager" is not installed
  Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
  Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
  Input device added: "HDA Intel Front Mic" "/dev/input/event7" QFlags(0x20)
  Input device added: "HDA Intel Rear Mic" "/dev/input/event8" QFlags(0x20)
  Input device added: "HDA Intel Line" "/dev/input/event9" QFlags(0x20)
  Input device added: "HDA Intel Line Out" "/dev/input/event10" QFlags(0x20)
  Input device added: "HDA Intel Front Headphone" "/dev/input/event11" 
QFlags(0x20)
  Input device added: "Twin USB Joystick" "/dev/input/event5" QFlags()
  Input device added: "Twin USB Joystick" "/dev/input/event6" QFlags()
  Input device added: "BTC USB Multimedia Keyboard" "/dev/input/event2" 
QFlags(0x1|0x10)
  Input device added: "BTC USB Multimedia Keyboard" "/dev/input/event3" 
QFlags(0x1)
  Input device added: "Genius Optical Mouse" "/dev/input/event4" QFlags(0x2)
  Input device added: "UVC Camera (046d:0802)" "/dev/input/event12" QFlags(0x1)
  Failed to create OpenGL context for format QSurfaceFormat(version 2.0, 
options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, 
blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, 
swapBehavior 2, swapInterval 1, profile  0) 
  Aborted (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  2 02:18:38 2016
  InstallationDate: Installed on 2016-04-27 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1578196] Re: External Display Port monitor not working

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  External Display Port monitor not working

Status in X.Org X server:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have three monitors on my Lenovo X250, one built-in and two
  connected via a Lenovo docking station :

  built-in: 1920x1080
  HP 2335: 1920x1200
  BenQ GW2765: 2560x1440

  The HP is connected via DVI and the BenQ via Display Port.

  In this configuration, I get my HP and built-in ok, but the BenQ
  doesn't show up at all (using xrandr --query).

  If I connect the BenQ via HDMI, then it shows up in xrandr --query,
  but the display is still blank (bandwidth issue?).

  Here's the output with the DVI + DP config :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767
  eDP1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 disconnected (normal left inverted right x axis y axis)
  DP2-2 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 495mm x 310mm
 1920x1200 59.95*+
 1600x1200 60.00  
 1280x1024 85.0275.0260.02  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  85.0075.0370.0760.00  
 832x624   74.55  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  and with built-in and BenQ only :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767
  eDP1 connected primary 1920x1080+0+360 (normal left inverted right x axis y 
axis) 276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 1920x1080 60.0050.0059.94  
 1680x1050 59.88  
 1600x900  59.98  
 1280x1024 75.0260.02  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 832x624   74.55  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP2-2 disconnected (normal left inverted right x axis y axis)
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  This looks relevant :

  

  I'm running kernel 4.6.0-040600rc6-generic (installed as part of the
  debugging process).

  (This bug is the 'next step' from
  )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for

[Touch-packages] [Bug 1575878] Re: Xorg freeze when see videos or animation 16.04

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Xorg freeze when see videos or animation 16.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When videos are played the system randomly freezes to start playing
  the video, or when it takes a few minutes. It also happens with
  animations webs. This happened with the previous kernel of 15.10 and
  with the current kernel of 16.04. The bios is the latest version and
  use public graphics drivers.

  If I do not watch videos or animations I can work full days without
  freezing.

  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: Wed Apr 27 21:01:26 2016
  DistUpgraded: 2016-04-21 20:00:24,411 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:2224]
  InstallationDate: Installed on 2016-01-14 (104 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20D9S00D00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=3e293fa3-ec43-4f0a-a925-562901db8088 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (6 days ago)
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0G00622 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn20D9S00D00:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0G00622WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20D9S00D00
  dmi.product.version: ThinkPad 11e
  dmi.sys.vendor: LENOVO
  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: Wed Apr 27 21:00:01 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1161 
   vendor IVO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after
  fresh xubuntu 16.04 installation

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hardware sound device is available, according to:
  aplay -l
  sudo lspci

  
  https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  student1739 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 27 22:06:16 2016
  InstallationDate: Installed on 2016-04-24 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  student1739 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Touch-packages] [Bug 1575899] Re: Text disappears after suspend

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

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

Title:
  Text disappears after suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After waking my laptop running Xenial after it having been suspended,
  a lot of applications (e.g. Terminal and all settings) does not render
  most of the text that should be there. Some of it shows up on
  mouseover, but most is just permanently invisible until reboot of
  system.

  Detected a very similar bug after I created this issue:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1528843

  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: Wed Apr 27 21:44:36 2016
  DistUpgraded: 2016-04-25 10:36:20,651 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2015-09-05 (234 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03eb:8a0c Atmel Corp.
   Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc.
   Bus 001 Device 005: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=6cc41411-46cb-4a14-a79a-038ee820f1aa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (2 days ago)
  dmi.bios.date: 12/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.206:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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: Wed Apr 27 16:42:36 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1512990] Re: package account-plugin-facebook (not installed) failed to install/upgrade: попытка перезаписать «/etc/signon-ui/webkit-options.d/www.facebook.com.conf», который уже

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

** This bug has been marked a duplicate of bug 1573787
   package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1

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

Title:
  package account-plugin-facebook (not installed) failed to
  install/upgrade: попытка перезаписать «/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf», который уже имеется в пакете
  kaccounts-providers 4:15.08.2-0ubuntu1

Status in account-plugins package in Ubuntu:
  Invalid
Status in kaccounts-providers package in Ubuntu:
  New

Bug description:
  install ubuntu-desktop

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: account-plugin-facebook (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Wed Nov  4 11:51:32 2015
  ErrorMessage: попытка перезаписать 
«/etc/signon-ui/webkit-options.d/www.facebook.com.conf», который уже имеется в 
пакете kaccounts-providers 4:15.08.2-0ubuntu1
  InstallationDate: Installed on 2015-02-21 (256 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: account-plugins
  Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: попытка перезаписать 
«/etc/signon-ui/webkit-options.d/www.facebook.com.conf», который уже имеется в 
пакете kaccounts-providers 4:15.08.2-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

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

Status in xorg package in Ubuntu:
  Confirmed

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

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

  Thanks,
  MZ

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

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

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

[Touch-packages] [Bug 1564876] Re: [Asus N551JM, Realtek ALC668, Mic, Internal] No autoswitch

[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Asus N551JM, Realtek ALC668, Mic, Internal] No autoswitch

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  No auto switch with internal microphone and external microphone on
  headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   mogost 1869 F...m pulseaudio
   /dev/snd/controlC1:  mogost 1869 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr  1 18:08:52 2016
  InstallationDate: Installed on 2016-03-29 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [hostname, Realtek ALC668, Mic, Internal] No autoswitch
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-04-01T00:51:58.276057

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

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

[Touch-packages] [Bug 1573203] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: eindeloze triggerlus; afgebroken

** Changed in: hicolor-icon-theme (Ubuntu)
   Importance: Undecided => High

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

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  eindeloze triggerlus; afgebroken

Status in hicolor-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  While upgrading from 15.10 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 21 21:20:25 2016
  Dependencies:
   
  ErrorMessage: eindeloze triggerlus; afgebroken
  InstallationDate: Installed on 2015-05-09 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
eindeloze triggerlus; afgebroken
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1573203/+subscriptions

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

[Touch-packages] [Bug 1573118] Re: "units" context property is app-global

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  "units" context property is app-global

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

Bug description:
  The "units" context property has no idea about which screen it is on,
  making it impossible to have different grid unit values per window in
  a single app. This would be the case, for example, when one app has
  multiple windows on different screens.

  We're landing a workaround for this for use in unity8 (the only case
  supported today where a single app has multiple windows on different
  screens).

  Long-term we might need UITK 2.0 to fix this proper.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 1.3.1918+16.04.20160404-0ubuntu1
  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 21 17:54:33 2016
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 157289] Re: Keyboard input sometimes stops working

2016-05-31 Thread Rolf Leggewie

https://launchpad.net/~r0lf/+archive/ubuntu/stable/+packages

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

Title:
  Keyboard input sometimes stops working

Status in kdewebdev-kde3 package in Ubuntu:
  Confirmed
Status in kile package in Ubuntu:
  Fix Released
Status in python-defaults package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Confirmed
Status in scim package in Ubuntu:
  Incomplete

Bug description:
  After the upgrade to 7.10, sometimes keyboard input stops working in
  just one program.

  When it happens, I can input data in a different program and copy-and-
  paste to the one without working input.

  It begins during program execution (In other words, while using a
  program it just occurs; It is not in this state from the beginning of
  program execution)

  I have SCIM installed, but am using English/Keyboard at the time this
  happens. While in the broken state, switching input modes to Japanese
  - Anthy does not fix the situation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdewebdev-kde3/+bug/157289/+subscriptions

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

[Touch-packages] [Bug 1572653] Re: keyboard does not show up on xenial

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

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

Title:
  keyboard does not show up on xenial

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Expected behaviour:

  Install ubuntu-keyboard, run maliit-server, click on place to enter
  text -> keyboard shows up.

  What happens:

  Running maliit-server after installing ubuntu-keyboard-english in
  terminal shows following error:

  WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const
  QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is
  not enabled

  Clicking on fields for entering text, does not cause the keyboard to
  show up.

  What I tried so far:

  export QT_IM_MODULE=Maliit
  export GTK_IM_MODULE=Maliit

  and

  gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled 
"[llibubuntu-keyboard-plugin.so,en_gb]"
  gconftool-2 -s --type list --list-type string /maliit/onscreen/active 
"[libubuntu-keyboard-plugin.so,en_gb]"

  according to

  https://github.com/maliit/framework

  and

  https://github.com/maliit/plugins

  but it still won't show up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1
  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: Wed Apr 20 18:03:03 2016
  InstallationDate: Installed on 2016-04-03 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.maliit.org.server.conf: [modified]
  mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195

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

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

[Touch-packages] [Bug 1572081] Re: Unable to reconnect to wi-fi after waking up from sleep

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Unable to reconnect to wi-fi after waking up from sleep

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After waking up from sleep my Laptop (Thinkpad T450s) was unable to
  connect to wi-fi. This doesn't seem to happen always but it happened
  when Laptop was in sleep mode overnight and in morning when I opened
  it - it won't connect to wifi.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  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
  CurrentDesktop: GNOME
  Date: Tue Apr 19 07:07:15 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-17 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160416)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev lxcbr0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.6  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  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/1572081/+subscriptions

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

[Touch-packages] [Bug 1572250] Re: Wrong type of Wi-Fi device (wlp2s0) after boot

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Wrong type of Wi-Fi device (wlp2s0) after boot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello
  My Wi-Fi adapter is Intel 7260. After boot I have

  nmcli device status
  DEVICE  TYPE  STATECONNECTION 
  wlp2s0  ethernet  unavailable  -- 
  lo  loopback  unmanaged--

  after some dirty fix (sudo rmmod iwlmvm iwlwifi && sudo modprobe
  iwlwifi)

  nmcli device status
  DEVICE  TYPE  STATE CONNECTION 
  wlp2s0  wifi  disconnected  -- 
  lo  loopback  unmanaged --

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  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
  CurrentDesktop: KDE
  Date: Tue Apr 19 22:22:59 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   #auto wlp2s0
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.123  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
libreCMC91f33459-b8b5-43ea-a742-a09720f20821  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1569679] Re: lxc failed to do lxc-checkpoint again

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

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

Title:
  lxc failed to do lxc-checkpoint again

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When doing lxc-checkpoint, it replies:

  lxc-checkpoint: criu.c: do_dump: 879 dump failed with 1

  Checkpointing xxx failed.

  

  About my ENV:

  # uname -a
  Linux ubuntu 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  # lsb_release -a
  Distributor ID:   Ubuntu
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  Codename: xenial

  # apt-cache policy lxc
  lxc:
Installed: 2.0.0-0ubuntu1
Candidate: 2.0.0-0ubuntu1
Version table:
   *** 2.0.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy criu
  criu:
Installed: 2.0-2ubuntu3
Candidate: 2.0-2ubuntu3
Version table:
   *** 2.0-2ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr 13 12:44:20 2016
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

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

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-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: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS 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:

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

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

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

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

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

Title:
Volume notification keeps popping up constantly(the notifyosd bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 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: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right

2016-05-31 Thread Daniel van Vugt

Other way round. This bug is older and has more detail/history. De-
duplicate under this one.

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

Title:
  Dash pauses/stutters during scope switching left/right

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

Bug description:
  Dash pauses/stutters during scope switching left/right.

  Watching the log:   tail -f ~/.cache/upstart/unity8-dash.log

  I can see error messages flood out whenever the dash pauses/stutters
  during left/right swipes:

  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"

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

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

[Touch-packages] [Bug 1497611] Re: navigation through scopes very slow

2016-05-31 Thread Daniel van Vugt

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1384374, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1384374
   Dash pauses/stutters during scope switching left/right

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

Title:
  navigation through scopes very slow

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I an using a Meizu MX4 with software version 15.04 (r4). Even though this is 
a powerfull phone moving between scopes is still laggy and slow also some auto 
refresh as you move to them. 
  I would like to suggest that auto refresh takes place in the background so 
all scopes are ready when you flick through them. 
  Also I wonder if a scope selection system would be a good idea so you could 
just direct to the scope you want and not have to scroll through many scopes 
before reaching the one you wish to use. 

  Note, The Today scope is improving slowly and the time for each item
  to show is reducing, but basically its still far too slow to be the
  main scope. If you refresh say the BBC news scope it completes in a 2
  seconds, the today scope still takes 10s (even after fixing the delay
  to show calls and texts). I understand people are working very hard to
  improve this key area.

  Thanks for your support

  Regards

  Dave H

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

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

[Touch-packages] [Bug 1583536] Re: mirtest-dev is hard to use as the objects used are compiled with LTO

2016-05-31 Thread Daniel van Vugt

Fix uncommitted from lp:mir/0.23 at revision 3509

** Changed in: mir/0.23
   Status: Fix Committed => Triaged

** Changed in: mir/0.23
Milestone: 0.23.0 => 0.23.1

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

Title:
  mirtest-dev is hard to use as the objects used are compiled with LTO

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  Linking against mirtest-dev in a downstream project fails as no
  symbols are not found in the archive.

  nm -gC /usr/lib/x86_64-linux-gnu/libmir-test-assist.a

  gives lots of "nm: FOO.cpp.o: plugin needed to handle lto object"
  errors

  Replacing the archive with one built without LTO fixes the problems.

  Adding LTO to the downstream project didn't.

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

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

[Touch-packages] [Bug 1587699] [NEW] Screen blank/black after splash screen

2016-05-31 Thread Hassan Williamson

Public bug reported:

It seems whenever I try to run `prime-select nvidia` I get a blank
screen after the splash screen. When I am running under `prime-select
intel` - I have no problems.

I triple boot, two of them being Ubuntu (one for testing one for every
day use), and the problem seems to lie only on the every day use one.
Both have 16.04 (except the main one got upgraded from 14.04, and the
testing one from 15.10). Both have the same version of nvidia
(`nvidia-361`). Both seem to have the same configuration. Yet the one I
want it to work on does not work.

I am more than happy to provide any logs needed of both installs to help
diagnose. From what I have seen so far, /etc/X11/xorg.conf are identical
on both.

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

2)
$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+13ubuntu3
  Candidate: 1:7.7+13ubuntu3
  Version table:
 *** 1:7.7+13ubuntu3 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy nvidia-361
nvidia-361:
  Installed: 361.42-0ubuntu2
  Candidate: 361.42-0ubuntu2
  Version table:
 *** 361.42-0ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages
100 /var/lib/dpkg/status

3) I expected to be able to see the lightdm screen after running in
nvidia mode (prime-select nvidia).

4) I see nothing on the screen, but I hear the Ubuntu boot sound
notifying me that the login screen is there. Also, if I type my password
in I can hear my hard drive spin up and the LED blink - telling me that
clearly something is happening.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01: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.1)
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Wed Jun  1 03:04:39 2016
DistUpgraded: 2016-05-13 01:31:31,411 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.2.0-36-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
 virtualbox, 5.0.18, 4.2.0-36-generic, x86_64: installed
 virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:397d]
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GF108M [GeForce GT 540M] [17aa:397d]
InstallationDate: Installed on 2014-12-31 (517 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: LENOVO HuronRiver Platform
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=dddc1c5f-ac3e-48b9-90c3-cd0effbf6a55 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-05-13 (19 days ago)
dmi.bios.date: 10/21/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 45CN38WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.name: HuronRiver Platform
dmi.product.version: Ideapad Z570
dmi.sys.vendor: LENOVO
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.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress

2016-05-31 Thread Shih-Yuan Lee

** Patch removed: "network-manager_1.2.0-0ubuntu0.16.04.3.debdiff"
   
https://bugs.launchpad.net/oem-priority/+bug/1585863/+attachment/4670449/+files/network-manager_1.2.0-0ubuntu0.16.04.3.debdiff

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

Title:
  WiFi malfunction after suspend & resume stress

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

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)   

 
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2

 
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

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

  Expected result:
  The WiFi still functioned.

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

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

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

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

[Touch-packages] [Bug 1570310] Re: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2

2016-05-31 Thread Ari Dwi Utomo

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Opinion

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

Title:
  package systemd 229-4ubuntu4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Opinion

Bug description:
  I was upgrading from 15.10 to 16.04 when this error occur.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  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: Wed Apr 13 21:41:53 2016
  DpkgTerminalLog:
   Preparing to unpack .../systemd_229-4ubuntu4_amd64.deb ...
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  DuplicateSignature:
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2016-01-08 (96 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X455LJ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=70fa96eb-e0d8-4e65-b049-9cb150759b40 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-04-13 (0 days ago)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X455LJ.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X455LJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX455LJ.203:bd04/22/2015:svnASUSTeKCOMPUTERINC.:pnX455LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X455LJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1587690] Re: systemd-resolved crashed with SIGSEGV

2016-05-31 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1586991, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1587690/+attachment/4673909/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1587690/+attachment/4673912/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1587690/+attachment/4673918/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1587690/+attachment/4673920/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1587690/+attachment/4673921/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1587690/+attachment/4673922/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1587690/+attachment/4673924/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1586991
   systemd-resolved crashed with SIGSEGV in dns_transaction_cache_answer()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-resolved crashed with SIGSEGV

Status in systemd package in Ubuntu:
  New

Bug description:
  Restart and open apport

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  Uname: Linux 4.6.0-040600-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Tue May 31 21:44:10 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2015-07-26 (310 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.6.0-040600-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x55da05b18ee7:mov0x5c(%rax),%r8d
   PC (0x55da05b18ee7) ok
   source "0x5c(%rax)" (0x005c) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Title: systemd-resolved crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1452941] Re: PPTP VPN fails to connect in 15.04, but works in 14.04/14.10

2016-05-31 Thread Takeuchi

This bug also affects me. The workaround to remove the gateway from the
static routes (leaving it blank) works like a charm!

Basically, just go to your static route configuration (ipv4 tab >
Advanced) and leave the gateway blank.

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

Title:
  PPTP VPN fails to connect in 15.04, but works in 14.04/14.10

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I can create a PPTP VPN connection and connect to a remote network in
  Ubuntu 14.04/14.10 (Unity live boot DVD) but the connection does not
  work in Ubuntu 15.04 (Unity live boot USB), even though I am using the
  exact same GUI configuration settings in the Network-Manager (I have
  confirmed this several times).  In addition to the live boot
  instances, the PPTP VPN connected without problems for me on my
  14.04/14.10 installs, but failed on a fresh harddisk install of Ubuntu
  MATE 15.04.

  The error that I get in a notification pop-up window when trying to
  connect on 15.04 is: "The VPN connection 'VPN connection 1' failed
  because the VPN service returned invalid configuration."

  ubuntu@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  ubuntu@ubuntu:~$ apt-cache policy network-manager
  network-manager:
Installed: 0.9.10.0-4ubuntu15
Candidate: 0.9.10.0-4ubuntu15
Version table:
   *** 0.9.10.0-4ubuntu15 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CurrentDesktop: Unity
  Date: Thu May  7 22:55:12 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.20 
   207.173.246.134 via 192.168.0.1 dev wlan0  src 192.168.0.20
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
LANbeforetime  1fefef93-2d1c-41eb-ad55-3f6c234d7023  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
 
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1504698] Re: NetworkManager crashes after reboot

2016-05-31 Thread Daniel Kusytsch

This bug is introduced between network manager versions
0.9.10.0-4ubuntu23 and 1.0.4-0ubuntu1. Just tested network-manager
1.2.2-0ubuntu3 and the bug is still present.

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

Title:
  NetworkManager crashes after reboot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my HP Chromebook 14  from 15.04 to 15.10 beta. After cold
  boot, NetworkManager crashes and I get the popup to send a bug report
  for a NM crash. There is no network, either. Restarting the
  NetworkManager service from a terminal fixes the issue ... until next
  reboot :)

  ~$ sudo service NetworkManager restart

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Oct  9 16:39:39 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 600 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.38  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
MilanoFamily  fbced2d1-aa52-4d01-81dd-9f56594e0911  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyUSB0  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
------  
   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
------
  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/1504698/+subscriptions

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

[Touch-packages] [Bug 1579267] Re: plymouth-start.service: After: reference to non-existent keyboard-setup.service

2016-05-31 Thread Mathieu Trudel-Lapierre

** Changed in: console-setup (Ubuntu)
   Status: New => In Progress

** Changed in: console-setup (Ubuntu)
   Importance: Undecided => Medium

** Also affects: console-setup (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: console-setup (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: console-setup (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: console-setup (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: console-setup (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  plymouth-start.service: After: reference to non-existent keyboard-
  setup.service

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  In Progress

Bug description:
  16.04 amd64.

  plymouth-start.service refers to a non-existent keyboard-
  setup.service:

  $ grep keyboard -r /lib/systemd/system/*
  /lib/systemd/system/plymouth-start.service:After=systemd-udev-trigger.service 
systemd-udevd.service keyboard-setup.service
  tj@T300CHI:~$ apt-file search keyboard-setup.service
  tj@T300CHI:~$

  The file only exists in 16.10 in console-setup-linux

  This caught me out whilst I was debugging some console-setup issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1579267/+subscriptions

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

[Touch-packages] [Bug 1584069] Re: change_profile rules need a modifier to allow non-secureexec transitions

2016-05-31 Thread Tyler Hicks

Fix committed as r3469

** Changed in: apparmor
   Status: In Progress => Fix Committed

** Changed in: apparmor (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  change_profile rules need a modifier to allow non-secureexec
  transitions

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  As it stands today, all exec transitions triggered by a change_profile
  rule cause the AT_SECURE flag in the auxiliary vector to be set due to
  the kernel function apparmor_bprm_secureexec() returning 1 while
  setting up the execution environment. This causes libc to always scrub
  the environment variables during such an exec transition.

  There should be a way to indicate, in the policy language, that
  AT_SECURE should not be triggered. This would be equivalent to the
  file rule type having the Px permission to trigger AT_SECURE and the
  px permission to not trigger it. The file rule type even has an
  'unsafe' modifier keyword that could be reused as the change_profile
  modifier keyword.

  Steps to show that AT_SECURE is being set:

  # Build a test program to dump the AT_SECURE flag
  $ cat < print_at_secure.c
  #include 
  #include 

  int main(void)
  {
printf("AT_SECURE = %lu\n", getauxval(AT_SECURE));
return 0;
  }
  EOF
  $ gcc -o print_at_secure print_at_secure.c

  # Load the test profile that allows all file accesses and any change_profile 
operations
  $ echo "profile test { file, change_profile, }" | sudo apparmor_parser -qr

  # Run bash under the test profile
  $ aa-exec -p test -- bash

  # Show the AT_SECURE is not set on exec
  $ ./print_at_secure
  AT_SECURE = 0

  # Set up an exec transition (change_profile from the test profile back to the 
test profile)
  $ echo "exec test" > /proc/self/attr/exec

  # See that AT_SECURE is now set on exec
  $ ./print_at_secure
  AT_SECURE = 1

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

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

[Touch-packages] [Bug 1565717] Re: No connection after returning from area without coverage

2016-05-31 Thread Tony Espy

OK, so there are two low-level problems:

1. InProgress error returned by SetProperty('Active',true) call to ofono
for a gprs-context.

Alfonso's first syslog shows that this can happen, but I'm not sure
exactly how to reproduce.  NM would've had to start activation, then
Attached bounced down and back up again, without ofono canceling the
context activation.  The next time NM tried to activate, in theory it'd
be returned InProgress.

Right now, NMModemOfono::stage1_prepare_done() always emits a failed
MODEM_PREPARE_RESULT for any error returned by ofono in response to the
SetProperty call.

The fix is to check explicitly for error == InProgress, and just return
without emitting a result ( this is the same thing that happens if no
error is returned ).

2. The context in question is already active.

This can be reproduced by killing NetworkManager, when it restarts, it
gets stuck in the Prepare stage.

This is because ofono doesn't send an error if SetProperty('Active',
true) would have no effect on the property's value ( ie. if it's already
true ).  Furthermore, as the context 'Settings' property is already
populated, context_property_changed() is never invoked for the
'Settings', so a MODEM_PREPARE_RESULT is never sent, true or false, so
the device is stuck in PREPARE state.

The fix involves the following changes to NMModemOfono:

do_context_activate() should check the cached value of 'Active', and if
true, should call a new function called process_context_settings(),
which should be based on the current context_property_changed().  This
will result in a PREPARE_RESULT being generated, and thus the device
should no longer get stuck in PREPARE state.

In theory this should work, as NM should just deal with any EEXISTS
errors when it tries to re-configure the IP address, routing table
entries, and DNS nameservers.  It this *doesn't* just work, then we may
need some upstream assistance.

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

Title:
  No connection after returning from area without coverage

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  After moving in an out of my own "faraday cage" an ubuntu phone, NM
  got into an state where *both* WiFi and cellular data were
  disconnected and NM was not able to recover.

  
  * This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 336
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-17 09:19:51
  version version: 336
  version ubuntu: 20160517
  version device: 20160329-a9bacdb
  version custom: 20160505-975-38-9
  

  Originally reported for:

  NM version:
  network-manager  0.9.10.0-4ubuntu15.1.11

  root@ubuntu-phablet:/home/phablet# system-image-cli -i
  current build number: 298
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-30 16:58:21
  version version: 298
  version ubuntu: 20160330
  version device: 20160323-1467d3c
  version custom: 20160324--36-54-vivid

  phablet@ubuntu-phablet:~$ nmcli d
  DEVICE   TYPE  STATE CONNECTION
  ril_0gsm   connecting (prepare)  /214050030479893/context1
  wlan0wifi  disconnected  --
  ril_1gsm   unavailable   --
  ifb0 ifb   unmanaged --
  ifb1 ifb   unmanaged --
  lo   loopback  unmanaged --
  ip6tnl0  unknown   unmanaged --
  sit0 unknown   unmanaged --
  tunl0unknown   unmanaged --

  phablet@ubuntu-phablet:~$ nmcli c
  NAME   UUID  TYPE 
DEVICE
  WLAN_1609  fe9b17ad-88fa-43b7-bcab-8fbc1985ce42  
802-11-wireless  --
  Wireless   98ff5b6f-b0d9-471a-b867-8a7be51e12c2  
802-11-wireless  --
  Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089  
802-11-wireless  --
  /234304107917083/context1  1f192cdc-ccea-2dc3-fa13-619ed3053828  gsm  
--
  /214321010036211/context1  0992421f-2369-0765-ceaa-ba2a3091e111  gsm  
--
  /214050030479893/context1  d30e4f19-9d00-ab1f-ab43-6d9c1b628556  gsm  
ril_0
  /214019301737411/context1  88b28978-e2fc-6336-8665-b0ae78d321ae  gsm  
--

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  Settings = { Gateway=10.50.83.25 
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0 
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
  Name = Pepephone
  Type = internet
  AccessPointName = gprs.pepephone.com

[Touch-packages] [Bug 1522992] Re: /usr/bin/lxc-stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

2016-05-31 Thread Łukasz Zemczak

I should be able to take care of it, yes. Let me add that to my TODO
list.

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

Title:
  /usr/bin/lxc-
  stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding lxc.  This problem was most recently seen with version
  1.1.5-0ubuntu0.15.04.3, the problem page at
  https://errors.ubuntu.com/problem/d640a68bf7343705899d7ca8c6bc070d477cd845
  contains more details.

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

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

[Touch-packages] [Bug 1497611] Re: navigation through scopes very slow

2016-05-31 Thread Dave H

Hi Kevin,

Regarding the speed and operation of the dash/scope scrolling and swiping, I 
read a report that the “turn the book page” current scope style, could change 
to a vertical swipe,  similar to the one used in the browser. I tried this idea 
using the browser and would like to say how flat and uninteresting it is when 
compared to the natural action of swiping right/left through full pages. I 
think this idea is a real mistake and could reduce appeal of scopes and there 
aesthetic look and feel. I think a quick link approach (as suggested above) 
“using the page dots” could work great, and you don’t need to start again from 
scratch with an uninteresting, easy solution. Please can you reconsider this 
important scope navigation and focus on improving the current method speed and 
refresh. 
Your support is appreciated.

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

Title:
  navigation through scopes very slow

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I an using a Meizu MX4 with software version 15.04 (r4). Even though this is 
a powerfull phone moving between scopes is still laggy and slow also some auto 
refresh as you move to them. 
  I would like to suggest that auto refresh takes place in the background so 
all scopes are ready when you flick through them. 
  Also I wonder if a scope selection system would be a good idea so you could 
just direct to the scope you want and not have to scroll through many scopes 
before reaching the one you wish to use. 

  Note, The Today scope is improving slowly and the time for each item
  to show is reducing, but basically its still far too slow to be the
  main scope. If you refresh say the BBC news scope it completes in a 2
  seconds, the today scope still takes 10s (even after fixing the delay
  to show calls and texts). I understand people are working very hard to
  improve this key area.

  Thanks for your support

  Regards

  Dave H

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

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

[Touch-packages] [Bug 1504698] Re: NetworkManager crashes after reboot

2016-05-31 Thread Daniel Kusytsch

This bug is also present in the current 16.04 LTS release, the crash can
be prevented by blacklisting the cdc_ether driver. The 3g modem module I
believe is responsible for the crash is the huawei mu733. This bug was
not present in the 15.04 release.

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

Title:
  NetworkManager crashes after reboot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my HP Chromebook 14  from 15.04 to 15.10 beta. After cold
  boot, NetworkManager crashes and I get the popup to send a bug report
  for a NM crash. There is no network, either. Restarting the
  NetworkManager service from a terminal fixes the issue ... until next
  reboot :)

  ~$ sudo service NetworkManager restart

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Oct  9 16:39:39 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 600 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.38  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
MilanoFamily  fbced2d1-aa52-4d01-81dd-9f56594e0911  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyUSB0  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
------  
   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
------
  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/1504698/+subscriptions

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

[Touch-packages] [Bug 1504698] Re: NetworkManager crashes after reboot

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

Title:
  NetworkManager crashes after reboot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my HP Chromebook 14  from 15.04 to 15.10 beta. After cold
  boot, NetworkManager crashes and I get the popup to send a bug report
  for a NM crash. There is no network, either. Restarting the
  NetworkManager service from a terminal fixes the issue ... until next
  reboot :)

  ~$ sudo service NetworkManager restart

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Oct  9 16:39:39 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 600 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.38  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
MilanoFamily  fbced2d1-aa52-4d01-81dd-9f56594e0911  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyUSB0  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
------  
   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
------
  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/1504698/+subscriptions

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

[Touch-packages] [Bug 1587642] Re: On boot, the following notice: ? System Program Problem Detected. Also monitor setting missing from menu

2016-05-31 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1587141, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1587642/+attachment/4673761/+files/CoreDump.gz

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1587642/+attachment/4673768/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1587642/+attachment/4673770/+files/ProcStatus.txt

** This bug has been marked a duplicate of bug 1587141
   systemd-resolved crashed with SIGABRT: Assertion 'p->n_ref > 0' failed at 
../src/resolve/resolved-dns-packet.c:184, function dns_packet_unref(

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  On boot, the following notice: ? System Program Problem Detected.
  Also monitor setting missing from menu

Status in systemd package in Ubuntu:
  New

Bug description:
  monitor settings missing from menu

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic i686
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: i386
  Date: Tue May 31 11:21:20 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2016-05-14 (17 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160513)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VIA Technologies, Inc. P4X400-8235
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=959cce9b-a4f6-442c-8257-c8469fe3e02d ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/19/2003
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: P4X400-8235
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/19/2003:svnVIATechnologies,Inc.:pnP4X400-8235:pvr:rvn:rnP4X400-8235:rvr:cvn:ct3:cvr:
  dmi.product.name: P4X400-8235
  dmi.sys.vendor: VIA Technologies, Inc.

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

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

[Touch-packages] [Bug 1500627] Re: Indic languages Layouts (e.g. Hindi, Bengali, Tamil, Telugu, Punjabi etc.) for Ubuntu Touch

2016-05-31 Thread Anupam

Here are my inelegant workarounds for
Bengali:
https://uappexplorer.com/app/type-bangla.anupam
Devanagari (Sanskrit/ Hindi/ Marathi/ Nepali)):
https://uappexplorer.com/app/type-devanagari.anupam

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

Title:
  Indic languages Layouts (e.g. Hindi, Bengali, Tamil, Telugu, Punjabi
  etc.) for Ubuntu Touch

Status in ubuntu-keyboard:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  There are no keyboard layouts for Indic languages in ubuntu touch.
  Please provide layouts for languages like Hindi, Bengali, Tamil,
  Telugu etc. or an option to add custom layouts.

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

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

[Touch-packages] [Bug 1543351] Re: Add on-screen-keyboard support for Xmir/Libertine apps

2016-05-31 Thread Dave H

Hi, have just received my BQ M10 HD tablet (white one), great to see
Ubuntu Touch working similar to my MX4. As other users have said, the
one thing that hits you when you fire up LibreOffice is the lack of the
on screen keyboard. After using my daughters 10.1” HP pavilion X2 with
Windows 10, I was surprised that no on screen keyboard was offered on
Ubuntu Touch. The idea to add manual switch should be fine. Good to see
that its planned for OTA-12, thanks for your support.

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

Title:
  Add on-screen-keyboard support for Xmir/Libertine apps

Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in Libertine:
  In Progress
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  From perspective of product management - this is currently not a
  requirement, just want to capture it for future

  we currently can't interact with puritine apps relying on the OSK

  to add this feature in where text-box selection on an xapp results in
  triggering the osk, in unity8 would be a very large/complicated
  effort. However, with a manual capability to trigger the OSK this
  could be achieved.

  For design team
  one idea was to add a show/hide button for the OSK.
  realizing this may be undesirable to add another indicator item - a follow-on 
idea might be to add an alpha button in the corner of the xmir-root window (the 
window that holds any xapp at the moment)
  this way the button presence would only be limited to the Xapp interaction.

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

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

[Touch-packages] [Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up

2016-05-31 Thread Guga

Were you able to confirm this? It seems very odd, since regular DHCP
operations are usually performed with userspace clients, not ipconfig
(usually used in early userspace/startup environments).

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

Title:
  Delay during PXE Boot, IP-Config gives up

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Trusty:
  Fix Released
Status in klibc source package in Wily:
  Fix Committed
Status in klibc source package in Xenial:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  [Impact]
  PXE booting users with live images or other minimal setups using klibc-utils.

  [Test case]
  Attempt to PXE boot using Ubuntu live images; see below for details.

  [Regression potential]
  This forces the yiaddr (client requested/current IP) to be set to 0 when 
sending DHCP messages; currently the messages are DHCPREQUEST and DHCPDISCOVER, 
which should typically only happen when there is no IP set on the device and it 
is otherwise unable to receive unicast (on account of not being configured). 
Should there be a need to send other messages which would require setting the 
yiaddr value to the current configured IP address, a naive change would break. 
The yiaddr variable would need to be adjusted to pull value from a new 
location, or initialized directly by the callers to dhcp_send() where the 
business logic would reside.

  ---

  Attempting to PXE boot both the 12.04.3 and 14.04 Live images.   PXE
  boot works normally (PXE Menu, select desired image, image begins
  loading), then the boot process hangs while IP-Config attempts to get
  an IP address:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 3 secs - giving up

  These lines appear very quickly (5 seconds has NOT elapsed), after
  about a minute, we get this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 4 secs - giving up

  Some time later, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 6 secs - giving up

  Until finally, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 9 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: eth0 guessed broadcast address 172.25.11.31
  IP-Config: eth0 complete (dhcp from 172.25.10.20):
  (snip)

  While watching the DHCP server logs, Ubuntu is either not sending a
  DHCP Discover at times, or is not replying back with a DHCPRequest
  during these sessions, presumably ignoring an response from the DHCP
  server.  From the initial booting of the system via PXE, to when
  Ubuntu finally shows the desktop, almost 12 minutes will have elapsed.

  I am seeing this same behavior on both 12.04.3 and 14.04.  After
  finding a number of similar erros via Google and no real resolution, I
  have opened this bug.

  The system experiencing this issue has multiple ethernet interfaces
  (actual HW, not a VM), some Google found solutions suggest hard coding
  DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't
  acceptable as a system attempting to PXE boot may be using an
  alternate port for the network.

  I have found what looks to be a very similar bug filed for Debian,
  #584583, which also contains a patch for this issue (under Debian).

  I have no problems in PXE booting to various Windows, RedHat, Centos,
  or Fedora OSs.  Ubuntu is the only Live OS that I'm attempting to boot
  at present.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Jun  6 20:22:09 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug

[Touch-packages] [Bug 1579267] Re: plymouth-start.service: After: reference to non-existent keyboard-setup.service

2016-05-31 Thread Mathieu Trudel-Lapierre

Nice catch.

There is a keyboard-setup.init script; but that's not being installed
either because for upstart, all these were replaced by a single upstart
job to deal with the keyboards.

The net result appears to be that keymap is not correctly set in a VT --
I'll look to find other reports of this issue, there is bound to be
others.

There is another fix I need to land for console-setup related to the
move from upstart to systemd; we can land all this together.

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

Title:
  plymouth-start.service: After: reference to non-existent keyboard-
  setup.service

Status in console-setup package in Ubuntu:
  New

Bug description:
  16.04 amd64.

  plymouth-start.service refers to a non-existent keyboard-
  setup.service:

  $ grep keyboard -r /lib/systemd/system/*
  /lib/systemd/system/plymouth-start.service:After=systemd-udev-trigger.service 
systemd-udevd.service keyboard-setup.service
  tj@T300CHI:~$ apt-file search keyboard-setup.service
  tj@T300CHI:~$

  The file only exists in 16.10 in console-setup-linux

  This caught me out whilst I was debugging some console-setup issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1579267/+subscriptions

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

[Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right

also, do we want to consolidate/consider this bug a dupe under bug
1497611

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

Title:
  Dash pauses/stutters during scope switching left/right

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

Bug description:
  Dash pauses/stutters during scope switching left/right.

  Watching the log:   tail -f ~/.cache/upstart/unity8-dash.log

  I can see error messages flood out whenever the dash pauses/stutters
  during left/right swipes:

  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"

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

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

[Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right

@tsdgeos - let's just consider this covered under the kpi effort, loop
back and update with results

** No longer affects: unity8 (Ubuntu RTM)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Albert Astals Cid (aacid)

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

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

Title:
  Dash pauses/stutters during scope switching left/right

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

Bug description:
  Dash pauses/stutters during scope switching left/right.

  Watching the log:   tail -f ~/.cache/upstart/unity8-dash.log

  I can see error messages flood out whenever the dash pauses/stutters
  during left/right swipes:

  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"

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

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

[Touch-packages] [Bug 1567350] Re: Web Browser performance/behaviour regression opening a new tab OTA-9 -> OTA-10

2016-05-31 Thread Olivier Tilloy

Yes, that’s because there’s only one instance of the new tab view at
most, so when one has already been instantiated, opening another new
blank tab is very cheap.

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

Title:
  Web Browser performance/behaviour regression opening a new tab OTA-9
  -> OTA-10

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

Bug description:
  Having upgraded from OTA-9 to OTA-10 on my daily phone, it seems
  opening a new tab UX is considerably slower for me than before
  upgrading.

  The experience now is:  1. press new tab button, 2. the bottom bar
  goes away, old web page is shown. 3. Only 2 seconds later, new tab
  opens.

  I don't remember anymore exactly how it was OTA-9, but there wasn't an
  UX problem for me there. The wait time was definitely considerably
  shorter, and maybe the bottom bar didn't disappear before the new tab
  was really opened.

  I've checked that the CPU usage isn't up by any other process, so this
  behavior change would seem to be within webbrowser/oxide.

  Device is Bq Aquaris E4.5.

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

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

[Touch-packages] [Bug 1511824] Re: Can't login as ordinary user with lightdm

2016-05-31 Thread Akshay Jain

I am getting the same problem with a fresh install of Ubuntu 16.04 LTS.
Tried the workarounds from odroid forum, but doesn't seem to help.
Is this bug going to be fixed?

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

Title:
  Can't login as ordinary user with lightdm

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I can't login as ordinary user rose with lightdm.
  It is an Ubuntu 15.04 for armv7l .
  At the beginning I saw the already reported issues with kwallet, which is not 
installed. I commented out the corresponding lines in. I have now:

  root@odroid6:~# cat /etc/pam.d/lightdm
  #%PAM-1.0
  auth requisite pam_nologin.so
  auth sufficient pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  auth optional pam_gnome_keyring.so
  #auth optional pam_kwallet.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  session required pam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optional pam_gnome_keyring.so auto_start
  #session optional pam_kwallet.so auto_start
  session required pam_env.so readenv=1
  session required pam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale
  @include common-password

  and

  root@odroid6:~# cat /etc/pam.d/lightdm-greeter
  #%PAM-1.0
  auth required pam_permit.so
  auth optional pam_gnome_keyring.so
  #auth optional pam_kwallet.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  session required pam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optional pam_gnome_keyring.so auto_start
  #session optional pam_kwallet.so auto_start
  session required pam_env.so readenv=1
  session required pam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale

  It seems that my password is accepted (login via ssh works perfectly),
  but with lightdm I get only a black screen with mouse cursor. Login as
  user odroid which is in group nopasswdlogin with lightdm works.

  After trying to login as user rose, I have to login with ssh and kill
  all processes owned by rose. At the end of /var/log/auth.log I see:

  Oct 28 19:34:17 odroid6 lightdm: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" not met by user "rose"
  Oct 28 19:34:26 odroid6 lightdm: pam_unix(lightdm-greeter:session): session 
closed for user lightdm
  Oct 28 19:34:26 odroid6 lightdm: pam_unix(lightdm:session): session opened 
for user rose by (uid=0)
  Oct 28 19:34:26 odroid6 systemd-logind[651]: New session c8 of user rose.
  Oct 28 19:34:26 odroid6 systemd: pam_unix(systemd-user:session): session 
opened for user rose by (uid=0)
  Oct 28 19:35:10 odroid6 systemd-logind[651]: Removed session c6.
  Oct 28 19:35:10 odroid6 systemd: pam_unix(systemd-user:session): session 
closed for user lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.2-0ubuntu1.1
  Uname: Linux 3.10.82-57 armv7l
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: armhf
  Date: Fri Oct 30 18:14:21 2015
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2015-10-28T17:40:04.609656
  mtime.conffile..etc.pam.d.lightdm.greeter: 2015-10-28T17:53:38.848444

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

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

[Touch-packages] [Bug 1497611] Re: navigation through scopes very slow

realize things have changed quite a bunch since this bug was logged. but
we do have an activity ongoing investigating potential areas of
improvement for dash/scope scrolling and swiping.

We really should consider some investigation just into the flow as
outlined by 2) of comment #7 above.


** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Albert Astals Cid (aacid)

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

Title:
  navigation through scopes very slow

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I an using a Meizu MX4 with software version 15.04 (r4). Even though this is 
a powerfull phone moving between scopes is still laggy and slow also some auto 
refresh as you move to them. 
  I would like to suggest that auto refresh takes place in the background so 
all scopes are ready when you flick through them. 
  Also I wonder if a scope selection system would be a good idea so you could 
just direct to the scope you want and not have to scroll through many scopes 
before reaching the one you wish to use. 

  Note, The Today scope is improving slowly and the time for each item
  to show is reducing, but basically its still far too slow to be the
  main scope. If you refresh say the BBC news scope it completes in a 2
  seconds, the today scope still takes 10s (even after fixing the delay
  to show calls and texts). I understand people are working very hard to
  improve this key area.

  Thanks for your support

  Regards

  Dave H

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

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

[Touch-packages] [Bug 1522992] Re: /usr/bin/lxc-stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

@lukasz could you do the cherry pick

** Changed in: canonical-devices-system-image
 Assignee: Pat McGowan (pat-mcgowan) => Łukasz Zemczak (sil2100)

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

Title:
  /usr/bin/lxc-
  stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding lxc.  This problem was most recently seen with version
  1.1.5-0ubuntu0.15.04.3, the problem page at
  https://errors.ubuntu.com/problem/d640a68bf7343705899d7ca8c6bc070d477cd845
  contains more details.

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

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

[Touch-packages] [Bug 1586100] Re: can't add an ubuntu one account

2016-05-31 Thread Rodney Dawes

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

This is caused by the app being broken as uploaded to the server, due to
a bug in the server which I've marked this bug a duplicate of. This
should be fixed in the production server soon, but until it is, trying
to install some of the apps from this developer will cause this issue to
happen.

** This bug has been marked a duplicate of bug 1585337
   Uploading snap as click breaks the world

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

Title:
  can't add an ubuntu one account

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Incomplete

Bug description:
  M10 "forgot" my ubuntu one account. While trying to install something
  from the store I need to enter my ubuntu one account information which
  is weired because I already did in the past and no worries so far.
  When I enter the information and try to log in I still get the reply
  that I don't have an account. I should go to the account settings. But
  there is no option to add an ubuntu one account.

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

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

[Touch-packages] [Bug 1567350] Re: Web Browser performance/behaviour regression opening a new tab OTA-9 -> OTA-10

It's quite noticeable on M10
FWIW if you open a second new tab while the first is displayed its immediate

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

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

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

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Web Browser performance/behaviour regression opening a new tab OTA-9
  -> OTA-10

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

Bug description:
  Having upgraded from OTA-9 to OTA-10 on my daily phone, it seems
  opening a new tab UX is considerably slower for me than before
  upgrading.

  The experience now is:  1. press new tab button, 2. the bottom bar
  goes away, old web page is shown. 3. Only 2 seconds later, new tab
  opens.

  I don't remember anymore exactly how it was OTA-9, but there wasn't an
  UX problem for me there. The wait time was definitely considerably
  shorter, and maybe the bottom bar didn't disappear before the new tab
  was really opened.

  I've checked that the CPU usage isn't up by any other process, so this
  behavior change would seem to be within webbrowser/oxide.

  Device is Bq Aquaris E4.5.

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

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

[Touch-packages] [Bug 1579389] Re: wireless keeps freezing

Can you attach /var/log/syslog when this occurs. and the output of
"nmcli d"

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

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

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  wireless keeps freezing

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi there,

  After i did update my ubuntu to OTA 10.1 on my bq 4.5, my wireless
  began to freeze everytime the phone idles, it doesn't matter if i am
  home or at work or in a cafe, everytime the phone is doing nothing the
  wireless stop working, So i have to turn it off and then on and
  everything works fine till the phone idles again.

  I have asked on IRC and i was informed to come here report a bug. If
  you guys want me to send you files or anything just give me the
  commands i need to type in my terminal or what files i need to send to
  here.

  Regards,

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

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

[Touch-packages] [Bug 1518385] Re: Proximity sensor kept active after call ended

@alf - should this be covered under ota12 with the repowerd release?

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

Title:
  Proximity sensor kept active after call ended

Status in Canonical System Image:
  Confirmed
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Open the dialer app.
  - Make a call.
  - Accept the call in the receiver phone.
  - Leave the phone for a minute.
  - Finish the call on the receiver phone.

  Expected result.
  - Leaving the phone for a minute must not dim the screen.
  - After the call is finished, the proximity sensor must be deactivated.

  Actual result.
  - After a minute the screen dims.
  - After the call is finished, the proximity sensor is active.

  current build number: 27
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en

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

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

[Touch-packages] [Bug 1584348] Re: app blocked after suspend

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  app blocked after suspend

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

Bug description:
  When you let an app opened after a while (about hours) and after that you try 
to work with it the app sometimes does not respond.
  I saw it with a lot of apps (camera, dialer, facebook, telegram, webbrowser...

  Atached you'll find a video where you can see me trying to use camera
  app without any result.

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

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

[Touch-packages] [Bug 1586050] Re: Splashscreen icon rotates several times when app uses desktop flag X-Ubuntu-Rotates-Window-Contents=true

2016-05-31 Thread Daniel d'Andrada

** Changed in: qtmir
   Status: In Progress => Triaged

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  Splashscreen icon rotates several times when app uses desktop flag X
  -Ubuntu-Rotates-Window-Contents=true

Status in Canonical System Image:
  In Progress
Status in QtMir:
  Triaged
Status in camera-app package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  On the BQ M10 (frieza), launching an app while holding the device in
  landscape orientation makes its splashscreen icon rotate several times
  without any apparent reason if the desktop file contains the flag X
  -Ubuntu-Rotates-Window-Contents=true

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

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

[Touch-packages] [Bug 1586219] Re: U1 login window opens behind pay-ui window

2016-05-31 Thread Daniel d'Andrada

** Changed in: qtmir (Ubuntu)
   Status: Triaged => In Progress

** Changed in: unity8 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  U1 login window opens behind pay-ui window

Status in Canonical System Image:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  In today's phone images, a very basic test case fails: Purchasing an
  app on a freshly-flashed phone.

  Specifically, after tapping the app's price button to initiate a
  purchase, the pay-ui's "Loading..." dialog appears and never
  disappears or times out.  If I hit its "Cancel" button, I see the U1
  login window.  Completing the login then returns the view to the app's
  summary screen in the click store.

  What's supposed to happen is:
  - Tap the price button.
  - Get a U1 login window.
  - Complete the login.
  - Get a payment confirmation window.

  I'm not completely sure what causes this, but it looks like the U1 login 
window is simply appearing underneath the pay-ui dialog instead of above it.  
Dobey found this error in the logs:
  2016-05-26 20:34:53,467 - WARNING - QWindow::fromWinId(): platform plugin 
does not support foreign windows.

  This should probably be fixed before OTA12, since it's a step backward
  in the first-time app purchase flow.

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

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

[Touch-packages] [Bug 1586219] Re: U1 login window opens behind pay-ui window

2016-05-31 Thread Michał Sawicz

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

** Changed in: qtmir (Ubuntu)
   Importance: Undecided => Critical

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => Critical

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

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

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  U1 login window opens behind pay-ui window

Status in Canonical System Image:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  In today's phone images, a very basic test case fails: Purchasing an
  app on a freshly-flashed phone.

  Specifically, after tapping the app's price button to initiate a
  purchase, the pay-ui's "Loading..." dialog appears and never
  disappears or times out.  If I hit its "Cancel" button, I see the U1
  login window.  Completing the login then returns the view to the app's
  summary screen in the click store.

  What's supposed to happen is:
  - Tap the price button.
  - Get a U1 login window.
  - Complete the login.
  - Get a payment confirmation window.

  I'm not completely sure what causes this, but it looks like the U1 login 
window is simply appearing underneath the pay-ui dialog instead of above it.  
Dobey found this error in the logs:
  2016-05-26 20:34:53,467 - WARNING - QWindow::fromWinId(): platform plugin 
does not support foreign windows.

  This should probably be fixed before OTA12, since it's a step backward
  in the first-time app purchase flow.

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

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

[Touch-packages] [Bug 1586668] Re: Unity launcher shows gaps between application icons

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Unity launcher shows gaps between application icons

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

Bug description:
  I do not have a reliable way to reproduce this bug, but it has been
  reproducible quite often. The Unity launcher (sidebar) can reach a
  weird state where a gap (the size of an application icon) is visible
  between 2 application icons. As you scroll the launcher up and down,
  you will notice that the missing application icon is *behind* its
  adjacent application icon. When you click on the adjacent application
  icon, it opens the application which is hidden beneath.

  BQ Aquaris E4.5
  RC-Proposed r345

  This issue has been reproducible for quite some images .. maybe even
  from r300 onwards.

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

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

[Touch-packages] [Bug 1586219] Re: U1 login window opens behind pay-ui window

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  U1 login window opens behind pay-ui window

Status in Canonical System Image:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  In today's phone images, a very basic test case fails: Purchasing an
  app on a freshly-flashed phone.

  Specifically, after tapping the app's price button to initiate a
  purchase, the pay-ui's "Loading..." dialog appears and never
  disappears or times out.  If I hit its "Cancel" button, I see the U1
  login window.  Completing the login then returns the view to the app's
  summary screen in the click store.

  What's supposed to happen is:
  - Tap the price button.
  - Get a U1 login window.
  - Complete the login.
  - Get a payment confirmation window.

  I'm not completely sure what causes this, but it looks like the U1 login 
window is simply appearing underneath the pay-ui dialog instead of above it.  
Dobey found this error in the logs:
  2016-05-26 20:34:53,467 - WARNING - QWindow::fromWinId(): platform plugin 
does not support foreign windows.

  This should probably be fixed before OTA12, since it's a step backward
  in the first-time app purchase flow.

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

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

[Touch-packages] [Bug 1587598] Re: Review android implementation for display control during calls and notifications

** Also affects: dialer-app (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Review android implementation for display control during calls and
  notifications

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

Bug description:
  For example  
http://androidxref.com/5.1.1_r6/xref/packages/apps/InCallUI/src/com/android/incallui/ProximitySensor.java#174
  has some interesting logic.

  In our case I am unsure where this logic would live.

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

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

[Touch-packages] [Bug 1586955] Re: User can swipe the incoming call notification dialog

2016-05-31 Thread Michał Sawicz

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Incomplete

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

** Also affects: ubuntu-ux
   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/1586955

Title:
  User can swipe the incoming call notification dialog

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  current build number: 338
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  
  Test Case:
  1. With DUT locked and display turned off, send a call to the DUT
  2. On DUT, when the incoming call notification is displayed, change the 
volume with the hardware buttons
  3. Wait until the answer dialog is displayed again and do a left edge swipe

  Aktual result
  User can swipe the incoming call notification dialog, leaving no way to take 
or reject the call.

  Expected result
  The dialog cannot be dismissed.

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

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

[Touch-packages] [Bug 1552371] Re: Unexpected display on

2016-05-31 Thread Alejandro J. Cura

The "home" button accidentally turning the screen on is confirmed in
this thread:
https://plus.google.com/u/0/108188125572924200710/posts/aBuWYcnSyQt?cfem=1

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

Title:
  Unexpected display on

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  NOTE: kgunn suggests this bug be about 1) not 2) here

  1)
  I have been noticing my phone and tablet occasionally turning on without 
interaction. Several times with my phone in my pocket I found it in the 
emergency call UI
  I also see the tablet display turn on while lying idle on the desk. Freiza & 
Arale

  2)
  I have reproduced one case such that turning on a BT device (headset) causes 
the phone to light up and display the volume slider. Similarly turning on the 
BT keyboard while the tablet screen is off caused the display to turn on.These 
may be as intended.

  I suspect other BT events can similarly resume the device and/or turn on the 
display if it happens to be awake due to the 5 min polling timer.
  The proximity sensor is also not honored when this happens, if its covered 
the screen still comes on.

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

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

[Touch-packages] [Bug 1524648] Re: Display doesn't turn on for incoming phone call when proximity sensor triggered

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

This sounds like bug #1543948 so suping it there, change back if you
disagree.

** This bug has been marked a duplicate of bug 1543948
   Proximity sensor stops reporting events on arale

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

Title:
  Display doesn't turn on for incoming phone call when proximity sensor
  triggered

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  I just received two phone calls.  In each case the phone started
  ringing but the screen stayed black.  In the first case I let it ring
  for a while hoping that it would magically wake up, since some bugs do
  seem to work that way.  But nothing happened.  I was unwilling to
  press the power button since in iOS that immediately hangs up the
  call.  Eventually however I did press it, and the screen woke up.  But
  I was too late to answer the call.  When the person phoned back the
  screen was black again, so I pressed the power button and was then
  able to slide the slider to answer the call.

  I don't think this is the same as Bug #1493574, since that bug seems
  to happen after the phone has been answered.

  Syslog of about the right time attached.  Phone reports the times of
  the calls as 15:41 and 15:47.

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

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

[Touch-packages] [Bug 1524648] Re: Display doesn't turn on for incoming phone call when proximity sensor triggered

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

** Tags added: display-control

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

Title:
  Display doesn't turn on for incoming phone call when proximity sensor
  triggered

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  I just received two phone calls.  In each case the phone started
  ringing but the screen stayed black.  In the first case I let it ring
  for a while hoping that it would magically wake up, since some bugs do
  seem to work that way.  But nothing happened.  I was unwilling to
  press the power button since in iOS that immediately hangs up the
  call.  Eventually however I did press it, and the screen woke up.  But
  I was too late to answer the call.  When the person phoned back the
  screen was black again, so I pressed the power button and was then
  able to slide the slider to answer the call.

  I don't think this is the same as Bug #1493574, since that bug seems
  to happen after the phone has been answered.

  Syslog of about the right time attached.  Phone reports the times of
  the calls as 15:41 and 15:47.

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

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

[Touch-packages] [Bug 1587321] Re: Browser: Path component of URL is hidden by default

2016-05-31 Thread Olivier Tilloy

Thanks for the detailed argumentation, your concerns make sense. Let’s
see what the design team thinks.

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

Title:
  Browser: Path component of URL is hidden by default

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Current behaviour:

  In the web browser the URL gets truncated to just the (sub)domain
  part. For example, the URL of the 'report a bug' form on Launchpad is:

  https://bugs.launchpad.net/canonical-devices-system-image/+filebug

  What is displayed in the browser is:

      bugs.launchpad.net

  The rest of the URL won't show until you touch the address bar. This
  behaviour is problematic, because it hides one of the primary
  attributes of the open web.

  Expected behaviour:

  By default the URL should not be hidden. Because space is constrained
  on the typical devices this browser is used on, the protocol part can
  be omitted by default, as long as the typical lock icon is present for
  HTTPS URL (see attached image). So by default:

  bugs.launchpad.net/canonical-devices-system-image/+filebug

  On touch on the address bar:

  https://bugs.launchpad.net/canonical-devices-system-image/+filebug

  I would recommend following the standard behaviour of modern web
  browsers to emphasize the domain part of the URL in black (with the
  rest of the URL in grey) as well.

  Device: Meizu Pro 5 (OTA 10.2)

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

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

[Touch-packages] [Bug 1560398] Re: Proximity sensor during call doesn't allow dialing options

** Tags added: display-control

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

Title:
  Proximity sensor during call doesn't allow dialing options

Status in Canonical System Image:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  I'm not sure if this is a duplicate of any of the proximity bugs
  already reported (https://bugs.launchpad.net/canonical-devices-system-
  image/+bug/1512100,  https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1493574, https://bugs.launchpad.net/canonical-
  devices-system-image/+bug/1524648,  https://bugs.launchpad.net
  /canonical-devices-system-image/+bug/1523308 to name a few).

  On arale, rc-proposed I made a call, but at a certain point I needed
  to choose an option on an IVR. When I took the phone off my ear, the
  screen would indeed wake up, but when I wanted to press a key number
  (after some trouble to bring up the keyboard altogether) I wouldn't be
  able because the screen would turn off. Eventually I managed to
  "trick" the phone being quick, but it took me some time. Hanging up
  was somehow less painful.

  Maybe a matter of adjusting the distance from which the screen turns
  off during calls?

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

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

[Touch-packages] [Bug 1518385] Re: Proximity sensor kept active after call ended

** Tags added: display-control

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

Title:
  Proximity sensor kept active after call ended

Status in Canonical System Image:
  Confirmed
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Open the dialer app.
  - Make a call.
  - Accept the call in the receiver phone.
  - Leave the phone for a minute.
  - Finish the call on the receiver phone.

  Expected result.
  - Leaving the phone for a minute must not dim the screen.
  - After the call is finished, the proximity sensor must be deactivated.

  Actual result.
  - After a minute the screen dims.
  - After the call is finished, the proximity sensor is active.

  current build number: 27
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en

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

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

[Touch-packages] [Bug 1477939] Re: [mako] Telephony service crashes leave proximity sensor enabled when no call is active

** Tags added: display-control

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

Title:
  [mako] Telephony service crashes leave proximity sensor enabled when
  no call is active

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I had a situation where my phone screen was turned off, but covering
  the proximity sensor and exposing it again turned the screen back on.
  The led to the lock screen being activated while the phone was in my
  pocket. Making and ending a call stopped this behaviour. Further
  investigation and discussion highlighted that ofonod, telephony-
  service-approver and telephony-service-handler all had crash files
  present. It seems that when the telephony service is restarted after a
  crash, it doesn't restore the proximity sensor state.

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

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

[Touch-packages] [Bug 1522992] Re: /usr/bin/lxc-stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

2016-05-31 Thread Stéphane Graber

As far as I know, it's impossible to hit this code path on wily, but we
will push the fix as part of 1.1.6 there anyway.

As far as vivid, it's end of life so we won't be doing a SRU there, but
you're welcome to take care of it.

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

Title:
  /usr/bin/lxc-
  stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding lxc.  This problem was most recently seen with version
  1.1.5-0ubuntu0.15.04.3, the problem page at
  https://errors.ubuntu.com/problem/d640a68bf7343705899d7ca8c6bc070d477cd845
  contains more details.

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

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

[Touch-packages] [Bug 1522992] Re: /usr/bin/lxc-stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

2016-05-31 Thread Stéphane Graber

This was already fixed upstream:
https://github.com/lxc/lxc/commit/23820d548dcd876bd4a8416f80a4d5d1253cd7dd

Vivid is end of life, so if you want a fix for the phone, you could
cherry-pick this into the overlay PPA.

Alternatively we do intend on putting out a 1.1.6 release before 1.1.x
goes entirely end of life in September.

** Changed in: lxc (Ubuntu)
   Status: Incomplete => Triaged

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

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

Title:
  /usr/bin/lxc-
  stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding lxc.  This problem was most recently seen with version
  1.1.5-0ubuntu0.15.04.3, the problem page at
  https://errors.ubuntu.com/problem/d640a68bf7343705899d7ca8c6bc070d477cd845
  contains more details.

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

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

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

** Tags removed: screencontrol
** Tags added: display-control

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

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in powerd package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

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

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

[Touch-packages] [Bug 1522992] Re: /usr/bin/lxc-stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

2016-05-31 Thread Stéphane Graber

We'd need a reproducer.

** Changed in: lxc (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  /usr/bin/lxc-
  stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding lxc.  This problem was most recently seen with version
  1.1.5-0ubuntu0.15.04.3, the problem page at
  https://errors.ubuntu.com/problem/d640a68bf7343705899d7ca8c6bc070d477cd845
  contains more details.

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

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

[Touch-packages] [Bug 1587321] Re: Browser: Path component of URL is hidden by default

2016-05-31 Thread Jeroen Hoek

It is an understandable design decision, and from an aesthetic
standpoint truncating the URL does make sense.

My objection is twofold. One problem is that in my opinion truncating
the URL limits the usability of the browser. Even though plenty of
website do make a mess of anything behind the /, other websites and
services do have understandable, bookmarkable URLs that aid the user in
his or her browsing. Thankfully the URL is still a usable part of many
websites, and modern Javasript frameworks too (traditionally the place
where URLs were mangled for technical reasons) are now once again
embracing proper and usable URLs (e.g., EmberJS).

Philosophically, I worry about hiding something as empowering and basic
to the web as the URL. While I can sympathise with the notion that the
path, query, and fragment parts of a HTTP URL are often technical
details that may clutter the UI and confuse some users, I feel that
hiding it is not in the spirit of the open web, and does not benefit
users in the long run.

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

Title:
  Browser: Path component of URL is hidden by default

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Current behaviour:

  In the web browser the URL gets truncated to just the (sub)domain
  part. For example, the URL of the 'report a bug' form on Launchpad is:

  https://bugs.launchpad.net/canonical-devices-system-image/+filebug

  What is displayed in the browser is:

      bugs.launchpad.net

  The rest of the URL won't show until you touch the address bar. This
  behaviour is problematic, because it hides one of the primary
  attributes of the open web.

  Expected behaviour:

  By default the URL should not be hidden. Because space is constrained
  on the typical devices this browser is used on, the protocol part can
  be omitted by default, as long as the typical lock icon is present for
  HTTPS URL (see attached image). So by default:

  bugs.launchpad.net/canonical-devices-system-image/+filebug

  On touch on the address bar:

  https://bugs.launchpad.net/canonical-devices-system-image/+filebug

  I would recommend following the standard behaviour of modern web
  browsers to emphasize the domain part of the URL in black (with the
  rest of the URL in grey) as well.

  Device: Meizu Pro 5 (OTA 10.2)

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

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

[Touch-packages] [Bug 1587580] [NEW] No way to escape an ampersand in UCAction

2016-05-31 Thread Stefano Verzegnassi

Public bug reported:

Let's say we have an Ubuntu.Action as follow:

import Ubuntu.Components 1.3 as Ubuntu
Ubuntu.Action {
text: "Apps & Scopes"
}

UCAction translates the ampersand as a mnemonic, using QKeySequence.
A way to escape a mnemonic in Qt is to add another ampersand. The resulting 
string is "Apps && Scopes".

The UITK component seems not to take in account this situation, since:

- How the string should be shown in e.g. an ActionBar:
"Apps & Scopes"

- How the string is displayed instead in an ActionBar:
"Apps && Scopes"

QKeySequence returns no mnemonic as expected, but UCAction shows two
ampersands.

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

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

Title:
  No way to escape an ampersand in UCAction

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

Bug description:
  Let's say we have an Ubuntu.Action as follow:

  import Ubuntu.Components 1.3 as Ubuntu
  Ubuntu.Action {
  text: "Apps & Scopes"
  }

  UCAction translates the ampersand as a mnemonic, using QKeySequence.
  A way to escape a mnemonic in Qt is to add another ampersand. The resulting 
string is "Apps && Scopes".

  The UITK component seems not to take in account this situation, since:

  - How the string should be shown in e.g. an ActionBar:
  "Apps & Scopes"

  - How the string is displayed instead in an ActionBar:
  "Apps && Scopes"

  QKeySequence returns no mnemonic as expected, but UCAction shows two
  ampersands.

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

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

[Touch-packages] [Bug 1197134] Re: All SDK applications require access to /dev/binder

2016-05-31 Thread Jamie Strandboge

sharecash1023, you closed this bug by mistake.

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: lxc-android-config (Ubuntu)
   Status: New => Confirmed

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

Title:
  All SDK applications require access to /dev/binder

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  Confirmed
Status in apparmor-easyprof-ubuntu source package in Saucy:
  Won't Fix
Status in lxc-android-config source package in Saucy:
  Won't Fix
Status in apparmor-easyprof-ubuntu source package in Trusty:
  Won't Fix
Status in lxc-android-config source package in Trusty:
  Won't Fix
Status in apparmor-easyprof-ubuntu source package in Utopic:
  Won't Fix
Status in lxc-android-config source package in Utopic:
  Won't Fix

Bug description:
  SDK applications sometimes need the following AppArmor policy to run:

    /dev/binder rw,

  The writes to /dev/binder allow applications to attack binder directly
  which weakens our application confinement policy because there is no
  mediation between binder services.

  The following are the binder services that Ubuntu currently uses:
  - camera
  - media playback service (used by media-hub)

  location was in this group but is already moved away. surface flinger
  was used as a fallback but has been removed. vibrate is not
  implemented but when it is it will only use our API (ie, not binder).
  sensors was implemented as usensors in 14.10. Of the remaining binder
  services listed above, camera is still present for video recording and
  media playback service implements a subset of the android API for
  media playback (it is used by media-hub).

  This bug will be resolved when /dev/binder is no longer used or it is
  only used by one service and therefore the /dev/binder access can move
  into the appropriate policy group.

  Right now, because all apps needs access to /dev/binder, all apps end
  up with access to the camera and media playback services even when
  these policy groups are not specified. Getting rid of /dev/binder
  access is for fine-grained application confinement to work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1197134/+subscriptions

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

[Touch-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

Ok, I hit "close" on that "Could not install 'gconf2'" window, and now
it's hung at trying to unpack baobab_3.18.1-1ubuntu1_amd64.deb

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

Well, if you can tell me how to get you that crash file, I'll do it; but
nothing I am trying is working.

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1586773] Re: CR: query for mobile data volume

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

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  CR: query for mobile data volume

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I as a user want to know or query the consumed mobile data volume per
  day and current month without asking the provider for this values.

  This could be implemented for example in the free space of System
  Settings --> Mobile

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

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

[Touch-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

I tried to run:

I tried to run:

apport-collect 1587550
You need to run 'sudo apt-get install python-apport' for apport-collect to work.

I don't want to run apt-get in the middle of an upgrade, so I tried:

sudo apport-bug /var/crash/gconf2.0.crash
[sudo] password for []: 
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import GLib, Wnck, GdkX11, Gdk
dev@ThinkPad-T530:~$ 
(firefox:17827): dconf-CRITICAL **: unable to create file 
'/home/dev/.cache/dconf/user': Permission denied.  dconf will not work properly.

In the browser I get:

Invalid OpenID transaction

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1587541] Re: systemd-resolved crashed with SIGABRT

2016-05-31 Thread Martin Pitt

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

** This bug is no longer a duplicate of private bug 1587521
** This bug has been marked a duplicate of bug 1587141
   systemd-resolved crashed with SIGABRT: Assertion 'p->n_ref > 0' failed at 
../src/resolve/resolved-dns-packet.c:184, function dns_packet_unref(

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

Title:
  systemd-resolved crashed with SIGABRT

Status in systemd package in Ubuntu:
  New

Bug description:
  no idea.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Tue May 31 09:39:06 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2016-02-05 (115 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=0ff2a1b3-7d37-460b-8dd4-8319c566650a ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-resolved crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z97 Killer
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Killer:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1587550/+attachment/4673621/+files/lspci.txt

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

sudo update-manager -d
Checking for a new Ubuntu release
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
authenticate 'xenial.tar.gz' against 'xenial.tar.gz.gpg' 
extracting 'xenial.tar.gz'
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gconf2.0.crash'

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

I guess I can't post the crash file. Launchpad barfs. Sorry.

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1587550/+attachment/4673620/+files/apt.log

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1587541] Re: systemd-resolved crashed with SIGABRT

2016-05-31 Thread Brian Mingus

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

Bug #1587521 doesn't exist!

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

Title:
  systemd-resolved crashed with SIGABRT

Status in systemd package in Ubuntu:
  New

Bug description:
  no idea.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Tue May 31 09:39:06 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2016-02-05 (115 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=0ff2a1b3-7d37-460b-8dd4-8319c566650a ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-resolved crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z97 Killer
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Killer:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1415902] Re: [Sdk]Bottom edge can get stuck part way exposed

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

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

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

Title:
  [Sdk]Bottom edge can get stuck part way exposed

Status in Ubuntu Clock App:
  Incomplete
Status in messaging-app package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  
  Steps to reproduce:-

  1. Open contacts (or another app with bottom edge such as clock or messaging)
  2. Swipe up from the bottom slowly with one finger.
  3. When half way swiped up, use another finger to swipe in from the right

  Observe the bottom edge panel is now stuck half way up

  4. Go back to the app.

  Note the bottom edge panel is still stuck half way up.

  
  I would expect the bottom edge panel to disappear/cancel or completely rise 
up (depending on how far you pull it) at step 3 or 4.

  Screenshots:-
  http://people.canonical.com/~alan/screenshots/device-2015-01-29-130655.png
  http://people.canonical.com/~alan/screenshots/device-2015-01-29-130713.png

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

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

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

Public bug reported:

Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
guess it's an upgrade to "testing".  Result is a window saying:

Could not install 'gconf2'

The upgrade will continue but the 'gconf2' package may not be in a
working state. Please consider submitting a bug report about it.

dependency problems - leaving triggers unprocessed

[Close]

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


** Tags: update-manager

** Attachment added: "apt-term.log"
   
https://bugs.launchpad.net/bugs/1587550/+attachment/4673617/+files/apt-term.log

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Attachment added: "history.log"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1587550/+attachment/4673619/+files/history.log

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1415902] Re: [Sdk]Bottom edge can get stuck part way exposed

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

** Changed in: messaging-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Sdk]Bottom edge can get stuck part way exposed

Status in Ubuntu Clock App:
  Incomplete
Status in messaging-app package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  
  Steps to reproduce:-

  1. Open contacts (or another app with bottom edge such as clock or messaging)
  2. Swipe up from the bottom slowly with one finger.
  3. When half way swiped up, use another finger to swipe in from the right

  Observe the bottom edge panel is now stuck half way up

  4. Go back to the app.

  Note the bottom edge panel is still stuck half way up.

  
  I would expect the bottom edge panel to disappear/cancel or completely rise 
up (depending on how far you pull it) at step 3 or 4.

  Screenshots:-
  http://people.canonical.com/~alan/screenshots/device-2015-01-29-130655.png
  http://people.canonical.com/~alan/screenshots/device-2015-01-29-130713.png

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

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

[Touch-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Attachment added: "main.log"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1587550/+attachment/4673618/+files/main.log

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Touch-packages] [Bug 1510570] Re: BLE pairing fail

2016-05-31 Thread Guilhem Lettron

I try another merge request with AutoEnable parameter here:
https://code.launchpad.net/~guilhem-fr/bluez/ubuntu-autoenable/+merge/296115

It's based on previous patch submit here.

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Touch-packages] [Bug 1587541] Re: systemd-resolved crashed with SIGABRT

2016-05-31 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1587521, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1587541/+attachment/4673599/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1587541/+attachment/4673602/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1587541/+attachment/4673608/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1587541/+attachment/4673610/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1587541/+attachment/4673611/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1587541/+attachment/4673612/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1587541/+attachment/4673615/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1587521

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-resolved crashed with SIGABRT

Status in systemd package in Ubuntu:
  New

Bug description:
  no idea.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Tue May 31 09:39:06 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2016-02-05 (115 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=0ff2a1b3-7d37-460b-8dd4-8319c566650a ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-resolved crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z97 Killer
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Killer:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1583203] Re: Logitech M557 mouse 'Windows' button blocks OSK