[Touch-packages] [Bug 1447689] Re: Camera does not store location info when available

[Florian Boucault]

** Changed in: camera-app
   Status: In Progress => Fix Released

** Changed in: qtubuntu-camera
 Assignee: Florian Boucault (fboucault) => (unassigned)

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

Title:
  Camera does not store location info when available

Status in camera-app:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in qtubuntu-camera:
  New
Status in qtubuntu-camera package in Ubuntu:
  Fix Released

Bug description:
  Version: ubuntu-touch/stable/bq-aquaris.en r21 krillin
  Version: ubuntu-touch/stable/bq-aquaris.en r21 vegeta

  Steps to reproduce:
   * Open HERE app and ensure you location is detected
   * In my case I had a network based location, no GPS lock
   * Open the Camera app
   * Swipe up bottom edge
   * Click on location button
   * turn on location
   * close settings
   * take a photo
   * examine the photo e.g. on desktop using identify cmd from imagemagick 
package

  Expected result:
   - somewhere in the EXIF metadata a location is stored

  Actual result:
   - no apparent location information

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

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

[Touch-packages] [Bug 1299073] Re: [desktop] Video recording is not working

[Florian Boucault]

** Changed in: camera-app
   Status: In Progress => Confirmed

** Changed in: camera-app (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  [desktop] Video recording is not working

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in cheese package in Ubuntu:
  Confirmed
Status in guvcview package in Ubuntu:
  Confirmed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Video recording used to work fine on my trusty desktop, but now it
  freezes the application and video does not record.

  Steps to reproduce:

  1) Start camera-app in desktop mode ($ DESKTOP_MODE=1 camera-app)
  2) Switch to video
  3) Press the red button

  Expected behaviour:

  The app records  video correctly

  Actual behaviour:

  The videocamera freezes (still image) and video is not recorded
  The following error shows in the terminal:

  libv4l2: error setting pixformat: Device or resource busy
  CameraBin error: "Device '/dev/video0' is busy" 
  CameraBin error: "Could not negotiate format" 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: camera-app 2.9.1+14.04.20140307-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 28 16:32:32 2014
  InstallationDate: Installed on 2013-06-17 (283 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: camera-app
  UpgradeStatus: Upgraded to trusty on 2014-01-20 (66 days ago)

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

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

[Touch-packages] [Bug 1355051] Re: Camera app has two unsynced bug lists

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Low

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

Title:
  Camera app has two unsynced bug lists

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  The camera app has two unsynced bug lists.
  
  

  This unnecessarily risks quality: some bugs are only in one list, some
  people will know about only the other list, and even when a bug is in
  both lists they can have different importance levels.

  For these reasons, Ubuntu Touch policy is to track bugs on packages,
  not projects. 

  To fix this:
  1. Go through each bug reported on the project, and move it to the package.
  2. At , change 
"Bugs are tracked:" to "Somewhere else".

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

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

[Touch-packages] [Bug 1517527] [NEW] Properly handle google.co.* (and more generally google based urls where the SLD is not google)

[Alexandre Abreu]

Public bug reported:

See https://bugs.launchpad.net/webapps-core/+bug/1517102

URL patterns such as google.co.* that cover google.co.uk, google.co.in,
etc. are not valid, so might trigger a redirect to the browser in some
instances,

** Affects: webapps-core
 Importance: High
 Assignee: Alexandre Abreu (abreu-alexandre)
 Status: Triaged

** Affects: webapps-sprint
 Importance: High
 Assignee: Alexandre Abreu (abreu-alexandre)
 Status: Triaged

** Affects: webbrowser-app (Ubuntu)
 Importance: High
 Assignee: Alexandre Abreu (abreu-alexandre)
 Status: Triaged

** Changed in: webapps-core
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

** Changed in: webapps-core
   Importance: Undecided => High

** Changed in: webapps-core
   Status: New => Triaged

** Also affects: webapps-sprint
   Importance: Undecided
   Status: New

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

** Changed in: webapps-sprint
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

** Changed in: webapps-sprint
Milestone: None => sprint-16

** Changed in: webapps-sprint
   Importance: Undecided => High

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

** Changed in: webapps-sprint
   Status: New => Triaged

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

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

Title:
  Properly handle google.co.* (and more generally google based urls
  where the SLD is not google)

Status in The Webapps-core project:
  Triaged
Status in webapps-sprint:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  See https://bugs.launchpad.net/webapps-core/+bug/1517102

  URL patterns such as google.co.* that cover google.co.uk,
  google.co.in, etc. are not valid, so might trigger a redirect to the
  browser in some instances,

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-core/+bug/1517527/+subscriptions

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

[Touch-packages] [Bug 1517531] Re: Doesn't handle ringtone changes

[Bill Filler]

** Changed in: telephony-service (Ubuntu)
 Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)

