[Touch-packages] [Bug 1502635] Re: bonded interface not starting automatically

[Revati S Hiremath]

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

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

Title:
  bonded interface not starting automatically

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Upgraded over 15.04 to 15.10 Final Beta.  Have a LACP bonded interface
  with two NICs. Using NetworkManager to handle the NIC bonding.  After
  upgrading to 15.10, the bond0 interface no long auto starts when the
  system comes up.  If I manually do a ifconfig bond0 up, it will start.
  As a workaround I added this to rc.local, but not sure where to look
  to see why it's failing in 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
  Uname: Linux 4.2.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct  4 10:43:06 2015
  InstallationDate: Installed on 2012-12-18 (1019 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JournalErrors:
   No journal files were found.
   -- No entries --
  NetDevice.bonding_masters:
   Error: command ['udevadm', 'info', '--query=all', '--path', 
'/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found
   
   X: INTERFACE_MAC=Error: command ['cat', 
'/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: 
/sys/class/net/bonding_masters/address: Not a directory
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-10-03T20:26:36.767583
  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/1502635/+subscriptions

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

[Touch-packages] [Bug 1502635] Re: bonded interface not starting automatically

[Revati S Hiremath]

The patch for the above solution is attached.

** Attachment added: "bugs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+attachment/4506401/+files/bugs.txt

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

Title:
  bonded interface not starting automatically

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Upgraded over 15.04 to 15.10 Final Beta.  Have a LACP bonded interface
  with two NICs. Using NetworkManager to handle the NIC bonding.  After
  upgrading to 15.10, the bond0 interface no long auto starts when the
  system comes up.  If I manually do a ifconfig bond0 up, it will start.
  As a workaround I added this to rc.local, but not sure where to look
  to see why it's failing in 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
  Uname: Linux 4.2.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct  4 10:43:06 2015
  InstallationDate: Installed on 2012-12-18 (1019 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JournalErrors:
   No journal files were found.
   -- No entries --
  NetDevice.bonding_masters:
   Error: command ['udevadm', 'info', '--query=all', '--path', 
'/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found
   
   X: INTERFACE_MAC=Error: command ['cat', 
'/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: 
/sys/class/net/bonding_masters/address: Not a directory
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-10-03T20:26:36.767583
  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/1502635/+subscriptions

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

[Touch-packages] [Bug 1510407] [NEW] Cursor image is dislocated on start up

[Daniel d'Andrada]

Public bug reported:

Steps to reproduce the issue:

- Log into a unity8-mir session on a desktop/laptop
- While you're still in the unity8 lockscreen, move the mouse pointer to the 
left, trying to hit the left boundary of the screen. You will see that the 
cursor never reaches the left edge the screen but even so the launcher still 
gets activated.

Changing the cursor shape, like moving the pointer over window border or
dragging a window, solves the issue.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Daniel d'Andrada (dandrader)
 Status: In Progress

** Description changed:

  Steps to reproduce the issue:
  
  - Log into a unity8-mir session on a desktop/laptop
  - While you're still in the unity8 lockscreen, move the mouse pointer to the 
left, trying to hit the left boundary of the screen. You will see that the 
cursor never reaches the left edge the screen but even so the launcher still 
gets activated.
+ 
+ Changing the cursor shape, like moving the pointer over window border or
+ dragging a window, solves the issue.

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

** Changed in: unity8 (Ubuntu)
   Status: New => 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/1510407

Title:
  Cursor image is dislocated on start up

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce the issue:

  - Log into a unity8-mir session on a desktop/laptop
  - While you're still in the unity8 lockscreen, move the mouse pointer to the 
left, trying to hit the left boundary of the screen. You will see that the 
cursor never reaches the left edge the screen but even so the launcher still 
gets activated.

  Changing the cursor shape, like moving the pointer over window border
  or dragging a window, solves the issue.

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

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

[Touch-packages] [Bug 1456616] [NEW] unable to rotate a pdf coming from Firefox (Google maps)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In Firefox, I used maps.google.com to display a map. I made a PDF file of this 
map using 'printing' function in Firefox.
This document is in landscape format.
If I try to rotate it, the page become gray without anything.
Same way, if I try to print it telling to the printer to use landscape format, 
the printer print a white page !

Everything works well with Okular and the same file.

Ubuntu 15.04 64 bits
Evince 3.14.2-0ubuntu2

** Affects: evince
 Importance: Medium
 Status: Invalid

** Affects: poppler (Ubuntu)
 Importance: Low
 Status: Fix Released


** Tags: landscape rotate vivid
-- 
unable to rotate a pdf coming from Firefox (Google maps)
https://bugs.launchpad.net/bugs/1456616
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to poppler in Ubuntu.

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

[Touch-packages] [Bug 1456616] Re: unable to rotate a pdf coming from Firefox (Google maps)

[Sebastien Bacher]

The new poppler is in Ubuntu now
https://launchpad.net/ubuntu/+source/poppler/0.37.0-0ubuntu1

** Package changed: evince (Ubuntu) => poppler (Ubuntu)

** Changed in: poppler (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  unable to rotate a pdf coming from Firefox (Google maps)

Status in Evince:
  Invalid
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  In Firefox, I used maps.google.com to display a map. I made a PDF file of 
this map using 'printing' function in Firefox.
  This document is in landscape format.
  If I try to rotate it, the page become gray without anything.
  Same way, if I try to print it telling to the printer to use landscape 
format, the printer print a white page !

  Everything works well with Okular and the same file.

  Ubuntu 15.04 64 bits
  Evince 3.14.2-0ubuntu2

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

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

[Touch-packages] [Bug 1510388] Re: Grey buttons with white text look disabled (but they're not)

[Daniel van Vugt]

I think the common convention is:
High contrast between text colour and background = enabled
Low contrast between text colour and background = disabled

So where we use white text on a grey button, it doesn't look like a
valid button that's pushable.

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

Title:
  Grey buttons with white text look disabled (but they're not)

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Grey buttons with white text look disabled (but they're not).

  E.g. The Unity8 logout dialog.

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

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

[Touch-packages] [Bug 1510388] [NEW] Grey buttons with white text look disabled (but they're not)

[Daniel van Vugt]

Public bug reported:

Grey buttons with white text look disabled (but they're not).

E.g. The Unity8 logout dialog.

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

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

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

** Description changed:

- Grey buttons with white text look disabled (but they're not)
+ Grey buttons with white text look disabled (but they're not).
+ 
+ E.g. The Unity8 logout dialog.

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

Title:
  Grey buttons with white text look disabled (but they're not)

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Grey buttons with white text look disabled (but they're not).

  E.g. The Unity8 logout dialog.

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

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

[Touch-packages] [Bug 1487740] Re: /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 tha

[Marius Gedminas]

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

** This bug has been marked a duplicate of bug 1502173
   Python warnings: modules imported without specifying a version first

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

Title:
  /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.

Status in apport package in Ubuntu:
  Invalid

Bug description:
  Get that error when reporting:

  
  ubuntu-bug apport
  /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

  /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without 
specifying a version first. Use gi.require_version('GdkX11', '3.0') before 
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk

  
  Note that these pygiwarnings are all around logged into journalctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apport 2.18-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-5.5-generic 4.2.0-rc7
  Uname: Linux 4.2.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CrashReports:
   640:1000:1000:9227:2015-08-22 17:14:40.642790071 +0200:2015-08-22 
17:14:40.642790071 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:1000:20332:2015-08-22 17:14:35.130552303 +0200:2015-08-22 
17:14:35.130552303 +0200:/var/crash/_usr_sbin_aptd.0.crash
  CurrentDesktop: GNOME
  Date: Sat Aug 22 18:43:10 2015
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1510388] Re: Grey buttons with white text look disabled (but they're not)

[Sebastien Bacher]

Confirmed, I got that feedback from friends trying a bq phone as well.

Just as a note, that's what is recommended on
https://design.ubuntu.com/apps/building-blocks/buttons for neutral
buttons as well so the design/documentation would need to be updated,
it's not really an unity8 specific issue

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

Title:
  Grey buttons with white text look disabled (but they're not)

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Grey buttons with white text look disabled (but they're not).

  E.g. The Unity8 logout dialog.

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

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

[Touch-packages] [Bug 1510388] Re: Grey buttons with white text look disabled (but they're not)

[Albert Astals Cid]

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

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

Title:
  Grey buttons with white text look disabled (but they're not)

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Grey buttons with white text look disabled (but they're not).

  E.g. The Unity8 logout dialog.

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

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

[Touch-packages] [Bug 1485682] Re: Mouse pointer flickers at using DisplayLink

[Hannes Bochmann]

I have the same problem.

I installed the Vivid enablement stack like suggested on
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and using now the
kernel 3.19 but sadly nothing changed.

If I switch from Unity to Gnome the flickering disappears but I would
prefer to keep Unity as I like the launcher. Maybe this helps.

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using the new official DisplayLink driver for Ubuntu from
  http://www.displaylink.com/downloads/ubuntu.php for my USB-
  DisplayLink-Adapter causes on the two main monitors (DisplayPort and
  internal monitor) a flickering mouse. The pointer doesn't flicker on
  third monitor (DisplayLink monitor).

  This also seems to be related to this bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223

  Using:

  * Ubuntu 14.04.3 (Kernel 3.16)
  * DisplayLink Ubuntu driver 1.0.68
  * XOrg  1:7.7+1ubuntu8.1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,imgpng,scale,vpswitch,grid,move,mousepoll,snap,gnomecompat,resize,place,workarounds,unitymtgrabhandles,session,expo,wall,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Aug 17 18:31:55 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  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: Dell Device [1028:058b]
  InstallationDate: Installed on 2014-05-30 (444 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS L322X
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Aug 17 18:16:57 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   22136 
   vendor GSM
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1510388] Re: Grey buttons with white text look disabled (but they're not)

[Sebastien Bacher]

Design says they are working on updates to the SDK and that it's going
to address this issue

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

Title:
  Grey buttons with white text look disabled (but they're not)

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Grey buttons with white text look disabled (but they're not).

  E.g. The Unity8 logout dialog.

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

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

[Touch-packages] [Bug 1505725] Re: Tab close buttons should use haptics

[Ugo Riboni]

** Changed in: webbrowser-app (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Tab close buttons should use haptics

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

Bug description:
  The tab close buttons should use haptics to indicate a successful
  button press, like most other buttons on the phone do.

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

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

[Touch-packages] [Bug 1510394] [NEW] Unity8 renders mir_demo_client_multiwin as either black or just a shadow - never any colour

[Daniel van Vugt]

Public bug reported:

Unity8 renders mir_demo_client_multiwin as either black or just a shadow
- never any colour.

Might be related to bug 1497085?

** Affects: qtmir
 Importance: Undecided
 Status: New

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

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

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

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

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

Title:
  Unity8 renders mir_demo_client_multiwin as either black or just a
  shadow - never any colour

Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 renders mir_demo_client_multiwin as either black or just a
  shadow - never any colour.

  Might be related to bug 1497085?

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

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

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

[cethru]

Had the same problem: NM was hanging after system start and i had no nm-
applet and no network connection.

Solution for me on Ubuntu 15.10, wired lan, manually entered network 
configuration was:
sudo killall NetworkManager
sudo service NetworkManager start
sudo reboot

Shouldn't systemd start NM?

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

Title:
  Not working network connection after boot

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

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

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

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

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

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

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1510407] Re: Cursor image is dislocated on start up

[Launchpad Bug Tracker]

** Branch linked: lp:~dandrader/unity8/cursorStartup

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

Title:
  Cursor image is dislocated on start up

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce the issue:

  - Log into a unity8-mir session on a desktop/laptop
  - While you're still in the unity8 lockscreen, move the mouse pointer to the 
left, trying to hit the left boundary of the screen. You will see that the 
cursor never reaches the left edge the screen but even so the launcher still 
gets activated.

  Changing the cursor shape, like moving the pointer over window border
  or dragging a window, solves the issue.

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

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

[Touch-packages] [Bug 1460752] Re: Can't read Thai character.

[Ratchanan Srirattanamet]

@Lukasz
Sorry for the long delay. I've talked with Thai font maintainer (Theppitak 
Karoonboonyanan), he has recommend me to include the following:
-UI font: fonts-tlwg-waree
-San Serif font: fonts-tlwg-garuda and fonts-tlwg-laksaman
-Serif font: fonts-tlwg-kinnari
-Monospace font: fonts-tlwg-typo
-Handwriting font: fonts-tlwg-purisa (optionnal)

Can you tell me how to test these things?

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

Title:
  Can't read Thai character.

Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid
Status in ubuntu-touch-meta package in Ubuntu RTM:
  In Progress

Bug description:
  Step to reproduce: Use browser on the phone, go to
  http://www.alanwood.net/unicode/thai.html

  Expected result:Thai character is readable. See "Readable Thai character.png"
  What happens:They're unreadable. See "Unreadable Thai character.png"

  Version: Ubuntu Touch 15.10 channel devel-proposed image revision 211
  Device: LG L90 Dual (I'm doing a port)

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

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

[Touch-packages] [Bug 1510388] Re: Grey buttons with white text look disabled (but they're not)

[Daniel van Vugt]

A really dark grey would probably be less visually confusing.

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

Title:
  Grey buttons with white text look disabled (but they're not)

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Grey buttons with white text look disabled (but they're not).

  E.g. The Unity8 logout dialog.

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

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

[Touch-packages] [Bug 1410191] Re: /usr/bin/unity8-dash:11:data:qGetPtrHelper:d_func:get:QQmlBoundSignalExpression::function

[Launchpad Bug Tracker]

This bug was fixed in the package unity-scopes-shell -
0.5.5+15.10.20151019-0ubuntu3

---
unity-scopes-shell (0.5.5+15.10.20151019-0ubuntu3) xenial; urgency=medium

  * Hard-code Python 3.5 instead of Python 3.4.

 -- Matthias Klose   Fri, 23 Oct 2015 21:45:34 +0200

** Changed in: unity-scopes-shell (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  
/usr/bin/unity8-dash:11:data:qGetPtrHelper:d_func:get:QQmlBoundSignalExpression::function

Status in Canonical System Image:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  Fix Released

Bug description:
  Steps:
  * go to any scope requiring an online account
  * trigger the account creation
  * wait for the web view to load
  * tap the home button in the launcher

  Expected:
  * the account UI goes away and you're presented with the leftmost scope

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.02.4+bzr1517~ubuntu15.04.1, the problem page at
  https://errors.ubuntu.com/problem/c4ec750d94b30e1a9388be31c466e547a26952bd
  contains more details.

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

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

[Touch-packages] [Bug 1502635] Re: bonded interface not starting automatically

[Ubuntu Foundations Team Bug Bot]

The attachment "bugs.txt" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  bonded interface not starting automatically

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Upgraded over 15.04 to 15.10 Final Beta.  Have a LACP bonded interface
  with two NICs. Using NetworkManager to handle the NIC bonding.  After
  upgrading to 15.10, the bond0 interface no long auto starts when the
  system comes up.  If I manually do a ifconfig bond0 up, it will start.
  As a workaround I added this to rc.local, but not sure where to look
  to see why it's failing in 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
  Uname: Linux 4.2.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct  4 10:43:06 2015
  InstallationDate: Installed on 2012-12-18 (1019 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JournalErrors:
   No journal files were found.
   -- No entries --
  NetDevice.bonding_masters:
   Error: command ['udevadm', 'info', '--query=all', '--path', 
'/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found
   
   X: INTERFACE_MAC=Error: command ['cat', 
'/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: 
/sys/class/net/bonding_masters/address: Not a directory
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-10-03T20:26:36.767583
  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/1502635/+subscriptions

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

[Touch-packages] [Bug 1510386] Re: RGBX windows become discoloured (more white or completely transparent) and corrupt in the Unity8 window switcher

[Daniel van Vugt]

Also, in a stroke of fragment shader weirdness, the offending windows
appear clear through the Alt+Tab switcher's otherwise blurred
background.

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

Title:
  RGBX windows become discoloured (more white or completely transparent)
  and corrupt in the Unity8 window switcher

Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  RGBX windows become discoloured (more white or completely transparent)
  and corrupt in the Unity8 window switcher (Alt+Tab)

  This is most noticeable in Xmir, but also with:  mir_demo_client_multiwin -p2 
-a--desktop_file_hint=unity8
  (ignoring the fact that Unity8 also doesn't show the correct colours)

  This might help: I fixed the same bug in Mir's demo shells yesterday:
  https://code.launchpad.net/~vanvugt/mir/fix-1423462/+merge/275661

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

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

[Touch-packages] [Bug 1510382] Re: Window contents become slightly blurry after moving/resizing the window

[Daniel van Vugt]

Workaround: Close the window and reopen it, being careful never to move
or resize it.

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

Title:
  Window contents become slightly blurry after moving/resizing the
  window

Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.

  I first noticed this in Xmir. But now see you can reproduce it just by
  opening System Settings.

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

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

[Touch-packages] [Bug 1510386] [NEW] RGBX windows become discoloured (more white or completely transparent) and corrupt in the Unity8 window switcher

[Daniel van Vugt]

Public bug reported:

RGBX windows become discoloured (more white or completely transparent)
and corrupt in the Unity8 window switcher (Alt+Tab)

This is most noticeable in Xmir, but also with:  mir_demo_client_multiwin -p2 
-a--desktop_file_hint=unity8
(ignoring the fact that Unity8 also doesn't show the correct colours)

This might help: I fixed the same bug in Mir's demo shells yesterday:
https://code.launchpad.net/~vanvugt/mir/fix-1423462/+merge/275661

** Affects: qtmir
 Importance: High
 Status: New

** Affects: qtmir (Ubuntu)
 Importance: High
 Status: New

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

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

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

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

** Changed in: unity8 (Ubuntu)
   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/1510386

Title:
  RGBX windows become discoloured (more white or completely transparent)
  and corrupt in the Unity8 window switcher

Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  RGBX windows become discoloured (more white or completely transparent)
  and corrupt in the Unity8 window switcher (Alt+Tab)

  This is most noticeable in Xmir, but also with:  mir_demo_client_multiwin -p2 
-a--desktop_file_hint=unity8
  (ignoring the fact that Unity8 also doesn't show the correct colours)

  This might help: I fixed the same bug in Mir's demo shells yesterday:
  https://code.launchpad.net/~vanvugt/mir/fix-1423462/+merge/275661

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

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

[Touch-packages] [Bug 1501383] Re: App scope is blank and unresponsive when logging in desktop mode

[Daniel van Vugt]

Confirmed this used to be a problem for me, but it seems to be working
better (on wily desktop) today.

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

Title:
  App scope is blank and unresponsive when logging in desktop mode

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When logging in to Unity 8 desktop mode, the App scope is blank and
  unresponsive.  I have to close the window and then the new App scope
  window that is automatically started works fine.

  This occurs with Unity 8 on both a Wily machine and a Vivid+overlay
  machine.

  I'll attach unity8.log and unity8-dash.log soon.

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

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

[Touch-packages] [Bug 1501383] Re: App scope is blank and unresponsive when logging in desktop mode

[Launchpad Bug Tracker]

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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1501383

Title:
  App scope is blank and unresponsive when logging in desktop mode

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When logging in to Unity 8 desktop mode, the App scope is blank and
  unresponsive.  I have to close the window and then the new App scope
  window that is automatically started works fine.

  This occurs with Unity 8 on both a Wily machine and a Vivid+overlay
  machine.

  I'll attach unity8.log and unity8-dash.log soon.

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

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

[Touch-packages] [Bug 1474539] Re: FTBFS with Python 3.5

[Launchpad Bug Tracker]

This bug was fixed in the package cigi-ccl - 3.3.3a+svn818-10ubuntu1

---
cigi-ccl (3.3.3a+svn818-10ubuntu1) xenial; urgency=medium

  * Build using swig3.0 with an additional fix for upstream issue #509.
LP: #1474539.

 -- Matthias Klose   Sun, 25 Oct 2015 00:02:40 +0200

** Changed in: cigi-ccl (Ubuntu)
   Status: New => Fix Released

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

Title:
  FTBFS with Python 3.5

Status in apport package in Ubuntu:
  Fix Released
Status in blist package in Ubuntu:
  Fix Released
Status in cigi-ccl package in Ubuntu:
  Fix Released
Status in kubuntu-driver-manager package in Ubuntu:
  Fix Released
Status in libguestfs package in Ubuntu:
  Fix Released
Status in lives package in Ubuntu:
  New
Status in shiboken package in Ubuntu:
  Fix Released
Status in apport source package in Wily:
  Fix Released
Status in blist source package in Wily:
  Fix Released
Status in cigi-ccl source package in Wily:
  New
Status in kubuntu-driver-manager source package in Wily:
  Fix Released
Status in libguestfs source package in Wily:
  Fix Released
Status in lives source package in Wily:
  New
Status in shiboken source package in Wily:
  Fix Released

Bug description:
  We're in the process of starting the Python 3.5 transition for Wily.
  As such, we've identified a number of packages which FTBFS with Python
  3.5.  We're also soon starting the transition to gcc5.  These are the
  packages that FTBFS in both transitions.

  Here is a link to the Python 3.5 failure in the PPA:

  https://launchpadlibrarian.net/210474236/buildlog_ubuntu-wily-
  amd64.apport_2.17.3-0ubuntu4_BUILDING.txt.gz

  See also:

  
https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter=apport_filter=published_filter=

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

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

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Andrea Bernabei]

@Saviq: my question still stands :)

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

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  In Progress
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
 Ubuntu.Components 1.3
 Ubuntu.Components.ListItems 1.3
 Ubuntu.Components.Pickers 1.3
 Ubuntu.Components.Popups 1.3
 Ubuntu.Components.Styles 1.3
 Ubuntu.Components.Themes 1.3
 Ubuntu.Components.Themes.Ambiance 1.3
 Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
 Ubuntu.Layouts 1.0
 Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

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

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

[Touch-packages] [Bug 1510218] Re: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY

[Loïc Molinari]

Cool, thanks.

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

Title:
  mir_connection_get_egl_pixel_format() crashes if libEGL is loaded
  RTLD_LAZY

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

Bug description:
  mir_connection_get_egl_pixel_format() crashes on Android (at least)
  when used in QtUbuntu. There might be some specific conditions
  triggering the issue there because I haven't been able to reproduce it
  in a standalone test [1] trying to follow the same initialisation
  process.

  This is strange because if I directly call
  "eglGetConfigAttrib(display, config, EGL_NATIVE_VISUAL_ID, )"
  it works perfectly fine.

  Here's a QtUbuntu branch [2] using the function.

  [1] 
http://bazaar.launchpad.net/~loic.molinari/+junk/ubuntu-touch-test/view/head:/ubuntu-touch-test.c
  [2] 
lp:~loic.molinari/qtubuntu/requested-surface-format-fix-use-mir_connection_get_egl_pixel_format

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

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

[Touch-packages] [Bug 1510146] Re: missing tooltips

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1501337
   Support the global title HTML attribute

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

Title:
  missing tooltips

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When mouseover on an image or link, there is no tooltip to display the
  "title" attribute text

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

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

[Touch-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[Marc Reymann]

So, there's still no fix for 12.04 in the standard repos? I mean,
Precise is called "LTS" after all.

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

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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

[Touch-packages] [Bug 1510218] Re: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY

[Daniel van Vugt]

** Branch linked: lp:~vanvugt/mir/fix-1510218

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

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

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

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

Title:
  mir_connection_get_egl_pixel_format() crashes if libEGL is loaded
  RTLD_LAZY

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

Bug description:
  mir_connection_get_egl_pixel_format() crashes on Android (at least)
  when used in QtUbuntu. There might be some specific conditions
  triggering the issue there because I haven't been able to reproduce it
  in a standalone test [1] trying to follow the same initialisation
  process.

  This is strange because if I directly call
  "eglGetConfigAttrib(display, config, EGL_NATIVE_VISUAL_ID, )"
  it works perfectly fine.

  Here's a QtUbuntu branch [2] using the function.

  [1] 
http://bazaar.launchpad.net/~loic.molinari/+junk/ubuntu-touch-test/view/head:/ubuntu-touch-test.c
  [2] 
lp:~loic.molinari/qtubuntu/requested-surface-format-fix-use-mir_connection_get_egl_pixel_format

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

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

[Touch-packages] [Bug 1510218] Re: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY

[Daniel van Vugt]

Never mind. I've proposed a nice clean fix now that doesn't compromise
by introducing dependencies.

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

Title:
  mir_connection_get_egl_pixel_format() crashes if libEGL is loaded
  RTLD_LAZY

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

Bug description:
  mir_connection_get_egl_pixel_format() crashes on Android (at least)
  when used in QtUbuntu. There might be some specific conditions
  triggering the issue there because I haven't been able to reproduce it
  in a standalone test [1] trying to follow the same initialisation
  process.

  This is strange because if I directly call
  "eglGetConfigAttrib(display, config, EGL_NATIVE_VISUAL_ID, )"
  it works perfectly fine.

  Here's a QtUbuntu branch [2] using the function.

  [1] 
http://bazaar.launchpad.net/~loic.molinari/+junk/ubuntu-touch-test/view/head:/ubuntu-touch-test.c
  [2] 
lp:~loic.molinari/qtubuntu/requested-surface-format-fix-use-mir_connection_get_egl_pixel_format

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

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

[Touch-packages] [Bug 1460752] Re: Can't read Thai character.

[Łukasz Zemczak]

If you have a development device you could make it writeable, then do:
sudo apt-get update
sudo apt-get install fonts-tlwg-waree fonts-tlwg-garuda fonts-tlwg-laksaman 
fonts-tlwg-typo fonts-tlwg-kinnari

And restart your phone to see if it helped.

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

Title:
  Can't read Thai character.

Status in ubuntu-touch-meta package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid
Status in ubuntu-touch-meta package in Ubuntu RTM:
  In Progress

Bug description:
  Step to reproduce: Use browser on the phone, go to
  http://www.alanwood.net/unicode/thai.html

  Expected result:Thai character is readable. See "Readable Thai character.png"
  What happens:They're unreadable. See "Unreadable Thai character.png"

  Version: Ubuntu Touch 15.10 channel devel-proposed image revision 211
  Device: LG L90 Dual (I'm doing a port)

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

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

[Touch-packages] [Bug 736788] Re: 13d3:3304 IMC Networks bluetooth doesn't work

[Martin Wimpress]

Providing linux-firmware-nonfree is installed, this work in Ubuntu
15.10.

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

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

Title:
  13d3:3304 IMC Networks bluetooth doesn't work

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: bluez

  The "13d3:3304 IMC Networks" internal bluetooth module found in Asus
  U36JC notebook is not working in Ubuntu Maverick nor Natty.

  The systems certainly knows about presence of the bluetooth module -
  the icon in status bar is visible and allows to switch it on/off, but
  nothing else works.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
  Uname: Linux 2.6.38-6-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 4c3a0145220348e366d02efaed27e66e
  CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
  Date: Thu Mar 17 12:03:47 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
  InterestingModules: sco bnep l2cap btusb bluetooth
  MachineType: ASUSTeK Computer Inc. U36JC
  ProcEnviron:
   LANGUAGE=cs_CZ:en
   PATH=(custom, user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic 
root=UUID=2d566c56-67c7-4af1-a443-a8c80061120c ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36JC.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36JC
  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.:bvrU36JC.205:bd01/26/2011:svnASUSTeKComputerInc.:pnU36JC:pvr1.0:rvnASUSTeKComputerInc.:rnU36JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U36JC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

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

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

[Touch-packages] [Bug 1510144] Re: desktop mousewheel scrolling is erratic

[Olivier Tilloy]

I’m not seeing that. Can you please be more specific. Are you seeing it
on all pages, or only specific pages? Can you reliably reproduce the
issue with a certain set of steps? What versions of webbrowser-app and
liboxideqtcore0 are installed?

** Changed in: webbrowser-app (Ubuntu)
   Status: New => 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/1510144

Title:
  desktop mousewheel scrolling is erratic

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  When scrolling web pages on the desktop using the scrollwheel (or two-
  finger scrolling on a trackpad) the page will often jump up or down
  the page before performing the scroll in the size and direction of the
  scroll event. My guess is that the scroll position isn't being updated
  properly somewhere, so the scroll event tries to start at a different
  location from where the content currently is.

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

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

[Touch-packages] [Bug 1510378] Re: Missing window open/close animations on desktop

[Vesa Rautiainen]

** Changed in: ubuntu-ux
 Assignee: (unassigned) => Vesa Rautiainen (vesar)

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

Title:
  Missing window open/close animations on desktop

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 (on desktop) is missing window open/close animations

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

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

[Touch-packages] [Bug 1509846] Re: lightdm crashes on window open in Ubuntu 15.10 intel

[Christopher M. Penalver]

rubo77, as per http://support.lenovo.com/us/en/products/laptops-and-
netbooks/yoga-series/yoga-2-pro-lenovo an update to your computer's
buggy and outdated BIOS is available (76CN43WW). If you update to this
following https://help.ubuntu.com/community/BIOSUpdate does it change
anything?

If it doesn't, could you please both specify what happened, and provide the 
output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the
information above is provided, then please mark this report Status New.
Otherwise, please mark this as Invalid.

Thank you for your understanding.

** Tags added: bios-outdated-43

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

Title:
  lightdm crashes on window open in Ubuntu 15.10 intel

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 15.10 I get crashes, when I open a new window in an already
  started application. It happens irregularely, but I can force the
  crash if I open several new message windows in thunderbird. But it
  also happens in other applilcations, for example a new terminal
  window.

  This is the output during the crash in /var/log/Xorg.0.log
  [   253.500] (EE)
  [   253.500] (EE) Backtrace:
  [   253.500] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55f09075b62e]
  [   253.500] (EE) 1: /usr/bin/X (0x55f0905a7000+0x1b8999) [0x55f09075f999]
  [   253.500] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f44130a8000+0x352f0) 
[0x7f44130dd2f0]
  [   253.500] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x24f18) [0x7f440f4a3f18]
  [   253.500] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x26157) [0x7f440f4a5157]
  [   253.500] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x2b4b1) [0x7f440f4aa4b1]
  [   253.500] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x804e4) [0x7f440f4ff4e4]
  [   253.501] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x80e2c) [0x7f440f4ffe2c]
  [   253.501] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x82e1a) [0x7f440f501e1a]
  [   253.501] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x4197c) [0x7f440f4c097c]
  [   253.501] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x59906) [0x7f440f4d8906]
  [   253.501] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55f090604654]
  [   253.501] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55f09075f274]
  [   253.501] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55f09060a502]
  [   253.501] (EE) 14: /usr/bin/X (0x55f0905a7000+0xf495a) [0x55f09069b95a]
  [   253.501] (EE) 15: /usr/bin/X (0x55f0905a7000+0xf5ef5) [0x55f09069cef5]
  [   253.501] (EE) 16: /usr/bin/X (0x55f0905a7000+0x5818f) [0x55f0905ff18f]
  [   253.501] (EE) 17: /usr/bin/X (0x55f0905a7000+0x5c34b) [0x55f09060334b]
  [   253.501] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f44130c8a40]
  [   253.501] (EE) 19: /usr/bin/X (_start+0x29) [0x55f0905ed6c9]
  [   253.501] (EE)
  [   253.501] (EE) Segmentation fault at address 0x0
  [   253.501] (EE)
  Fatal server error:
  [   253.501] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [   253.501] (EE)
  [   253.501] (EE)
  Please consult the The X.Org Foundation support
   at http://wiki.x.org 
   for help.
  [   253.501] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [   253.502] (EE)
  [   253.502] (II) AIGLX: Suspending AIGLX clients for VT switch
  [   253.588] (EE) Server terminated with error (1). Closing log file.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu3
  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
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-11-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2015-10-20 (6 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily 

[Touch-packages] [Bug 1507446] Re: monitor goes into power save after boot

[Christopher M. Penalver]

neilbags, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1507446/comments/32
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  monitor goes into power save after boot

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  This is happening a few seconds after X starts - i can see the mouse
  pointer for a second then display goes to sleep.

  Switching with Ctrl-Alt-F1 then back to Ctrl-Alt-F7 wakes it back up.

  Only happens on first boot, not on resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  Uname: Linux 4.2.3-040203-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Oct 19 16:05:42 2015
  InstallationDate: Installed on 2015-10-15 (3 days ago)
  InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.128  Wed Aug 26 10:38:05 
PDT 2015
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04)
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304-updates, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304-updates, 304.128, 4.2.3-040203-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation NV44 [Quadro NVS 285] [10de:0165] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:029d]
  InstallationDate: Installed on 2015-10-15 (10 days ago)
  InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323)
  MachineType: Dell Inc. OptiPlex 755
  NonfreeKernelModules: nvidia
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.3-040203-generic 
root=UUID=c5beb1f1-5579-4d89-990f-7ea06edbca9b ro
  Tags:  trusty ubuntu
  Uname: Linux 4.2.3-040203-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd10/02/2007:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1.1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Oct 26 14:21:19 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputBarcode Reader   KEYBOARD, id 8
   inputBarcode Reader   KEYBOARD, id 9
   inputLogitech Trackball   MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1

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

-- 
Mailing list: 

[Touch-packages] [Bug 1474533] Re: Taps at the bottom of the screen trigger a bottom edge gesture

[Olivier Tilloy]

** Summary changed:

- While full screen videos should disable bottom edge
+ Taps at the bottom of the screen trigger a bottom edge gesture

** Description changed:

  It is too easy to trigger a bottom edge action when using the video
- timeline in landscape mode. While i play a video full screen i would
- expect the bottom edge to be disabled especially in landscape mode
+ timeline in landscape mode.
+ 
+ It’s also almost impossible to tap a link at the very bottom of a page
+ without triggering the bottom edge gesture.

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

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

Title:
  Taps at the bottom of the screen trigger a bottom edge gesture

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  It is too easy to trigger a bottom edge action when using the video
  timeline in landscape mode.

  It’s also almost impossible to tap a link at the very bottom of a page
  without triggering the bottom edge gesture.

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

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

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Zsombor Egri]

Victor and others, in order to get the header height you need to set the
Page.header first. Page.header is null by default, so no wonder you
cannot get the height. You can do something like

Page {
header: PageHeader {
}

}

Then you will have the header set and you can use that to get the
height. The component is present in UITK trunk, however I do not see its
documentation under d.u.c...

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

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  In Progress
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
 Ubuntu.Components 1.3
 Ubuntu.Components.ListItems 1.3
 Ubuntu.Components.Pickers 1.3
 Ubuntu.Components.Popups 1.3
 Ubuntu.Components.Styles 1.3
 Ubuntu.Components.Themes 1.3
 Ubuntu.Components.Themes.Ambiance 1.3
 Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
 Ubuntu.Layouts 1.0
 Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

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

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

[Touch-packages] [Bug 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10

[Luke]

Raymond,
You set status: New → Incomplete
but I'm not sure exactly what you need from me or want me to do. I'd love t get 
this issue fixed for everyone, just tell me what you want.

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

Title:
  No right channel sound on Creative Xtreme Audio (CA0106)  in  Ubuntu
  14.04-15.10

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD,
  There is no sound on right channel. But it works perfectly in Win
  7/10. It also worked perfectly on Ubuntu 12.04 My sound card is
  Creative Xtreme Audio (PCI CA0106).

  In the forum, many users also have experienced this bug with the
  incorrect default alsamixer settings.

  http://ubuntuforums.org/showthread.php?t=2217724

  Here are my alsa-info.sh results.

  http://www.alsa-
  project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16

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

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

[Touch-packages] [Bug 1510218] Re: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY

[Loïc Molinari]

> Wouldn't it just be the Android platform plugin that would be linked
to libEGL?

(And not libmirclient)

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

Title:
  mir_connection_get_egl_pixel_format() crashes if libEGL is loaded
  RTLD_LAZY

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

Bug description:
  mir_connection_get_egl_pixel_format() crashes on Android (at least)
  when used in QtUbuntu. There might be some specific conditions
  triggering the issue there because I haven't been able to reproduce it
  in a standalone test [1] trying to follow the same initialisation
  process.

  This is strange because if I directly call
  "eglGetConfigAttrib(display, config, EGL_NATIVE_VISUAL_ID, )"
  it works perfectly fine.

  Here's a QtUbuntu branch [2] using the function.

  [1] 
http://bazaar.launchpad.net/~loic.molinari/+junk/ubuntu-touch-test/view/head:/ubuntu-touch-test.c
  [2] 
lp:~loic.molinari/qtubuntu/requested-surface-format-fix-use-mir_connection_get_egl_pixel_format

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

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

[Touch-packages] [Bug 1510218] Re: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY

[Loïc Molinari]

> I'm not promising a fix, because this is an intentional feature.

Do you have other nice features like that? :)

> mir_connection_get_egl_pixel_format() crashes if you're not linked to
libEGL

QtUbuntu is linked to libEGL.

> Unfortunately we can't link to EGL. Because then you have:
>   (a) Software clients linked to libEGL;

Wouldn't it just be the Android platform plugin that would be linked to
libEGL?

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

Title:
  mir_connection_get_egl_pixel_format() crashes if libEGL is loaded
  RTLD_LAZY

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

Bug description:
  mir_connection_get_egl_pixel_format() crashes on Android (at least)
  when used in QtUbuntu. There might be some specific conditions
  triggering the issue there because I haven't been able to reproduce it
  in a standalone test [1] trying to follow the same initialisation
  process.

  This is strange because if I directly call
  "eglGetConfigAttrib(display, config, EGL_NATIVE_VISUAL_ID, )"
  it works perfectly fine.

  Here's a QtUbuntu branch [2] using the function.

  [1] 
http://bazaar.launchpad.net/~loic.molinari/+junk/ubuntu-touch-test/view/head:/ubuntu-touch-test.c
  [2] 
lp:~loic.molinari/qtubuntu/requested-surface-format-fix-use-mir_connection_get_egl_pixel_format

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

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

[Touch-packages] [Bug 1510360] Re: maximize, close, launch goes full screen with no buttons

[Michael Zanetti]

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

** Branch linked: lp:~mzanetti/unity8/panel-button-fixes

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

Title:
  maximize, close, launch goes full screen with no buttons

Status in canonical-pocket-desktop:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  so i was testing for bug 1504269
  on nexus4
  last update: 2015-10-26 14:09:21
  version version: 54
  version ubuntu: 20151026
  version device: 20150911
  version custom: 20150929-2-vivid

  i had the mouse & keyboard connected, no external monitor
  i had dash & system settings open
  i maximized dash, then reset to windowed mode with same button
  i maximized u-s-s, then i accidentally hit "quit" button
  i relaunched u-s-s
  expected: to either launch back in window mode as maximized with buttons
  actual: launched in full screen, but as in phone mode - with no buttons

  noticed that subsequent launch of phone app (while in this state)
  first appeared as a full screen phone mode - but after blanking and
  using switcher, phone app went to windowed mode as expected, but u-s-s
  persisted in the state of phone mode full screen no buttons. launched
  a few other apps, all were in windowed mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1510360/+subscriptions

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

[Touch-packages] [Bug 1507982] Re: [regression] OTA7 broke previously working app

[Daniel van Vugt]

Hmm, actually bug 1498281 might be the cause here (even if libmirclient8
isn't actually in the click package).

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

Title:
  [regression] OTA7 broke previously working app

Status in Canonical System Image:
  Won't Fix
Status in Mir:
  Won't Fix
Status in Mir 0.16 series:
  Won't Fix
Status in Mir 0.17 series:
  Won't Fix
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  OTA7 broke previously working app
  after OTA7 update on Meizu MX4, glmark2 stopped working 
https://uappexplorer.com/app/glmark2.sturmflut
  system updates should not break apps

  
  ~/.cache/upstart$ cat application-click-glmark2.sturmflut_glmark2_0.4.1.log
  libust[24877/24879]: Error: Error opening shm /lttng-ust-wait-5-32011 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24877/24879]: Error: Error opening shm /lttng-ust-wait-5-32011 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24877/24878]: Error: Error opening shm /lttng-ust-wait-5 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24877/24878]: Error: Error opening shm /lttng-ust-wait-5 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  Error: Couldn't connect to the Mir display server
  Error: main: Could not initialize canvas
  [1445336019.182277]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/buildd/mir-0.13.3+15.04.20150617/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  libust[24922/24923]: Error: Error opening shm /lttng-ust-wait-5 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24922/24923]: Error: Error opening shm /lttng-ust-wait-5 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24922/24924]: Error: Error opening shm /lttng-ust-wait-5-32011 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24922/24924]: Error: Error opening shm /lttng-ust-wait-5-32011 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  Error: Couldn't connect to the Mir display server
  Error: main: Could not initialize canvas
  [1445336029.784398]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/buildd/mir-0.13.3+15.04.20150617/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"

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

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

[Touch-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time

[Paul TREHIOU]

Is this corrected in the 15.10 ?

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

Title:
  Unable to mount lvmcache root device at boot time

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I'm experimenting with Vivid Vervet on a virtual machine and tried a
  new LVM feature, lvmcache. I made a cache for the root file system,
  rebuilt the initrd and rebooted the VM.

  At boot time, the system failed to activate the root LV. After some
  investigation, I found out, it's because the initrd is missing some
  essential stuff needed for activating a cached LV.

  The initrd was missing the dm-cache module. I regenerated the initrd
  with explicitly listing dm-cache in /etc/initramfs-tools/modules, but
  the system still can't boot up, because now it is missing the
  /usr/sbin/cache_check utility.

  As SSDs are becoming more and more common, I think it will be common
  to use them as cache for root file systems, thus it is mandatory to
  make sure that an initrd can mount an lvmcached root device when
  necessary, preferably without /etc/initramfs-tools/modules and other
  manual initrd hacking.

  System details:

  Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
  2015 x86_64 x86_64 x86_64 GNU/Linux

  Distributor ID:   Ubuntu
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  Codename: vivid

  LVM version: 2.02.111(2) (2014-09-01)
  Library version: 1.02.90 (2014-09-01)
  Driver version:  4.28.0

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

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

[Touch-packages] [Bug 592303] Re: rsync transfer failed: File name too long (36)

[robertvo]

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

I found this problem before but i have fixed this easily. There are many
tool available for long path error. I have used Long path tool and it
works great. You can try it. It is easy to fix this error using this
tool.

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

Title:
  rsync transfer failed: File name too long (36)

Status in rsync:
  New
Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: rsync

  Trying to rsync my encrypted home folder to another ubuntu machine
  (with exactly the same release and package version of rsync). Most
  transfers succeed, but occasionally I see:

  rsync: recv_generator: mkdir 
"/mnt/backupuuid/mnt/home/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWYZkOJAsGSXo-S.cpRFq3wvU.Dtozd29e1O4rDGDN9cc6pEme5GOKs67U--/ECRYPTFS_FNEK_ENCRYPTED.FXYZkOJAsGSXo-S.cpRFq3wvU.Dtozd29e1Oj3Vo5jUgBfJ.o-NKs.75Rbf3tBnbdAGWQ29J2e5laBE-/ECRYPTFS_FNEK_ENCRYPTED.FWYZkOJAsGSXo-S.cpRFq3wvU.Dtozd29e1OnAMGEJ-0sE.Yiwc37kTNQk--/ECRYPTFS_FNEK_ENCRYPTED.FbYZkOJAsGSXo-S.cpRFq3wvU.Dtozd29e1OwVHHPKxU7rcIFxmidLe3rp8pLAFfEgvTPilQAb4uRdmqWVGPNC9iGn5.W-fCXDmqHBnVSSWE2Nuj6l6JAUSwwOjvStnWm3f2u1mp4iaKbgmNHIlyr7wCHIS.CHnK-H.E"
 failed: File name too long (36)
  *** Skipping any contents from this failed directory ***

  ~ $ lsb_release -rd ; apt-cache policy rsync
  Description:Ubuntu 10.04 LTS
  Release:10.04
  rsync:
Installed: 3.0.7-1ubuntu1
Candidate: 3.0.7-1ubuntu1
Version table:
   *** 3.0.7-1ubuntu1 0
  500 http://software.linux.ibm.com/pub/ubuntu-repository/ lucid/main 
Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1510187] Re: "Save Link" doesn't work for attachment.cgi type image/png

[Olivier Tilloy]

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

This is indeed a duplicate of bug #1500742.

I’ll copy the steps to reproduce there.

** This bug has been marked a duplicate of bug 1500742
   Downloading a file requires its mime-type to be known in advance

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

Title:
  "Save Link" doesn't work for attachment.cgi type image/png

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 r146

  1. Go to .
  2. Scroll down to the "Attachments" list.
  3. Long-tap on "An idea for a good solution".
  4. Choose "Save link".

  What happens: "Sorry, there aren't currently any apps installed that
  can handle this type of content."

  What should happen: The Gallery is offered as an app to save the image
  to.

  This might be a specific example of bug 1500742, but I can't tell
  because it doesn't have steps to reproduce.

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

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

[Touch-packages] [Bug 1500742] Re: Downloading a file requires its mime-type to be known in advance

[Olivier Tilloy]

** Description changed:

  On touch devices, this is what happens when a user clicks on a link that
  triggers a download, or triggers one from the context menu:
  
-  - oxide issues a downloadRequested signal with a URL, and optionally 
headers, a suggested filename and a mime type
-  - the browser instantiates a Downloader component and calls its 
downloadMimeType() method, which converts the passed mime type to a well-known 
content type (e.g. ContentType.Pictures) and instantiates a SingleDownload 
component, passing it the headers and content type
-  - the SingleDownload instance, once its gets assigned a unique download ID 
by the DownloadManager, shows a ContentPeerPicker on screen which uses the 
passed in content type to prompt the user to choose a target application that 
will own the downloaded file
-  - the actual downloading of the file doesn’t start until the user has picked 
a target application
+  - oxide issues a downloadRequested signal with a URL, and optionally 
headers, a suggested filename and a mime type
+  - the browser instantiates a Downloader component and calls its 
downloadMimeType() method, which converts the passed mime type to a well-known 
content type (e.g. ContentType.Pictures) and instantiates a SingleDownload 
component, passing it the headers and content type
+  - the SingleDownload instance, once its gets assigned a unique download ID 
by the DownloadManager, shows a ContentPeerPicker on screen which uses the 
passed in content type to prompt the user to choose a target application that 
will own the downloaded file
+  - the actual downloading of the file doesn’t start until the user has picked 
a target application
  
  This works well if the mime type is known in advance, and can be trusted
  (indeed a server can lie about the mime types of files it serves). In
  several cases, the mime type isn’t known in advance (or cannot be
  trusted), and the browser will outright refuse to download the file
  because it doesn’t know which application to transfer ownership to.
  
  There must be a way to decouple the actual downloading from the target
  application selection, so that the mime type is not mandatory
  information, and users can pick which application to transfer ownership
  to after the file has been downloaded.
+ 
+ 
+ 
+ Steps to observe the issue (from bug #1510187):
+ 
+ 1. Go to .
+ 2. Scroll down to the "Attachments" list.
+ 3. Long-tap on "An idea for a good solution".
+ 4. Choose "Save link".
+ 
+ What happens: "Sorry, there aren't currently any apps installed that can
+ handle this type of content."
+ 
+ What should happen: The Gallery is offered as an app to save the image
+ to.

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

Title:
  Downloading a file requires its mime-type to be known in advance

Status in content-hub package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  On touch devices, this is what happens when a user clicks on a link
  that triggers a download, or triggers one from the context menu:

   - oxide issues a downloadRequested signal with a URL, and optionally 
headers, a suggested filename and a mime type
   - the browser instantiates a Downloader component and calls its 
downloadMimeType() method, which converts the passed mime type to a well-known 
content type (e.g. ContentType.Pictures) and instantiates a SingleDownload 
component, passing it the headers and content type
   - the SingleDownload instance, once its gets assigned a unique download ID 
by the DownloadManager, shows a ContentPeerPicker on screen which uses the 
passed in content type to prompt the user to choose a target application that 
will own the downloaded file
   - the actual downloading of the file doesn’t start until the user has picked 
a target application

  This works well if the mime type is known in advance, and can be
  trusted (indeed a server can lie about the mime types of files it
  serves). In several cases, the mime type isn’t known in advance (or
  cannot be trusted), and the browser will outright refuse to download
  the file because it doesn’t know which application to transfer
  ownership to.

  There must be a way to decouple the actual downloading from the target
  application selection, so that the mime type is not mandatory
  information, and users can pick which application to transfer
  ownership to after the file has been downloaded.

  

  Steps to observe the issue (from bug #1510187):

  1. Go to .
  2. Scroll down to the "Attachments" 

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-system-settings -
0.3+16.04.20151023.1-0ubuntu1

---
ubuntu-system-settings (0.3+16.04.20151023.1-0ubuntu1) xenial; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Ken VanDine ]
  * Bump Ubuntu.Components imports to 1.3 and fixed UbuntuShape
deprecations (LP: #1508363)

  [ jonas-drange ]
  * re-add silentMode property to repair the silent mode switch

 -- ci-train-...@canonical.com (Jonas G. Drange)  Fri, 23 Oct 2015
14:57:29 +

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  In Progress
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
 Ubuntu.Components 1.3
 Ubuntu.Components.ListItems 1.3
 Ubuntu.Components.Pickers 1.3
 Ubuntu.Components.Popups 1.3
 Ubuntu.Components.Styles 1.3
 Ubuntu.Components.Themes 1.3
 Ubuntu.Components.Themes.Ambiance 1.3
 Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
 Ubuntu.Layouts 1.0
 Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

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

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

[Touch-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[Stefan Huehner]

Hi Marc,
please check comment #33 from Serge. He explained that formally lxc in precise 
is not covered by lts.

However a very special case as a LTS update in main in precise (kernel) did 
break unrelated software (lxc) which is a clear regression.
And then not having that other software not in being in main -> skips it from 
LTS is lets say very annoying.

@Robert:
using that higher version of lxc is not a perfect drop-up replacement either as 
usage changed compared to old precise lxc (i.e. no lxc-list anymore but lxc-ls 
-f) and maybe other changes.


We'll probably look into backporting the lxc fix for precise as we have quite a 
few machines affected. But no ETA, so if anybody else here can pick that up 
before that would be very welcome.


@Serge:
Any chance to get some policy statement from Ubuntu here?  As i see maybe that 
example as very special regression caused by lts update should maybe warrant 
fixing items not in main if broken by 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/1504781

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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

[Touch-packages] [Bug 1510382] Re: Window contents become slightly blurry after moving/resizing the window

[Daniel van Vugt]

Hmm, does Unity8 track window position using sub-pixel accuracy? :)

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

Title:
  Window contents become slightly blurry after moving/resizing the
  window

Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.

  I first noticed this in Xmir. But now see you can reproduce it just by
  opening System Settings.

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

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

[Touch-packages] [Bug 1507480] Re: Privilege escalation through Python module imports

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.14.1-0ubuntu3.18

---
apport (2.14.1-0ubuntu3.18) trusty-security; urgency=medium

  * test_backend_apt_dpkg.py: Reset internal apt caches between tests. Avoids
random test failures due to leaking paths from previous test cases.
  * SECURITY FIX: When determining the path of a Python module for a program
like "python -m module_name", avoid actually importing and running the
module; this could lead to local root privilege escalation. Thanks to
Gabriel Campana for discovering this and the fix!
(CVE-2015-1341, LP: #1507480)

 -- Martin Pitt   Thu, 22 Oct 2015 15:15:37
+0200

** Changed in: apport (Ubuntu Trusty)
   Status: In Progress => Fix Released

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

Title:
  Privilege escalation through Python module imports

Status in Apport:
  In Progress
Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Vivid:
  Fix Released
Status in apport source package in Wily:
  Fix Released
Status in apport source package in Xenial:
  In Progress

Bug description:
  Gabriel Campana  reported a security
  vulnerability in Apport:

  ummary
  ===

  A privilege escalation was discovered in apport.

  
  Details
  ===

  The command line of the process triggering the coredump is checked to
  determine if it's a script. If the interpreter is Python and the first
  argument is ``-m``, the method ``_python_module_path`` is called to find
  the path of the culprit module
  (``/usr/lib/python3/dist-packages/apport/report.py``)::

  @classmethod
  def _python_module_path(klass, module):
  '''Determine path of given Python module'''

  module = module.replace('/', '.')

  try:
  m = __import__(module)
  m
  except:
  return None

  [...]

  Any Python module in ``sys.path`` can be imported because the variable
  ``module`` is under control of the attacker. It should be noted that
  ``_python_module_path`` is called with euid=0, and apport relies on the
  process name to determine if the process is an interpreter. A crash of
  Python isn't required to reach this function: any process name starting
  with ``python`` and producing a core dump is enough. As an example, the
  following bash script triggers the bug::

 #!/bin/bash

  cat < python.c
  int main(void) { *(int *)0 = 0; return 0; }
  EOF
  gcc -o python python.c
  ./python -m venv.__main__

  and results in the creation of a "lightweight virtual Python
  environment" in the root directory::

  $ ./lol.sh
  ./lol.sh: line 8:  7665 Segmentation fault  (core dumped)
  $ ls -l / | head -4
  total 100
  drw-rw   5 root root  4096 Sep 29 16:09 7665
  drwxr-xr-x   2 root root  4096 Sep 29 05:41 bin
  drwxr-xr-x   3 root root  4096 Sep 29 06:20 boot

  
  Criticity
  =

  Importing an arbitrary module is a security issue because a few standard
  modules rely on files in the home directory associated to the uid of the
  dumped process. A fully working exploit has been written (targetting
  Python2 and Python3), giving an instant root shell to the attacker.
  While the exploitation is straightforward for Python2, a bit more work
  was required to find a suitable module for Python3.

  The vulnerability seems to be limited to Ubuntu Dekstop because apport
  is disabled on Ubuntu Server.

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

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

[Touch-packages] [Bug 1500450] Re: /usr/share/apport/package_hook:FileExistsError:/usr/share/apport/package_hook@64:make_report_file

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.14.1-0ubuntu3.18

---
apport (2.14.1-0ubuntu3.18) trusty-security; urgency=medium

  * test_backend_apt_dpkg.py: Reset internal apt caches between tests. Avoids
random test failures due to leaking paths from previous test cases.
  * SECURITY FIX: When determining the path of a Python module for a program
like "python -m module_name", avoid actually importing and running the
module; this could lead to local root privilege escalation. Thanks to
Gabriel Campana for discovering this and the fix!
(CVE-2015-1341, LP: #1507480)

 -- Martin Pitt   Thu, 22 Oct 2015 15:15:37
+0200

** Changed in: apport (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  
/usr/share/apport/package_hook:FileExistsError:/usr/share/apport/package_hook@64:make_report_file

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Vivid:
  Fix Released

Bug description:
  If the SRU fixes the issue we should not see the new version of the
  package in the following buckets.

  Trusty / Vivid SRU Bucket
  -
  https://errors.ubuntu.com/problem/9265493993332196b8be4f1bb3aac669a6fc60fe

  Precise SRU Bucket
  --
  https://errors.ubuntu.com/problem/f200105584e29484b216d31ad21edc08ff473db3

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.19-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/df0a3ad32b9c2a7f173b2959a64b16b7ed139af4
  contains more details.

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

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

[Touch-packages] [Bug 1508826] Re: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all when headset plugged in

[Dan Watkins]

Following Raymond's advice in #7, I have swapped the pins using
hdajackretask and now have working headphone audio and mic. When I
initially plugged the headset in, things were muted, so I had to go in
to alsamixer to sort that out.

$ cat /lib/firmware/hda-jack-retask.fw
[codec]
0x10ec0292 0x17aa220e 0

[pincfg]
0x12 0x90a60130
0x13 0x4000
0x14 0x90170110
0x15 0x222140af
0x16 0x0321403f
0x18 0x41f0
0x19 0x21a11010
0x1a 0x03a11020
0x1b 0x41f0
0x1d 0x40738105
0x1e 0x41f0

[model]
auto


** Attachment added: "hdajackretask GUI setup"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1508826/+attachment/4506595/+files/hda-jack-retask.png

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

Title:
  [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at
  all when headset plugged in

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Sounds works fine through the internal speakers, but once I plug a
  headset or headphones (I tried two things, in case one was broken) in
  to the audio out, I get nothing.

  Looking in alsamixer, plugging the headset in mutes the 'Speaker'
  output and unmutes the 'Headphone' output, and restores the Master
  volume to its previous headset-in value. Unplugging the headset does
  the opposite (mutes 'Headphone'; unmutes 'Speaker'), as I would
  expect.

  This was working on vivid, so a definite regression, I think.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  daniel 5155 F pulseaudio
   /dev/snd/controlC0:  daniel 5155 F pulseaudio
  Date: Thu Oct 22 09:37:39 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-04 (412 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  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:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error 
response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: Upgraded to wily on 2015-10-21 (0 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET70WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Victor Thompson]

Zsombor,

Functionally, there already is a header, so why should a developer need
to define one explicitly? Won't explicitly defining one override the
already visible header?

What I'm asking for is simply a means of ascertaining the current
header's height. I believe the inability to do so, currently, is a
regression.

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

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  In Progress
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
 Ubuntu.Components 1.3
 Ubuntu.Components.ListItems 1.3
 Ubuntu.Components.Pickers 1.3
 Ubuntu.Components.Popups 1.3
 Ubuntu.Components.Styles 1.3
 Ubuntu.Components.Themes 1.3
 Ubuntu.Components.Themes.Ambiance 1.3
 Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
 Ubuntu.Layouts 1.0
 Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

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

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

[Touch-packages] [Bug 1508357] Re: Tooltips have a black squares outside of its rounded corners

[Will Cooke]

** Changed in: gtk+3.0 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Tooltips have a black squares outside of its rounded corners

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  Hover over any elements on a gtk apps making a tooltip appearing.

  See that the tooltip is rectangular, containing rounded corner with a 
gradient.
  However, the external part is just plain black and don't have transparency as 
expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1508357/+subscriptions

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

[Touch-packages] [Bug 1499437] Re: [desktop] Dragging a bookmark to a folder activates the bookmark

[Ugo Riboni]

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/listItemContentDrag

** Branch linked: lp:~uriboni/webbrowser-app/bookmark-drag-to-folder

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

Title:
  [desktop] Dragging a bookmark to a folder activates the bookmark

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  I’m consistently seeing this on my desktop (running vivid + UITK from
  the overlay PPA), and it makes the following autopilot test fail:
  
webbrowser_app.tests.test_new_tab_view.TestNewTabViewContentsWide.test_drag_bookmarks
  (see bug #1499411).

  It seems to be a recent regression (maybe the latest landing of the
  UITK), although I can’t tell for sure.

  Steps to reproduce:
   1) Open a new tab
   2) Open the bookmarks section of the new tab view if not open already
   3) Hover the mouse over the second bookmark in the list in the right panel 
(the first bookmark is a special case, it can’t be dragged)
   4) Move the cursor to the grip that appears on the right of the list item
   5) Press the left mouse button and start dragging leftwards

  Expected result: the drag actually starts, the bookmark can be moved
  to another folder.

  Current result: the drag doesn’t start, instead releasing the mouse
  button activates the bookmark, thus opening it in the tab.

  Note: in step 5, if you start dragging downward (or upward) first,
  then leftward, the drag is correctly initiated.

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

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

[Touch-packages] [Bug 1507480] Re: Privilege escalation through Python module imports

[Launchpad Bug Tracker]

** Branch linked: lp:apport

** Branch linked: lp:~ubuntu-core-dev/ubuntu/wily/apport/ubuntu

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

Title:
  Privilege escalation through Python module imports

Status in Apport:
  In Progress
Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Vivid:
  Fix Released
Status in apport source package in Wily:
  Fix Released
Status in apport source package in Xenial:
  In Progress

Bug description:
  Gabriel Campana  reported a security
  vulnerability in Apport:

  ummary
  ===

  A privilege escalation was discovered in apport.

  
  Details
  ===

  The command line of the process triggering the coredump is checked to
  determine if it's a script. If the interpreter is Python and the first
  argument is ``-m``, the method ``_python_module_path`` is called to find
  the path of the culprit module
  (``/usr/lib/python3/dist-packages/apport/report.py``)::

  @classmethod
  def _python_module_path(klass, module):
  '''Determine path of given Python module'''

  module = module.replace('/', '.')

  try:
  m = __import__(module)
  m
  except:
  return None

  [...]

  Any Python module in ``sys.path`` can be imported because the variable
  ``module`` is under control of the attacker. It should be noted that
  ``_python_module_path`` is called with euid=0, and apport relies on the
  process name to determine if the process is an interpreter. A crash of
  Python isn't required to reach this function: any process name starting
  with ``python`` and producing a core dump is enough. As an example, the
  following bash script triggers the bug::

 #!/bin/bash

  cat < python.c
  int main(void) { *(int *)0 = 0; return 0; }
  EOF
  gcc -o python python.c
  ./python -m venv.__main__

  and results in the creation of a "lightweight virtual Python
  environment" in the root directory::

  $ ./lol.sh
  ./lol.sh: line 8:  7665 Segmentation fault  (core dumped)
  $ ls -l / | head -4
  total 100
  drw-rw   5 root root  4096 Sep 29 16:09 7665
  drwxr-xr-x   2 root root  4096 Sep 29 05:41 bin
  drwxr-xr-x   3 root root  4096 Sep 29 06:20 boot

  
  Criticity
  =

  Importing an arbitrary module is a security issue because a few standard
  modules rely on files in the home directory associated to the uid of the
  dumped process. A fully working exploit has been written (targetting
  Python2 and Python3), giving an instant root shell to the attacker.
  While the exploitation is straightforward for Python2, a bit more work
  was required to find a suitable module for Python3.

  The vulnerability seems to be limited to Ubuntu Dekstop because apport
  is disabled on Ubuntu Server.

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

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

[Touch-packages] [Bug 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10

[Luke]

Raymond,

Filed a bug upstream: https://bugs.freedesktop.org/show_bug.cgi?id=92690

Is there anything else I should add? Thank you so much for your help!

** Bug watch added: freedesktop.org Bugzilla #92690
   https://bugs.freedesktop.org/show_bug.cgi?id=92690

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

Title:
  No right channel sound on Creative Xtreme Audio (CA0106)  in  Ubuntu
  14.04-15.10

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD,
  There is no sound on right channel. But it works perfectly in Win
  7/10. It also worked perfectly on Ubuntu 12.04 My sound card is
  Creative Xtreme Audio (PCI CA0106).

  In the forum, many users also have experienced this bug with the
  incorrect default alsamixer settings.

  http://ubuntuforums.org/showthread.php?t=2217724

  Here are my alsa-info.sh results.

  http://www.alsa-
  project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16

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

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

[Touch-packages] [Bug 1510270] Re: fwupdate build fails on i386 with assertion fail ../../bfd/elf32-i386.c:5245

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.25.51.20151027-0ubuntu1

---
binutils (2.25.51.20151027-0ubuntu1) xenial; urgency=medium

  * Snapshot, taken from the trunk 20151027.
- Fix PR ld/19175. LP: #1510270.

 -- Matthias Klose <d...@ubuntu.com>  Tue, 27 Oct 2015 08:18:33 +0100

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

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

Title:
  fwupdate build fails on i386 with assertion fail
  ../../bfd/elf32-i386.c:5245

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  New

Bug description:
  fwupdate appears to fail to build on i386 using
  2.25.51.20151022-0ubuntu3:

  [...]
  Preparing to unpack .../binutils_2.25.51.20151022-0ubuntu3_i386.deb ...
  Unpacking binutils (2.25.51.20151022-0ubuntu3) over (2.25.1-6ubuntu1) ...
  [...]

  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fpic 
-Wall -fshort-wchar -fno-strict-aliasing -fno-merge-constants -ffreestanding 
-fno-stack-protector -fno-stack-check --std=c11 -DCONFIG_ia32 -D__KERNEL__ 
-I/usr/include/efi/ -I/usr/include/efi/ia32/ 
-iquote/«BUILDDIR»/fwupdate-0.4+git20151015.081427/include "-DDEBUGDIR=L\"/\"" 
-mno-mmx -mno-sse -mno-red-zone -nostdinc -maccumulate-outgoing-args -m32 
-I/usr/lib/gcc/i686-linux-gnu/5/include -c -o fwupdate.o fwupdate.c
  fwupdate.c: In function 'allocate':
  fwupdate.c:50:10: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
*addr = (void *)pageaddr;
^
  In file included from /usr/include/efi/efi.h:35:0,
   from fwupdate.c:11:
  fwupdate.c: In function 'free':
  fwupdate.c:63:43: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
rc = uefi_call_wrapper(BS->FreePages, 2, (EFI_PHYSICAL_ADDRESS)addr,
 ^
  /usr/include/efi/ia32/efibind.h:283:51: note: in definition of macro 
'uefi_call_wrapper'
   #define uefi_call_wrapper(func, va_num, ...) func(__VA_ARGS__)
 ^
  fwupdate.c: In function 'apply_capsules':
  fwupdate.c:525:11: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 (EFI_PHYSICAL_ADDRESS)(VOID *)cbd);
 ^
  /usr/include/efi/ia32/efibind.h:283:51: note: in definition of macro 
'uefi_call_wrapper'
   #define uefi_call_wrapper(func, va_num, ...) func(__VA_ARGS__)
 ^
  fwupdate.c: In function 'read_file':
  fwupdate.c:88:4: warning: 'b' may be used uninitialized in this function 
[-Wmaybe-uninitialized]
  CopyMem(newb, b, bs * n_blocks);
  ^
  fwupdate.c: In function 'efi_main':
  fwupdate.c:160:3: warning: 'buf' may be used uninitialized in this function 
[-Wmaybe-uninitialized]
 FreePool(buf);
 ^
  fwupdate.c:130:8: note: 'buf' was declared here
void *buf;
  ^
  gcc -nostdlib -Wl,--warn-common -Wl,--no-undefined -Wl,--fatal-warnings 
-shared -Wl,-Bsymbolic -L/usr/lib -L/usr/lib -Wl,--build-id=sha1 
/usr/lib/crt0-efi-ia32.o -shared -o fwupdate.so fwupdate.o -lefi -lgnuefi \
/usr/lib/gcc/i686-linux-gnu/5/libgcc.a \
-T elf_ia32_efi.lds
  /usr/bin/ld: BFD (GNU Binutils for Ubuntu) 2.25.51.20151022 assertion fail 
../../bfd/elf32-i386.c:5245
  /usr/bin/ld: BFD (GNU Binutils for Ubuntu) 2.25.51.20151022 assertion fail 
../../bfd/elf32-i386.c:5245
  collect2: error: ld returned 1 exit status
  make[3]: *** [fwupdate.so] Error 1

  See https://launchpadlibrarian.net/222906940/buildlog_ubuntu-
  xenial-i386.fwupdate_0.4%2Bgit20151015.081427-0ubuntu3_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1510407] Re: Cursor image is dislocated on start up

[Gerry Boland]

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

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

Title:
  Cursor image is dislocated on start up

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce the issue:

  - Log into a unity8-mir session on a desktop/laptop
  - While you're still in the unity8 lockscreen, move the mouse pointer to the 
left, trying to hit the left boundary of the screen. You will see that the 
cursor never reaches the left edge the screen but even so the launcher still 
gets activated.

  Changing the cursor shape, like moving the pointer over window border
  or dragging a window, solves the issue.

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

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

[Touch-packages] [Bug 1510055] [NEW] indicator-datetime hangs on changing or adding a location when proxy set to pac file

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When behind a default closed firewall (e.g. on a university campus)
where we set a proxy pac file, indicator-datetime hangs when you try to
change the location under time and date settings.

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
indicator-datetime hangs on changing or adding a location when proxy set to pac 
file
https://bugs.launchpad.net/bugs/1510055
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to indicator-datetime in Ubuntu.

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

[Touch-packages] [Bug 1485682] Re: Mouse pointer flickers at using DisplayLink

[Christopher M. Penalver]

Hannes Bochmann, it will help immensely if you filed a new report with Ubuntu 
via a terminal:
ubuntu-bug xorg

Please ensure you have the package xdiagnose installed, and that you
click the Yes button for attaching additional debugging information.

Also, please feel free to subscribe me to it.

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using the new official DisplayLink driver for Ubuntu from
  http://www.displaylink.com/downloads/ubuntu.php for my USB-
  DisplayLink-Adapter causes on the two main monitors (DisplayPort and
  internal monitor) a flickering mouse. The pointer doesn't flicker on
  third monitor (DisplayLink monitor).

  This also seems to be related to this bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223

  Using:

  * Ubuntu 14.04.3 (Kernel 3.16)
  * DisplayLink Ubuntu driver 1.0.68
  * XOrg  1:7.7+1ubuntu8.1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,imgpng,scale,vpswitch,grid,move,mousepoll,snap,gnomecompat,resize,place,workarounds,unitymtgrabhandles,session,expo,wall,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Aug 17 18:31:55 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  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: Dell Device [1028:058b]
  InstallationDate: Installed on 2014-05-30 (444 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS L322X
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Aug 17 18:16:57 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   22136 
   vendor GSM
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1510218] Re: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY

[Daniel van Vugt]

** Changed in: mir
   Importance: Medium => High

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

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

Title:
  mir_connection_get_egl_pixel_format() crashes if libEGL is loaded
  RTLD_LAZY

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

Bug description:
  mir_connection_get_egl_pixel_format() crashes on Android (at least)
  when used in QtUbuntu. There might be some specific conditions
  triggering the issue there because I haven't been able to reproduce it
  in a standalone test [1] trying to follow the same initialisation
  process.

  This is strange because if I directly call
  "eglGetConfigAttrib(display, config, EGL_NATIVE_VISUAL_ID, )"
  it works perfectly fine.

  Here's a QtUbuntu branch [2] using the function.

  [1] 
http://bazaar.launchpad.net/~loic.molinari/+junk/ubuntu-touch-test/view/head:/ubuntu-touch-test.c
  [2] 
lp:~loic.molinari/qtubuntu/requested-surface-format-fix-use-mir_connection_get_egl_pixel_format

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

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

[Touch-packages] [Bug 1139453] Re: NVidia HDMI sound plays only on one monitor

[svecpetr]

solved in ubuntu 14.04

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

Title:
  NVidia HDMI sound plays only on one monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  in ubuntu 13.04, 12.10, 12.04 with nvidia drivers 310, 304 or current-
  versions

  ubuntu can play sound on HDMI (ok)

  but didn't work change select/change on what HDMI cable/monitor should
  sound go

  sound goes always on same monitor, is imposibble to change it to
  another (second) monitor)

  see enclosure sound play always from left monitor if is selected HDMI
  /DisplayPort3 and from left monitor if is selected HDMI/DisplayPort 2

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nvidia-310 310.32-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
  Uname: Linux 3.8.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  Date: Sat Mar  2 08:21:07 2013
  InstallationDate: Installed on 2013-03-02 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130301)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-310
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1506723] Re: Initial downward scroll using touchpad is too fast

[Olivier Tilloy]

Are you seeing this behaviour when using a physical mouse with a mouse
wheel to scroll up/down, by any chance?

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

Title:
  Initial downward scroll using touchpad is too fast

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  After opening a tab in the Browser app on the desktop which can be
  scrolled, I find that the initial downward scrolling speed is much too
  fast when using a two-finger slide on my laptop touchpad. This causes
  me to unexpectedly skip large amounts of content. Scrolling up and
  subsequent downward scrolls go at the much more reasonable expected
  speed, however.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: webbrowser-app 0.23+15.10.20150929-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 16 00:51:17 2015
  InstallationDate: Installed on 2015-08-29 (47 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150828)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1510250] Re: screen comes on without interaction

[Launchpad Bug Tracker]

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

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

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

Title:
  screen comes on without interaction

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

Bug description:
  Pat and I just discussing.
  Pat has seen this on MX4, I've seen this very consistently on Nexus7.
  I would say the Nexus7 screen would turn on by itself every couple of hours 
or so.

  MX4 running rc-proposed r145, phone was plugged in and charging

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

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

[Touch-packages] [Bug 1507480] Re: Privilege escalation through Python module imports

[Marc Deslauriers]

** Information type changed from Private Security to Public Security

** Changed in: apport (Ubuntu Xenial)
 Assignee: Martin Pitt (pitti) => Marc Deslauriers (mdeslaur)

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

Title:
  Privilege escalation through Python module imports

Status in Apport:
  In Progress
Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Vivid:
  Fix Released
Status in apport source package in Wily:
  Fix Released
Status in apport source package in Xenial:
  In Progress

Bug description:
  Gabriel Campana  reported a security
  vulnerability in Apport:

  ummary
  ===

  A privilege escalation was discovered in apport.

  
  Details
  ===

  The command line of the process triggering the coredump is checked to
  determine if it's a script. If the interpreter is Python and the first
  argument is ``-m``, the method ``_python_module_path`` is called to find
  the path of the culprit module
  (``/usr/lib/python3/dist-packages/apport/report.py``)::

  @classmethod
  def _python_module_path(klass, module):
  '''Determine path of given Python module'''

  module = module.replace('/', '.')

  try:
  m = __import__(module)
  m
  except:
  return None

  [...]

  Any Python module in ``sys.path`` can be imported because the variable
  ``module`` is under control of the attacker. It should be noted that
  ``_python_module_path`` is called with euid=0, and apport relies on the
  process name to determine if the process is an interpreter. A crash of
  Python isn't required to reach this function: any process name starting
  with ``python`` and producing a core dump is enough. As an example, the
  following bash script triggers the bug::

 #!/bin/bash

  cat < python.c
  int main(void) { *(int *)0 = 0; return 0; }
  EOF
  gcc -o python python.c
  ./python -m venv.__main__

  and results in the creation of a "lightweight virtual Python
  environment" in the root directory::

  $ ./lol.sh
  ./lol.sh: line 8:  7665 Segmentation fault  (core dumped)
  $ ls -l / | head -4
  total 100
  drw-rw   5 root root  4096 Sep 29 16:09 7665
  drwxr-xr-x   2 root root  4096 Sep 29 05:41 bin
  drwxr-xr-x   3 root root  4096 Sep 29 06:20 boot

  
  Criticity
  =

  Importing an arbitrary module is a security issue because a few standard
  modules rely on files in the home directory associated to the uid of the
  dumped process. A fully working exploit has been written (targetting
  Python2 and Python3), giving an instant root shell to the attacker.
  While the exploitation is straightforward for Python2, a bit more work
  was required to find a suitable module for Python3.

  The vulnerability seems to be limited to Ubuntu Dekstop because apport
  is disabled on Ubuntu Server.

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

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

[Touch-packages] [Bug 1510250] Re: screen comes on without interaction

[Pat McGowan]

** Description changed:

  Pat and I just discussing.
  Pat has seen this on MX4, I've seen this very consistently on Nexus7.
  I would say the Nexus7 screen would turn on by itself every couple of hours 
or so.
+ 
+ MX4 running rc-proposed r145, phone was plugged in and charging

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

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

Title:
  screen comes on without interaction

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

Bug description:
  Pat and I just discussing.
  Pat has seen this on MX4, I've seen this very consistently on Nexus7.
  I would say the Nexus7 screen would turn on by itself every couple of hours 
or so.

  MX4 running rc-proposed r145, phone was plugged in and charging

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

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

[Touch-packages] [Bug 1444718] Re: No network message from dialer even though there is full network

[Malte Mayer]

BQ Aquaris E 4.5

Ubuntu 15.04 (r26)

** Attachment added: "screenshot20151027_122734077.png"
   
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1444718/+attachment/4506553/+files/screenshot20151027_122734077.png

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

Title:
  No network message from dialer even though there is full network

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  I noticed that sometimes dialer-app and messages-app tell there is no
  network access (gsm network), however top bar indicators for both SIMs
  have full signal strenghts. It is impossible that I really had no
  network, so this is dialer (and sms app) problem. Reporting this
  problem only for dialer-app.

  I pressume it has something to do with low battery state. I've notice
  this situation twice when battery was reaching low level (between 2%
  and 5%).

  HW: bq Aqarius E4.5
  SW: Ubuntu 14.10 (r20)
  last updated on: 1/22/14

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

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

[Touch-packages] [Bug 1510511] [NEW] machinectl pull-raw fails

[Dimitri John Ledkov]

Public bug reported:

$ machinectl pull-raw https://cloud-images.ubuntu.com/trusty/current
/trusty-server-cloudimg-amd64-disk1.img

fails to expand /var/lib/machines.raw or /var/lib/machines, and thus
fails to complete:

SHA256 checksum of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
 is valid.
gpg: Signature made Wed 21 Oct 2015 16:06:28 BST using RSA key ID 7DB87C81
gpg: Good signature from "UEC Image Automatic Signing Key " 
[unknown]
gpg: WARNING: Using untrusted key!
Signature verification succeeded.
Unpacking QCOW2 file.
Failed to convert qcow2 image: No space left on device
Exiting.

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

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

Title:
  machinectl pull-raw fails

Status in systemd package in Ubuntu:
  New

Bug description:
  $ machinectl pull-raw https://cloud-images.ubuntu.com/trusty/current
  /trusty-server-cloudimg-amd64-disk1.img

  fails to expand /var/lib/machines.raw or /var/lib/machines, and thus
  fails to complete:

  SHA256 checksum of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
 is valid.
  gpg: Signature made Wed 21 Oct 2015 16:06:28 BST using RSA key ID 7DB87C81
  gpg: Good signature from "UEC Image Automatic Signing Key 
" [unknown]
  gpg: WARNING: Using untrusted key!
  Signature verification succeeded.
  Unpacking QCOW2 file.
  Failed to convert qcow2 image: No space left on device
  Exiting.

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

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

[Touch-packages] [Bug 1510510] [NEW] Error with geotagging (fixed position defined as geotag)

[Nicolas DERIVE]

Public bug reported:

When tacking photographs using camera-app, I experience various problems
with geotagging. Sometimes I don't get any geotag (picture 1.jpg) and
most of the time I got a wrong geocoding, that is always the same, and
some place I never went to (2.jpg, 3.jpg are examples of photos with
known places to demonstrate that, Versailles castle orangeraie and
Eiffel tower in France).

If more info/tests are needed, don't hesitate to ask.

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

** Attachment added: "example with no geotagging"
   https://bugs.launchpad.net/bugs/1510510/+attachment/4506563/+files/1.jpg

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

Title:
  Error with geotagging (fixed position defined as geotag)

Status in camera-app package in Ubuntu:
  New

Bug description:
  When tacking photographs using camera-app, I experience various
  problems with geotagging. Sometimes I don't get any geotag (picture
  1.jpg) and most of the time I got a wrong geocoding, that is always
  the same, and some place I never went to (2.jpg, 3.jpg are examples of
  photos with known places to demonstrate that, Versailles castle
  orangeraie and Eiffel tower in France).

  If more info/tests are needed, don't hesitate to ask.

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

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

[Touch-packages] [Bug 1510511] Re: machinectl pull-raw fails

[Dimitri John Ledkov]

wily, 225-1ubuntu9

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

Title:
  machinectl pull-raw fails

Status in systemd package in Ubuntu:
  New

Bug description:
  $ machinectl pull-raw https://cloud-images.ubuntu.com/trusty/current
  /trusty-server-cloudimg-amd64-disk1.img

  fails to expand /var/lib/machines.raw or /var/lib/machines, and thus
  fails to complete:

  SHA256 checksum of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
 is valid.
  gpg: Signature made Wed 21 Oct 2015 16:06:28 BST using RSA key ID 7DB87C81
  gpg: Good signature from "UEC Image Automatic Signing Key 
" [unknown]
  gpg: WARNING: Using untrusted key!
  Signature verification succeeded.
  Unpacking QCOW2 file.
  Failed to convert qcow2 image: No space left on device
  Exiting.

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

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

[Touch-packages] [Bug 1510510] Re: Error with geotagging (fixed position defined as geotag)

[Nicolas DERIVE]

** Attachment added: "example with wrong geotagging (1)"
   
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1510510/+attachment/4506564/+files/2.jpg

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

Title:
  Error with geotagging (fixed position defined as geotag)

Status in camera-app package in Ubuntu:
  New

Bug description:
  When tacking photographs using camera-app, I experience various
  problems with geotagging. Sometimes I don't get any geotag (picture
  1.jpg) and most of the time I got a wrong geocoding, that is always
  the same, and some place I never went to (2.jpg, 3.jpg are examples of
  photos with known places to demonstrate that, Versailles castle
  orangeraie and Eiffel tower in France).

  If more info/tests are needed, don't hesitate to ask.

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

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

[Touch-packages] [Bug 1510510] Re: Error with geotagging (fixed position defined as geotag)

[Nicolas DERIVE]

I experience these problems on a Nexus 4 (mako), configured on ubuntu-
touch/stable/bq-aquaris.en. Both OTA-6 and OTA-7 are affected.

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

Title:
  Error with geotagging (fixed position defined as geotag)

Status in camera-app package in Ubuntu:
  New

Bug description:
  When tacking photographs using camera-app, I experience various
  problems with geotagging. Sometimes I don't get any geotag (picture
  1.jpg) and most of the time I got a wrong geocoding, that is always
  the same, and some place I never went to (2.jpg, 3.jpg are examples of
  photos with known places to demonstrate that, Versailles castle
  orangeraie and Eiffel tower in France).

  If more info/tests are needed, don't hesitate to ask.

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

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

[Touch-packages] [Bug 1510510] Re: Error with geotagging (fixed position defined as geotag)

[Nicolas DERIVE]

** Attachment added: "example with wrong geotagging (3)"
   
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1510510/+attachment/4506565/+files/3.jpg

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

Title:
  Error with geotagging (fixed position defined as geotag)

Status in camera-app package in Ubuntu:
  New

Bug description:
  When tacking photographs using camera-app, I experience various
  problems with geotagging. Sometimes I don't get any geotag (picture
  1.jpg) and most of the time I got a wrong geocoding, that is always
  the same, and some place I never went to (2.jpg, 3.jpg are examples of
  photos with known places to demonstrate that, Versailles castle
  orangeraie and Eiffel tower in France).

  If more info/tests are needed, don't hesitate to ask.

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

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

[Touch-packages] [Bug 1502145] Re: Apps can keep screen lit permanently

[Chris Coulson]

** Changed in: oxide/1.10
Milestone: None => 1.10.4

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

Title:
  Apps can keep screen lit permanently

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Fix Released
Status in Oxide 1.10 series:
  Fix Committed
Status in qtmir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  rc-proposed, r140, krillin

  There are times when it seems the display blanking policy stops
  working and the display stays on until I press the power button.

  Steps to reproduce:
  * install and start Siete
  * put it in background

  Expected outcome:
  * the display is switched off after a predetermined amount of time

  Actual outcome:
  * the display stays on forever

  ==

  Now that apps can request the screen to stay on, they can do so
  regardless of whether they're focused/visible or not.

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

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

[Touch-packages] [Bug 1500450] Re: /usr/share/apport/package_hook:FileExistsError:/usr/share/apport/package_hook@64:make_report_file

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.0.1-0ubuntu17.13

---
apport (2.0.1-0ubuntu17.13) precise-security; urgency=medium

  * SECURITY FIX: When determining the path of a Python module for a program
like "python -m module_name", avoid actually importing and running the
module; this could lead to local root privilege escalation. Thanks to
Gabriel Campana for discovering this and the fix!
(CVE-2015-1341, LP: #1507480)

 -- Martin Pitt   Thu, 22 Oct 2015 15:50:47
+0200

** Changed in: apport (Ubuntu Precise)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1341

** Changed in: apport (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

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

Title:
  
/usr/share/apport/package_hook:FileExistsError:/usr/share/apport/package_hook@64:make_report_file

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Vivid:
  Fix Released

Bug description:
  If the SRU fixes the issue we should not see the new version of the
  package in the following buckets.

  Trusty / Vivid SRU Bucket
  -
  https://errors.ubuntu.com/problem/9265493993332196b8be4f1bb3aac669a6fc60fe

  Precise SRU Bucket
  --
  https://errors.ubuntu.com/problem/f200105584e29484b216d31ad21edc08ff473db3

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.19-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/df0a3ad32b9c2a7f173b2959a64b16b7ed139af4
  contains more details.

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

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

[Touch-packages] [Bug 1500450] Re: /usr/share/apport/package_hook:FileExistsError:/usr/share/apport/package_hook@64:make_report_file

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.17.2-0ubuntu1.7

---
apport (2.17.2-0ubuntu1.7) vivid-security; urgency=medium

  * test_backend_apt_dpkg.py: Reset internal apt caches between tests. Avoids
random test failures due to leaking paths from previous test cases.
  * SECURITY FIX: When determining the path of a Python module for a program
like "python -m module_name", avoid actually importing and running the
module; this could lead to local root privilege escalation. Thanks to
Gabriel Campana for discovering this and the fix!
(CVE-2015-1341, LP: #1507480)

 -- Martin Pitt   Thu, 22 Oct 2015 15:05:43
+0200

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

Title:
  
/usr/share/apport/package_hook:FileExistsError:/usr/share/apport/package_hook@64:make_report_file

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Vivid:
  Fix Released

Bug description:
  If the SRU fixes the issue we should not see the new version of the
  package in the following buckets.

  Trusty / Vivid SRU Bucket
  -
  https://errors.ubuntu.com/problem/9265493993332196b8be4f1bb3aac669a6fc60fe

  Precise SRU Bucket
  --
  https://errors.ubuntu.com/problem/f200105584e29484b216d31ad21edc08ff473db3

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.19-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/df0a3ad32b9c2a7f173b2959a64b16b7ed139af4
  contains more details.

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

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

[Touch-packages] [Bug 1510259] Re: contact cannot be shared with iPhone

[Pat McGowan]

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

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

Title:
  contact cannot be shared with iPhone

Status in Canonical System Image:
  In Progress
Status in address-book-app package in Ubuntu:
  In Progress

Bug description:
  Share a contact from the address book either via MMS or sending via Gmail
  Try to open the contact on iPhone
  It cannot be open properly. Only the name appears and for the contents it 
shows "No cards" only

  Try this on Android to see what happens

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

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

[Touch-packages] [Bug 1510254] Re: avatars for contacts not imported properly

[Pat McGowan]

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

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

Title:
  avatars for contacts not imported properly

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

Bug description:
  import a contact from gmail webapp or send one from another phone via MMS
  When you save it in address book the avatar is not saved and it should be

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

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

[Touch-packages] [Bug 1510558] Re: ppa shortcut handler exception stops shortcut resolution

[Launchpad Bug Tracker]

** Branch linked: lp:~barry/software-properties/lp1510558

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

Title:
  ppa shortcut handler exception stops shortcut resolution

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  This build failure occurred:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-xenial/xenial/i386/s/software-
  properties/20151026_184437@/log.gz

  While that's probably a temporary failure, it would still be better to
  log the exception and continue trying other shortcut handlers.

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

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

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

[Hitechcomputergeek]

I forgot to mention, now I get "Couldn't determine hostname for lock
file: File name too long" when I try to run nano as both me AND root.

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

Title:
  nano segfaults as root after upgrade to 15.10

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 15.10
  Release:  15.10

  nano:
Installed: 2.4.2-1
Candidate: 2.4.2-1
Version table:
   *** 2.4.2-1 0
  500 http://mirror.bytemark.co.uk/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  
  After upgrading Ubuntu 15.04 to 15.10, when I run nano as root on a file it 
just segfaults. I'm not having this problem on other 15.04->15.10 upgrades

  strace is https://p.defau.lt/?q7xGwt3HoqB74xTawUUHDA
  catchsegv is https://p.defau.lt/?0SPQY_bDj6F6j1ZKeToQoA

  
  Under gdb with nano-dbgsym installed, it gives

  #0  main (argc=2, argv=0x7fffe688) at ../../src/nano.c:2768

  
  If I run it as sudo nano filename.txt, it gives an error as below rather than 
segfaulting

  [ Couldn't determine hostname for lock file: File name too long ]


  Both my user and root have the same locale settings. I've tried
  regenerating the locales

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

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

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

[Hitechcomputergeek]

I'm getting this too. When I tried to nano my ~/bashrc file (just as me,
not as root), the first two times it segfaulted. The third (and any
later) times, now it displays "Couldn't determine hostname for lock
file: File name too long" for ANY file I try to open or create. Upgraded
from Ubuntu 15.04 to 15.10 two days ago. Attached is the crash log that
apport created when nano segmentation faulted the first two times.

** Attachment added: "crash log"
   
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1509081/+attachment/4506693/+files/_bin_nano.1000.crash

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

Title:
  nano segfaults as root after upgrade to 15.10

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 15.10
  Release:  15.10

  nano:
Installed: 2.4.2-1
Candidate: 2.4.2-1
Version table:
   *** 2.4.2-1 0
  500 http://mirror.bytemark.co.uk/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  
  After upgrading Ubuntu 15.04 to 15.10, when I run nano as root on a file it 
just segfaults. I'm not having this problem on other 15.04->15.10 upgrades

  strace is https://p.defau.lt/?q7xGwt3HoqB74xTawUUHDA
  catchsegv is https://p.defau.lt/?0SPQY_bDj6F6j1ZKeToQoA

  
  Under gdb with nano-dbgsym installed, it gives

  #0  main (argc=2, argv=0x7fffe688) at ../../src/nano.c:2768

  
  If I run it as sudo nano filename.txt, it gives an error as below rather than 
segfaulting

  [ Couldn't determine hostname for lock file: File name too long ]


  Both my user and root have the same locale settings. I've tried
  regenerating the locales

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

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

[Touch-packages] [Bug 1475751] Re: need phablet support for mods to /etc/lxc/lxc-usernet (vivid+stable ppa overaly)

[Christopher Townsend]

Hey Stéphane,

I agree that hardcoding the phablet user is not the best way to go about
this.  This is really only needed for The Future in which devices use a
kernel that supports unprivileged containers.  I think at this juncture,
going about the way where members of a lxc-net group automatically get
10 veth devices is best.

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

Title:
  need phablet support for mods to /etc/lxc/lxc-usernet (vivid+stable
  ppa overaly)

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

Bug description:
  we have a need for phablet to use a network inside a container, currently the 
/etc/lxc/lxc-usernet file is readonly
  would need to be modified to contain something like
  phablet veth lxcbr0 10

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

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

[Touch-packages] [Bug 1510378] Re: Missing window open/close animations on desktop

[kevin gunn]

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

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

Title:
  Missing window open/close animations on desktop

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Unity8 (on desktop) is missing window open/close animations

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

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

[Guilhem Lettron]

** Description changed:

  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 informations: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
+ 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

-- 
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:
  New

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 1509743] Re: systemd daemon-reload timed out in package trigger

[Gregory Kramida]

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

** This bug has been marked a duplicate of bug 1506404
   package systemd 225-1ubuntu7 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

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

Title:
  systemd daemon-reload timed out in package trigger

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I just upgrame my system and it crash

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  Date: Fri Oct 23 22:42:52 2015
  DuplicateSignature: package:systemd:225-1ubuntu9:el subproceso instalado el 
script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-01-15 (282 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lsusb:
   Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire 4738
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=b0abb672-eb5c-474a-a86f-cc3df3e1101d ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: systemd
  Title: package systemd 225-1ubuntu9 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to wily on 2015-08-04 (81 days ago)
  dmi.bios.date: 05/27/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE41_CP
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.16:bd05/27/2011:svnAcer:pnAspire4738:pvrV1.16:rvnAcer:rnJE41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 4738
  dmi.product.version: V1.16
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1440111] Re: [calendar] Reminder notifications are not integrated into system notifications

[Pat McGowan]

see also bug #1321309 and bug #1401802

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  [calendar] Reminder notifications are not integrated into system
  notifications

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Calendar App:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  The calendar app does not use the standard notification system. You
  can't find it in the "Notifications" area of System Settings, and it
  uses its own notification sound regardless of what is set in "Sound".

  Also, reminders are not muted when the phone is in silent mode (I
  guess it's related).

  I'm on bq Aquaris, r20 and with the latest calendar-app.

  --- --- --- ---
  UX Comment:

  Calendar Notifications need to be overhauled:
  -- Calendar Notifications are displayed for too brief a period and should 
conform to the same timing as other notifications.

  -- Calendar Notifications are not currently appearing in the
  notification tray within indicators and should be.

  -- Calendar Notification title is misleading ('Alarm') and should make
  clear that the notification relates to a calendar event ('Event') and
  not a alarm-clock event.

  -- Calendar Notification's should NOT override silent mode (unlike
  clock-alarms) although the notification should still be displayed,
  appear in the notification within indicators and cause the device to
  vibrate (if enabled) - This is accepted/common behaviour for
  notifications of this type on mobile.

  Notifications Spec:
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit

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

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

[Touch-packages] [Bug 1440111] Re: [calendar] Reminder notifications are not integrated into system notifications

[Pat McGowan]

lets make a plan for this and the related bugs

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  [calendar] Reminder notifications are not integrated into system
  notifications

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Calendar App:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  The calendar app does not use the standard notification system. You
  can't find it in the "Notifications" area of System Settings, and it
  uses its own notification sound regardless of what is set in "Sound".

  Also, reminders are not muted when the phone is in silent mode (I
  guess it's related).

  I'm on bq Aquaris, r20 and with the latest calendar-app.

  --- --- --- ---
  UX Comment:

  Calendar Notifications need to be overhauled:
  -- Calendar Notifications are displayed for too brief a period and should 
conform to the same timing as other notifications.

  -- Calendar Notifications are not currently appearing in the
  notification tray within indicators and should be.

  -- Calendar Notification title is misleading ('Alarm') and should make
  clear that the notification relates to a calendar event ('Event') and
  not a alarm-clock event.

  -- Calendar Notification's should NOT override silent mode (unlike
  clock-alarms) although the notification should still be displayed,
  appear in the notification within indicators and cause the device to
  vibrate (if enabled) - This is accepted/common behaviour for
  notifications of this type on mobile.

  Notifications Spec:
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit

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

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] BLE pairing fail

[Guilhem Lettron]

Public bug reported:

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 informations: 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

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


** Tags: wily

** Branch linked: lp:~guilhem-fr/bluez/autoenable

** Branch linked: lp:ubuntu/wily/bluez

** Summary changed:

- BLE pairing failed
+ BLE pairing fail

-- 
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:
  New

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 informations: 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 1492570] Re: /usr/share/apport/kernel_crashdump accesses files in insecure manner

[Mathew Hodson]

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

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

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

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

Title:
  /usr/share/apport/kernel_crashdump accesses files in insecure manner

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Vivid:
  Fix Released
Status in apport source package in Wily:
  Fix Released

Bug description:
  On Ubuntu Vivid Linux distribution upstart or SysV init invokes the
  program /usr/share/apport/kernel_crashdump at boot to prepare crash
  dump files for sending. This action is performed with root privileges.
  As the crash dump directory /var/crash/ is world writable and
  kernel_crashdump performs file access in unsafe manner, any local user
  may trigger a denial of service or escalate to root privileges. If
  symlink and hardlink protection is enabled (which should be the
  default for any modern system), only denial of service is possible.

  Problematic syscall in kernel_crashdump is:

  open("/var/crash/linux-image-3.19.0-18-generic.0.crash", 
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, 0666) = 30
  ...
  open("/var/crash/vmcore.log", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 31

  Thus the output file is opened unconditionally and without O_EXCL or
  O_NOFOLLOW. Also opening of input file does not care about links.

  By sym- or hardlinking from the predictable dump file name to the
  vmcore.log, kernel_crashdump will recursively include its own dump as
  logfile, thus filling the disk. This also works with symlink and
  hardlink protection turned on.

  By symlinking to other files (with symlink protection off), arbitrary
  files can be overwritten to gain root privileges.

  # lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04

  # apt-cache policy apport
  apport:
Installed: 2.17.2-0ubuntu1.3
Candidate: 2.17.2-0ubuntu1.3
Version table:
   *** 2.17.2-0ubuntu1.3 0
  500 http://archive.ubuntu.com/ubuntu/ vivid-updates/main i386 Packages
  100 /var/lib/dpkg/status
   2.17.2-0ubuntu1.1 0
  500 http://archive.ubuntu.com/ubuntu/ vivid-security/main i386 
Packages
   2.17.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main i386 Packages

  
  See 
http://www.halfdog.net/Security/2015/ApportKernelCrashdumpFileAccessVulnerabilities/
 for more information and follow the link on the bottom if you know what you 
are doing (user: InvitedOnly, pass: w0f63smR).

  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1

  Anyone helping to fix, analyze, mitigate, the security issue at
  
http://www.halfdog.net/Security/2015/ApportKernelCrashdumpFileAccessVulnerabilities/
  to improve security is allowed to view and use this resource. It
  may be passed on (including password) to other security engineers
  under the same conditions at your own risk. Free circulation
  of that resource is allowed as soon as password protection was
  removed or when stated on the page itself.
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v1

  iEYEARECAAYFAlXqzOcACgkQxFmThv7tq+7GTwCgiwCkUqsB0qiwGIktUMIPqgXY
  9bYAni2R8hAZVWWrtPZ+xsDgHGgWq2gL
  =Y4E5
  -END PGP SIGNATURE-

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

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

[Touch-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep

[Marius B. Kotsbak]

** Tags added: erm wily

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

Title:
  [Dell M4800] DPMS support broken, fails to wake up the monitor after
  putting it to sleep

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and 
either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the 
display shuts off, it will not wake up anymore, and the screen stays dark. A 
cycle of the following will leave the display dark:
  xset dpms force off; sleep 30; xset dpms force on

  WORKAROUND: A restart of the Xserver will bring back the display.

  WORKAROUND: Don't allow DPMS to switch off the display:
  xset dpms 0 0 0

  xset -q -d :0.0
  Keyboard Control:
    auto repeat:  onkey click percent:  0LED mask:  
    XKB indicators:
  00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
  03: Compose: off04: Kana:off05: Sleep:   off
  06: Suspend: off07: Mute:off08: Misc:off
  09: Mail:off10: Charging:off11: Shift Lock:  off
  12: Group 2: off13: Mouse Keys:  off
    auto repeat delay:  500repeat rate:  20
    auto repeating keys:  00ffdbbf
  fadfffefffed
  9fff
  fff7
    bell percent:  50bell pitch:  400bell duration:  100
  Pointer Control:
    acceleration:  2/1threshold:  4
  Screen Saver:
    prefer blanking:  yesallow exposures:  yes
    timeout:  0cycle:  0
  Colors:
    default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
  Font Path:
    
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
  DPMS (Energy Star):
    Standby: 0Suspend: 0Off: 0
    DPMS is Enabled
    Monitor is On

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 12:06:30 2014
  InstallationDate: Installed on 2014-01-07 (3 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1429427] Re: Unexplainable time jumps in CRON

[Roger Dueck]

I've had some of the same time jumps in CRON's syslog entries, but where
I really noticed it was during roughly the same time-frame in my apache2
logs.

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

Title:
  Unexplainable time jumps in CRON

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  On my main server I see unexplainable time jumps backwards in the syslog. 
Those jumps affect CRON.
  Example:

  Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD (
/storage/exec/status-nostromo.sh >/dev/null 2>&1)
  Feb  7 05:40:01 nostromo CRON[20389]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD (
/storage/exec/checkip.sh 2>/dev/null 1>/dev/null)

  For debugging I did the following:
  Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When 
CRON logged a wrong time, xclock did NOT show any time jump but seemed to 
freeze for a fraction of a second.
  Open a screen and start a script that will once per second read the time (in 
unix seconds) and compare the read time with the time read a second ago. If the 
current time was smaller, the script would send an email with a process list 
from before and after the jump. The script also never detected any time jump.

  In summary, my current impression is that there might be a bug in CRON 
because no other programm seems to be able to see the "wrong" time. The server 
in question is syslog server for 4 servers and 3 network devices. The time 
jumps exclusively show in syslog entries from the local CRON instance. Not in 
any remote syslog entry and not in any other local syslog entry, e.g. from 
DHCPD, bind, tftpd, etc. etc.
  Also, after a reboot, things work ok for several days upto about 2 or 3 
weeks. Then the "time jumps" start to occur with increasing frequency.

  I don't use user crontabs but maintain all jobs in /etc/crontab. I
  have number of jobs which are triggered every minute and another
  number of jobs which are triggered every 5 minutes (maybe some CRON
  internal counter overflow problem?).

  Hardware:
  Asus P9D-V
  Intel Xeon E3-1240L V3
  16GB ECC RAM
  128GB SSD System
  3x3TB ZFS RaidZ2 storage
  1x3TB Misc. data

  CMOS battery already changed and board inspected.

  nostromo:~ # lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  nostromo:~ # apt-cache policy cron
  cron:
Installed: 3.0pl1-124ubuntu2
Candidate: 3.0pl1-124ubuntu2
Version table:
   *** 3.0pl1-124ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1510604] [NEW] upgrade to 15.10: got an error from dpkg for pkg: 'systemd': 'subprocess installed post-installation script returned error exit status 1'

[Gregory Kramida]

Public bug reported:

Ubuntu release: Ubuntu 15.10
Package version: not sure (upgrading from 225-1ubuntu9 to ??? during distro 
upgrade)

In the dist-upgrade log, error is reported as:
error from dpkg for pkg: 'systemd': 'subprocess installed post-installation 
script returned error exit status 1'

This causes a slew of other errors, which look like dependency problems
during the upgrade. I am attaching the upgrade log.

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

** Attachment added: "distribution upgrade (15.04 -> 15.10) log"
   https://bugs.launchpad.net/bugs/1510604/+attachment/4506753/+files/main.log

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

Title:
  upgrade to 15.10: got an error from dpkg for pkg: 'systemd':
  'subprocess installed post-installation script returned error exit
  status 1'

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu release: Ubuntu 15.10
  Package version: not sure (upgrading from 225-1ubuntu9 to ??? during distro 
upgrade)

  In the dist-upgrade log, error is reported as:
  error from dpkg for pkg: 'systemd': 'subprocess installed post-installation 
script returned error exit status 1'

  This causes a slew of other errors, which look like dependency
  problems during the upgrade. I am attaching the upgrade log.

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

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

[Touch-packages] [Bug 1509747] Re: Intermittent lxc failures on wily

[Adam Stokes]

I'm also running into this issue when attempting to deploy a service
with juju + wily template, the template lxc container fails to stop so
cloning doesn't perform.

** Tags added: cloud-installer

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

Title:
  Intermittent lxc failures on wily

Status in juju-core:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Frequently, when creating an lxc container on wily (either through
  --to lxc:#, or using the local provider on wily), the template never
  stops and errors out here:

  [ 2300.885573] cloud-init[2758]: Cloud-init v. 0.7.7 running 'modules:final' 
at Sun, 25 Oct 2015 00:28:57 +. Up 182 seconds.
  [ 2300.886101] cloud-init[2758]: Cloud-init v. 0.7.7 finished at Sun, 25 Oct 
2015 00:29:03 +. Datasource DataSourceNoCloudNet 
[seed=/var/lib/cloud/seed/nocloud-net][dsmode=net].  Up 189 seconds
  [  OK  ] Started Execute cloud user/final scripts.
  [  OK  ] Reached target Multi-User System.
  [  OK  ] Reached target Graphical Interface.
   Starting Update UTMP about System Runlevel Changes...
  [  OK  ] Started /dev/initctl Compatibility Daemon.
  [FAILED] Failed to start Update UTMP about System Runlevel Changes.
  See 'systemctl status systemd-update-utmp-runlevel.service' for details.

  Attaching to the container and running the above command yields:

  ubuntu@cherylj-wily-local-lxc:~$ sudo lxc-attach --name juju-wily-lxc-template
  root@juju-wily-lxc-template:~# systemctl status 
systemd-update-utmp-runlevel.service
  ● systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel 
Changes
 Loaded: loaded (/lib/systemd/system/systemd-update-utmp-runlevel.service; 
static; vendor preset: enabled)
 Active: failed (Result: exit-code) since Sun 2015-10-25 00:30:29 UTC; 2h 
23min ago
   Docs: man:systemd-update-utmp.service(8)
 man:utmp(5)
Process: 3963 ExecStart=/lib/systemd/systemd-update-utmp runlevel 
(code=exited, status=1/FAILURE)
   Main PID: 3963 (code=exited, status=1/FAILURE)

  Oct 25 00:29:46 juju-wily-lxc-template systemd[1]: Starting Update UTMP about 
System Runlevel Changes...
  Oct 25 00:30:29 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Main process exited, code=exited, 
status=1/FAILURE
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: Failed to start Update 
UTMP about System Runlevel Changes.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Unit entered failed state.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Failed with result 'exit-code'.

  
  I have seen this on ec2 and in canonistack.  The canonistack machine is 
available for further debugging.  Ping me for access.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions

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

[Touch-packages] [Bug 1509747] Re: Intermittent lxc failures on wily

[Cheryl Jennings]

Is there anything else needed from the container?  I'm going to mark
this back to new as I've uploaded the requested information.

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

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

Title:
  Intermittent lxc failures on wily

Status in juju-core:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Frequently, when creating an lxc container on wily (either through
  --to lxc:#, or using the local provider on wily), the template never
  stops and errors out here:

  [ 2300.885573] cloud-init[2758]: Cloud-init v. 0.7.7 running 'modules:final' 
at Sun, 25 Oct 2015 00:28:57 +. Up 182 seconds.
  [ 2300.886101] cloud-init[2758]: Cloud-init v. 0.7.7 finished at Sun, 25 Oct 
2015 00:29:03 +. Datasource DataSourceNoCloudNet 
[seed=/var/lib/cloud/seed/nocloud-net][dsmode=net].  Up 189 seconds
  [  OK  ] Started Execute cloud user/final scripts.
  [  OK  ] Reached target Multi-User System.
  [  OK  ] Reached target Graphical Interface.
   Starting Update UTMP about System Runlevel Changes...
  [  OK  ] Started /dev/initctl Compatibility Daemon.
  [FAILED] Failed to start Update UTMP about System Runlevel Changes.
  See 'systemctl status systemd-update-utmp-runlevel.service' for details.

  Attaching to the container and running the above command yields:

  ubuntu@cherylj-wily-local-lxc:~$ sudo lxc-attach --name juju-wily-lxc-template
  root@juju-wily-lxc-template:~# systemctl status 
systemd-update-utmp-runlevel.service
  ● systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel 
Changes
 Loaded: loaded (/lib/systemd/system/systemd-update-utmp-runlevel.service; 
static; vendor preset: enabled)
 Active: failed (Result: exit-code) since Sun 2015-10-25 00:30:29 UTC; 2h 
23min ago
   Docs: man:systemd-update-utmp.service(8)
 man:utmp(5)
Process: 3963 ExecStart=/lib/systemd/systemd-update-utmp runlevel 
(code=exited, status=1/FAILURE)
   Main PID: 3963 (code=exited, status=1/FAILURE)

  Oct 25 00:29:46 juju-wily-lxc-template systemd[1]: Starting Update UTMP about 
System Runlevel Changes...
  Oct 25 00:30:29 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Main process exited, code=exited, 
status=1/FAILURE
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: Failed to start Update 
UTMP about System Runlevel Changes.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Unit entered failed state.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Failed with result 'exit-code'.

  
  I have seen this on ec2 and in canonistack.  The canonistack machine is 
available for further debugging.  Ping me for access.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions

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

[Touch-packages] [Bug 1510201] Re: AdaptativeLayout take longer to show a page

[Bill Filler]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

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

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

Title:
  AdaptativeLayout take longer to show a page

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Device: krillin
  Image: Ubuntu 15.04 (r153)

  
  I created a small/simple example with Pages using the new AdaptativeLayout.

  On this example the second page takes about 2.6 secs to show the page.
  While it only took 1.3 secs (Still a long time) when using PageStack.

  
  OBS:  You can easily change the example to use PageStack just changing the 
commented lines.

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

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

[Touch-packages] [Bug 1509262] Re: UA override not used on redirect

[Chris Coulson]

** Changed in: oxide
 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/1509262

Title:
  UA override not used on redirect

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

Bug description:
  How to reproduce on Aquaris E4.5:

  - open the web browser
  - search for a song on google
  - click on a youtube video
  - while page is loading turn up the volume to maximum
  - when page is completely loaded tap on video to make it start

  
  What should happen:
  - music video should start at maximum volume

  What really happens:
  - music video don't start, even if you continue to tap on it

  How to fix:

  - close the web browser
  - open the web browser
  - wait for the page to reload
  - play music video

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

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