** Changed in: telephony-service (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- Doesn't handle ringtone changes
+ ringtone changes not applied until after reboot

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: telephony-service (Ubuntu)
   Status: New => Confirmed

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

Title:
  ringtone changes not applied until after reboot

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

Bug description:
  When changing the ringtone in system settings, the newly selected
  ringtone isn't used for incoming calls until telephone-service-
  approver is restarted.

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

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

[Touch-packages] [Bug 1484405] Re: The detele dialog can't switch to landscape mode when deleting a photo in photo roll in landscape mode

[Florian Boucault]

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

** This bug has been marked a duplicate of bug 1513310
   The "Delete media" pop up window does not rotate with the screen in camera 
app.

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

Title:
  The detele dialog can't switch to landscape mode when deleting a photo
  in photo roll in landscape mode

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  current build number: 87
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-08-13 07:28:23
  version version: 87
  version ubuntu: 20150813
  version device: 20150804-2287567
  version custom: 20150716-819-8-42

  Steps:
  1.Open the camera
  2.Turn your phone to landscape mode and take a picture
  3.Swipe to the right to the photo roll
  4.Press the menu key in the top right corner of the phone
  5.Delete

  Expectation:
  The dialog of the delete confirmation will be displayed in landscape mode 
just like the photo roll page

  Actual result:
  The photoroll page is in landscape mode as the background page, but the 
dialog confirmation for deleting is in portrait mode

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

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

[Touch-packages] [Bug 1514099] Re: Zoom level and reported zoom level mismatch when restore from suspend

[Florian Boucault]

** Changed in: camera-app
   Status: New => In Progress

** Changed in: camera-app
 Assignee: (unassigned) => Ugo Riboni (uriboni)

** Changed in: camera-app
   Importance: Undecided => High

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

Title:
  Zoom level and reported zoom level mismatch when restore from suspend

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

Bug description:
  On Aquaris 4.5 r26.

  Steps to reproduce:

  1. Pinch zoom to maximum zoom.
  2. Take a photo.
  3. Press power button to turn screen off.
  4. Press power button to turn screen back on.
  5. Slide to unlock.
  6. Enter pin.

  Expected results: camera still on maximum zoom.
  Actual results: camera on minimum zoom.

  7. Pinch to zoom in again.

  Expected results: camera zooms in again.
  Actual results: cannot zoom in at all. Zoom control appears and displays 
maximum zoom.

  Speculation: the UI thinks the camera is on maximum zoom so doesn't
  send any zoom change request to the backend. But the camera restored
  to minimum zoom when restoring from standby.

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

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

[Touch-packages] [Bug 1517029] Re: Real zoom level and reported zoom level mismatch when switching recording mode

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: camera-app
   Importance: Undecided => Medium

** Changed in: camera-app
   Status: New => Confirmed

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

Title:
  Real zoom level and reported zoom level mismatch when switching
  recording mode

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  - ensure you are in photo mode, not video mode
  - zoom to maximum zoom 
  - switch to video mode
  - switch back to photo mode

  What happens:
  - viewfinder is not zoomed, but zoom UI still reports maximum zoom

  Expected, any of the following:
  - viewfinder is not zoomed, and zoom UI reports no zoom
  - viewfinder is fully zoomed, and zoom UI reports full zoom

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

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

[Touch-packages] [Bug 1517051] Re: Preserve zoom level if possible when switching between video and photo recording

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

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

Title:
  Preserve zoom level if possible when switching between video and photo
  recording

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Currently when switching between video and photo recording the zoom
  level is reset to no zoom.

  Ideally the zoom should be preserved when switching recording modes,
  so users do not need to re-frame the scene that they had already
  framed before switching modes.

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

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

[Touch-packages] [Bug 1500824] Re: [camera] Video stops recording on incoming call

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [camera] Video stops recording on incoming call

Status in camera-app:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  While recording at a sports event a few days ago, I received an
  incoming call. I declined to take the call, but the recording had
  stopped all the same, and I lost the most important few seconds of the
  race.

  The desired behavior, if I could choose, would be to let the phone
  continue recording while the user decides whether to accept the call.

  Then, if the user declines the call, continue recording and switch
  back to the camera app (no interruptions in the recording), but

  if the user accepts the call, interrupt the recording and take the
  call instead.

  Best regards,
  Ari

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

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

[Touch-packages] [Bug 1475895] Re: Camera froze taking picture and would no longer show a preview

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => High

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

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

Title:
  Camera froze taking picture and would no longer show a preview

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  MX4 running 59 from rc-proposed

  Zoom fully, took 1 picture which worked fine, took a second picture and the 
view froze, and the picture was not taken.
  Stopped the app.
  Started the camera again, the view is black and the controls cause the camera 
to freeze.
  A reboot cleared it.

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

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

[Touch-packages] [Bug 1495461] Re: Phone freezes when trying to record a video

[Florian Boucault]

Patrik, Nobody: I guess one reboot after the update that brought in the
"prompt the user for mic access" feature was necessary. Can we close?

** Changed in: camera-app
   Status: New => Incomplete

** Changed in: camera-app (Ubuntu)
   Status: New => Incomplete

** Changed in: camera-app
   Importance: Undecided => High

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

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

Title:
  Phone freezes when trying to record a video

Status in camera-app:
  Incomplete
Status in camera-app package in Ubuntu:
  Incomplete

Bug description:
  [Description]

  This bug affects both E4.5 and E5 devices, as reported by some users
  on IRC. I use:

  OS build number: 5
  Ubuntu image part: 20150825.1
  Device build: VEGETA01A-S23A_BQ_L100EN_2005_150825
  Customization image part: 20150821-887-33-32-vivid

  [Reproduction]

  Whenever I try to record a video on my E5 and I switch in the camera
  app from taking pictures to record videos and hit the record button
  the phone freezes.

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

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

[Touch-packages] [Bug 1517560] [NEW] Delete dialog is inconsistent with design recommendations

[Sebastien Bacher]

Public bug reported:

Similar to what is reported on bug #1389617 for camera/gallery, when
deleting a contact the current dialog has some issues

* it uses yes/no descriptions rather than verbs, it makes interaction
more difficult (if you tap "delete" you now what you are doing, if it's
"yes" you need more context)

* the colors are non standard, the delete action is green where
https://design.ubuntu.com/apps/building-blocks/buttons recommends red
for destructive actions

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

** Affects: address-book-app (Ubuntu)
 Importance: Low
 Status: New

** Changed in: address-book-app (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Delete dialog is inconsistent with design recommendations

Status in Ubuntu UX:
  New
Status in address-book-app package in Ubuntu:
  New

Bug description:
  Similar to what is reported on bug #1389617 for camera/gallery, when
  deleting a contact the current dialog has some issues

  * it uses yes/no descriptions rather than verbs, it makes interaction
  more difficult (if you tap "delete" you now what you are doing, if
  it's "yes" you need more context)

  * the colors are non standard, the delete action is green where
  https://design.ubuntu.com/apps/building-blocks/buttons recommends red
  for destructive actions

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

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

[Touch-packages] [Bug 1517560] Re: Delete dialog is inconsistent with design recommendations

[Sebastien Bacher]

** Attachment added: "the current dialog"
   
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1517560/+attachment/4521511/+files/old.png

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

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

Title:
  Delete dialog is inconsistent with design recommendations

Status in Ubuntu UX:
  New
Status in address-book-app package in Ubuntu:
  New

Bug description:
  Similar to what is reported on bug #1389617 for camera/gallery, when
  deleting a contact the current dialog has some issues

  * it uses yes/no descriptions rather than verbs, it makes interaction
  more difficult (if you tap "delete" you now what you are doing, if
  it's "yes" you need more context)

  * the colors are non standard, the delete action is green where
  https://design.ubuntu.com/apps/building-blocks/buttons recommends red
  for destructive actions

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

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

[Touch-packages] [Bug 1505705] Re: [sound] Subwoofer slider works in mysterious ways

[Sebastien Bacher]

** Bug watch added: GNOME Bug Tracker #753847
   https://bugzilla.gnome.org/show_bug.cgi?id=753847

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=753847
   Importance: Unknown
   Status: Unknown

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

Title:
  [sound] Subwoofer slider works in mysterious ways

Status in gnome-control-center:
  Unknown
Status in HWE Next:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  Sometimes it follows master volume and sometimes it doesn't.

  Same as:
  https://bugzilla.gnome.org/show_bug.cgi?id=753847

  Also raised by OEM team.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1505705/+subscriptions

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

[Touch-packages] [Bug 1256419] Re: libstdc++ pretty-printers don't work with Python 3

[Matthias Klose]

fixed in trusty with the 4.8.4 backport

** Changed in: gcc-4.8 (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 gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1256419

Title:
  libstdc++ pretty-printers don't work with Python 3

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-4.9 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Released
Status in gcc-4.9 source package in Trusty:
  Invalid
Status in gcc-4.8 package in Debian:
  Fix Released
Status in gcc-4.9 package in Debian:
  Fix Released

Bug description:
  Ubuntu builds gdb's Python support against Python 3, but the STL
  pretty-printers shipped with libstdc++ don't support Python 3:

  (gdb) python
  >import os, sys
  >stldir = '/usr/share/gcc-4.7/python/'
  >if os.path.isdir(stldir):
  >  sys.path.insert(0, stldir)
  >  from libstdcxx.v6.printers import register_libstdcxx_printers
  >  register_libstdcxx_printers (None)
  >end
  Traceback (most recent call last):
File "", line 5, in 
File "/usr/share/gcc-4.7/python/libstdcxx/v6/printers.py", line 45
  raise ValueError, "Cannot find type %s::%s" % (str(orig), name)
  ^
  SyntaxError: invalid syntax
  Error while executing Python code.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gcc-4.8 4.8.1-10ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov 29 15:06:03 2013
  InstallationDate: Installed on 2012-12-02 (362 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: gcc-4.8
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (41 days ago)

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

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

[Touch-packages] [Bug 1517564] Re: Settings "Clear" buttons use wrong side

[Sebastien Bacher]

** Attachment added: "current webbrowser dialog"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1517564/+attachment/4521514/+files/screenshot20151118_182545930.png

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

Title:
  Settings "Clear" buttons use wrong side

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

Bug description:
  Using ota8 candidate, open the webbrowser, go to settings ->
  privacy -> Clear Browsing History/Cache

  The confirmations dialog have a layout with "Cancel" on the left and
  "Clear" on the right in green. Wouldn't it make more sense to have it
  red and on the left?

  https://design.ubuntu.com/apps/building-blocks/buttons lists
  Delete/Archive/etc as destructive and red examples, "Clear" seems in
  that category

  http://design.ubuntu.com/apps/getting-started/design-vision has
  "Negative actions such as deletion go on the left,"

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

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

[Touch-packages] [Bug 1517564] [NEW] Settings "Clear" buttons use wrong side

[Sebastien Bacher]

Public bug reported:

Using ota8 candidate, open the webbrowser, go to settings ->
privacy -> Clear Browsing History/Cache

The confirmations dialog have a layout with "Cancel" on the left and
"Clear" on the right in green. Wouldn't it make more sense to have it
red and on the left?

https://design.ubuntu.com/apps/building-blocks/buttons lists
Delete/Archive/etc as destructive and red examples, "Clear" seems in
that category

http://design.ubuntu.com/apps/getting-started/design-vision has
"Negative actions such as deletion go on the left,"

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

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

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

Title:
  Settings "Clear" buttons use wrong side

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

Bug description:
  Using ota8 candidate, open the webbrowser, go to settings ->
  privacy -> Clear Browsing History/Cache

  The confirmations dialog have a layout with "Cancel" on the left and
  "Clear" on the right in green. Wouldn't it make more sense to have it
  red and on the left?

  https://design.ubuntu.com/apps/building-blocks/buttons lists
  Delete/Archive/etc as destructive and red examples, "Clear" seems in
  that category

  http://design.ubuntu.com/apps/getting-started/design-vision has
  "Negative actions such as deletion go on the left,"

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

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

[Touch-packages] [Bug 1517555] [NEW] Delete dialog is inconsistent with design recommendations

[Sebastien Bacher]

Public bug reported:

Similar to what is reported on bug #1389617 for camera/gallery, when
deleting a contact the current dialog has some issues

* it uses yes/no descriptions rather than verbs, it makes interaction
more difficult (if you tap "delete" you now what you are doing, if it's
"yes" you need more context)

* the colors are non standard, the delete action is green where
https://design.ubuntu.com/apps/building-blocks/buttons recommends red
for destructive actions

** Affects: address-book-app (Ubuntu)
 Importance: Low
 Status: Invalid

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

Title:
  Delete dialog is inconsistent with design recommendations

Status in address-book-app package in Ubuntu:
  Invalid

Bug description:
  Similar to what is reported on bug #1389617 for camera/gallery, when
  deleting a contact the current dialog has some issues

  * it uses yes/no descriptions rather than verbs, it makes interaction
  more difficult (if you tap "delete" you now what you are doing, if
  it's "yes" you need more context)

  * the colors are non standard, the delete action is green where
  https://design.ubuntu.com/apps/building-blocks/buttons recommends red
  for destructive actions

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

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

[Touch-packages] [Bug 1517555] Re: Delete dialog is inconsistent with design recommendations

[Sebastien Bacher]

duplicate

** Changed in: address-book-app (Ubuntu)
   Importance: Undecided => Low

** Changed in: address-book-app (Ubuntu)
   Status: New => Invalid

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

Title:
  Delete dialog is inconsistent with design recommendations

Status in address-book-app package in Ubuntu:
  Invalid

Bug description:
  Similar to what is reported on bug #1389617 for camera/gallery, when
  deleting a contact the current dialog has some issues

  * it uses yes/no descriptions rather than verbs, it makes interaction
  more difficult (if you tap "delete" you now what you are doing, if
  it's "yes" you need more context)

  * the colors are non standard, the delete action is green where
  https://design.ubuntu.com/apps/building-blocks/buttons recommends red
  for destructive actions

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

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

[Touch-packages] [Bug 1517132] Re: Assert when after log-in inside the session

[kevin gunn]

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

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

Title:
  Assert when after log-in inside the session

Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  I'm trying to start unity8 session on the laptop"

  After logging in from lightdm i get the "unity8 screen locker".

  There i input the password again and then unity8 crashes/aborts, the
  log says

  terminate called after throwing an instance of 
'boost::exception_detail::clone_impl'
what():  Failed to wait for event: La crida al sistema ha estat interrompuda
  ()

  
  where "La crida al sistema ha estat interrompuda" translates roughly to "The 
system call was interrupted".

  Found the "Failed to wait for event:" in mir in 
  ./src/common/dispatch/threaded_dispatcher.cpp:207:
 "Failed to wait for event"}));

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

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

[Touch-packages] [Bug 1507062] Re: After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection

[Pauli]

Seems like network-manager 1.0.4-0ubuntu5.1 fixed this bug. That makes
this like duplicate of LP: #1512749

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

Title:
  After suspend resume network manager fails to set default route entry
  to routing table for mobile broadband connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  This is regression from 10.04.

  It seems to reproduce often but not always which might point to some
  kind of race condition handled badly.

  Basic setup:
  * Huawei USB 3G modem
  * Network manager set to auto connect with saved pin
  * Laptop which has very few suspend-resume issues so I use suspending all the 
time

  I noticed the bug that modem led and network manager indicated that
  there was a connection. But connection didn't seems to work.

  My initial workaround in hurry was just to pull the modem from laptop
  and restart both modem manager and network manager. (they don't like
  modem unplugging or individual restarts but those are long standing
  separated bugs that I haven't cared to report) After restarting
  connection comes up working.

  I decided to investigate what is broken after resume and I could
  narrow issue to be that default route is missing from routing table.
  That resulted to very simple fix where I can simple manually add the
  missing default route.

  Broken table after suspend:

  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  link-local  *   255.255.0.0 U 1000   00 ppp0
  rantapallo  *   255.255.255.255 UH75000 ppp0

  Working table before suspend:
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  default *   0.0.0.0 U 75000 ppp0
  link-local  *   255.255.0.0 U 1000   00 ppp0
  rantapallo  *   255.255.255.255 UH75000 ppp0

  
  Command to add the missing route manually:

  sudo route add default netmask 0.0.0.0  metric 750 dev ppp0

  
  That is at least so far only missing part of connection setup after suspend. 
I will report a separate bug if I see a different error causing similar 
reconnecting failure after suspend-resume.

  apport should include syslog with detailed log from suspend-resume and
  service restarts to get correct route tables.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 17 03:19:00 2015
  InstallationDate: Installed on 2011-11-02 (1444 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IpRoute:
   default dev ppp0  scope link  metric 750 
   169.254.0.0/16 dev ppp0  scope link  metric 1000 
   176.93.96.110 dev ppp0  proto kernel  scope link  src 176.93.96.110  metric 
750
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2015-10-10 (6 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   ttyUSB0  gsm   connected/org/freedesktop/NetworkManager/Devices/3  
Dna dna internet  17b039cf-5b74-42af-af9a-d84c2519b250  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  
------  
   
   wlan0wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
------  
   
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
------
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1517564] Re: Settings "Clear" buttons use wrong side

[Sebastien Bacher]

** Attachment added: "the suggested changes"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1517564/+attachment/4521515/+files/screenshot20151118_182818439.png

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

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

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

Title:
  Settings "Clear" buttons use wrong side

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

Bug description:
  Using ota8 candidate, open the webbrowser, go to settings ->
  privacy -> Clear Browsing History/Cache

  The confirmations dialog have a layout with "Cancel" on the left and
  "Clear" on the right in green. Wouldn't it make more sense to have it
  red and on the left?

  https://design.ubuntu.com/apps/building-blocks/buttons lists
  Delete/Archive/etc as destructive and red examples, "Clear" seems in
  that category

  http://design.ubuntu.com/apps/getting-started/design-vision has
  "Negative actions such as deletion go on the left,"

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

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

[Touch-packages] [Bug 1517093] Re: HTM builtins aren't treated as compiler barriers on powerpc

[Matthias Klose]

** Also affects: gcc-4.8 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  HTM builtins aren't treated as compiler barriers on powerpc

Status in gcc-4.8 package in Ubuntu:
  New
Status in gcc-5 package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  HTM builtins aren't treated as compiler barriers on powerpc
   
  Contact Information = berg...@us.ibm.com 
   
  ---Steps to Reproduce---

   This bug is a mirror of the (fixed) upstream FSF bugzilla 
https://gcc.gnu.org/PR67281
  All relevant information regarding the bug and the fix can be found there.  
This bugzilla is to track backporting of the fix to the GCC 4.8, 4.9 and 5 
based compilers.
   
  Userspace tool common name: GCC 
  Userspace rpm: gcc-4.8, gcc-4.9 and gcc-5

  == Comment: #1
  The fix for the FSF GCC 5 branch was committed with:

  r228846 | bergner | 2015-10-15 11:38:47 -0500 (Thu, 15 Oct 2015) | 16
  lines

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  == Comment: #2 
  The fix for the FSF GCC 4.9 branch was committed with:

  r228847 | bergner | 2015-10-15 11:40:14 -0500 (Thu, 15 Oct 2015) | 16
  lines

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  == Comment: #3
  Since the FSF 4.8 branch is closed, here is a backport of the fix along with 
another
  simple HTM wrong code bug to GCC 4.8.

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  Backport from mainline:
  2015-08-03  Peter Bergner  

  * config/rs6000/htm.md (tabort.): Restrict the source operand to
  using a base register.

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

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

[Touch-packages] [Bug 1516245] Re: Full URL of page not shown unless user clicks on it

[James Mulholland]

** Changed in: ubuntu-ux
   Status: Triaged => Opinion

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

Title:
  Full URL of page not shown unless user clicks on it

Status in Ubuntu UX:
  Opinion
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  By default, the browser only shows the host name of the page. However,
  the full URL is shown when clicking on it.

  There's really no reason to do this, so why not show the entire URL
  all the time (or at least as much of it as fits in the URL bar)

  phablet@ubuntu-phablet:~/public_html$ lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04
  phablet@ubuntu-phablet:~/public_html$ apt-cache policy webbrowser-app
  webbrowser-app:
Installed: 0.23+15.04.20151103-0ubuntu1
Candidate: 0.23+15.04.20151103-0ubuntu1
Version table:
   *** 0.23+15.04.20151103-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-snapshot/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.23+15.04.20150416-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

  What I expected to happen:
URL should be visible entirely all the time (or at least as much as fits)

  What happened instead:
Only host name of page is shown. Rest of URL is only shown after clicking 
on it.

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

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

[Touch-packages] [Bug 1513909] Re: unity8 crash on unplug of monitor

[kevin gunn]

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

** Changed in: canonical-pocket-desktop
   Status: New => In Progress

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

Title:
  unity8 crash on unplug of monitor

Status in canonical-pocket-desktop:
  In Progress
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Stability of hotplug is much better -  so this is not a duplicate of bug 
1488863
  Maybe every 1/4 unplug event will see unity8 crashstrangely, didn't 
capture a crash log until now.

  This configuration is 
  latest PD image + silo 18 (with point release fixes for Mir0.17)
  also libertine/puritine installed
  xmir is from libertine devel ppa

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

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

[Touch-packages] [Bug 1509005] Re: [regression] mir-client-platform-mesa-dev pkg-config file dropped

[Mathew Hodson]

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

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

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

Title:
  [regression] mir-client-platform-mesa-dev pkg-config file dropped

Status in Mir:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Released
Status in mesa source package in Wily:
  Confirmed
Status in mir source package in Wily:
  Confirmed
Status in xorg-server source package in Wily:
  Fix Committed

Bug description:
  the mir-client-platform-mesa-dev pkg-config file was dropped in wily,
  leading to build errors for such optional packages like mesa and xorg-
  server.

  Even if you have a feature freeze exception, you shouldn't break
  existing API's after feature freeze.

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

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

[Touch-packages] [Bug 657551] Re: console-setup doesn't start

[Serhiy Zahoriya]

No, setupcon --save doesn't help on 15.10.

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

Title:
  console-setup doesn't start

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: console-setup

  On startup console-setup doesn't startup and I have wrong font on my console 
- it doesn't display Cyrillic.
  When I try to start it by hand I get:
  xxx@xxx:~/$ sudo service console-setup start
  console-setup stop/waiting

  When I do dpkg-reconfigure I get console font loaded until next reboot.
  I have all maveric, recently updated from 10.04. All updates installed 
regularly.
  Please let me know if I can provide any more information.
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: console-setup 1.34ubuntu15
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  Date: Sun Oct 10 01:29:48 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, user)
   LANG=ru_RU.utf8
   SHELL=/bin/bash
  SourcePackage: console-setup

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Tony Espy]

And some more details, by adding 'env QDBUS_DEBUG=1' to the unity8
upstart job, I'm getting a lot more detail without having to further
modify the code.

I'm seeing "Adding rule" log statements produced by
QDBusConnectionPrivate, but no corresponding "Removing rule" logs, so
sounds like my previous theory is on track ( ie. that reference counting
may be the cause ).  That said, I'll need to add some more logging and
rebuild...

Also, while examining the DBus log, it looks like every time the plugin
sees a 'PropertiesChanged' message from the AccessPoint, it calls
"GetAll", which is pointless as all the changed properties are
transmitted with the signal...

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  In Progress
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1231818] Re: Installing powerd removes modemmanager

[Snehal]

** Changed in: powerd (Ubuntu)
 Assignee: (unassigned) => Snehal (snehaltkr)

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

Title:
  Installing powerd removes modemmanager

Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  According to bug 1193222, comment #13, I need to install powerd in
  order to get the screen to sleep on inactivity if I use Mir (the
  default for Saucy) as display manager.

  But if I try to install powerd, modemmanager gets removed:

  till@till-twist:~$ sudo apt-get install powerd
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libhardware2 libhybris libmedia1 libubuntu-application-api1 ofono
  The following packages will be REMOVED:
modemmanager
  The following NEW packages will be installed:
libhardware2 libhybris libmedia1 libubuntu-application-api1 ofono powerd
  0 upgraded, 6 newly installed, 1 to remove and 0 not upgraded.
  Need to get 854 kB of archives.
  After this operation, 1.237 kB of additional disk space will be used.
  Do you want to continue [Y/n]? n
  Abort.
  till@till-twist:~$ 

  This means that I can either have the feature of the screen going to
  sleep or cellular data support, not both.

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

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

[Touch-packages] [Bug 1517560] Re: Delete dialog is inconsistent with design recommendations

[Sebastien Bacher]

that dialog use actions for the buttons and red for the delete one

** Attachment added: "the suggested changes"
   
https://bugs.launchpad.net/ubuntu-ux/+bug/1517560/+attachment/4521512/+files/new.png

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

Title:
  Delete dialog is inconsistent with design recommendations

Status in Ubuntu UX:
  New
Status in address-book-app package in Ubuntu:
  New

Bug description:
  Similar to what is reported on bug #1389617 for camera/gallery, when
  deleting a contact the current dialog has some issues

  * it uses yes/no descriptions rather than verbs, it makes interaction
  more difficult (if you tap "delete" you now what you are doing, if
  it's "yes" you need more context)

  * the colors are non standard, the delete action is green where
  https://design.ubuntu.com/apps/building-blocks/buttons recommends red
  for destructive actions

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

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

[Touch-packages] [Bug 1517560] Re: Delete dialog is inconsistent with design recommendations

[Launchpad Bug Tracker]

** Branch linked: lp:~seb128/address-book-app/delete-dialog-tweaks

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

Title:
  Delete dialog is inconsistent with design recommendations

Status in Ubuntu UX:
  New
Status in address-book-app package in Ubuntu:
  New

Bug description:
  Similar to what is reported on bug #1389617 for camera/gallery, when
  deleting a contact the current dialog has some issues

  * it uses yes/no descriptions rather than verbs, it makes interaction
  more difficult (if you tap "delete" you now what you are doing, if
  it's "yes" you need more context)

  * the colors are non standard, the delete action is green where
  https://design.ubuntu.com/apps/building-blocks/buttons recommends red
  for destructive actions

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

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

Re: [Touch-packages] [Bug 1517135] [NEW] ifupdown segfaults

[Rustom]

On Tue, Nov 17, 2015 at 10:30 PM, Rustom  wrote:

> Public bug reported:
>
> Note that I added this as comment on bug #1439109
>
> It is actually more similar to  #1432173 which is a duplicate of above
>
> I get :
>
> $ systemctl status -l ifup-wait-all-auto.service
> ● ifup-wait-all-auto.service - Wait for all "auto" /etc/network/interfaces
> to be up for network-online.target
>Loaded: loaded (/lib/systemd/system/ifup-wait-all-auto.service; static;
> vendor preset: enabled)
>Active: active (exited) since Mon 2015-11-16 07:33:22 IST; 27s ago
>  Docs: man:interfaces(5)
>man:ifup(8)
>   Process: 514 ExecStart=/bin/sh -ec for i in $(ifquery --list --exclude
> lo --allow auto); do INTERFACES="$INTERFACES$i "; done; [ -n "$INTERFACES"
> ] || exit 0; while ! ifquery --state $INTERFACES >/dev/null; do sleep 1;
> done; for i in $INTERFACES; do while [ -e /run/network/ifup-$i.pid ]; do
> sleep 0.2; done; done (code=exited, status=0/SUCCESS)
>  Main PID: 514 (code=exited, status=0/SUCCESS)
>CGroup: /system.slice/ifup-wait-all-auto.service
>
> Nov 16 07:32:53 xxx systemd[1]: Starting Wait for all "auto"
> /etc/network/interfaces to be up for network-online.target...
> Nov 16 07:32:54 xxx sh[514]: Segmentation fault
> Nov 16 07:33:22 xxx systemd[1]: Started Wait for all "auto"
> /etc/network/interfaces to be up for network-online.target.
> $ sudo vi /etc/resolv.conf
>
> I tried what looked like solutions offered here:
> 1.
> $ sudo update-rc.d networking remove
> $ sudo update-rc.d networking defaults
>
> [I am assuming that r.cd is a misspelling of rc.d]
>
> No change
>
> 2. Reinstalled ifupdown
> I believe I used to see two segfaults. Now I see one
>
> Ubuntu wily
> ifupdown 0.7.54ubuntu1
> systemd 225-1ubuntu9
>
> $ cat /etc/network/interfaces
> # interfaces(5) file used by ifup(8) and ifdown(8)
> auto lo
> iface lo inet loopback
>
> auto enp7s0
> iface enp7s0 inet dhcp
>
>
[Just in case others look here]
It looks that commenting out all of /etc/network/interfaces seems to remove
this problem

[Does it cause new ones?? No idea... Right now net is up (wired) Wireless
is down but thats been so since wily upgrade, ie a couple of weeks]

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

Title:
  ifupdown segfaults

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Note that I added this as comment on bug #1439109

  It is actually more similar to  #1432173 which is a duplicate of above

  I get :

  $ systemctl status -l ifup-wait-all-auto.service
  ● ifup-wait-all-auto.service - Wait for all "auto" /etc/network/interfaces to 
be up for network-online.target
 Loaded: loaded (/lib/systemd/system/ifup-wait-all-auto.service; static; 
vendor preset: enabled)
 Active: active (exited) since Mon 2015-11-16 07:33:22 IST; 27s ago
   Docs: man:interfaces(5)
 man:ifup(8)
Process: 514 ExecStart=/bin/sh -ec for i in $(ifquery --list --exclude lo 
--allow auto); do INTERFACES="$INTERFACES$i "; done; [ -n "$INTERFACES" ] || 
exit 0; while ! ifquery --state $INTERFACES >/dev/null; do sleep 1; done; for i 
in $INTERFACES; do while [ -e /run/network/ifup-$i.pid ]; do sleep 0.2; done; 
done (code=exited, status=0/SUCCESS)
   Main PID: 514 (code=exited, status=0/SUCCESS)
 CGroup: /system.slice/ifup-wait-all-auto.service

  Nov 16 07:32:53 xxx systemd[1]: Starting Wait for all "auto" 
/etc/network/interfaces to be up for network-online.target...
  Nov 16 07:32:54 xxx sh[514]: Segmentation fault
  Nov 16 07:33:22 xxx systemd[1]: Started Wait for all "auto" 
/etc/network/interfaces to be up for network-online.target.
  $ sudo vi /etc/resolv.conf

  I tried what looked like solutions offered here:
  1.
  $ sudo update-rc.d networking remove
  $ sudo update-rc.d networking defaults

  [I am assuming that r.cd is a misspelling of rc.d]

  No change

  2. Reinstalled ifupdown
  I believe I used to see two segfaults. Now I see one

  Ubuntu wily
  ifupdown 0.7.54ubuntu1
  systemd 225-1ubuntu9

  $ cat /etc/network/interfaces
  # interfaces(5) file used by ifup(8) and ifdown(8)
  auto lo
  iface lo inet loopback

  auto enp7s0
  iface enp7s0 inet dhcp

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ifupdown 0.7.54ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 17 22:26:04 2015
  InstallationDate: Installed on 2012-12-22 (1060 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: 

[Touch-packages] [Bug 1501588] Re: Wily's wpasupplicant frequently fails on WPA enterprise networks

[Adam]

Me too.  Same problem, and downgrading fixes it for me too.

What exactly do the WPA Supplicant people think is wrong with the RADIUS
servers?  I can't find that anywhere online.

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

Title:
  Wily's wpasupplicant frequently fails on WPA enterprise networks

Status in hostap:
  Unknown
Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from vivid to wily on my laptop, I'm running
  into problems when connecting to my home WPA2 enterprise network.

  Typically the first connection immediately after the driver is loaded
  works as expected, however any further reconnection and the occasional
  roaming between APs cause wpasupplicant to freeze entirely requiring
  me to kill it and most often also reload my wireless driver to get
  things working again.

  ## A failed (hanging) association looks like:
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): Activation: 
(wifi) connection 'stgraber.net-secure' has security, and secrets exist.  No 
new secrets needed.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'ssid' 
value 'stgraber.net-secure'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'scan_ssid' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'key_mgmt' value 'WPA-EAP'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'eap' 
value 'TLS'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'fragment_size' value '1300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'ca_cert' value '/home/stgraber/data/certs/stgraber-radius/ca.crt'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key' value '/home/stgraber/data/certs/stgraber-radius/castiana.p12'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key_passwd' value ''
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'identity' value 'castiana'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'bgscan' value 'simple:30:-65:300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'proactive_key_caching' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Connection 
disconnected (reason -3)
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associated -> disconnected
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: set interface 
ap_scan to 1
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: disconnected -> scanning
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: SME: Trying to 
authenticate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana kernel: [102903.079940] wlan0: authenticate with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.085128] wlan0: send auth to 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Trying to associate 
with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: scanning -> authenticating
  Sep 30 23:31:07 castiana kernel: [102903.086942] wlan0: authenticated
  Sep 30 23:31:07 castiana kernel: [102903.090103] wlan0: associate with 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: authenticating -> associating
  Sep 30 23:31:07 castiana kernel: [102903.101962] wlan0: RX AssocResp from 
24:a4:3c:c8:69:03 (capab=0x411 status=0 aid=1)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Associated with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.103701] wlan0: associated
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associating -> associated
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-STARTED 
EAP authentication started
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-METHOD 
EAP vendor 0 method 13 (TLS) selected
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PEER-CERT depth=2 
subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal 
Infrastructure/CN=stgraber.net Root CA/name=stgraber.net Infrastructure Root 
CA/emailAddress=stgra...@stgraber.org' 

[Touch-packages] [Bug 1472913] Re: Dialogs and Content-hub page are always in portrait

[Florian Boucault]

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

** This bug has been marked a duplicate of bug 1390451
   photo deletion confirmation dialog does not rotate to landscape

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

Title:
  Dialogs and Content-hub page are always in portrait

Status in camera-app:
  New
Status in camera-app package in Ubuntu:
  New

Bug description:
  When you try to delete a photo, the dialog is always in portrait. When
  you try to share a photo, the content-hub page is also in portrait.

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

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

[Touch-packages] [Bug 1471666] Re: [MX4] 4K record

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

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

Title:
  [MX4] 4K record

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

Bug description:
  Hello,
  in camera options there is no possibility to record video in 4K. Max. is 
1080p. Even on origami wallpaper (that to win invate of MX4) there was 
information about recording in 4K. How hard that will be to solve that? I'm not 
technical guy, but is that only to edit old/add new header "4K" and two numbers 
of new resolution video output?

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

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

[Touch-packages] [Bug 1517531] [NEW] ringtone changes not applied until after reboot

[Ken VanDine]

Public bug reported:

When changing the ringtone in system settings, the newly selected
ringtone isn't used for incoming calls until telephone-service-approver
is restarted.

** Affects: canonical-devices-system-image
 Importance: High
 Assignee: Bill Filler (bfiller)
 Status: Confirmed

** Affects: telephony-service (Ubuntu)
 Importance: High
 Assignee: Tiago Salem Herrmann (tiagosh)
 Status: Confirmed

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

Title:
  ringtone changes not applied until after reboot

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

Bug description:
  When changing the ringtone in system settings, the newly selected
  ringtone isn't used for incoming calls until telephone-service-
  approver is restarted.

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

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

[Touch-packages] [Bug 1498280] Re: App doesnt display correctly on widescreen.

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: New => Fix Released

** Changed in: camera-app
   Status: New => Fix Released

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

Title:
  App doesnt display correctly on widescreen.

Status in camera-app:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  Seems to be optimized for vertical screens. Can only see half of the
  output on my laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: camera-app 3.0.0+15.10.20150707-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 21 23:28:10 2015
  InstallationDate: Installed on 2014-11-20 (305 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: camera-app
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: 2015-07-01 14:58:02
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1509640] Re: Installation of utorch breaks flash

[Florian Boucault]

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

** This bug has been marked a duplicate of bug 1396123
   Camera-app should warn the user when the camera hw is not available (used by 
another app)

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

Title:
  Installation of utorch breaks flash

Status in camera-app:
  New
Status in camera-app package in Ubuntu:
  New

Bug description:
  whenever I install a package such as utorch, the camera does not seem
  to be able to use the flash or video light.

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

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

[Touch-packages] [Bug 1441937] Re: PhotoRoll header visible on top of content picker

[Florian Boucault]

** Changed in: camera-app
   Status: In Progress => Fix Released

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

Title:
  PhotoRoll header visible on top of content picker

Status in camera-app:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  See https://bugs.launchpad.net/tangxi/+bug/1438618

  This is arale only, the header is not disappearing when the content
  picker is being shown during share operation.

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

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

[Touch-packages] [Bug 1517260] Re: Two thumbnail requests for each image in photo roll view

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

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

Title:
  Two thumbnail requests for each image in photo roll view

Status in camera-app:
  Confirmed
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  I'm seeing two requests for thumbnails when scrolling in the photo
  roll view.

  thumbnailer-service: [23:45:47.191] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151104_043132332.jpg (248,0): 
0.027926 sec (MISS)"
  thumbnailer-service: [23:45:47.201] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151104_043132332.jpg (248,248): 
0.036288 sec (MISS)"
  thumbnailer-service: [23:45:47.608] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151104_043130161.jpg (248,0): 
0.025118 sec (MISS)"
  thumbnailer-service: [23:45:47.619] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151104_043130161.jpg (248,248): 
0.034762 sec (MISS)"

  Note that, for each image, one requests is for (248,0), followed by
  another request for (248,248).

  This is decidedly sub-optimal because it makes two round-trips to the
  thumbnailer for each image and causes the thumbnailer to cache two
  thumbnails. This reduces the effectiveness of the cache and wastes
  CPU.

  To reproduce, take around 30 photos. In a shell on the device, run

  thumbnailer-admin clear

  Run a

  tail -f ~/.cache/upstart/dbus.log

  Now start the camera app. Change to the photo roll view and slowly
  scroll down. As each new image comes into view, there are two requests
  sent to the thumbnailer for each image.

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

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

[Touch-packages] [Bug 1444170] Re: python code does not pass the flake8 static checks

[Florian Boucault]

** Changed in: camera-app
   Status: In Progress => Fix Released

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

Title:
  python code does not pass the flake8 static checks

Status in camera-app:
  Fix Released
Status in qakit:
  New
Status in ubuntu-keyboard:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard source package in Vivid:
  New
Status in webbrowser-app source package in Vivid:
  New

Bug description:
  Flake8 checks that the python code follows the right code style, and
  does some static checks for errors.

  This branch is not passing the static tests.

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

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

[Touch-packages] [Bug 1445753] Re: "No media available" label shows in camera preview with long translations

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  "No media available" label shows in camera preview with long
  translations

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  See the attached screenshot. The translation in Catalan for "No media
  available." is longer than the English string, making the letters not
  visible in the screenshot spill out to the camera preview.

  The label size for that message should probably be limited to the
  width of the photo roll, so that longer messages don't affect the
  camera preview.

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

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

[Touch-packages] [Bug 1449917] Re: camera-app can't work in vivid

[Florian Boucault]

Please provide more information: what device you are testing that on?
what camera are you using? What version of Ubuntu?

** Changed in: camera-app
   Status: New => Incomplete

** Changed in: camera-app (Ubuntu)
   Status: New => Incomplete

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

Title:
  camera-app can't work in vivid

Status in camera-app:
  Incomplete
Status in camera-app package in Ubuntu:
  Incomplete

Bug description:
  the version is 3.0.0+15.04.20150313-0ubuntu1, it's black screen.

  cheese 3.14.1-2ubuntu4 works fine.

  And also below command works fine.

  $ gst-launch-1.0 v4l2src ! xvimagesink

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

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

[Touch-packages] [Bug 1447562] Re: There should be levels on the screen to see whether one holds the camera level

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Wishlist

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  There should be levels on the screen to see whether one holds the
  camera level

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Many digital cmeras, especially Ricoh and recent Panasonic ansd
  Olympus, show levels on their screen to make it easier to hold the
  camera level, which is very important for landscape and architecture
  shots.

  Olympus and Ricoh have one horizontal level at the bottom to make
  horizontal lines in the picture beine level and one vertical level on
  the right side of the screen to make the optical axis level and so
  vertical lines being vertical, especially with a wide angle lens.
  Panasonic cameras have something like an artificial horizon in the
  middle of the picture.

  This would also be a great feature for Ubuntu's camera app, to not
  come home with the Leaning Tower of Paris.

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

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

[Touch-packages] [Bug 1484405] Re: The detele dialog can't switch to landscape mode when deleting a photo in photo roll in landscape mode

[Florian Boucault]

Related to https://bugs.launchpad.net/camera-app/+bug/1390451

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

** Changed in: camera-app (Ubuntu)
   Importance: Low => Medium

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

Title:
  The detele dialog can't switch to landscape mode when deleting a photo
  in photo roll in landscape mode

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  current build number: 87
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-08-13 07:28:23
  version version: 87
  version ubuntu: 20150813
  version device: 20150804-2287567
  version custom: 20150716-819-8-42

  Steps:
  1.Open the camera
  2.Turn your phone to landscape mode and take a picture
  3.Swipe to the right to the photo roll
  4.Press the menu key in the top right corner of the phone
  5.Delete

  Expectation:
  The dialog of the delete confirmation will be displayed in landscape mode 
just like the photo roll page

  Actual result:
  The photoroll page is in landscape mode as the background page, but the 
dialog confirmation for deleting is in portrait mode

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

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

[Touch-packages] [Bug 1488788] Re: The picture still contains location information even when the location tagging is off

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

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

Title:
  The picture still contains location information even when the location
  tagging is off

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

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 109
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-30 02:57:15
  version version: 109
  version ubuntu: 20150825.1
  version device: 20150821-736d127
  version custom: 20150821-887-33-32-vivid

  Steps:
  1.Disable geotagging 
  2.Take a picture
  3.Transfer to desktop
  4.(install exiftool) Run "exiftool -gpslatitude -gpslongitude "

  Expectation:
  Verify that the picture doesn't contain location information

  Actual result:
  After step 4, there is still location information shows up in the terminal

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

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

[Touch-packages] [Bug 1517470] Re: /usr/bin/webapp-container:6:base::debug::BreakDebugger:logging::LogMessage::~LogMessage:oxide::BrowserContext::AssertNoContextsExist:oxide::BrowserProcessMainImpl::S

[Alexandre Abreu]

Just to be more precise, "an oxide context mismanagement" in the webapp
container ...

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

Title:
  /usr/bin/webapp-
  
container:6:base::debug::BreakDebugger:logging::LogMessage::~LogMessage:oxide::BrowserContext::AssertNoContextsExist:oxide::BrowserProcessMainImpl::Shutdown:qt_call_post_routines

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding webbrowser-app.  This problem was most recently seen with
  version 0.23+16.04.20151103bzr1264pkg0vivid5107+autopilot0, the
  problem page at
  https://errors.ubuntu.com/problem/8140ac614184b545ddcd30185930f36215a649cf
  contains more details.

  Rank 2 on errors.u.c for rc-proposed/meizu.en/arale

  The amount of crash reports increased significantly with webapp-
  container 0.23+15.04.20151103-0ubuntu1

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

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

[Touch-packages] [Bug 1517102] Re: Gmail webapp account renewal not successful

[Alexandre Abreu]

Nothing changed, just that the pattern is found in the Exec line and I
think might be a left over from an earlier version (or just a mistake),
it was never an allowed form. For google, we allow e.g. www.google.*
where the * is expanded to [^\\./] after but google.co.* is not a valid
pattern (which probably should be treated as a separate "bug"),

And yes it should be fixed,

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

Title:
  Gmail webapp account renewal not successful

Status in The Webapps-core project:
  New
Status in webapps-sprint:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  MX4 running rc-proposed 167

  I ran the gmail webapp which I have done in the past.
   I had a google account configured, and gmail was permitted to use it

  Open gmail, get directed to login with ubuntu one
  login into ubuntu one
  redirect to a webbrowser instance with my google account home displayed and 
no option for mail
  Close the browser
  the ubuntu one screen is still up but has no navigation available, so close 
that too
  close the gmail webapp

  I repeated that entire thing more than once, but third time I reopened
  the webapp it showed me the mail using my account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-core/+bug/1517102/+subscriptions

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

[Touch-packages] [Bug 1478974] Re: [camera] Toggling flash requires 1 swipe + 4 taps

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => High

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

Title:
  [camera] Toggling flash requires 1 swipe + 4 taps

Status in camera-app:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 r74

  1. Launch the Camera app.
  2. Try to turn the flash on/off.

  What happens: You need one swipe, then four taps:
  a. swipe up to reveal the camera controls
  b. tap the flash button
  c. tap the setting you want
  d. tap anywhere outside the settings to return to the controls
  e. tap anywhere outside the controls to return to the camera.

  By this time, whatever you want to take a photo of has probably
  disappeared or gotten bored.

  In comparison, toggling the flash in:
  * iOS Camera takes two taps
  * Windows Phone Camera takes either one or two taps, depending on which 
setting you want.

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

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

[Touch-packages] [Bug 1489833] Re: [Camera] If camera-app's access to the camera is revoked, it's hard to tell what's wrong

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => High

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

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Camera] If camera-app's access to the camera is revoked, it's hard to
  tell what's wrong

Status in camera-app:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  From a discussion between the Ubuntu phone insiders:

  with ota6, the camera app asks you for permission to use the camera. need to 
put yes. not sure how to check whether the phone thinks it got a yes or a no.
  yes, i accept and all is black..
  I also accepted it, but I needed to activate it somewhere in the settings 
somehow…
  Systen Settings -> Security & Privacy -> Other app access -> Camera
  I thought I accidently pressed the wrong button, but I'm not the only one…
  yep and if you acc denied then you have no idea what's happening
  not to mention that the settings are basically hidden :))
  Systen Settings -> Security & Privacy -> Other app access -> Camera 
  the camera really ought to say "camera access revoked; re-enable in system 
settings" if it's revoked
  yeah, that would be good

  It is possible to revoke the camera app's access to the camera. This
  is, I suppose, OK, but if it's been done then the camera app should
  display "access revoked" or similar, rather than just a black screen,
  and explain how to re-enable access.

  I suppose letting an app know that it has been revoked (rather than
  just lying by giving it a black screen and claiming that that's what
  the camera sees) is a security violation (should apps know they have
  been revoked?) but the revocation settings are well-hidden (as
  mentioned) and people will be very confused if they accidentally
  revoke the camera-app's access to the camera and don't know how to
  turn it back on; the camera app could be a lot more helpful here.

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

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

[Touch-packages] [Bug 1416882] Re: [desktop] camera-app makes segmentation fault when closed under load

[Florian Boucault]

We do not support the camera app on Ubuntu 14.10 anymore. Sorry.

** Changed in: camera-app
   Status: New => Won't Fix

** Changed in: camera-app (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [desktop] camera-app makes segmentation fault when closed under load

Status in camera-app:
  Won't Fix
Status in camera-app package in Ubuntu:
  Won't Fix

Bug description:

$ env LANG=C camera-app
Import path added "/usr/lib/x86_64-linux-gnu/camera-app"
Camera app directory "/usr/share/camera-app/"
unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work 
properly.
Provide your application identifier in $APP_ID environment 
variable.
Focus mode selection is not supported
APP_ID isn't set, the handler can not be registered
No media control support for org.qt-project.qt.cameraflashcontrol/5.0
No flash control support
No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
No exposure control support
APP_ID isn't set, the handler ignored

** (camera-app:26756): WARNING **: Unable to register app: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application ID
The camera doesn't support zooming.
QFileSystemWatcher::removePaths: list is empty
file:///usr/share/camera-app/GalleryView.qml:34: TypeError: Cannot read 
property 'selectionType' of null
Speicherzugriffsfehler (Speicherabzug geschrieben)

  "Speicherzugriffsfehler (Speicherabzug geschrieben)" means
  "segmentation fault (core dumped)" (`LANG` is ignored as you can see).

  There're no consequences noticable, but might cause any in the future
  as you can imagine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: camera-app 3.0.0+14.10.20141008-0ubuntu1
  Uname: Linux 3.18.5-031805-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  1 19:29:32 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-26 (5 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: camera-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1501588] Re: Wily's wpasupplicant frequently fails on WPA enterprise networks

[Adam]

Nevermind, I found the redhat bug with the RADIUS info.

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

Title:
  Wily's wpasupplicant frequently fails on WPA enterprise networks

Status in hostap:
  Unknown
Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from vivid to wily on my laptop, I'm running
  into problems when connecting to my home WPA2 enterprise network.

  Typically the first connection immediately after the driver is loaded
  works as expected, however any further reconnection and the occasional
  roaming between APs cause wpasupplicant to freeze entirely requiring
  me to kill it and most often also reload my wireless driver to get
  things working again.

  ## A failed (hanging) association looks like:
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): Activation: 
(wifi) connection 'stgraber.net-secure' has security, and secrets exist.  No 
new secrets needed.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'ssid' 
value 'stgraber.net-secure'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'scan_ssid' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'key_mgmt' value 'WPA-EAP'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'eap' 
value 'TLS'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'fragment_size' value '1300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'ca_cert' value '/home/stgraber/data/certs/stgraber-radius/ca.crt'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key' value '/home/stgraber/data/certs/stgraber-radius/castiana.p12'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key_passwd' value ''
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'identity' value 'castiana'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'bgscan' value 'simple:30:-65:300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'proactive_key_caching' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Connection 
disconnected (reason -3)
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associated -> disconnected
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: set interface 
ap_scan to 1
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: disconnected -> scanning
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: SME: Trying to 
authenticate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana kernel: [102903.079940] wlan0: authenticate with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.085128] wlan0: send auth to 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Trying to associate 
with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: scanning -> authenticating
  Sep 30 23:31:07 castiana kernel: [102903.086942] wlan0: authenticated
  Sep 30 23:31:07 castiana kernel: [102903.090103] wlan0: associate with 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: authenticating -> associating
  Sep 30 23:31:07 castiana kernel: [102903.101962] wlan0: RX AssocResp from 
24:a4:3c:c8:69:03 (capab=0x411 status=0 aid=1)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Associated with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.103701] wlan0: associated
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associating -> associated
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-STARTED 
EAP authentication started
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-METHOD 
EAP vendor 0 method 13 (TLS) selected
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PEER-CERT depth=2 
subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal 
Infrastructure/CN=stgraber.net Root CA/name=stgraber.net Infrastructure Root 
CA/emailAddress=stgra...@stgraber.org' 
hash=87b9750baadddac7f05164d7fde3a0eb3d3efe0c948b430a3ecd093c629956e9
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PEER-CERT 

[Touch-packages] [Bug 1450282] Re: Next photo will replace previous photo after take a photo with Camera

[Florian Boucault]

Please provide more information: what device you are testing that on?
what camera are you using? What version of Ubuntu?


** Changed in: camera-app
   Status: New => Incomplete

** Changed in: camera-app (Ubuntu)
   Status: New => Incomplete

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

Title:
  Next photo will replace previous photo after take a photo with Camera

Status in camera-app:
  Incomplete
Status in camera-app package in Ubuntu:
  Incomplete

Bug description:
  Boot to desktop.

  Open the Pictures folder then launched Camera to take a photo,after
  photo has been created, then take photo again.

  Found sometimes the new photo can be created successfully but
  sometimes will replace previous photo.

  Steps to Reproduce:
  1. Boot to desktop
  2. Open the Pictures folder then launched Camera to take a photo
  3. after photo has been created, then take photo again.
  4. Found sometimes the new photo can be created successfully but sometimes 
will replace previous photo.

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

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

[Touch-packages] [Bug 1447605] Re: Video mode should not have an HDR setting

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

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

Title:
  Video mode should not have an HDR setting

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

Bug description:
  Version: ubuntu-touch/stable/bq-aquaris.en r21 krillin
  Version: ubuntu-touch/stable/bq-aquaris.en r21 vegeta
  Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin

  Steps to reproduce:
   * open camera app
   * select video mode
   * swipe up from bottom edge
   * note settings available

  Expected results:
   - only settings relevant to video recording are displayed

  Actual results:
   - HDR is shown but isn't applicable to video mode

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

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

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select "accept"
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1517102] Re: Gmail webapp account renewal not successful

[Alexandre Abreu]

I created

https://bugs.launchpad.net/webapps-core/+bug/1517527

to cover the google.co.* case

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

Title:
  Gmail webapp account renewal not successful

Status in The Webapps-core project:
  New
Status in webapps-sprint:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  MX4 running rc-proposed 167

  I ran the gmail webapp which I have done in the past.
   I had a google account configured, and gmail was permitted to use it

  Open gmail, get directed to login with ubuntu one
  login into ubuntu one
  redirect to a webbrowser instance with my google account home displayed and 
no option for mail
  Close the browser
  the ubuntu one screen is still up but has no navigation available, so close 
that too
  close the gmail webapp

  I repeated that entire thing more than once, but third time I reopened
  the webapp it showed me the mail using my account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-core/+bug/1517102/+subscriptions

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

[Touch-packages] [Bug 1477435] Re: Video still keeps recording after removing sd card when set data storage to sd card in video mode.

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => High

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

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

Title:
  Video still keeps recording after removing sd card when set data
  storage to sd card in video mode.

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  system-image-cli -i
  current build number: 74
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-07-23 02:58:12
  version version: 74
  version ubuntu: 20150722
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

  step by step
  1. Open camera and switch to video mode.
  2.set data storage to  sd card
  3. Tap record button to record a video
  4. Remove SD card.
  Expected result
  The video should be stopped  to record.
  Actual result
  The video still keep recording.

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

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

[Touch-packages] [Bug 1473170] Re: camera preview in camera app on arale is pixelated

[Florian Boucault]

** Changed in: camera-app
   Importance: Undecided => Medium

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  camera preview in camera app on arale is pixelated

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  When I try to take a picture with my arale, the preview in the camera
  app before taking a picture is poor.

  It's pixelated and looks more like its taking a 2mpx image.

  The captured photo itself has very nice quality.

  Tested mupltiple times on arale rc-proposed r58.

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

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

[Touch-packages] [Bug 1479638] Re: Flash light icon displays on but it is off in fact after switch from front video mode to rear video mode.

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => High

** Changed in: camera-app
   Importance: High => Medium

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Flash light icon displays on but it is off in fact  after switch from
  front video mode to rear video mode.

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  system-image-cli -i
  current build number: 81
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-07-30 04:19:12
  version version: 81
  version ubuntu: 20150730
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid


  Step by step
  1.Launch rear camera, change to video mode.
  2.set Flash to on.
  3.change to front video mode,
  4.Change to rear video mode.
  Expected result:
  Flash light is on
  Actual result
  After step 4, flash icon displays on. but flash light is off in fact.

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

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

[Touch-packages] [Bug 1494145] Re: The delete media dialog (or share the video dialog) will appear without being choosen in photoroll

[Florian Boucault]

** Changed in: camera-app
   Status: New => In Progress

** Changed in: camera-app
   Importance: Undecided => High

** Changed in: camera-app
 Assignee: (unassigned) => Florian Boucault (fboucault)

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

Title:
  The delete media dialog (or share the video dialog) will appear
  without being choosen in photoroll

Status in camera-app:
  In Progress
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  current build number: 109
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-09-10 06:07:46
  version version: 109
  version ubuntu: 20150910
  version device: 20150818-0b38025
  version custom: 20150814-887-8-46

  Steps:
  1.Open the camera
  2.Take a video with any length
  3.Swipe to photoroll
  4.Tap the top right corner menu ,There will be :share,delete,edit
  5.Tap Edit, the menu disappeared and the video will be full screen
  6.Tap the top right corner again 

  Expectation:
  After step 6#, there isn't any option to be chosen

  Actual result:
  The delete media dialog (or share the video dialog) will appear without being 
choosen in photoroll, and pops up the confirmation dialog

  Notes:It happens every time

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

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

[Touch-packages] [Bug 1498278] Re: Shouldnt allow to switch cameras when only a single camera is present

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

** Changed in: camera-app
   Importance: Medium => High

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

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

Title:
  Shouldnt allow to switch cameras when only a single camera is present

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  In fact, the app freezes when I try to do so...

  This happens on my Laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: camera-app 3.0.0+15.10.20150707-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 21 23:25:30 2015
  InstallationDate: Installed on 2014-11-20 (305 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: camera-app
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: 2015-07-01 14:58:02
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1517029] Re: Real zoom level and reported zoom level mismatch when switching recording mode or camera

[Ugo Riboni]

** Summary changed:

- Real zoom level and reported zoom level mismatch when switching recording mode
+ Real zoom level and reported zoom level mismatch when switching recording 
mode or camera

** Branch linked: lp:~uriboni/camera-app/reset-zoom-ui

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

Title:
  Real zoom level and reported zoom level mismatch when switching
  recording mode or camera

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  - ensure you are in photo mode, not video mode
  - zoom to maximum zoom 
  - switch to video mode
  - switch back to photo mode

  What happens:
  - viewfinder is not zoomed, but zoom UI still reports maximum zoom

  Expected, any of the following:
  - viewfinder is not zoomed, and zoom UI reports no zoom
  - viewfinder is fully zoomed, and zoom UI reports full zoom

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

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

[Touch-packages] [Bug 1389617] Re: [camera] + [gallery] Inconsistant dialogs between camera and gallery

[Launchpad Bug Tracker]

** Branch linked: lp:~seb128/gallery-app/delete-dialogs-tweaks

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

Title:
  [camera] + [gallery] Inconsistant dialogs between camera and gallery

Status in Ubuntu UX:
  Fix Committed
Status in camera-app package in Ubuntu:
  Invalid
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  Using rtm 142, camera and gallery have similar photo browsing views,
  yet their dialogs to delete photos has different label/buttons, it
  would be nice if those would be the same

  ---

  Desired visual design outcome:

  All neutral buttons should be: UbuntuColor.lightgrey

  All negative actions buttons should be Red (not orange)

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

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

[Touch-packages] [Bug 1516444] Re: ld hangs indefinitely statically linking binutils on ppc64el

[Matthias Klose]

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

** Bug watch added: Sourceware.org Bugzilla #19264
   http://sourceware.org/bugzilla/show_bug.cgi?id=19264

** Also affects: binutils via
   http://sourceware.org/bugzilla/show_bug.cgi?id=19264
   Importance: Unknown
   Status: Unknown

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

Title:
  ld hangs indefinitely statically linking binutils on ppc64el

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  The latest util-linux upload, 2.27.1-1ubuntu1, reproducibly fails to
  build on ppc64el because the build hangs indefinitely:

  https://launchpad.net/ubuntu/+source/util-
  linux/2.27.1-1ubuntu1/+build/8230106

  The hanging command is:

  /usr/bin/ld -plugin /usr/lib/gcc/powerpc64le-linux-
  gnu/5/liblto_plugin.so -plugin-opt=/usr/lib/gcc/powerpc64le-linux-
  gnu/5/lto-wrapper -plugin-opt=-fresolution=/tmp/cce7J0Br.res -plugin-
  opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt
  =-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-
  through=-lgcc_s --sysroot=/ --build-id --eh-frame-hdr -m elf64lppc
  --hash-style=gnu --as-needed -dynamic-linker /lib64/ld64.so.2 -z relro
  -o test_fdisk_ask /usr/lib/gcc/powerpc64le-linux-gnu/5
  /../../../powerpc64le-linux-gnu/crt1.o /usr/lib/gcc/powerpc64le-linux-
  gnu/5/../../../powerpc64le-linux-gnu/crti.o /usr/lib/gcc/powerpc64le-
  linux-gnu/5/crtbegin.o -L/usr/lib/gcc/powerpc64le-linux-gnu/5
  -L/usr/lib/gcc/powerpc64le-linux-gnu/5/../../../powerpc64le-linux-gnu
  -L/usr/lib/gcc/powerpc64le-linux-gnu/5/../../../../lib -L/lib
  /powerpc64le-linux-gnu -L/lib/../lib -L/usr/lib/powerpc64le-linux-gnu
  -L/usr/lib/../lib -L/usr/lib/gcc/powerpc64le-linux-gnu/5/../../..
  libfdisk/src/test_fdisk_ask-ask.o ./.libs/libfdisk.a /home/ubuntu
  /util-linux-2.27.1/.libs/libblkid.a /home/ubuntu/util-
  linux-2.27.1/.libs/libuuid.a -lgcc --as-needed -lgcc_s --no-as-needed
  -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/powerpc64le-
  linux-gnu/5/crtend.o /usr/lib/gcc/powerpc64le-linux-gnu/5
  /../../../powerpc64le-linux-gnu/crtn.o

  strace shows it repeatedly calling brk(), so presumably trying to
  allocate more memory in very small increments.

  It doesn't appear to be lto-related.  The symptom is reproducible when
  calling gcc with -fno-lto.

  I do not yet have a useful backtrace from ld for this, because for
  some reason recent versions of binutils are not getting dbgsym
  packages in the archive.

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

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

[Touch-packages] [Bug 1412916] Re: evince: Bad PDF rendering: invalid font scale

[Launchpad Bug Tracker]

This bug was fixed in the package poppler - 0.24.5-2ubuntu4.3

---
poppler (0.24.5-2ubuntu4.3) trusty; urgency=medium

  * debian/patches/git_matrix_not_invertable.patch:
- cairo: don't render text when text matrix is not invertable
  (lp: #1412916)

 -- Sebastien Bacher   Tue, 13 Oct 2015 16:10:18
+0100

** Changed in: poppler (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 poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1412916

Title:
  evince: Bad PDF rendering: invalid font scale

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  * Many PDFs do not display correctly, including the boarding passes from a
major European airline.

  * Printing a boarding pass is a common simple task which users expect to
work, and therefore should be fixed in the stable release.

  * See upstream bug report for discussion about the mechanism of the
  fix.

  [Test Case]

  * Attempt to view the test case in the linked upstream bug using 'evince
attachment.pdf'.

  * Observe corrupted text displayed.

  [Regression Potential]

  * Theoretically, other PDFs which currently display correctly could be
  displayed incorrectly after this change, but is intended to emulate
  acroread, so this is unlikely.

  * Patch has been reviewed and committed upstream, so should be safe.

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

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

[Touch-packages] [Bug 1472903] Re: Camera flash black screen one time after open camera app.

[Florian Boucault]

** Changed in: camera-app
   Status: In Progress => Fix Released

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

Title:
  Camera flash black screen one time after open camera app.

Status in camera-app:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  system-image-cli -i
  current build number: 62
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-07-09 02:09:42
  version version: 62
  version ubuntu: 20150708.1
  version device: 20150529-8e13c5f
  version custom: 20150707-800-29-17-vivid
  Precondition：
  The camera didn't run in the background
  Step by step
  1.Open the camera and check the screen.
  Expected result:
  Camera is opened normally.
  Actual result:
  open camera, camera screen flash black screen one time.

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

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

[Touch-packages] [Bug 1412916] Update Released

[Chris J Arges]

The verification of the Stable Release Update for poppler has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  evince: Bad PDF rendering: invalid font scale

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  * Many PDFs do not display correctly, including the boarding passes from a
major European airline.

  * Printing a boarding pass is a common simple task which users expect to
work, and therefore should be fixed in the stable release.

  * See upstream bug report for discussion about the mechanism of the
  fix.

  [Test Case]

  * Attempt to view the test case in the linked upstream bug using 'evince
attachment.pdf'.

  * Observe corrupted text displayed.

  [Regression Potential]

  * Theoretically, other PDFs which currently display correctly could be
  displayed incorrectly after this change, but is intended to emulate
  acroread, so this is unlikely.

  * Patch has been reviewed and committed upstream, so should be safe.

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

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

[Touch-packages] [Bug 1513310] Re: The "Delete media" pop up window does not rotate with the screen in camera app.

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  The "Delete media" pop up window does not rotate with the screen in
  camera app.

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

Bug description:
  current build number: 154
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-11-04 07:38:22
  version version: 154
  version ubuntu: 20151104
  version device: 20151016-0b38025
  version custom: 20150925-900-8-47

  Precondition:
  1.Some photos or video are saved in the device.
  2.Set Rotation lock as Off state.

  Steps:
  1.Launch camera->Swipe the screen,one picture or video will display.
  2.Tap the menu button and select "Delete",the pop up window "Delete media" 
displays.
  3.Rotate the screen and check the UI.

  Actual result:The pop up window does not rotate and the picture or video 
rotates.
  Expect result:The pop up window should also rotate.

  Comments:In addition,after tapping the menu button,if you select
  "Share" and enter "Share to "interface,rotate the screen,the screen
  also does not rotate.

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

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

[Touch-packages] [Bug 1445035] Re: Poor quality of photos - consider the use of software jpeg

[Florian Boucault]

We do not control how the BQ E4.5 phone converts the sensor information
into the final JPEG and therefore cannot implement this suggestion.

** Changed in: camera-app
   Status: New => Won't Fix

** Changed in: camera-app (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Poor quality of photos - consider the use of software jpeg

Status in camera-app:
  Won't Fix
Status in camera-app package in Ubuntu:
  Won't Fix

Bug description:
  Image quality on the bq aquaris phone is relatively low even on the
  highest quality setting. Numerous compression artifacts are visible
  like on pictures taken with a cheap Chinese tablet. On the other hand,
  imagemagick convert takes 2s on this CPU when converting 8 MP bmp file
  to jpeg. So please consider using software jpeg for the highest
  quality setting.

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

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

[Touch-packages] [Bug 1441095] Re: novatel: improve probing for Dell branded modems

[Chris J Arges]

Hello Bin, or anyone else affected,

Accepted network-manager into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/0.9.8.8-0ubuntu7.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: network-manager (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]

   * There is no gateway information in Network Manager. (See the picture in 
comment #74)
* Some ISPs like TW Mobile in Taiwan don't need the gateway to connect to 
Internet.
* Some ISPs like Chunghwa Telecom in Taiwan do need the gateway to connect 
to Internet.
* We need to see the gateway information in Network Manager to cover all 
ISPs.

  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

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

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

[Touch-packages] [Bug 1431211] Re: [desktop] camera-app preview screen twisted after maximizing the preview screen

[Florian Boucault]

We do not support the camera app on 14.04 anymore. Sorry.

** Changed in: camera-app
   Status: Incomplete => Won't Fix

** Changed in: camera-app (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  [desktop] camera-app preview screen twisted after maximizing the
  preview screen

Status in camera-app:
  Won't Fix
Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in camera-app package in Ubuntu:
  Won't Fix

Bug description:
  The preview screen of camera-app twisted after maximizing the preview screen.
  It has failure-rate, should be reproduced in 5 times of retries.
  version: 2.9.1+14.04.20130508-0ubuntu1

  ---
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong150206-trusty-amd64-20150214-1
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2015-02-17 (23 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150214-07:47
  NonfreeKernelModules: wl fglrx
  Package: camera-app 2.9.1+14.04.20140508-0ubuntu1 [origin: Canonical]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-45-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Florian Boucault]

** Changed in: camera-app
   Status: New => Triaged

** Changed in: camera-app
   Importance: Undecided => High

-- 
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:
  Triaged
Status in Canonical System Image:
  Triaged
Status in camera-app package in Ubuntu:
  Triaged

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/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 1303962] Re: please integrate mediascanner2 and media-hub with apparmor

[Jim Hodapp]

** Also affects: media-hub (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: media-hub (Ubuntu)
   Status: New => Fix Released

** Also affects: media-hub (Ubuntu RTM)
   Importance: Undecided
   Status: New

** No longer affects: media-hub

** Changed in: media-hub (Ubuntu RTM)
   Status: New => Fix Released

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

Title:
  please integrate mediascanner2 and media-hub with apparmor

Status in Thumbnailer:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in media-hub package in Ubuntu:
  Fix Released
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in media-hub package in Ubuntu RTM:
  Fix Released

Bug description:
  media-hub and mediascanner are separate processes from apps and are
  used to play and scan music and video files respectively. Up until
  now, apps would have to use the music_files_read or video_files_read
  reserved policy groups to access media. The problem is, these policy
  groups are reserved and not available to normal AppStore apps in order
  to prevent information leaks (this user has this video installed) and
  theft (can access the music and video directly). The path forward is
  that media-hub and mediascanner are helpers that apps can use and they
  should integrate with the trust store.

  AppStore apps:
   1. should be able to access their own content (installed or local)
   2. should not be able to access, play or otherwise enumerate other apps' 
media (ie, app 'foo' should not be able to play the facebook app's sound file
   3. AppStore apps should be able to enumerate the global music (~/Music) and 
video (~/Video) library via the mediascanner helper with permission from the 
user
   4. AppStore apps should be able to play the global music (~/Music) and video 
(~/Video) library via the media-hub with permission from the user
   5. AppStore apps should be able to have access to media files with 
permission from the user. This is already handled by the content-hub paradigm 
(though someone would need to add a media content provider for the content-hub 
to have this work)

  Both media-hub and mediascanner should do something like the below
  pseudo code:

  # see 'man aa_getcon()' from libapparmor-dev for more info
  # conn_name is the unique D-Bus connection name of the application connecting
  # to media-hub/mediascanner
  apparmor_profile = 
org.freedesktop.DBus.GetConnectionAppArmorSecurityContext(conn_name)

  pkgname = apparmor_profile.split('_')[0]
  if apparmor_profile == unconfined: # unconfined apps can access all the files
  allow access
  elif playback_file in ~/.local/share/$pkgname/... or playback_file in 
~/.cache/$pkgname/..: # apps can access their own files
  allow access
  elif $pkgname can access playback_file in trust store: # apps can access the 
files if user said so previously
  allow access
  elif playback_file in ~/Music:
  answer = prompt user for access to global music files
  if $answer == yes
  update trust store for $pkgname can enumerate/play ~/Music
  allow access
  else:
  deny access
  elif playback_file in ~/Videos:
  answer = prompt user for access to global video files
  if $answer == yes
  update trust store for $pkgname can enumerate/play ~/Videos
  allow access
  else:
  deny access
  else:
  deny access

  To have the best user experience and prevent multiple prompting,
  mediascanner and media-hub should use the same trust store database.
  I'm not sure that mediascanner2 offers a DBus API for enumerating
  global media files yet or not (music-app seems to be accessing files
  in ~/.cache/media-art/ and ~/.cache/mediascanner directly).

  UPDATE: 2014-05-02
  media-hub implemented '1' and '2' already (can access its own data, but not 
other apps' data) and was marked Fix Released. Trust store integration ('3' and 
'4') is now being tracked in bug #1315381.

  mediascanner2 still needs to implement '1' and '2'. The 'audio' and
  'video' policy groups will *not* add this access at this time.
  Instead, apps can use 'read_path' as part of their policy to have
  access to the mediascanner files. This is workable for the music app,
  but will block other apps from inclusion in the app store.

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

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

[Touch-packages] [Bug 1513310] Re: The "Delete media" pop up window does not rotate with the screen in camera app.

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

** Changed in: camera-app
 Assignee: (unassigned) => Ugo Riboni (uriboni)

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

Title:
  The "Delete media" pop up window does not rotate with the screen in
  camera app.

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

Bug description:
  current build number: 154
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-11-04 07:38:22
  version version: 154
  version ubuntu: 20151104
  version device: 20151016-0b38025
  version custom: 20150925-900-8-47

  Precondition:
  1.Some photos or video are saved in the device.
  2.Set Rotation lock as Off state.

  Steps:
  1.Launch camera->Swipe the screen,one picture or video will display.
  2.Tap the menu button and select "Delete",the pop up window "Delete media" 
displays.
  3.Rotate the screen and check the UI.

  Actual result:The pop up window does not rotate and the picture or video 
rotates.
  Expect result:The pop up window should also rotate.

  Comments:In addition,after tapping the menu button,if you select
  "Share" and enter "Share to "interface,rotate the screen,the screen
  also does not rotate.

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

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

[Touch-packages] [Bug 1472913] Re: Dialogs and Content-hub page are always in portrait

[Florian Boucault]

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

** This bug is no longer a duplicate of bug 1390451
   photo deletion confirmation dialog does not rotate to landscape
** This bug has been marked a duplicate of bug 1513310
   The "Delete media" pop up window does not rotate with the screen in camera 
app.

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

Title:
  Dialogs and Content-hub page are always in portrait

Status in camera-app:
  New
Status in camera-app package in Ubuntu:
  New

Bug description:
  When you try to delete a photo, the dialog is always in portrait. When
  you try to share a photo, the content-hub page is also in portrait.

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

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

[Touch-packages] [Bug 1517132] Re: Assert when after log-in inside the session

[Albert Astals Cid]

** Branch linked: lp:~aacid/mir/eintr_dispatch_loop

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

Title:
  Assert when after log-in inside the session

Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm trying to start unity8 session on the laptop"

  After logging in from lightdm i get the "unity8 screen locker".

  There i input the password again and then unity8 crashes/aborts, the
  log says

  terminate called after throwing an instance of 
'boost::exception_detail::clone_impl'
what():  Failed to wait for event: La crida al sistema ha estat interrompuda
  ()

  
  where "La crida al sistema ha estat interrompuda" translates roughly to "The 
system call was interrupted".

  Found the "Failed to wait for event:" in mir in 
  ./src/common/dispatch/threaded_dispatcher.cpp:207:
 "Failed to wait for event"}));

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

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

[Touch-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Chris J Arges]

** Tags removed: verification-done-vivid
** Tags added: verification-failed

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

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

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

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

[Touch-packages] [Bug 1378379] Re: [All Apps] Define rules to construct static splash screen in desktop file

[Florian Boucault]

** Changed in: camera-app
   Status: In Progress => Confirmed

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

Title:
  [All Apps] Define rules to construct static splash screen in desktop
  file

Status in camera-app:
  Confirmed
Status in dialer-app:
  Fix Released
Status in gallery-app:
  Fix Released
Status in mediaplayer-app:
  New
Status in messaging-app:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in The Webapps-core project:
  Triaged
Status in webbrowser-app:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  Fix Released
Status in gallery-app package in Ubuntu RTM:
  Fix Released
Status in messaging-app package in Ubuntu RTM:
  Fix Released
Status in webbrowser-app package in Ubuntu RTM:
  Fix Released

Bug description:
  Need to start making use of the static splash screen feature recently
  landed in unity8.

  How to use them can be found in:

  https://lists.launchpad.net/ubuntu-phone/msg09996.html

  And a current example is address-book-app.

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

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

[Touch-packages] [Bug 1429158] Re: Autopilot tests depend on qt4

[Florian Boucault]

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Medium

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Autopilot tests depend on qt4

Status in camera-app:
  Confirmed
Status in address-book-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in click-update-manager package in Ubuntu:
  New
Status in cordova-ubuntu package in Ubuntu:
  New
Status in gallery-app package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  Triaged
Status in mediaplayer-app package in Ubuntu:
  New
Status in notes-app package in Ubuntu:
  New
Status in ubuntu-html5-theme package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in unity-webapps-qml package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When installing the autopilot tests, they bring qt4 dependencies that
  are unnecessary.

  The package with the autopilot tests depends on libautopilot-qt, which
  installs both autopilot-qt4 and autopilot-qt5.

  We can remove that dependency and add autopilot-qt5 and qttestability-
  autopilot instead.

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

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

[Touch-packages] [Bug 1511074] Re: camera is missing auto focus options OFF

[Florian Boucault]

** Changed in: camera-app
   Status: New => Triaged

** Changed in: camera-app
   Importance: Undecided => Wishlist

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

Title:
  camera is missing auto focus options OFF

Status in camera-app:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Triaged

Bug description:
  camera is missing auto focus options ON/OFF

  i really need to turn OFF auto focus. i can't record the screen
  without turning OFF the auto focus, but there is no settings...

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

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

[Touch-packages] [Bug 1517538] [NEW] Crashes after exiting fullscreen

[Nikita Yerenkov-Scott]

Public bug reported:

I have noticed that recently upon going fullscreen in VLC on Ubuntu
GNOME 15.10 with GNOME 3.18 that on most occasions when I exit
fullscreen (even if I've only been in it for a few seconds) I get logged
out of my user session (my computer automatically puts me in TTY2 for
some reason at startup although there is another GUI session (not
console) in TTY7) and get taken to the user session at TTY7 where I am
met with the thing with the time on it that I have time slide up to log
in, though it is a metal colour (and not the one I set it to for
anything): Metal.png

But it is not even as though my user session has simply been somehow
moved there as that is actually a separate user session that asks me to
log in and not to unlock my old session. And when I then go to TTY2,
instead of finding my session, I find the console login screen of TTY2.
So now I am basically unable to use fullscreen in VLC (it doesn't appear
to happen when using anything else) because my session seems to get
destroyed every time.

And I am not sure if this is a bug with VLC or Xorg, so I thought I
should report it under both, I am also not sure if it would just happen
with VLC, but so far that has been the only fullscreen application to
have this happen at the same time as it running.

---

OS Information:

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename:   wily
Flavour: GNOME
GNOME Version: 3.18

Package Information:

xorg:
  Installed: 1:7.7+7ubuntu4
  Candidate: 1:7.7+7ubuntu4
  Version table:
 *** 1:7.7+7ubuntu4 0
500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status

vlc:
  Installed: 2.2.1-3
  Candidate: 2.2.1-3
  Version table:
 *** 2.2.1-3 0
500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
100 /var/lib/dpkg/status

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

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

** Attachment added: "Metal.png"
   https://bugs.launchpad.net/bugs/1517538/+attachment/4521458/+files/Metal.png

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

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

** No longer affects: xserver-xorg-driver-vesa

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

Title:
  Crashes after exiting fullscreen

Status in vlc package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I have noticed that recently upon going fullscreen in VLC on Ubuntu
  GNOME 15.10 with GNOME 3.18 that on most occasions when I exit
  fullscreen (even if I've only been in it for a few seconds) I get
  logged out of my user session (my computer automatically puts me in
  TTY2 for some reason at startup although there is another GUI session
  (not console) in TTY7) and get taken to the user session at TTY7 where
  I am met with the thing with the time on it that I have time slide up
  to log in, though it is a metal colour (and not the one I set it to
  for anything): Metal.png

  But it is not even as though my user session has simply been somehow
  moved there as that is actually a separate user session that asks me
  to log in and not to unlock my old session. And when I then go to
  TTY2, instead of finding my session, I find the console login screen
  of TTY2. So now I am basically unable to use fullscreen in VLC (it
  doesn't appear to happen when using anything else) because my session
  seems to get destroyed every time.

  And I am not sure if this is a bug with VLC or Xorg, so I thought I
  should report it under both, I am also not sure if it would just
  happen with VLC, but so far that has been the only fullscreen
  application to have this happen at the same time as it running.

  ---

  OS Information:

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 15.10
  Release:15.10
  Codename:   wily
  Flavour: GNOME
  GNOME Version: 3.18

  Package Information:

  xorg:
Installed: 1:7.7+7ubuntu4
Candidate: 1:7.7+7ubuntu4
Version table:
   *** 1:7.7+7ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  vlc:
Installed: 2.2.1-3
Candidate: 2.2.1-3
Version table:
   *** 2.2.1-3 0
  500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1473599] Re: gdb complains about missing Python module libstdcxx.v6.printers

[Matthias Klose]

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

** This bug has been marked a duplicate of bug 1446828
   gdb pretty printers do not auto-load on Trusty

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

Title:
  gdb complains about missing Python module libstdcxx.v6.printers

Status in gcc-4.8 package in Ubuntu:
  Confirmed

Bug description:
  This appears to be a regression of Debian Bug 726094
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726094

  Invoking GDB on any C++ program generates the message:

  Traceback (most recent call last):
File 
"/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
  from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named 'libstdcxx'

  My system info:
  $ lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04
  $ apt-cache policy libstdc++6-4.8-dbg
  libstdc++6-4.8-dbg:
Installed: 4.8.4-2ubuntu1~14.04
Candidate: 4.8.4-2ubuntu1~14.04
Version table:
   *** 4.8.4-2ubuntu1~14.04 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.8.2-19ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Expected to happen:
No Python tracebacks in GDB
  What happened instead:
ImportError: No module named 'libstdcxx'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libstdc++6-4.8-dbg 4.8.4-2ubuntu1~14.04
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Fri Jul 10 18:03:53 2015
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gcc-4.8
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (438 days ago)

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

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

[Touch-packages] [Bug 1514309] Re: Undefined Behavior in GCC 4.8 ios_base.h

[Matthias Klose]

** Package changed: gcc-defaults (Ubuntu) => gcc-4.8 (Ubuntu)

** Changed in: gcc-4.8 (Ubuntu)
   Status: New => Confirmed

** Also affects: gcc-4.8 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  Undefined Behavior in GCC 4.8 ios_base.h

Status in gcc-4.8 package in Ubuntu:
  Confirmed
Status in gcc-4.8 source package in Trusty:
  New

Bug description:
  On Linux, the distros often use libstdc++ rather than libc++ for
  Clang. Building libcxx is an art that I have never been able to
  untangle, and I think the maintainers have discovered the same.

  Below, I'm catching a UB finding when using Clang and libstdc++. This
  one has been around for some time. I first encountered it on Apple
  platforms. I regularly encounter it on Debian and Ubuntu.

  The fix is fairly easy, and I usually just do it: a couple of casts
  among unsigned and the flags. Also see http://lists.llvm.org/pipermail
  /cfe-dev/2015-January/040753.html.

  **

  $ cat ub.cxx
  #include 

  int main(int argc, char* argv[])
  {
std::cout << std::hex << argc << std::endl;
std::cout << std::dec << argc << std::endl;
return 0;
  }

  $ clang++ -fsanitize=undefined ub.cxx -o ub.exe

  $ ./ub.exe
  
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/ios_base.h:96:24:
 runtime error: load of value 4294967221, which is not a valid value for type 
'std::_Ios_Fmtflags'
  
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/ios_base.h:76:67:
 runtime error: load of value 4294967221, which is not a valid value for type 
'std::_Ios_Fmtflags'
  1
  1

  **

  $ g++ --version
  g++ (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4

  $ uname -a
  Linux ubuntu 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release
  No LSB modules are available.

  **

  $ apt-cache show g++
  Package: g++
  Priority: optional
  Section: devel
  Installed-Size: 34
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian GCC Maintainers 
  Architecture: amd64
  Source: gcc-defaults (1.124ubuntu6)
  Version: 4:4.8.2-1ubuntu6
  Provides: c++-compiler
  Depends: cpp (>= 4:4.8.2-1ubuntu6), gcc (>= 4:4.8.2-1ubuntu6), g++-4.8 (>= 
4.8.2-5~), gcc-4.8 (>= 4.8.2-5~)
  Suggests: g++-multilib
  Filename: pool/main/g/gcc-defaults/g++_4.8.2-1ubuntu6_amd64.deb
  Size: 1490
  MD5sum: 7332a4e9116b821e167a3d0236ca413a
  SHA1: 2c7201808be1029d21b7691c5a855535a4fcbd51
  SHA256: 02c3d204efe6c34bf3de655aaf6a9ce524511977aedf92d7bce7093d0581f977
  Description-en: GNU C++ compiler
   This is the GNU C++ compiler, a fairly portable optimizing compiler for C++.
   .
   This is a dependency package providing the default GNU C++ compiler.
  Description-md5: 4d44b18774ae5123b7c3f70d940cf655
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Build-Essential: yes
  Origin: Ubuntu
  Supported: 5y

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

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

[Touch-packages] [Bug 1446828] Re: gdb pretty printers do not auto-load on Trusty

[Launchpad Bug Tracker]

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

** Changed in: gcc-4.8 (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  gdb pretty printers do not auto-load on Trusty

Status in gcc-4.8 package in Ubuntu:
  Confirmed
Status in gcc-4.8 source package in Trusty:
  Confirmed

Bug description:
  On Ubuntu 14.04.2 (Trusty), the file in libstdc++6-4.8-dbg to auto-
  load the pretty printers doesn't resolve the right path to the
  printers. To reproduce, on a fresh install:

  $ cat test.cpp
  #include 
  int main() {
std::vector v;
v.push_back(1);
return 0;
  }
  $ g++ test.cpp -g
  $ gdb a.out -ex start
  Reading symbols from a.out...done.
  Temporary breakpoint 1 at 0x400956: file test.cpp, line 3.
  Starting program: /home/emaisin/a.out 
  Traceback (most recent call last):
File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
  from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named 'libstdcxx'

  Temporary breakpoint 1, main () at test.cpp:3
  3   std::vector v;
  (gdb) 

  It seems like the fixup for multiarch actually adds an extra "..":

  if not os.path.basename(os.path.dirname(__file__)).startswith('lib'):
  backdirs += 1 # multiarch subdir

  Removing these two lines almost makes it work:

  $ gdb a.out -ex start
  Reading symbols from a.out...done.
  Temporary breakpoint 1 at 0x400956: file test.cpp, line 3.
  Starting program: /home/emaisin/a.out 
  Traceback (most recent call last):
File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
  from libstdcxx.v6.printers import register_libstdcxx_printers
File 
"/usr/lib/x86_64-linux-gnu/../../share/gcc-4.8/python/libstdcxx/v6/printers.py",
 line 54
  raise ValueError, "Cannot find type %s::%s" % (str(orig), name)
  ^
  SyntaxError: invalid syntax

  Temporary breakpoint 1, main () at test.cpp:3
  3   std::vector v;

  
  That last problem is tracked in bug #1256419, which is still a pending issue 
in Trusty.

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

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

[Touch-packages] [Bug 1517572] [NEW] Applications window randomly freezes

[pl7ofit]

Public bug reported:

Applications window randomly freezes (firefox, steam)not unfreezes, only
kill, freezes only the application window, and DE worked well without
freezes

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 18 19:31:08 2015
InstallationDate: Installed on 2015-11-17 (1 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd amd64 apport-bug freeze radeon trusty xubuntu

** Tags added: amd xubuntu

** Tags added: radeon

** Description changed:

  Applications window randomly freezes (firefox, steam)not unfreezes, only
- kill, freezes only the application window, and DE worked without freezes
+ kill, freezes only the application window, and DE worked well without
+ freezes
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 18 19:31:08 2015
  InstallationDate: Installed on 2015-11-17 (1 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Applications window randomly freezes

Status in xorg package in Ubuntu:
  New

Bug description:
  Applications window randomly freezes (firefox, steam)not unfreezes,
  only kill, freezes only the application window, and DE worked well
  without freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 18 19:31:08 2015
  InstallationDate: Installed on 2015-11-17 (1 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels

[Stéphane Graber]

** Description changed:

+ == SRU ==
+ Rationale: LXC no longer starts on kernels > 3.2 and < 3.8
+ Test case: Try starting an LXC container on an affected kernel
+ Regression potential: Can't really get any worse. Change has been reviewed 
and tested upstream.
+ 
+ == Original bug report ==
  ubuntu-touch/devel-proposed/mako 350
  
  After flashing the device the boot hangs on the vendor logo.
  There is no crash file on the device but it seems that the android container 
fails to start.
  
- There is the following error in syslog 
+ There is the following error in syslog
  Nov 17 08:33:15 ubuntu-phablet kernel: [8.694826] init: 
lxc-android-config main process (918) terminated with status 255
  
  and in upstart/android.log:
-   lxc-start 1447749195.286 ERRORlxc_start - start.c:preserve_ns:149 - 
No such file or directory - failed to open '/proc/1055/ns/mnt'
-   lxc-start 1447749195.286 ERRORlxc_start - start.c:lxc_spawn:993 - 
failed to store namespace references
-   lxc-start 1447749195.408 ERRORlxc_start - start.c:__lxc_start:1192 
- failed to spawn 'android'
-   lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:344 - 
The container failed to start.
-   lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:348 - 
Additional information can be obtained by setting the --logfile and 
--logpriority options.
+   lxc-start 1447749195.286 ERRORlxc_start - start.c:preserve_ns:149 - 
No such file or directory - failed to open '/proc/1055/ns/mnt'
+   lxc-start 1447749195.286 ERRORlxc_start - start.c:lxc_spawn:993 - 
failed to store namespace references
+   lxc-start 1447749195.408 ERRORlxc_start - start.c:__lxc_start:1192 
- failed to spawn 'android'
+   lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:344 - 
The container failed to start.
+   lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:348 - 
Additional information can be obtained by setting the --logfile and 
--logpriority options.

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

Title:
  LXC's preserve_ns fails on < 3.8 kernels

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Committed
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Vivid:
  Triaged
Status in lxc source package in Wily:
  Fix Committed
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  == SRU ==
  Rationale: LXC no longer starts on kernels > 3.2 and < 3.8
  Test case: Try starting an LXC container on an affected kernel
  Regression potential: Can't really get any worse. Change has been reviewed 
and tested upstream.

  == Original bug report ==
  ubuntu-touch/devel-proposed/mako 350

  After flashing the device the boot hangs on the vendor logo.
  There is no crash file on the device but it seems that the android container 
fails to start.

  There is the following error in syslog
  Nov 17 08:33:15 ubuntu-phablet kernel: [8.694826] init: 
lxc-android-config main process (918) terminated with status 255

  and in upstart/android.log:
    lxc-start 1447749195.286 ERRORlxc_start - start.c:preserve_ns:149 - 
No such file or directory - failed to open '/proc/1055/ns/mnt'
    lxc-start 1447749195.286 ERRORlxc_start - start.c:lxc_spawn:993 - 
failed to store namespace references
    lxc-start 1447749195.408 ERRORlxc_start - start.c:__lxc_start:1192 
- failed to spawn 'android'
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:344 - 
The container failed to start.
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:348 - 
Additional information can be obtained by setting the --logfile and 
--logpriority options.

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

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

[Touch-packages] [Bug 1516245] Re: Full URL of page not shown unless user clicks on it

[James Mulholland]

This is a largely matter of personal preference and not a bug  - if you
look at other mobile browsers you'll see both approaches being used by
different products, e.g. :

- Opera Mobile Browser & - Safari Mobile Browser:  Only host name is shown
- Chrome Mobile Browser & Firefox Mobile Browser : As much as possible from the 
*beginning* of a URL is shown (so if a URL is longer than 14-20 characters, 
only part of the host portion of the URL is visible anyway).


Thank you for taking the time to give us your opinion on this (we have 
'opinion' and 'wishlist' categories for these sorts of items in future, as they 
are not  bugs)

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

Title:
  Full URL of page not shown unless user clicks on it

Status in Ubuntu UX:
  Opinion
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  By default, the browser only shows the host name of the page. However,
  the full URL is shown when clicking on it.

  There's really no reason to do this, so why not show the entire URL
  all the time (or at least as much of it as fits in the URL bar)

  phablet@ubuntu-phablet:~/public_html$ lsb_release -rd
  Description:Ubuntu 15.04
  Release:15.04
  phablet@ubuntu-phablet:~/public_html$ apt-cache policy webbrowser-app
  webbrowser-app:
Installed: 0.23+15.04.20151103-0ubuntu1
Candidate: 0.23+15.04.20151103-0ubuntu1
Version table:
   *** 0.23+15.04.20151103-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-snapshot/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.23+15.04.20150416-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

  What I expected to happen:
URL should be visible entirely all the time (or at least as much as fits)

  What happened instead:
Only host name of page is shown. Rest of URL is only shown after clicking 
on it.

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

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

[Touch-packages] [Bug 1517569] [NEW] after change my password using a character * i was unable to login in graphic mode, but in terminal it works ok, i change to a password without * and it works fine

[Tiago]

Public bug reported:

I'm using ubuntu 15.10 and recently change my password it works ok, but
after reboot my machine i can't login anymore using the graphic
interface, but when i enter the command line mode i can login normally.
I make sure that the problem was the password changed instaling ubuntu
in a virtual machine and trying the same thing, i realize that when i
use the * character in my password this error occurs. Once occurred the
first time i try to change the password and login again in graphic mode
but it doesn't work, only reinstalling the system.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lightdm 1.16.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
Date: Wed Nov 18 15:21:05 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-06 (12 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  after change my password using a character * i was unable to login in
  graphic mode, but in terminal it works ok, i change to a password
  without * and it works fine in all, graphic and terminal.

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 15.10 and recently change my password it works ok,
  but after reboot my machine i can't login anymore using the graphic
  interface, but when i enter the command line mode i can login
  normally. I make sure that the problem was the password changed
  instaling ubuntu in a virtual machine and trying the same thing, i
  realize that when i use the * character in my password this error
  occurs. Once occurred the first time i try to change the password and
  login again in graphic mode but it doesn't work, only reinstalling the
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Wed Nov 18 15:21:05 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (12 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1446828] Re: gdb pretty printers do not auto-load on Trusty

[Matthias Klose]

** Also affects: gcc-4.8 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  gdb pretty printers do not auto-load on Trusty

Status in gcc-4.8 package in Ubuntu:
  Confirmed
Status in gcc-4.8 source package in Trusty:
  Confirmed

Bug description:
  On Ubuntu 14.04.2 (Trusty), the file in libstdc++6-4.8-dbg to auto-
  load the pretty printers doesn't resolve the right path to the
  printers. To reproduce, on a fresh install:

  $ cat test.cpp
  #include 
  int main() {
std::vector v;
v.push_back(1);
return 0;
  }
  $ g++ test.cpp -g
  $ gdb a.out -ex start
  Reading symbols from a.out...done.
  Temporary breakpoint 1 at 0x400956: file test.cpp, line 3.
  Starting program: /home/emaisin/a.out 
  Traceback (most recent call last):
File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
  from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named 'libstdcxx'

  Temporary breakpoint 1, main () at test.cpp:3
  3   std::vector v;
  (gdb) 

  It seems like the fixup for multiarch actually adds an extra "..":

  if not os.path.basename(os.path.dirname(__file__)).startswith('lib'):
  backdirs += 1 # multiarch subdir

  Removing these two lines almost makes it work:

  $ gdb a.out -ex start
  Reading symbols from a.out...done.
  Temporary breakpoint 1 at 0x400956: file test.cpp, line 3.
  Starting program: /home/emaisin/a.out 
  Traceback (most recent call last):
File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
  from libstdcxx.v6.printers import register_libstdcxx_printers
File 
"/usr/lib/x86_64-linux-gnu/../../share/gcc-4.8/python/libstdcxx/v6/printers.py",
 line 54
  raise ValueError, "Cannot find type %s::%s" % (str(orig), name)
  ^
  SyntaxError: invalid syntax

  Temporary breakpoint 1, main () at test.cpp:3
  3   std::vector v;

  
  That last problem is tracked in bug #1256419, which is still a pending issue 
in Trusty.

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

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

[Touch-packages] [Bug 1517093] Re: HTM builtins aren't treated as compiler barriers on powerpc

[Matthias Klose]

** Also affects: gcc-4.8 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: gcc-5 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** No longer affects: gcc-5 (Ubuntu Trusty)

** Description changed:

  ---Problem Description---
  HTM builtins aren't treated as compiler barriers on powerpc
-  
- Contact Information = berg...@us.ibm.com 
-  
+ 
+ Contact Information = berg...@us.ibm.com
+ 
  ---Steps to Reproduce---
  
-  This bug is a mirror of the (fixed) upstream FSF bugzilla 
https://gcc.gnu.org/PR67281
+  This bug is a mirror of the (fixed) upstream FSF bugzilla 
https://gcc.gnu.org/PR67281
  All relevant information regarding the bug and the fix can be found there.  
This bugzilla is to track backporting of the fix to the GCC 4.8, 4.9 and 5 
based compilers.
-  
- Userspace tool common name: GCC 
+ 
+ Userspace tool common name: GCC
  Userspace rpm: gcc-4.8, gcc-4.9 and gcc-5
  
  == Comment: #1
  The fix for the FSF GCC 5 branch was committed with:
  
  r228846 | bergner | 2015-10-15 11:38:47 -0500 (Thu, 15 Oct 2015) | 16
  lines
  
- Backport from mainline
- 2015-10-14  Peter Bergner  
- Torvald Riegel  
+ Backport from mainline
+ 2015-10-14  Peter Bergner  
+ Torvald Riegel  
  
- PR target/67281
- * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
- (tabort, tabortc, tabortci, tbegin, tcheck, tend,
- trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
- (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
- *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
- (tabort, tabortc, tabortci, tbegin, tcheck, tend,
- trechkpt, treclaim, tsr, ttest): New define_expands.
- * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
- __TM_FENCE__ for htm.
- * doc/extend.texi: Update documentation for htm builtins.
+ PR target/67281
+ * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
+ (tabort, tabortc, tabortci, tbegin, tcheck, tend,
+ trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
+ (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
+ *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
+ (tabort, tabortc, tabortci, tbegin, tcheck, tend,
+ trechkpt, treclaim, tsr, ttest): New define_expands.
+ * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
+ __TM_FENCE__ for htm.
+ * doc/extend.texi: Update documentation for htm builtins.
  
- == Comment: #2 
+ == Comment: #2
  The fix for the FSF GCC 4.9 branch was committed with:
  
  r228847 | bergner | 2015-10-15 11:40:14 -0500 (Thu, 15 Oct 2015) | 16
  lines
  
- Backport from mainline
- 2015-10-14  Peter Bergner  
- Torvald Riegel  
+ Backport from mainline
+ 2015-10-14  Peter Bergner  
+ Torvald Riegel  
  
- PR target/67281
- * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
- (tabort, tabortc, tabortci, tbegin, tcheck, tend,
- trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
- (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
- *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
- (tabort, tabortc, tabortci, tbegin, tcheck, tend,
- trechkpt, treclaim, tsr, ttest): New define_expands.
- * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
- __TM_FENCE__ for htm.
- * doc/extend.texi: Update documentation for htm builtins.
+ PR target/67281
+ * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
+ (tabort, tabortc, tabortci, tbegin, tcheck, tend,
+ trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
+ (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
+ *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
+ (tabort, tabortc, tabortci, tbegin, tcheck, tend,
+ trechkpt, treclaim, tsr, ttest): New define_expands.
+ * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
+ __TM_FENCE__ for htm.
+ * doc/extend.texi: Update documentation for htm builtins.
  
  == Comment: #3
  Since the FSF 4.8 branch is closed, here is a backport of the fix along with 
another
  simple HTM wrong code bug to GCC 4.8.
  
- Backport from mainline
- 2015-10-14  Peter Bergner  
- Torvald Riegel  
+ Backport from mainline
+ 2015-10-14  Peter Bergner  
+ 

[Touch-packages] [Bug 1517571] [NEW] Unity8 is crashing under UITK tests

[Zoltan Balogh]

Public bug reported:

unity8 - 8.11+15.04.2
UITK - 1.3.1717+201511171416-staging-0+1.3.1688+15.10.20151018.1~ubuntu15.04.1 
(but the stock Overlay version does the same)

Install ubuntu-ui-toolkit-autopilot on the device and run

$ phablet-test-run
ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

or on the device

$ autopilot3 run
ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

The shell will crash and restart with this output from the test tools ->

[1447868985.090179]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/mir-AHj2eT/mir-0.17.1+15.04.20151105.1/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"
Failed to create screencast
Failed to connect to server. Error was :Failed to connect to server socket: 
Connection refused
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
/bin/bash: line 1: 3796 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run 
ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page


The `apport-bug unity8` gave this ->

The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third party package 
and try again.

** Affects: unity8 (Ubuntu)
 Importance: Critical
 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/1517571

Title:
  Unity8 is crashing under UITK tests

Status in unity8 package in Ubuntu:
  New

Bug description:
  unity8 - 8.11+15.04.2
  UITK - 
1.3.1717+201511171416-staging-0+1.3.1688+15.10.20151018.1~ubuntu15.04.1 (but 
the stock Overlay version does the same)

  Install ubuntu-ui-toolkit-autopilot on the device and run

  $ phablet-test-run
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

  or on the device

  $ autopilot3 run
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

  The shell will crash and restart with this output from the test tools
  ->

  [1447868985.090179]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/mir-AHj2eT/mir-0.17.1+15.04.20151105.1/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"
  Failed to create screencast
  Failed to connect to server. Error was :Failed to connect to server socket: 
Connection refused
  g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  /bin/bash: line 1: 3796 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 
run ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

  
  The `apport-bug unity8` gave this ->

  The problem cannot be reported:
  This is not an official Ubuntu package. Please remove any third party package 
and try again.

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

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

[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update

[Pat McGowan]

marking fixed for the terminal which is pre-installed for some images

** Changed in: canonical-devices-system-image
   Status: Invalid => Fix Released

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

Title:
  Font in Terminal is incorrectly massive since recent update

Status in Canonical System Image:
  Fix Released
Status in logviewer:
  New
Status in Ubuntu Terminal App:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Last know good image: 166
  Changes on 167: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog
  Landing request for Unity8/Mir: 
https://requests.ci-train.ubuntu.com/#/ticket/564

  After updating my Nexus 4 and Krillin over the weekend I notice the
  terminal now has really huge text. Even dialling down the font size in
  the app to 8pt results in huge unusable text.

  Before:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png
  After:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png

  With the same font size setting on both.

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

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

[Touch-packages] [Bug 1517571] Re: Unity8 is crashing under UITK tests

[Michael Zanetti]

** Package changed: unity8 (Ubuntu) => qtmir (Ubuntu)

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

Title:
  Unity8 is crashing under UITK tests

Status in qtmir package in Ubuntu:
  New

Bug description:
  unity8 - 8.11+15.04.2
  UITK - 
1.3.1717+201511171416-staging-0+1.3.1688+15.10.20151018.1~ubuntu15.04.1 (but 
the stock Overlay version does the same)

  Install ubuntu-ui-toolkit-autopilot on the device and run

  $ phablet-test-run
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

  or on the device

  $ autopilot3 run
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

  The shell will crash and restart with this output from the test tools
  ->

  [1447868985.090179]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/mir-AHj2eT/mir-0.17.1+15.04.20151105.1/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"
  Failed to create screencast
  Failed to connect to server. Error was :Failed to connect to server socket: 
Connection refused
  g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  /bin/bash: line 1: 3796 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 
run ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page

  
  The `apport-bug unity8` gave this ->

  The problem cannot be reported:
  This is not an official Ubuntu package. Please remove any third party package 
and try again.

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

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

[Touch-packages] [Bug 1517107] Re: $PATH is getting clobbered when starting a container with Upstart

[Stéphane Graber]

** Changed in: lxc (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  $PATH is getting clobbered when starting a container with Upstart

Status in lxc package in Ubuntu:
  Fix Committed
Status in lxc source package in Vivid:
  Triaged
Status in lxc source package in Wily:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  I have a script using the Python3 LXC API that starts up a container.
  If I use an Upstart job to call the script, the $PATH env var is
  getting clobbered and the container fails to start.

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

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

[Touch-packages] [Bug 1517093] Re: HTM builtins aren't treated as compiler barriers on powerpc

[Matthias Klose]

this needs PR64579 from 4.8.5.


** Changed in: gcc-4.8 (Ubuntu Trusty)
   Status: Incomplete => Confirmed

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

Title:
  HTM builtins aren't treated as compiler barriers on powerpc

Status in gcc-4.8 package in Ubuntu:
  New
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Confirmed

Bug description:
  ---Problem Description---
  HTM builtins aren't treated as compiler barriers on powerpc

  Contact Information = berg...@us.ibm.com

  ---Steps to Reproduce---

   This bug is a mirror of the (fixed) upstream FSF bugzilla 
https://gcc.gnu.org/PR67281
  All relevant information regarding the bug and the fix can be found there.  
This bugzilla is to track backporting of the fix to the GCC 4.8, 4.9 and 5 
based compilers.

  Userspace tool common name: GCC
  Userspace rpm: gcc-4.8, gcc-4.9 and gcc-5

  == Comment: #1
  The fix for the FSF GCC 5 branch was committed with:

  r228846 | bergner | 2015-10-15 11:38:47 -0500 (Thu, 15 Oct 2015) | 16
  lines

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  == Comment: #2
  The fix for the FSF GCC 4.9 branch was committed with:

  r228847 | bergner | 2015-10-15 11:40:14 -0500 (Thu, 15 Oct 2015) | 16
  lines

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  == Comment: #3
  Since the FSF 4.8 branch is closed, here is a backport of the fix along with 
another
  simple HTM wrong code bug to GCC 4.8.

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  Backport from mainline:
  2015-08-03  Peter Bergner  

  * config/rs6000/htm.md (tabort.): Restrict the source operand to
  using a base register.

  Acceptance creterium: No regressions in the testsuite, and the new
  test passes.

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

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

[Touch-packages] [Bug 1497420] Please test proposed package

[Chris J Arges]

Hello Chris, or anyone else affected,

Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxcfs package in Ubuntu:
  Fix Released
Status in cgmanager source package in Vivid:
  New
Status in lxc source package in Vivid:
  Fix Committed
Status in lxcfs source package in Vivid:
  New
Status in cgmanager source package in Wily:
  New
Status in lxc source package in Wily:
  Fix Committed
Status in lxcfs source package in Wily:
  New
Status in docker package in Debian:
  Fix Released

Bug description:
  Once systemd 226 is installed in an unprivileged Debian Sid container,
  lxc-attach no-longer functions:

  % lxc-attach -n siddy
  lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to 
cgmanager_move_pid_abs_sync failed: invalid request
  lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group 
/user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope
  lxc-attach: attach.c: lxc_attach: 909 error communicating with child process

  % journalctl -u cgmanager | tail -n 1
  Sep 18 20:20:44 astoria cgmanager[1169]: cgmanager:per_ctrl_move_pid_main: 
pid 21918 (uid 1000 gid 1000) may not write to 
/run/cgmanager/fs/none,name=systemd//user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope/tasks

  
  Full walkthrough:

  % lxc-create -n siddy -t download -- -d debian -r sid -a amd64
  Using image from local cache
  Unpacking the rootfs
  ...

  % lxc-start -n siddy
  % lxc-attach -n siddy

  root@siddy:/# apt-get update
  Get:1 http://http.debian.net sid InRelease [253 kB]
  ...
  Get:7 http://http.debian.net sid/non-free amd64 Packages [91.3 kB]

  Fetched 13.2 MB in 3s (3789 kB/s) 
 
  Reading package lists... Done

  
  root@siddy:/# apt-get install systemd
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libsystemd0
  Suggested packages:
systemd-ui systemd-container
  Recommended packages:
libpam-systemd dbus
  The following packages will be upgraded:
libsystemd0 systemd
  2 upgraded, 0 newly installed, 0 to remove and 47 not upgraded.
  Need to get 3668 kB of archives.
  After this operation, 1100 kB disk space will be freed.
  Do you want to continue? [Y/n] 
  Get:1 http://http.debian.net/debian/ sid/main libsystemd0 amd64 226-2 [242 kB]
  Get:2 http://http.debian.net/debian/ sid/main systemd amd64 226-2 [3426 kB]
  ...
  Setting up systemd (226-2) ...
  Installing new version of config file 
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh ...
  Installing new version of config file 
/etc/dbus-1/system.d/org.freedesktop.login1.conf ...
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Failed to set capabilities on file `/usr/bin/systemd-detect-virt' (Invalid 
argument)
  The value of the capability argument is not permitted for a file. Or the file 
is not a regular (non-symlink) file
  Failed to execute operation: File exists
  Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 
...

  root@siddy:/# exit

  % lxc-attach -n siddy
  lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to 
cgmanager_move_pid_abs_sync failed: invalid request
  lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group 
/user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope
  lxc-attach: attach.c: lxc_attach: 909 error communicating with child process

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/lxc/lxc-net]
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 

[Touch-packages] [Bug 1436723] Please test proposed package

[Chris J Arges]

Hello Chris, or anyone else affected,

Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Regression: Nested LXC is broken on Vivid

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Committed

Bug description:
  The nested LXC functionality seems to be broken on Vivid, at least
  with the following setup:

  Vivid (Host) -> Trusty (Outer LXC) -> Trusty (Inner LXC)

  What happens:

  The Inner LXC start command fails when trying to start with: 
http://pastebin.ubuntu.com/10682639/
  ( 631 cgroup error?  100 cgroups with this name already running seems to be 
the revelant error message).

  What is expected to happen:

  The inner LXC start command is expected to succeed and result in a
  running nested container.

  Steps to reproduce:

  - Install vivid server daily, update.
  - sudo apt-get install lxc
  - sudo lxc-create -n outer -t ubuntu -- --release trusty 
--mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER
  - sudo su
  - echo 'lxc.aa_profile = lxc-container-default-with-nesting' >> 
/var/lib/lxc/outer/config
  - exit
  - sudo lxc-start -n outer
  - (SSH to outer)
  - sudo apt-get update && sudo apt-get dist-upgrade
  - sudo apt-get install lxc
  - sudo lxc-create -n inner -t ubuntu -- --release trusty 
--mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER
  - sudo lxc-start -n inner

  Fails with: http://pastebin.ubuntu.com/10682639/
  Enabling debug logs for this action yields: 
http://pastebin.ubuntu.com/10682658/

  Control: The exact same scenario works on trusty and utopic. Tested by
  spinning up server installs (from isos) in KVMs and verifying
  manually.

  Any further log or information available on request, including KVM
  images demonstrating the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 26 08:43:56 2015
  InstallationDate: Installed on 2015-03-12 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1466458] Please test proposed package

[Chris J Arges]

Hello Kevin, or anyone else affected,

Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  template 'none' doesn't work with lxc-create

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Committed
Status in lxc source package in Wily:
  Fix Committed

Bug description:
  Hi,

  The man page lxc-create(1) says that with the '-t' option to specify a
  template '"none" can be used to force lxc-create to skip rootfs
  creation'.  This does not appear to work.

  root@somehost:/var/lib/lxc# lxc-create -n test.lol -t none
  lxc_container: lxccontainer.c: get_template_path: 867 No such file or 
directory - bad template: none
  lxc_container: lxccontainer.c: lxcapi_create: 1264 bad template: none
  lxc_container: lxc_create.c: main: 271 Error creating container test.lol

  There is no template in the templates dir corresponding to the 'none'
  template.  I've looked through the upstream tarballs from releases
  0.5.0, 0.6.0, ... , 1.0.0, 1.1.0, and there is no 'none' template in
  any.  Might be just a documentation mistake, I guess.  Could be a
  missing template, or maybe 'none' has a special meaning to the lxc-
  create binary; I haven't looked yet.

  I'll dig a little further.

  I'm using lxc 1.0.7-0ubuntu0.1 on Ubuntu 14.04 .

  thanks,
  Kevin

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:56:34 2015
  InstallationDate: Installed on 2012-01-13 (1251 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to vivid on 2015-05-14 (34 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxcsyslog:

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

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

[Touch-packages] [Bug 1441068] Please test proposed package

[Chris J Arges]

Hello Martin, or anyone else affected,

Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  lxc-destroy fails on btrfs subvolumes

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Committed
Status in lxc source package in Wily:
  Fix Committed

Bug description:
  $ sudo lxc-destroy -n adt-vivid
  [sudo] password for martin: 
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var/lib
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs
  lxc_container: lxccontainer.c: container_destroy: 2050 Error destroying 
rootfs for adt-vivid
  Destroying adt-vivid failed

  This is because the container rootfs has a btrfs subvolume:

  ID 557 gen 97073 top level 266 path @srv/lxc/adt-
  vivid/rootfs/var/lib/machines

  After "sudo btrfs subvolume delete /srv/lxc/adt-
  vivid/rootfs/var/lib/machines" I can remove the container.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 11:51:51 2015
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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