date:20160204

Besides the core issue with the song list, why does the music app ask
for *artist* art when I'm in the song list?

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

Title:
  Problems and crashes with local music collection

Status in Ubuntu Music App:
  New
Status in thumbnailer package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  We have just made a change to the thumbnailer that provides a 12x
  speed-up for extracting cover art from local music files with embedded
  artwork. I'm seeing serious problems with the song list in the music
  app with this new thumbnailer. I have tried very hard to find fault
  with what the thumbnailer is doing, but I don't think we are to blame.
  I need help getting to the bottom of this; I can't debug it myself.
  But I'm fairly confident that either the music app or the
  implementation of song list widget is doing something wrong.

  I've attached an archive that contains 1000 songs, each of which has
  embedded cover art. (It's the same boring image for all of them.)

  I'm seeing the problem on Mako, rc-proposed, build 359, which includes
  the new music app, I believe.

  The modified thumbnailer is available in silo 31. Please let me know
  when you no longer need the silo, so I can release it again. (We are
  really short on silos at the moment; it might be best to grab the
  vivid arm debs from the silo.)

  To reproduce the problem, install the silo, then:

  - Kill the music app
  - Clear out the Music folder
  - untar the song collection into the Music folder
  - run "thumbnailer-admin clear" to empty the caches
  - monitor the device with top and wait for the media scanner to finish 
indexing
  - Start the music app and go to the song list

  I'm seeing really weird behavior. Initially, the song list flickers a
  few times, redrawing itself each time. After a few seconds, it settles
  down. Now start scrolling slowly. It might work for some distance but,
  after a few songs, the song list is reset to the top (first song) and
  redraws itself.

  Now scroll down again, quickly. Again, the song list resets to the
  top.

  Each time this happens, the song list is populated with a bunch of
  extra songs. Each time I scroll down, it works fine for the region
  that was cached previously, and then things blow up as soon as the
  scroll moves into the as-yet unexplored part.

  Looking at the thumbnailer, I'm not seeing anything unusual. We
  deliver thumbnails as we should. But I notice that, for some reason,
  while scrolling in the song list, the music app also sends requests
  for artist art to the thumbnailer? Why? There is no artist in sight.

  Some of the songs in the collection have an empty artist field and the
  thumbnailer returns an error for that (because asking for artist art
  without an artist doesn't make sense). But there can be other errors,
  such as errors returned by the remote server.

  It looks like the song list resetting is related to the error return
  from the thumbnailer. Every time the thumbnailer reports that
  something could not be extracted, the song list misbehaves.

  If the already-thumbnailed list gets too long, you can run

  thumbnailer-admin clear

  to empty caches. (There doesn't ever seem to be a problem in the
  region of the list that has been cached already.)

  I'm also getting occasional crashes from the music app while trying
  all this. And, every now and then, I find a message such as

  DelegateModel::cancel(): index out of range 34 0

  in the music app log. (I have no idea whether that is related.)

  I'd really appreciate if someone can look at this urgently. We want to
  land the improved thumbnailer but, while things are in this state, we
  can't. As best as I can tell, the problem might be related to
  incorrect error handling when the ThumbnailerImageResponse returns a
  request with status "invalid", either in the music app, or somewhere
  in the qml machinery.

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

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

[Touch-packages] [Bug 1542175] Re: Problems and crashes with local music collection

Great, thanks for double-checking.

The log messages are expected. They simply indicate that something
didn't work when trying to get a thumbnail. It's not clear to me who is
to blame here. As far as the thumbnailer is concerned, it receives an
error indication from the server and returns an image response
indicating that the request failed.

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

Title:
  Problems and crashes with local music collection

Status in Ubuntu Music App:
  New
Status in thumbnailer package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  We have just made a change to the thumbnailer that provides a 12x
  speed-up for extracting cover art from local music files with embedded
  artwork. I'm seeing serious problems with the song list in the music
  app with this new thumbnailer. I have tried very hard to find fault
  with what the thumbnailer is doing, but I don't think we are to blame.
  I need help getting to the bottom of this; I can't debug it myself.
  But I'm fairly confident that either the music app or the
  implementation of song list widget is doing something wrong.

  I've attached an archive that contains 1000 songs, each of which has
  embedded cover art. (It's the same boring image for all of them.)

  I'm seeing the problem on Mako, rc-proposed, build 359, which includes
  the new music app, I believe.

  The modified thumbnailer is available in silo 31. Please let me know
  when you no longer need the silo, so I can release it again. (We are
  really short on silos at the moment; it might be best to grab the
  vivid arm debs from the silo.)

  To reproduce the problem, install the silo, then:

  - Kill the music app
  - Clear out the Music folder
  - untar the song collection into the Music folder
  - run "thumbnailer-admin clear" to empty the caches
  - monitor the device with top and wait for the media scanner to finish 
indexing
  - Start the music app and go to the song list

  I'm seeing really weird behavior. Initially, the song list flickers a
  few times, redrawing itself each time. After a few seconds, it settles
  down. Now start scrolling slowly. It might work for some distance but,
  after a few songs, the song list is reset to the top (first song) and
  redraws itself.

  Now scroll down again, quickly. Again, the song list resets to the
  top.

  Each time this happens, the song list is populated with a bunch of
  extra songs. Each time I scroll down, it works fine for the region
  that was cached previously, and then things blow up as soon as the
  scroll moves into the as-yet unexplored part.

  Looking at the thumbnailer, I'm not seeing anything unusual. We
  deliver thumbnails as we should. But I notice that, for some reason,
  while scrolling in the song list, the music app also sends requests
  for artist art to the thumbnailer? Why? There is no artist in sight.

  Some of the songs in the collection have an empty artist field and the
  thumbnailer returns an error for that (because asking for artist art
  without an artist doesn't make sense). But there can be other errors,
  such as errors returned by the remote server.

  It looks like the song list resetting is related to the error return
  from the thumbnailer. Every time the thumbnailer reports that
  something could not be extracted, the song list misbehaves.

  If the already-thumbnailed list gets too long, you can run

  thumbnailer-admin clear

  to empty caches. (There doesn't ever seem to be a problem in the
  region of the list that has been cached already.)

  I'm also getting occasional crashes from the music app while trying
  all this. And, every now and then, I find a message such as

  DelegateModel::cancel(): index out of range 34 0

  in the music app log. (I have no idea whether that is related.)

  I'd really appreciate if someone can look at this urgently. We want to
  land the improved thumbnailer but, while things are in this state, we
  can't. As best as I can tell, the problem might be related to
  incorrect error handling when the ThumbnailerImageResponse returns a
  request with status "invalid", either in the music app, or somewhere
  in the qml machinery.

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

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

[Touch-packages] [Bug 1542175] Re: Problems and crashes with local music collection

2016-02-04 Thread Victor Thompson

I can reproduce what you are seeing.

I see a lot of the following in the log:

Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus error: 
DBusInterface::GetArtistArt(): /: unity::InvalidArgumentException: 
Thumbnailer::get_artist_art(): artist is empty
ThumbnailerImageResponse::dbusCallFinished(): D-Bus error:  "Thumbnailer: 
RequestImpl::dbusCallFinished(): D-Bus error:DBusInterface::GetArtistArt(): /: 
unity::InvalidArgumentException: Thumbnailer::get_artist_art(): artist is empty

I also see the refreshes happening in views where the artist name isn't
blank. For instance, it refreshes/redraws when I click on a valid Artist
in the Artists tab. This would seem to suggest that it isn't just one
component misbehaving.

When I run with just my modest music library I also experience the same
redraw in the Songs tab, so I suspect it'd be problematic for most
users.

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

Title:
  Problems and crashes with local music collection

Status in Ubuntu Music App:
  New
Status in thumbnailer package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  We have just made a change to the thumbnailer that provides a 12x
  speed-up for extracting cover art from local music files with embedded
  artwork. I'm seeing serious problems with the song list in the music
  app with this new thumbnailer. I have tried very hard to find fault
  with what the thumbnailer is doing, but I don't think we are to blame.
  I need help getting to the bottom of this; I can't debug it myself.
  But I'm fairly confident that either the music app or the
  implementation of song list widget is doing something wrong.

  I've attached an archive that contains 1000 songs, each of which has
  embedded cover art. (It's the same boring image for all of them.)

  I'm seeing the problem on Mako, rc-proposed, build 359, which includes
  the new music app, I believe.

  The modified thumbnailer is available in silo 31. Please let me know
  when you no longer need the silo, so I can release it again. (We are
  really short on silos at the moment; it might be best to grab the
  vivid arm debs from the silo.)

  To reproduce the problem, install the silo, then:

  - Kill the music app
  - Clear out the Music folder
  - untar the song collection into the Music folder
  - run "thumbnailer-admin clear" to empty the caches
  - monitor the device with top and wait for the media scanner to finish 
indexing
  - Start the music app and go to the song list

  I'm seeing really weird behavior. Initially, the song list flickers a
  few times, redrawing itself each time. After a few seconds, it settles
  down. Now start scrolling slowly. It might work for some distance but,
  after a few songs, the song list is reset to the top (first song) and
  redraws itself.

  Now scroll down again, quickly. Again, the song list resets to the
  top.

  Each time this happens, the song list is populated with a bunch of
  extra songs. Each time I scroll down, it works fine for the region
  that was cached previously, and then things blow up as soon as the
  scroll moves into the as-yet unexplored part.

  Looking at the thumbnailer, I'm not seeing anything unusual. We
  deliver thumbnails as we should. But I notice that, for some reason,
  while scrolling in the song list, the music app also sends requests
  for artist art to the thumbnailer? Why? There is no artist in sight.

  Some of the songs in the collection have an empty artist field and the
  thumbnailer returns an error for that (because asking for artist art
  without an artist doesn't make sense). But there can be other errors,
  such as errors returned by the remote server.

  It looks like the song list resetting is related to the error return
  from the thumbnailer. Every time the thumbnailer reports that
  something could not be extracted, the song list misbehaves.

  If the already-thumbnailed list gets too long, you can run

  thumbnailer-admin clear

  to empty caches. (There doesn't ever seem to be a problem in the
  region of the list that has been cached already.)

  I'm also getting occasional crashes from the music app while trying
  all this. And, every now and then, I find a message such as

  DelegateModel::cancel(): index out of range 34 0

  in the music app log. (I have no idea whether that is related.)

  I'd really appreciate if someone can look at this urgently. We want to
  land the improved thumbnailer but, while things are in this state, we
  can't. As best as I can tell, the problem might be related to
  incorrect error handling when the ThumbnailerImageResponse returns a
  request with status "invalid", either in the music app, or somewhere
  in the qml machinery.

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

-- 
Mailing list: htt

[Touch-packages] [Bug 1542083] Re: broken video clip has extremely blurry icon when navigating to the camera roll

Ah, so *that's* what a broken video is :-)

I guess the fallback image that is returned is just really low quality.
We have branch waiting to be merged for this:

https://code.launchpad.net/~jamesh/thumbnailer/no-fallback-
albumart/+merge/263216

Once that merges, each app and scope can provide its own fallback art.

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

Title:
  broken video clip has extremely blurry icon when navigating to the
  camera roll

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

Bug description:
  from design:
  If for some reason thumbnail was not able to be generated after taking a 
video, the placeholder thumbnail is very blurry. Guessing that thumbnailer is 
not providing a thumbnail for this at needed size requested.

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

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

[Touch-packages] [Bug 1542083] Re: broken video clip has extremely blurry icon when navigating to the camera roll

Result above ^

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

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

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

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

Title:
  broken video clip has extremely blurry icon when navigating to the
  camera roll

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

Bug description:
  from design:
  If for some reason thumbnail was not able to be generated after taking a 
video, the placeholder thumbnail is very blurry. Guessing that thumbnailer is 
not providing a thumbnail for this at needed size requested.

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

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

[Touch-packages] [Bug 1542094] Re: [camera] LED & Flash toggles are shown even when no LED or Flash present on hardware

Can't test without Freiza but it's clear that the app knows how to that:
test with BQ Aquaris E4.5 with front camera: no flash option is
displayed.

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

Title:
  [camera] LED & Flash toggles are shown even when no LED or Flash
  present on hardware

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

Bug description:
  could be Freiza specific.

  We shouldn't be showing controls for flash, torchlight if they are not
  present on hardware, but apparently we are (according to design)

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

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

[Touch-packages] [Bug 1542083] Re: broken video clip has extremely blurry icon when navigating to the camera roll

** Attachment added: "example1.png"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542083/+attachment/4564314/+files/example1.png

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

Title:
  broken video clip has extremely blurry icon when navigating to the
  camera roll

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

Bug description:
  from design:
  If for some reason thumbnail was not able to be generated after taking a 
video, the placeholder thumbnail is very blurry. Guessing that thumbnailer is 
not providing a thumbnail for this at needed size requested.

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

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

[Touch-packages] [Bug 1542083] Re: broken video clip has extremely blurry icon when navigating to the camera roll

No need to go through all this debugging: just launch the camera, go to
the photo roll and make sure a broken video is available.

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

Title:
  broken video clip has extremely blurry icon when navigating to the
  camera roll

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

Bug description:
  from design:
  If for some reason thumbnail was not able to be generated after taking a 
video, the placeholder thumbnail is very blurry. Guessing that thumbnailer is 
not providing a thumbnail for this at needed size requested.

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

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

[Touch-packages] [Bug 1542077] Re: don't allow focus ring outside of viewfinder

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

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

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

Title:
  don't allow focus ring outside of viewfinder

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

Bug description:
  on windowed mode, clicking outside the 40/50GU view still focusses the
  focus; tapping black space shouldn’t trigger focussing

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

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

[Touch-packages] [Bug 1542075] Re: viewfinder should re-size to fit window

1) is a bug lower in the stack
2) you can't fill the entire available space without cropping the viewfinder
3) yes we should do that, however it limits the photo roll's possible sizes, 
which may be an acceptable tradeoff
4) maybe

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

Title:
  viewfinder should re-size to fit window

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

Bug description:
  in windowed mode, the viewfinder is currently fills the screen in the
  vertical orientation. If the window is made smaller the controls
  incorrectly rotate like the app thinks it's in landscape mode and
  bottom edge moves to the right.

  Lets discuss what to do here, but some options:

  1) resizing the window shouldn't change where the controls are located or the 
orientation
  2) resizing should make the viewfinder fill the available space. Should it 
use the largest vertical or horizontal dimension, or be fixed to the physical 
orientation of the phone?
  3) Should we not allow window resizing and instead lock the window size to 
the actual size of the viewfinder?
  4) If the phone is rotated, should the window size automatically change to 
reflect the phone orientation?

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

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

[Touch-packages] [Bug 1542081] Re: don't allow navigation while timer is going

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

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

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

Title:
  don't allow navigation while timer is going

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

Bug description:
  from design:
  shouldn’t be able to navigate to camera roll while timer is triggered; only 
actions that should be within the camera app available is cancelling the timer

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

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

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

2016-02-04 Thread Timo Jyrinki

As I started testing on my main daily phone, I noticed that there is
trouble with the Today scope when using the silo 32. It has problems
obtaining data / refreshing itself. It seems reproduable, but it's also
the only scope that seems to have problems. Maybe it's doing something
peculiar workarounding the existing networking problems?

Such a regression would of course not be acceptable. Reproducing of the
problem would be welcome.

** Also affects: today-scope
   Importance: Undecided
   Status: New

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

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  In Progress
Status in Today Scope:
  New
Status in connectivity-api package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

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

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

[Touch-packages] [Bug 1542087] Re: [camera] camera settings should be easier to dismiss

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

Title:
  [camera] camera settings should be easier to dismiss

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

Bug description:
  from design:
  any selected action in the bottom edge can not be dismissed by clicking in 
the bottom edge area; Can’t dismiss options selector (flash on/off etc) unless 
user clicks in upper 2/3s of screen (i.e. outside of where bottom edge area is) 
- when bottom edge is shown

  After discussing with Ben, the following should close the camera controls 
panel:
  1) clicking anywhere inside the component that shows the camera controls but 
not on a button
  2) clicking outside of the component

  So basically clicking anywhere on the screen other than on one of the
  control buttons should close the bottom edge

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

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

[Touch-packages] [Bug 1539068] Re: My Music scope no longer shows "get started!"

USB seems to be really flaky. I’ve just sent a question to the phablet
list about this. Thanks for confirming!

The weird thing is that I can’t get it to work at all, even with my one
known good cable. It always says that it failed to connect :(

It would be good to get reports from other people as to how well MTP
works for them on a Mac. If i'm not the only one with this problem, we
might have to come up with something better.

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

Title:
  My Music scope no longer shows "get started!"

Status in Canonical System Image:
  Fix Committed
Status in unity-scope-mediascanner package in Ubuntu:
  Fix Released

Bug description:
  The My Music scope no longer shows the "get started!" splash screen.
  The "My Videos" scope still seems to work though.

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

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

[Touch-packages] [Bug 1542088] Re: [camera] bottom edge hint should be clickable by mouse to activate

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

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

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

Title:
  [camera] bottom edge hint should be clickable by mouse to activate

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

Bug description:
  from design:
  behavior on touch is correct - tapping the bottom edge hint should animate 
the hint to reveal something is beneath

  behavior with mouse connected is not correct. Clicking the hint with
  mouse should activate the bottom edge panel but it does not. Just
  makes it wiggle.

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

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

[Touch-packages] [Bug 1542175] Re: Problems and crashes with local music collection

Adding thumbnailer and unity8-dash because I don't know which is the
guilty party...

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

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

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

Title:
  Problems and crashes with local music collection

Status in Ubuntu Music App:
  New
Status in thumbnailer package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  We have just made a change to the thumbnailer that provides a 12x
  speed-up for extracting cover art from local music files with embedded
  artwork. I'm seeing serious problems with the song list in the music
  app with this new thumbnailer. I have tried very hard to find fault
  with what the thumbnailer is doing, but I don't think we are to blame.
  I need help getting to the bottom of this; I can't debug it myself.
  But I'm fairly confident that either the music app or the
  implementation of song list widget is doing something wrong.

  I've attached an archive that contains 1000 songs, each of which has
  embedded cover art. (It's the same boring image for all of them.)

  I'm seeing the problem on Mako, rc-proposed, build 359, which includes
  the new music app, I believe.

  The modified thumbnailer is available in silo 31. Please let me know
  when you no longer need the silo, so I can release it again. (We are
  really short on silos at the moment; it might be best to grab the
  vivid arm debs from the silo.)

  To reproduce the problem, install the silo, then:

  - Kill the music app
  - Clear out the Music folder
  - untar the song collection into the Music folder
  - run "thumbnailer-admin clear" to empty the caches
  - monitor the device with top and wait for the media scanner to finish 
indexing
  - Start the music app and go to the song list

  I'm seeing really weird behavior. Initially, the song list flickers a
  few times, redrawing itself each time. After a few seconds, it settles
  down. Now start scrolling slowly. It might work for some distance but,
  after a few songs, the song list is reset to the top (first song) and
  redraws itself.

  Now scroll down again, quickly. Again, the song list resets to the
  top.

  Each time this happens, the song list is populated with a bunch of
  extra songs. Each time I scroll down, it works fine for the region
  that was cached previously, and then things blow up as soon as the
  scroll moves into the as-yet unexplored part.

  Looking at the thumbnailer, I'm not seeing anything unusual. We
  deliver thumbnails as we should. But I notice that, for some reason,
  while scrolling in the song list, the music app also sends requests
  for artist art to the thumbnailer? Why? There is no artist in sight.

  Some of the songs in the collection have an empty artist field and the
  thumbnailer returns an error for that (because asking for artist art
  without an artist doesn't make sense). But there can be other errors,
  such as errors returned by the remote server.

  It looks like the song list resetting is related to the error return
  from the thumbnailer. Every time the thumbnailer reports that
  something could not be extracted, the song list misbehaves.

  If the already-thumbnailed list gets too long, you can run

  thumbnailer-admin clear

  to empty caches. (There doesn't ever seem to be a problem in the
  region of the list that has been cached already.)

  I'm also getting occasional crashes from the music app while trying
  all this. And, every now and then, I find a message such as

  DelegateModel::cancel(): index out of range 34 0

  in the music app log. (I have no idea whether that is related.)

  I'd really appreciate if someone can look at this urgently. We want to
  land the improved thumbnailer but, while things are in this state, we
  can't. As best as I can tell, the problem might be related to
  incorrect error handling when the ThumbnailerImageResponse returns a
  request with status "invalid", either in the music app, or somewhere
  in the qml machinery.

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

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

[Touch-packages] [Bug 1539612] Re: Is not possible start camera, screen freezing after OTA9

2016-02-04 Thread Miroslav Kotora

Hi, 
It is ok.
I restored the service settings, reset everything.

Thanks you :)

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

Title:
  Is not possible start camera, screen freezing after OTA9

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

Bug description:
  it is not possible to make no images, screen freezes, the camera will
  not start

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

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

[Touch-packages] [Bug 1522316] Re: Icons are too big

2016-02-04 Thread Khurshid Alam

"NAUTILUS_CANVAS_ICON_SIZE_STANDARD  48" "STANDARD_ICON_GRID_WIDTH 155"
makes it exactly same as 3.14 IMHO. Not sure why Sebastien thinks its
too much spacious.

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

Title:
  Icons are too big

Status in Nautilus:
  Incomplete
Status in nautilus package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  On xenial the icons in nautilus (also on the Desktop) are too big.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  3 09:37:55 2015
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'date_modified']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2015-04-30 (216 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1542163] [NEW] flight mode indicator shown when not in flight mode

Public bug reported:

I was tinkering with flight mode and wifi on/off to test something. I'm
sorry, but I can't recall the steps I took to get the phone into this
state (Mako, rc-proposed, image 359).

The device is, as a matter of fact, *not* in flight mode (I can browse
web). Both wifi and flight mode icon are showing (see attached screen
shot).

When cross-checking with the settings app, it also shows the device in
flight mode (toggle is shown green). However, in the attached indicator
screen shot, flight mode is shown as off, but the airoplane icon is
visible as well (which should be impossible).

I tried turning flight mode off in the settings app. I can do this but
the aeroplane icon stays put, and when I pull down on the indicator,
flight mode shown as "on" there, even though the settings app toggle
shows "off".

When I use the toggle in the settings app to turn flight mode off and
wait about 20 seconds or so, the toggle turns back to "on" by itself,
without me touching the phone.

Also, with flight mode shown as "on" in both settings app and the pull-
down, I can pull down on the indicators and turn flight mode off. But,
when I swipe up again and look at the settings up, flight mode is still
shown as "on" there.

Now I turn flight mode off in the settings app and wait a while, and the
toggle moves by itself back to "on".

Cross-checking with the browser, I can still browse the web. Switching
to the settings app, it shows flight mode "on" but, when I pull down on
the indicator, it shows flight mode as "off".

The aeroplane icon is visible permanently while all this is going on.

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

** Attachment added: "screenshot20160205_151954855.png"

https://bugs.launchpad.net/bugs/1542163/+attachment/4564310/+files/screenshot20160205_151954855.png

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

Title:
flight mode indicator shown when not in flight mode

Status in indicator-network package in Ubuntu:
New

Bug description:
I was tinkering with flight mode and wifi on/off to test something.
I'm sorry, but I can't recall the steps I took to get the phone into
this state (Mako, rc-proposed, image 359).

The device is, as a matter of fact, *not* in flight mode (I can browse
web). Both wifi and flight mode icon are showing (see attached screen
shot).

When cross-checking with the settings app, it also shows the device in
flight mode (toggle is shown green). However, in the attached
indicator screen shot, flight mode is shown as off, but the airoplane
icon is visible as well (which should be impossible).

When I use the toggle in the settings app to turn flight mode off and
wait about 20 seconds or so, the toggle turns back to "on" by itself,
without me touching the phone.

Also, with flight mode shown as "on" in both settings app and the
pull-down, I can pull down on the indicators and turn flight mode off.
But, when I swipe up again and look at the settings up, flight mode is
still shown as "on" there.

Now I turn flight mode off in the settings app and wait a while, and
the toggle moves by itself back to "on".

Cross-checking with the browser, I can still browse the web. Switching
to the settings app, it shows flight mode "on" but, when I pull down
on the indicator, it shows flight mode as "off".

The aeroplane icon is visible permanently while all this is going on.

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

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

[Touch-packages] [Bug 1371403] Re: [PATCH] Please disable USB autosuspend for Avocent SC Secure KVM

2016-02-04 Thread Bryce Harrington

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

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

Title:
  [PATCH] Please disable USB autosuspend for Avocent SC Secure KVM

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Utopic:
  Won't Fix

Bug description:
  My mouse becomes temporarily become unresponsive to drags and clicks,
  until I right-click or give keyboard input, when it's been idle for a
  few seconds.  The same thing affects the keyboard.  In some cases the
  mouse cursor jumps back to the center of the screen.

  The mouse and keyboard are connected to a number of different
  computers via an 8-port Avocent SC Secure KVM.  When the mouse and/or
  keyboard are directly attached to one of the PCs, there is no problem.
  I've tested with different keyboards and mice as well, and they're
  similarly messed up.

  Only the computers running Ubuntu 14.04 are affected.  Two of the computers 
are identical hardware, differing only in Ubuntu versions - the 14.04 one is 
affected but the one with 13.04 is not.  I also have a machine with 12.04 on it 
connected to the KVM which is fine.
  I first noticed the problem when I upgraded to 13.10.

  In powertop I notice that autosuspend is enabled for the Avocent.  If
  I switch that off, then the problem disappears completely.  I can also
  prevent it by issuing:

    echo 'on' > '/sys/bus/usb/devices/3-10/power/control';

  where 3-10 is the Avocent (the number is different on each of my
  systems).

  I notice in 42-usb-hid-pm.rules there is a rule for Avocent devices:

    # Catch-all for Avocent HID devices. Keyed off interface in order to only
    # trigger on HID class devices.
    ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0624", 
ATTR{bInterfaceClass}=="03", TEST=="../power/control", 
ATTR{../power/control}="auto"

  However my KVM device doesn't appear to have a bInterfaceClass
  defined.

  In any case, the following udev rule corrects the problem for me:

  ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0624",
  ATTR{idProduct}=="0013", ATTR{product}=="SC Secure KVM",
  TEST=="power/control", ATTR{power/control}:="on"

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

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

[Touch-packages] [Bug 1539068] Re: My Music scope no longer shows "get started!"

2016-02-04 Thread Marcus Tomlinson

@Michi, to answer your earlier question: Yes AFT does work for me on
Mac. Although, I did need to unplug and plug the device in about 3 times
for it to recognise it.

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

Title:
  My Music scope no longer shows "get started!"

Status in Canonical System Image:
  Fix Committed
Status in unity-scope-mediascanner package in Ubuntu:
  Fix Released

Bug description:
  The My Music scope no longer shows the "get started!" splash screen.
  The "My Videos" scope still seems to work though.

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

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

[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2016-02-04 Thread SoftCoder

I keep seeing this error in 16.04 via ossec, and continuously:

OSSEC HIDS Notification.
2016 Feb 04 20:30:02

Received From: softcoder-linux->/var/log/syslog
Rule: 1002 fired (level 2) -> "Unknown problem somewhere in the system."
Portion of the log(s):

Feb  4 20:30:02 softcoder-linux colord[1096]: (colord:1096): Cd-WARNING
**: failed to get session [pid 26812]: No such device or address


 --END OF NOTIFICATION

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1540753] Re: Video thumbnails don't go into full-size cache

** Changed in: thumbnailer (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

Title:
  Video thumbnails don't go into full-size cache

Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Video thumbnails from vs-thumb should go into the full-size cache, but
  they don't. The logic for read() is broken, we need to add the full-
  size image, possibly down-scaled, there.

  Best way to deal with this is to factor out the logic for adding stuff
  to the full-size cache and then call that from both places?

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

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

[Touch-packages] [Bug 1542140] [NEW] scope doesn't handle exception during start()

Public bug reported:

I just ran up the scope while the mediascanner was still indexing a
large collection I had dropped into the music folder.

When I switched to the mediascanner scope, I ended up with a completely
blank screen, nothing shown at all. In registry log, I found this:

scoperunner: unity::ResourceException: Scope mediascanner-music: exception from 
start():
Tried to open a db with schema versino -1, while supported version is 10.

Trying to refresh didn't do anything. The bouncing bar showed up for a
while, and I was still left with a blank screen.

It seems that the scope eventually recovers. I left the phone sitting
there for a while and, next time I glanced at it, the scope had
populated the screen.

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

** Affects: unity-scope-mediascanner (Ubuntu)
 Importance: Undecided
 Status: New

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

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

Title:
  scope doesn't handle exception during start()

Status in mediascanner2 package in Ubuntu:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  New

Bug description:
  I just ran up the scope while the mediascanner was still indexing a
  large collection I had dropped into the music folder.

  When I switched to the mediascanner scope, I ended up with a
  completely blank screen, nothing shown at all. In registry log, I
  found this:

  scoperunner: unity::ResourceException: Scope mediascanner-music: exception 
from start():
  Tried to open a db with schema versino -1, while supported version is 10.

  Trying to refresh didn't do anything. The bouncing bar showed up for a
  while, and I was still left with a blank screen.

  It seems that the scope eventually recovers. I left the phone sitting
  there for a while and, next time I glanced at it, the scope had
  populated the screen.

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

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

[Touch-packages] [Bug 1540876] Re: Not all results recieved when there is a lot of them (>=3000?)

I had a look at the high water mark for the outgoing socket, and it is
at the default of zero, which, according to the zmq doc, means "no
limit". This will need a closer look to figure out why messages are
being lost.

** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

Title:
  Not all results recieved when there is a lot of them (>=3000?)

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  It looks like ZMQ high water-mark limits the number of results that
  can succesfuly be received by a client to something around 2000; this
  may depend on the result size and delays between pushes though. With
  3000 results in my test code I was receiving approximately 1900, the
  remainder was dropped on the floor. While these numbers are probably
  more than we will ever need, it may be worth looking into it. Perhaps
  ZMQ queue size can be increased, also a meaningful error in the logs
  about hitting such cases would be nice (if possible at all).

  I'll add a pointer to a sample test case from unity-scopes-shell at a
  later time, please contact me if I forget to do so ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1540876/+subscriptions

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

[Touch-packages] [Bug 1387908] Re: [udev] FIDO u2f security keys should be supported out of the box

2016-02-04 Thread Dimitri John Ledkov

Hi,

On ubuntu we ship libu2f-host as a package. Thus:

$ apt install libu2f-host0

"Solves" the problem. However, I do think it's not as user friendly as
it could be. And I'll attempt to get it included in ubuntu by default.

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  [udev] FIDO u2f security keys should be supported out of the box

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Utopic:
  Confirmed
Status in systemd source package in Vivid:
  Confirmed

Bug description:
  FIDO u2f is an emerging standard for public-private cryptography based
  2nd factor authentication, which improves on OTP by mitigating
  phishing, man-in-the-middle attacks and reply attacks.

  Google Chrome supports u2f devices which are now widely available from
  Yubico (new premium neo Yubikeys and Security keys).

  However, udev rules are required to setup permissions to allow the
  web-browsers which are running as regular users to access the devices
  in question.

  E.g.:

  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev",
  ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120"

  Something like that should be enabled by default, however probably not
  encode on the vendor/productid as other vendors will also make u2f
  devices.

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

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

[Touch-packages] [Bug 1542086] Re: /usr/bin/webapp-container:11:oxide:::oxide::ScriptMessageContentsHelper::OnReceiveScriptMessage:oxide::ScriptMessageContentsHelper::OnMessageReceived:content::WebCon

2016-02-04 Thread Alexandre Abreu

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

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

Title:
  /usr/bin/webapp-
  
container:11:oxide:::oxide::ScriptMessageContentsHelper::OnReceiveScriptMessage:oxide::ScriptMessageContentsHelper::OnMessageReceived:content::WebContentsImpl::OnMessageReceived:content::RenderFrameHostImpl::OnMessageReceived

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+15.10.20150929-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/cbd6b71bd915a6ff30ae589f54a7f1bf30360cd8
  contains more details.

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

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

[Touch-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

2016-02-04 Thread Claudio Alejandro Sanhueza Lobos

Fixed after following this:

http://askubuntu.com/questions/727127/last-upgrade-crashes-network-
manager-no-internet-connection-no-applet

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

Title:
network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Trusty:
Fix Committed

Bug description:
[Triage Notes]

This regression is caused by a libnl proposed update tracked in bug
1511735. It has not been released as an update, only proposed as an
update for early testing. If you volunteered to test proposed updates,
then thank you. Your care and attention will stop this regression from
hitting ordinary users, and we appreciate your contribution to Ubuntu.

If you are not aware that you volunteered to test proposed updates,
then please be aware that your system is configured to do so. In this
case, you probably should turn this off. I'd appreciate if someone
could explain how to do this in the comments.

[Impact]

* NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200
libnl-route-3-200) and when libnl is updated to proposed
3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM
validation packets.

This affects the 0.98 release of NetworkManager and has already
been fixed in newer releases.

* Backporting fixes from upstream release is required to prevent
NetworkManager from faulting which breaks networking on most
Desktop releases.

* All patches applied are already accepted upstream and newer Ubuntu
releases are not affected.

* Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating
libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing.

[Test Case]

* Reproduce crash test:
1. Download 14.04.03 Desktop iso, amd64
2. Launched in a VM, run from iso
3. In terminal, enable proposed
4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
5. sudo restart network-manager
# note the nm-applet disappears as NM has now crashed, no network
conn.
6. dmesg to confirm network-manager crash
7. sudo dpkg --install
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
8. sudo start network-manager
# nm-applet reappears, network connectivity restored

* Successful upgrade test:
1. Download 14.04.03 Desktop iso, amd64
2. Launched in a VM, run from iso
3. In a terminal, sudo dpkg --install
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
4. sudo restart network-manager # NM still runs, no crash, net up
5. enable trusty-proposed in /etc/apt/sources.list
6. sudo apt-get update
7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
8. sudo restart network-manager # NM still runs, no crash, net up.

[Regression Potential]

* NetworkManager is a highly visible package, so testing NetworkManager
functionality is critical. The patch does address the crash specificly
introduced by the updated libnl SRU.

* We need to ensure that users have installed this NetworkManager
update before installing libnl3 update (special phasing needed).

[Original Description]
Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

After installing updated libnl3 and restarting networkmanager, NM
crashes with:

/var/log/syslog shows:
init: network-manager main process (1057) killed by SEGV signal
init: network-manager main process ended, respawning
init: network-manager main process (1065) killed by SEGV signal
init: network-manager respawning too fast, stopped

The bug has been fixed in upstream 0.98 with these patches:

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

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

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

[Touch-packages] [Bug 1541532] Re: migrate UTC setting from /etc/default/rcS to adjtime

This bug was fixed in the package lupin - 0.57

---
lupin (0.57) xenial; urgency=medium

  * Set UTC or LOCAL in /etc/adjtime for systemd (based on change by Roger
Leigh in clock-setup 0.111; LP: #1541532).

 -- Colin Watson   Thu, 04 Feb 2016 23:12:04 +

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

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

Title:
  migrate UTC setting from  /etc/default/rcS to adjtime

Status in installation-guide package in Ubuntu:
  Fix Released
Status in lupin package in Ubuntu:
  Fix Released
Status in mbr package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in sysvinit package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in mbr package in Debian:
  New

Bug description:
  This has been an Ubuntu delta in systemd and perhaps other Ubuntu
  packages for a long time. But /etc/default/rcS is a SysV-ism, and no
  other setting in there is relevant. Steps:

   * Bump the version guard in systemd.conf for migrating the actual setting 
(keep until 16.04 LTS)
   * Ensure that we only look at the LOCAL setting during boot, and do no 
actual drift correction at boot, as the kernel does that by itself.
   * grep the archive for software which might directly look at or even write 
that file (Ubuntu specific config tools and the like).

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

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

[Touch-packages] [Bug 1542080] Re: Needs tar/xattr support to build docker

2016-02-04 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Needs tar/xattr support to build docker

Status in gccgo-4.9 package in Ubuntu:
  Confirmed
Status in gccgo-4.9 source package in Trusty:
  Triaged

Bug description:
  [Impact]
  docker.io does not build on archs that require gccgo.

  [Test Case]
  Build docker.io in trusty on an arch that requires gccgo. I used arm64.
  (Also need patch in LP: #1510288)

  [Regression Risk]
  This is an upstream patch that applies cleanly (other than file tree 
rearrangements), and it is adding new functionality.

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

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

[Touch-packages] [Bug 1541532] Re: migrate UTC setting from /etc/default/rcS to adjtime

2016-02-04 Thread Bug Watch Updater

** Changed in: mbr (Debian)
   Status: Unknown => New

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

Title:
  migrate UTC setting from  /etc/default/rcS to adjtime

Status in installation-guide package in Ubuntu:
  Fix Released
Status in lupin package in Ubuntu:
  New
Status in mbr package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in sysvinit package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in mbr package in Debian:
  New

Bug description:
  This has been an Ubuntu delta in systemd and perhaps other Ubuntu
  packages for a long time. But /etc/default/rcS is a SysV-ism, and no
  other setting in there is relevant. Steps:

   * Bump the version guard in systemd.conf for migrating the actual setting 
(keep until 16.04 LTS)
   * Ensure that we only look at the LOCAL setting during boot, and do no 
actual drift correction at boot, as the kernel does that by itself.
   * grep the archive for software which might directly look at or even write 
that file (Ubuntu specific config tools and the like).

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

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

[Touch-packages] [Bug 1502282] Re: "unknown" connectivity status problematic

Here is the code in QueryMetadata that set this:

it = var.find("internet_connectivity");
if (it != var.end())
{
internet_connectivity_ = it->second.get_bool() ? 
QueryMetadata::Connected : QueryMetadata::Disconnected;
}
else
{
internet_connectivity_ = QueryMetadata::Unknown;
}

So, the only way for this not to be set is if the status isn't passed in
by the caller.

ActionMetadata and PerformAction derive from QueryMetadata, so they get
this setting for free. At least going by this brief look, I'd say that
the shell doesn't set the status for activation and preview.

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

Title:
  "unknown" connectivity status problematic

Status in The Savilerow project:
  New
Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  metadata provides a scope a network connectivity status enum with three 
possible states:
  * connected
  * disconnected
  * unknown

  Sometimes unknown is the current state. This is quite problematic
  because in general a scopes that queries the network (that is, most
  scopes) need to know whether there is network or is not network and
  depending on this either make the network queries or display an error
  message.

  A status of unknown connectivity leaves the scope with no valid option:
  * the scope could assume the network is down and provide the user an error 
message. But often the network is not actually down, so this interrupts the 
user's flow unnecessarily
  *  the scope could assume the network is up, but this is dangerous if it is 
not up

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

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

[Touch-packages] [Bug 1404302] Re: liblttng-ust0 Error opening shm /lttng-ust-wait-5

2016-02-04 Thread Gerry Boland

===test2.qml
import QtQuick 2.3
import Ubuntu.Content 0.1

Rectangle { color: "pink" }

===test.qml==
import QtQuick 2.0

Rectangle {
color: "red"
Loader { id: loader; anchors.fill: parent; }
MouseArea { 
anchors.fill: parent
onClicked: loader.source = "test2.qml"
}
}

Run:

LTTNG_UST_DEBUG=1 aa-exec-click -p com.ubuntu.camera_camera_3.0.0.611 --
qmlscene test.qml --desktop_file_hint=dialer-app

which enables extra LTTng output. I get some from Mir at startup - still
no LTTng warning messages printing. But then I hit the screen, to load
Ubuntu.Content plugin. I then get messages that ubuntu-app-launch
registers tracepoints, and the warning messages start repeating.

My log here: http://pastebin.ubuntu.com/14883688/

Maybe UAL imported as library is doing it? I don't know yet

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

Title:
  liblttng-ust0 Error opening shm /lttng-ust-wait-5

Status in Client Developer Experience:
  Confirmed
Status in platform-api:
  New
Status in content-hub package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Confined apps don't have access to this and continuously produce this
  error message in stderr:

  libust[31283/31285]: Error: Error opening shm /lttng-ust-wait-5 (in
  get_wait_shm() at lttng-ust-comm.c:958)

  
  This is printed to the application's log about once every other second and 
makes it hard to read the application's own debug output. For a better app 
developer experience this message should be silenced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1404302/+subscriptions

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

[Touch-packages] [Bug 1502282] Re: "unknown" connectivity status problematic

You are always free to ignore the network status. It was moved in mainly
as a convenience feature, to allow a scope to immediately notice if, for
example, the device is in flight mode. Given the problems with
NetworkAccessManager (still not completely resolved), I would probably
interpret "unknown" to mean "available" and go ahead, and only pay
attention if the status indicates "network down".

The issue with ActionMetadata and PerformAction not receiving the
network status needs looking at.

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

Title:
  "unknown" connectivity status problematic

Status in The Savilerow project:
  New
Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  metadata provides a scope a network connectivity status enum with three 
possible states:
  * connected
  * disconnected
  * unknown

  Sometimes unknown is the current state. This is quite problematic
  because in general a scopes that queries the network (that is, most
  scopes) need to know whether there is network or is not network and
  depending on this either make the network queries or display an error
  message.

  A status of unknown connectivity leaves the scope with no valid option:
  * the scope could assume the network is down and provide the user an error 
message. But often the network is not actually down, so this interrupts the 
user's flow unnecessarily
  *  the scope could assume the network is up, but this is dangerous if it is 
not up

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

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

[Touch-packages] [Bug 1542083] Re: broken video clip has extremely blurry icon when navigating to the camera roll

This sets full trace for the thumbnailer:

gsettings set com.canonical.Unity.Thumbnailer log-level 2

If you want to start out with a cold cache, you can run

thumbnailer-admin clear

Then run a trace on ~phablet/.cache/upstart/dbus.log

The trace shows the requested dimensions for each thumbnail. Check
whether the dimensions being asked for are correct. If too small, the
problem is outside the thumbnailer. If dimensions are as expected, and
the video contains embedded cover art, the embedded cover art will be
returned scaled down to the requested size; if the dimensions of the
embedded cover art are smaller than the requested dimensions, the cover
art will be returned at the size it was found in the video.

Otherwise, if the video does not contain cover art, the thumbnailer will
extract a still frame and return that still frame, scaled down to the
requested size. In this case, the only way the image would be blurry if
the still frame itself is blurry, or if the video has ridiculously small
dimensions.

To confirm what's going on, run

/usr/lib/x86_64-linux-gnu/thumbnailer/vs-thumb 
video.tiff

Then check video.tiff by looking at it with a browser or image viewer.
This completely bypasses the thumbnailer and verifies whether the image
is being extracted correctly and omits any scaling; the command simply
dumps whatever image was found as cover art, or whatever screenshot was
extracted.

You can also talk to the thumbnailer:

thumbnailer-admin get 

This drops the thumbnail at the largest available resolution into the
current directory.

To request a specific size, use

thumbnail-admin get --size=200 

This adds the image to the cache and returns it (or returns it from the
cache if it was cached earlier) after running it through the scaler.

man thumbnailer

and

man thumbnailer-service

provide more detail.

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

Title:
  broken video clip has extremely blurry icon when navigating to the
  camera roll

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

Bug description:
  from design:
  If for some reason thumbnail was not able to be generated after taking a 
video, the placeholder thumbnail is very blurry. Guessing that thumbnailer is 
not providing a thumbnail for this at needed size requested.

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

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

[Touch-packages] [Bug 1404302] Re: liblttng-ust0 Error opening shm /lttng-ust-wait-5

2016-02-04 Thread Gerry Boland

Yep, as test, inside
/usr/share/click/preinstalled/com.ubuntu.camera/current create this
simple QML file: test.qml:

import QtQuick 2.0
import Ubuntu.Content 0.1

Rectangle {
color: "red"
}

and execute with:

aa-exec-click -p com.ubuntu.camera_camera_3.0.0.611 -- qmlscene test.qml
--desktop_file_hint=dialer-app

You'll get the LTTng messages printed

** Also affects: content-hub (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: content-hub (Ubuntu)
   Importance: Undecided => High

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

Title:
  liblttng-ust0 Error opening shm /lttng-ust-wait-5

Status in Client Developer Experience:
  Confirmed
Status in platform-api:
  New
Status in content-hub package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Confined apps don't have access to this and continuously produce this
  error message in stderr:

  libust[31283/31285]: Error: Error opening shm /lttng-ust-wait-5 (in
  get_wait_shm() at lttng-ust-comm.c:958)

  
  This is printed to the application's log about once every other second and 
makes it hard to read the application's own debug output. For a better app 
developer experience this message should be silenced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1404302/+subscriptions

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

[Touch-packages] [Bug 1404302] Re: liblttng-ust0 Error opening shm /lttng-ust-wait-5

2016-02-04 Thread Gerry Boland

Playing around with the camera app, I found that if I removed the
"Ubuntu.Content" plugin, the LTTng message stopped. So suspect something
content hub is linking with

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

Title:
  liblttng-ust0 Error opening shm /lttng-ust-wait-5

Status in Client Developer Experience:
  Confirmed
Status in platform-api:
  New
Status in content-hub package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Confined apps don't have access to this and continuously produce this
  error message in stderr:

  libust[31283/31285]: Error: Error opening shm /lttng-ust-wait-5 (in
  get_wait_shm() at lttng-ust-comm.c:958)

  
  This is printed to the application's log about once every other second and 
makes it hard to read the application's own debug output. For a better app 
developer experience this message should be silenced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1404302/+subscriptions

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

[Touch-packages] [Bug 1542094] [NEW] [camera] LED & Flash toggles are shown even when no LED or Flash present on hardware

Public bug reported:

could be Freiza specific.

We shouldn't be showing controls for flash, torchlight if they are not
present on hardware, but apparently we are (according to design)

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

** Affects: camera-app (Ubuntu)
 Importance: High
 Assignee: Florian Boucault (fboucault)
 Status: New

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

** Changed in: camera-app (Ubuntu)
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: camera-app (Ubuntu)
 Assignee: Bill Filler (bfiller) => Florian Boucault (fboucault)

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

** Changed in: canonical-devices-system-image
   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/1542094

Title:
  [camera] LED & Flash toggles are shown even when no LED or Flash
  present on hardware

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

Bug description:
  could be Freiza specific.

  We shouldn't be showing controls for flash, torchlight if they are not
  present on hardware, but apparently we are (according to design)

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

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

[Touch-packages] [Bug 1542088] [NEW] [camera] bottom edge hint should be clickable by mouse to activate

Public bug reported:

from design:
behavior on touch is correct - tapping the bottom edge hint should animate the 
hint to reveal something is beneath

behavior with mouse connected is not correct. Clicking the hint with
mouse should activate the bottom edge panel but it does not. Just makes
it wiggle.

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

** Affects: camera-app (Ubuntu)
 Importance: High
 Assignee: Florian Boucault (fboucault)
 Status: New

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

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

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

** 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
Milestone: None => ww08-2016

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

Title:
  [camera] bottom edge hint should be clickable by mouse to activate

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

Bug description:
  from design:
  behavior on touch is correct - tapping the bottom edge hint should animate 
the hint to reveal something is beneath

  behavior with mouse connected is not correct. Clicking the hint with
  mouse should activate the bottom edge panel but it does not. Just
  makes it wiggle.

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

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

[Touch-packages] [Bug 1542083] Re: broken video clip has extremely blurry icon when navigating to the camera roll

Also, why does it say "broken" video clip in the title. Is there
something wrong with the clip?

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

Title:
  broken video clip has extremely blurry icon when navigating to the
  camera roll

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

Bug description:
  from design:
  If for some reason thumbnail was not able to be generated after taking a 
video, the placeholder thumbnail is very blurry. Guessing that thumbnailer is 
not providing a thumbnail for this at needed size requested.

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

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

[Touch-packages] [Bug 1542083] Re: broken video clip has extremely blurry icon when navigating to the camera roll

Can we have a copy of the offending video? That would help a lot.

What sort of video is this? One that was taken with the camera, or was
it added to the device from somewhere else?

If the video was copied from somewhere else and contains cover art, that
cover art will be used. Because the thumbnailer never up-scales, if the
embedded cover art is small, it ends up getting up-scaled by display
widget, which might be what causes it to look blurry.

We really need an example file to figure out what is going on.

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

Title:
  broken video clip has extremely blurry icon when navigating to the
  camera roll

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

Bug description:
  from design:
  If for some reason thumbnail was not able to be generated after taking a 
video, the placeholder thumbnail is very blurry. Guessing that thumbnailer is 
not providing a thumbnail for this at needed size requested.

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

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

[Touch-packages] [Bug 1542087] [NEW] [camera] camera settings should be easier to dismiss

Public bug reported:

from design:
any selected action in the bottom edge can not be dismissed by clicking in the 
bottom edge area; Can’t dismiss options selector (flash on/off etc) unless user 
clicks in upper 2/3s of screen (i.e. outside of where bottom edge area is) - 
when bottom edge is shown

After discussing with Ben, the following should close the camera controls panel:
1) clicking anywhere inside the component that shows the camera controls but 
not on a button
2) clicking outside of the component

So basically clicking anywhere on the screen other than on one of the
control buttons should close the bottom edge

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

** Affects: camera-app (Ubuntu)
 Importance: High
 Assignee: Florian Boucault (fboucault)
 Status: New

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

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

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

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

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

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

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

** Summary changed:

- [camera] bottom edge should be easier to dismiss
+ [camera] camera settings should be easier to dismiss

** Description changed:

  from design:
  any selected action in the bottom edge can not be dismissed by clicking in 
the bottom edge area; Can’t dismiss options selector (flash on/off etc) unless 
user clicks in upper 2/3s of screen (i.e. outside of where bottom edge area is) 
- when bottom edge is shown
  
- After discussing with Ben, the following should close the bottom edge:
- 1) clicking anywhere inside the component that shows the bottom edge but not 
on a button
+ After discussing with Ben, the following should close the bottom edge 
settings:
+ 1) clicking anywhere inside the component that shows the camera controls but 
not on a button
  2) clicking outside of the component
  
  So basically clicking anywhere on the screen other than on one of the
- buttons should close the bottom edge
+ control buttons should close the bottom edge

** Description changed:

  from design:
  any selected action in the bottom edge can not be dismissed by clicking in 
the bottom edge area; Can’t dismiss options selector (flash on/off etc) unless 
user clicks in upper 2/3s of screen (i.e. outside of where bottom edge area is) 
- when bottom edge is shown
  
- After discussing with Ben, the following should close the bottom edge 
settings:
+ After discussing with Ben, the following should close the camera controls 
panel:
  1) clicking anywhere inside the component that shows the camera controls but 
not on a button
  2) clicking outside of the component
  
  So basically clicking anywhere on the screen other than on one of the
  control buttons should close the bottom edge

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

Title:
  [camera] camera settings should be easier to dismiss

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

Bug description:
  from design:
  any selected action in the bottom edge can not be dismissed by clicking in 
the bottom edge area; Can’t dismiss options selector (flash on/off etc) unless 
user clicks in upper 2/3s of screen (i.e. outside of where bottom edge area is) 
- when bottom edge is shown

  After discussing with Ben, the following should close the camera controls 
panel:
  1) clicking anywhere inside the component that shows the camera controls but 
not on a button
  2) clicking outside of the component

  So basically clicking anywhere on the screen other than on one of the
  control buttons should close the bottom edge

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

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

[Touch-packages] [Bug 1542086] [NEW] /usr/bin/webapp-container:11:oxide:::oxide::ScriptMessageContentsHelper::OnReceiveScriptMessage:oxide::ScriptMessageContentsHelper::OnMessageReceived:content::WebC

2016-02-04 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: kylin-15.04 trusty vivid wily

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

Title:
  /usr/bin/webapp-
  
container:11:oxide:::oxide::ScriptMessageContentsHelper::OnReceiveScriptMessage:oxide::ScriptMessageContentsHelper::OnMessageReceived:content::WebContentsImpl::OnMessageReceived:content::RenderFrameHostImpl::OnMessageReceived

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+15.10.20150929-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/cbd6b71bd915a6ff30ae589f54a7f1bf30360cd8
  contains more details.

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

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

[Touch-packages] [Bug 1542085] [NEW] /usr/bin/telephony-service-approver:11:QString::fromUtf8:QDebug::operator:AalMediaPlaylistControl::setPlaybackMode:QMediaPlaylistPrivate::syncControls:QMediaPlayli

2016-02-04 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

** Affects: telephony-service (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

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

Title:
  /usr/bin/telephony-service-
  
approver:11:QString::fromUtf8:QDebug::operator:AalMediaPlaylistControl::setPlaybackMode:QMediaPlaylistPrivate::syncControls:QMediaPlaylist::setMediaObject

Status in telephony-service package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding telephony-service.  This problem was most recently seen with
  version 0.1+15.04.20160105-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/da58c9738754537262cb32b5dfc279d98a1a0393
  contains more details.

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

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

[Touch-packages] [Bug 1542080] Re: Needs tar/xattr support to build docker

2016-02-04 Thread dann frazier

** Changed in: gccgo-4.9 (Ubuntu Trusty)
   Status: New => Triaged

** Patch added: "libgo-add-tar-xattr-support.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1542080/+attachment/4564171/+files/libgo-add-tar-xattr-support.debdiff

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

Title:
  Needs tar/xattr support to build docker

Status in gccgo-4.9 package in Ubuntu:
  Confirmed
Status in gccgo-4.9 source package in Trusty:
  Triaged

Bug description:
  [Impact]
  docker.io does not build on archs that require gccgo.

  [Test Case]
  Build docker.io in trusty on an arch that requires gccgo. I used arm64.
  (Also need patch in LP: #1510288)

  [Regression Risk]
  This is an upstream patch that applies cleanly (other than file tree 
rearrangements), and it is adding new functionality.

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

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

[Touch-packages] [Bug 1541532] Re: migrate UTC setting from /etc/default/rcS to adjtime

** Branch linked: lp:lupin

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

Title:
  migrate UTC setting from  /etc/default/rcS to adjtime

Status in installation-guide package in Ubuntu:
  Fix Released
Status in lupin package in Ubuntu:
  New
Status in mbr package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in sysvinit package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in mbr package in Debian:
  Unknown

Bug description:
  This has been an Ubuntu delta in systemd and perhaps other Ubuntu
  packages for a long time. But /etc/default/rcS is a SysV-ism, and no
  other setting in there is relevant. Steps:

   * Bump the version guard in systemd.conf for migrating the actual setting 
(keep until 16.04 LTS)
   * Ensure that we only look at the LOCAL setting during boot, and do no 
actual drift correction at boot, as the kernel does that by itself.
   * grep the archive for software which might directly look at or even write 
that file (Ubuntu specific config tools and the like).

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

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

[Touch-packages] [Bug 1542083] [NEW] broken video clip has extremely blurry icon when navigating to the camera roll

Public bug reported:

from design:
If for some reason thumbnail was not able to be generated after taking a video, 
the placeholder thumbnail is very blurry. Guessing that thumbnailer is not 
providing a thumbnail for this at needed size requested.

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

** Affects: camera-app (Ubuntu)
 Importance: Medium
 Assignee: Florian Boucault (fboucault)
 Status: New

** Affects: thumbnailer (Ubuntu)
 Importance: Medium
 Status: New

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

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

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

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

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

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

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

** Changed in: camera-app (Ubuntu)
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: camera-app (Ubuntu)
 Assignee: Bill Filler (bfiller) => 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/1542083

Title:
  broken video clip has extremely blurry icon when navigating to the
  camera roll

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

Bug description:
  from design:
  If for some reason thumbnail was not able to be generated after taking a 
video, the placeholder thumbnail is very blurry. Guessing that thumbnailer is 
not providing a thumbnail for this at needed size requested.

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

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

[Touch-packages] [Bug 1534340] Re: openssh server 6.6 does not report max auth failures

This bug was fixed in the package openssh - 1:6.6p1-2ubuntu2.6

---
openssh (1:6.6p1-2ubuntu2.6) trusty; urgency=medium

  * debian/control, debian/rules: enable libaudit support. (LP:
#1478087)

openssh (1:6.6p1-2ubuntu2.5) trusty-proposed; urgency=medium

  * Backport upstream reporting of max auth attempts, so that fail2bail
and similar tools can learn the IP address of brute forcers.
(LP: #1534340)
- debian/patches/report-max-auth.patch

 -- Mathieu Trudel-Lapierre   Tue, 26 Jan 2016
10:38:35 -0500

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

Title:
  openssh server 6.6 does not report max auth failures

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Fix Released

Bug description:
  Brute force attacks against openssh on Trusty will not log "max auth"
  key-based attempts, leaving their brute forcing invisible to the logs
  and anything that consumes logs, like fail2ban. Version 6.7 introduced
  the logging, but it's missing in Trusty. Since Trusty is LTS, it would
  seem sensible to have this feature backported.

  [Impact] Bruce force attempts using private keys are invisible to
  logs, which renders defenses like fail2ban useless.

  [Test case] Create 20 SSH keys, try to log in over SSH, note lack of
  logging the failures.

  [Regression Potential] Very unlikely regression potential as the "max
  auth" condition is already handled in code, it just wasn't logging.
  The change only adds the missing logging.

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

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

[Touch-packages] [Bug 1529454] Update Released

The verification of the Stable Release Update for lightdm 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1529454

Title:
  dm-tool add-nested-seat fails

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Won't Fix
Status in lightdm source package in Wily:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  dm-tool add-nested-seat doesn't work anymore.

  [Test Case]
  1. Log in
  2. From a terminal run "dm-tool add-nested-seat"

  Expected result:
  A window opens with a login screen

  Observed result:
  A window opens with a black screen. An error is reported in the terminal:
  Unable to add seat: GDBus.Error:org.freedesktop.DBus.Error.Failed: Failed to 
start seat

  [Regression Potential]
  The code change could affect other remote X server configurations, though 
this seems unlikely. Regression tests confirm other behaviour still works.

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

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

[Touch-packages] [Bug 1478087] Re: Add libaudit support

This bug was fixed in the package openssh - 1:6.6p1-2ubuntu2.6

---
openssh (1:6.6p1-2ubuntu2.6) trusty; urgency=medium

  * debian/control, debian/rules: enable libaudit support. (LP:
#1478087)

openssh (1:6.6p1-2ubuntu2.5) trusty-proposed; urgency=medium

  * Backport upstream reporting of max auth attempts, so that fail2bail
and similar tools can learn the IP address of brute forcers.
(LP: #1534340)
- debian/patches/report-max-auth.patch

 -- Mathieu Trudel-Lapierre   Tue, 26 Jan 2016
10:38:35 -0500

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

Title:
  Add libaudit support

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.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Triaged
Status in openssh source package in Trusty:
  Fix Released
Status in shadow source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Triaged
Status in openssh source package in Vivid:
  Triaged
Status in shadow source package in Vivid:
  Triaged
Status in lightdm source package in Wily:
  Fix Released
Status in openssh source package in Wily:
  Fix Released
Status in shadow source package in Wily:
  Fix Released
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]
  Auditing support is a commonly used feature in large enterprises, and allows 
better tracking of actions happening on secured systems, especially when it 
comes to accounting for login events.

  Such systems fail to correctly list login events in aureport due to
  some software not integrating libaudit.

  [Test Case]
  1) Install auditd
  2) Login to the system multiple times (or allow for others to connect to the 
system)
  3) Run aureport -l

  System should list login information.

  [Regression Potential]
  There is minimal risk for issues since libaudit support only allows for 
generating extra logging saved on the local system. A possible side-effect of 
this may be that systems on which auditing is enabled and where there are many 
users of the affected software (see bug tasks), such as many logins over SSH, 
there may be an increased demand on disk space necessary for the auditing data.

  ---

  -- Problem Description --
  We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried 
to
  ssh to lakelp1 several times and found that "aureport -l" couldn't print out 
the login
  info.

  root@lakelp1:~# /etc/init.d/auditd status
   * auditd is running.

  root@lakelp1:~# auditctl -e 1
  AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 
lost=12 backlog=1

  root@lakelp1:~# grep -i login /var/log/audit/audit.log
  type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=4 res=1
  type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=5 res=1
  type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=6 res=1
  type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=7 res=1
  type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=8 res=1

  root@lakelp1:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  

  This looks like a bug in aureport or libaudit. In addition to giving
  admins falsely empty record selections, this would prevent successful
  completion of a Common Criteria certification.

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

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

[Touch-packages] [Bug 1529454] Re: dm-tool add-nested-seat fails

This bug was fixed in the package lightdm - 1.16.7-0ubuntu1

---
lightdm (1.16.7-0ubuntu1) wily; urgency=medium

  * New upstream release:
- Fix dm-tool add-local-seat not working because LightDM is trying to
  connect with TCP/IP (LP: #1529454)

 -- Robert Ancell   Mon, 25 Jan 2016
17:35:34 +1300

** Changed in: lightdm (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  dm-tool add-nested-seat fails

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Won't Fix
Status in lightdm source package in Wily:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  dm-tool add-nested-seat doesn't work anymore.

  [Test Case]
  1. Log in
  2. From a terminal run "dm-tool add-nested-seat"

  Expected result:
  A window opens with a login screen

  Observed result:
  A window opens with a black screen. An error is reported in the terminal:
  Unable to add seat: GDBus.Error:org.freedesktop.DBus.Error.Failed: Failed to 
start seat

  [Regression Potential]
  The code change could affect other remote X server configurations, though 
this seems unlikely. Regression tests confirm other behaviour still works.

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

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

[Touch-packages] [Bug 1542077] [NEW] don't allow focus ring outside of viewfinder

Public bug reported:

on windowed mode, clicking outside the 40/50GU view still focusses the
focus; tapping black space shouldn’t trigger focussing

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

** Affects: camera-app (Ubuntu)
 Importance: High
 Assignee: Florian Boucault (fboucault)
 Status: New

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

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

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

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

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

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

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

Title:
  don't allow focus ring outside of viewfinder

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

Bug description:
  on windowed mode, clicking outside the 40/50GU view still focusses the
  focus; tapping black space shouldn’t trigger focussing

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

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

[Touch-packages] [Bug 1542081] [NEW] don't allow navigation while timer is going

Public bug reported:

from design:
shouldn’t be able to navigate to camera roll while timer is triggered; only 
actions that should be within the camera app available is cancelling the timer

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

** Affects: camera-app (Ubuntu)
 Importance: Medium
 Assignee: Florian Boucault (fboucault)
 Status: New

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

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

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

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

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

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

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

Title:
  don't allow navigation while timer is going

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

Bug description:
  from design:
  shouldn’t be able to navigate to camera roll while timer is triggered; only 
actions that should be within the camera app available is cancelling the timer

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

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

[Touch-packages] [Bug 1542080] [NEW] Needs tar/xattr support to build docker

2016-02-04 Thread dann frazier

Public bug reported:

[Impact]
docker.io does not build on archs that require gccgo.

[Test Case]
Build docker.io in trusty on an arch that requires gccgo. I used arm64.
(Also need patch in LP: #1510288)

[Regression Risk]
This is an upstream patch that applies cleanly (other than file tree 
rearrangements), and it is adding new functionality.

** Affects: gccgo-4.9 (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: gccgo-4.9 (Ubuntu Trusty)
 Importance: Undecided
 Status: Triaged

** Also affects: gccgo-4.9 (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 gccgo-4.9 in Ubuntu.
https://bugs.launchpad.net/bugs/1542080

Title:
  Needs tar/xattr support to build docker

Status in gccgo-4.9 package in Ubuntu:
  Confirmed
Status in gccgo-4.9 source package in Trusty:
  Triaged

Bug description:
  [Impact]
  docker.io does not build on archs that require gccgo.

  [Test Case]
  Build docker.io in trusty on an arch that requires gccgo. I used arm64.
  (Also need patch in LP: #1510288)

  [Regression Risk]
  This is an upstream patch that applies cleanly (other than file tree 
rearrangements), and it is adding new functionality.

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

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

[Touch-packages] [Bug 1542080] Re: Needs tar/xattr support to build docker

2016-02-04 Thread dann frazier

** Attachment added: "failed build log"
   
https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1542080/+attachment/4564170/+files/docker.io.buildlog.FAILED.gz

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

Title:
  Needs tar/xattr support to build docker

Status in gccgo-4.9 package in Ubuntu:
  Confirmed
Status in gccgo-4.9 source package in Trusty:
  Triaged

Bug description:
  [Impact]
  docker.io does not build on archs that require gccgo.

  [Test Case]
  Build docker.io in trusty on an arch that requires gccgo. I used arm64.
  (Also need patch in LP: #1510288)

  [Regression Risk]
  This is an upstream patch that applies cleanly (other than file tree 
rearrangements), and it is adding new functionality.

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

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

[Touch-packages] [Bug 1542075] Re: viewfinder should re-size to fit window

to elaborate on 4) currently there is no visual feedback to the user
when the screen is rotated

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

Title:
  viewfinder should re-size to fit window

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

Bug description:
  in windowed mode, the viewfinder is currently fills the screen in the
  vertical orientation. If the window is made smaller the controls
  incorrectly rotate like the app thinks it's in landscape mode and
  bottom edge moves to the right.

  Lets discuss what to do here, but some options:

  1) resizing the window shouldn't change where the controls are located or the 
orientation
  2) resizing should make the viewfinder fill the available space. Should it 
use the largest vertical or horizontal dimension, or be fixed to the physical 
orientation of the phone?
  3) Should we not allow window resizing and instead lock the window size to 
the actual size of the viewfinder?
  4) If the phone is rotated, should the window size automatically change to 
reflect the phone orientation?

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

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

[Touch-packages] [Bug 1542075] [NEW] viewfinder should re-size to fit window

Public bug reported:

in windowed mode, the viewfinder is currently fills the screen in the
vertical orientation. If the window is made smaller the controls
incorrectly rotate like the app thinks it's in landscape mode and bottom
edge moves to the right.

Lets discuss what to do here, but some options:

1) resizing the window shouldn't change where the controls are located or the 
orientation
2) resizing should make the viewfinder fill the available space. Should it use 
the largest vertical or horizontal dimension, or be fixed to the physical 
orientation of the phone?
3) Should we not allow window resizing and instead lock the window size to the 
actual size of the viewfinder?
4) If the phone is rotated, should the window size automatically change to 
reflect the phone orientation?

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

** Affects: camera-app (Ubuntu)
 Importance: High
 Assignee: Florian Boucault (fboucault)
 Status: New

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

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

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

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

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

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

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

Title:
  viewfinder should re-size to fit window

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

Bug description:
  in windowed mode, the viewfinder is currently fills the screen in the
  vertical orientation. If the window is made smaller the controls
  incorrectly rotate like the app thinks it's in landscape mode and
  bottom edge moves to the right.

  Lets discuss what to do here, but some options:

  1) resizing the window shouldn't change where the controls are located or the 
orientation
  2) resizing should make the viewfinder fill the available space. Should it 
use the largest vertical or horizontal dimension, or be fixed to the physical 
orientation of the phone?
  3) Should we not allow window resizing and instead lock the window size to 
the actual size of the viewfinder?
  4) If the phone is rotated, should the window size automatically change to 
reflect the phone orientation?

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

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

[Touch-packages] [Bug 1534340] Update Released

The verification of the Stable Release Update for openssh 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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1534340

Title:
  openssh server 6.6 does not report max auth failures

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Fix Committed

Bug description:
  Brute force attacks against openssh on Trusty will not log "max auth"
  key-based attempts, leaving their brute forcing invisible to the logs
  and anything that consumes logs, like fail2ban. Version 6.7 introduced
  the logging, but it's missing in Trusty. Since Trusty is LTS, it would
  seem sensible to have this feature backported.

  [Impact] Bruce force attempts using private keys are invisible to
  logs, which renders defenses like fail2ban useless.

  [Test case] Create 20 SSH keys, try to log in over SSH, note lack of
  logging the failures.

  [Regression Potential] Very unlikely regression potential as the "max
  auth" condition is already handled in code, it just wasn't logging.
  The change only adds the missing logging.

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

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

[Touch-packages] [Bug 1541865] Re: package manager keys incorrect

2016-02-04 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package manager keys incorrect

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  dpkg fails with error every time I install new software

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-66-generic 3.13.0-66.108
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hatmer 2099 F pulseaudio
   /dev/snd/controlC1:  hatmer 2099 F pulseaudio
  Date: Fri Jan 29 12:37:11 2016
  DuplicateSignature: 
package:linux-image-3.13.0-66-generic:3.13.0-66.108:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=8e6ea026-d120-4177-ae1f-68374517efa3
  InstallationDate: Installed on 2015-10-22 (105 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20AVCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=2d312f9c-f7c9-444a-86eb-eb79cbc6eb14 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-3.13.0-66-generic 3.13.0-66.108 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET37WW(1.10)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 Std
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET37WW(1.10):bd11/12/2013:svnLENOVO:pn20AVCTO1WW:pvrThinkPadL540:rvnLENOVO:rn20AVCTO1WW:rvr0B98405Std:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AVCTO1WW
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1541865] Re: package manager keys incorrect

2016-02-04 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package manager keys incorrect

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  dpkg fails with error every time I install new software

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-66-generic 3.13.0-66.108
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hatmer 2099 F pulseaudio
   /dev/snd/controlC1:  hatmer 2099 F pulseaudio
  Date: Fri Jan 29 12:37:11 2016
  DuplicateSignature: 
package:linux-image-3.13.0-66-generic:3.13.0-66.108:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=8e6ea026-d120-4177-ae1f-68374517efa3
  InstallationDate: Installed on 2015-10-22 (105 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 20AVCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=2d312f9c-f7c9-444a-86eb-eb79cbc6eb14 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-3.13.0-66-generic 3.13.0-66.108 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET37WW(1.10)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 Std
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET37WW(1.10):bd11/12/2013:svnLENOVO:pn20AVCTO1WW:pvrThinkPadL540:rvnLENOVO:rn20AVCTO1WW:rvr0B98405Std:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AVCTO1WW
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1478087] Re: Add libaudit support

This bug was fixed in the package shadow - 1:4.1.5.1-1ubuntu9.2

---
shadow (1:4.1.5.1-1ubuntu9.2) trusty; urgency=medium

  * debian/control, debian/rules: re-enable libaudit support. (LP:
#1478087)

 -- Mathieu Trudel-Lapierre   Fri, 22 Jan 2016
11:21:57 -0500

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

Title:
  Add libaudit support

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.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Triaged
Status in openssh source package in Trusty:
  Fix Committed
Status in shadow source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Triaged
Status in openssh source package in Vivid:
  Triaged
Status in shadow source package in Vivid:
  Triaged
Status in lightdm source package in Wily:
  Fix Released
Status in openssh source package in Wily:
  Fix Released
Status in shadow source package in Wily:
  Fix Released
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]
  Auditing support is a commonly used feature in large enterprises, and allows 
better tracking of actions happening on secured systems, especially when it 
comes to accounting for login events.

  Such systems fail to correctly list login events in aureport due to
  some software not integrating libaudit.

  [Test Case]
  1) Install auditd
  2) Login to the system multiple times (or allow for others to connect to the 
system)
  3) Run aureport -l

  System should list login information.

  [Regression Potential]
  There is minimal risk for issues since libaudit support only allows for 
generating extra logging saved on the local system. A possible side-effect of 
this may be that systems on which auditing is enabled and where there are many 
users of the affected software (see bug tasks), such as many logins over SSH, 
there may be an increased demand on disk space necessary for the auditing data.

  ---

  -- Problem Description --
  We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried 
to
  ssh to lakelp1 several times and found that "aureport -l" couldn't print out 
the login
  info.

  root@lakelp1:~# /etc/init.d/auditd status
   * auditd is running.

  root@lakelp1:~# auditctl -e 1
  AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 
lost=12 backlog=1

  root@lakelp1:~# grep -i login /var/log/audit/audit.log
  type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=4 res=1
  type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=5 res=1
  type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=6 res=1
  type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=7 res=1
  type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=8 res=1

  root@lakelp1:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  

  This looks like a bug in aureport or libaudit. In addition to giving
  admins falsely empty record selections, this would prevent successful
  completion of a Common Criteria certification.

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

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

[Touch-packages] [Bug 1478087] Update Released

The verification of the Stable Release Update for shadow 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1478087

Title:
  Add libaudit support

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.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Triaged
Status in openssh source package in Trusty:
  Fix Committed
Status in shadow source package in Trusty:
  Fix Released
Status in lightdm source package in Vivid:
  Triaged
Status in openssh source package in Vivid:
  Triaged
Status in shadow source package in Vivid:
  Triaged
Status in lightdm source package in Wily:
  Fix Released
Status in openssh source package in Wily:
  Fix Released
Status in shadow source package in Wily:
  Fix Released
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]
  Auditing support is a commonly used feature in large enterprises, and allows 
better tracking of actions happening on secured systems, especially when it 
comes to accounting for login events.

  Such systems fail to correctly list login events in aureport due to
  some software not integrating libaudit.

  [Test Case]
  1) Install auditd
  2) Login to the system multiple times (or allow for others to connect to the 
system)
  3) Run aureport -l

  System should list login information.

  [Regression Potential]
  There is minimal risk for issues since libaudit support only allows for 
generating extra logging saved on the local system. A possible side-effect of 
this may be that systems on which auditing is enabled and where there are many 
users of the affected software (see bug tasks), such as many logins over SSH, 
there may be an increased demand on disk space necessary for the auditing data.

  ---

  -- Problem Description --
  We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried 
to
  ssh to lakelp1 several times and found that "aureport -l" couldn't print out 
the login
  info.

  root@lakelp1:~# /etc/init.d/auditd status
   * auditd is running.

  root@lakelp1:~# auditctl -e 1
  AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 
lost=12 backlog=1

  root@lakelp1:~# grep -i login /var/log/audit/audit.log
  type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=4 res=1
  type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=5 res=1
  type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=6 res=1
  type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=7 res=1
  type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=8 res=1

  root@lakelp1:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  

  This looks like a bug in aureport or libaudit. In addition to giving
  admins falsely empty record selections, this would prevent successful
  completion of a Common Criteria certification.

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

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

[Touch-packages] [Bug 1537136] Re: ISST-LTE: no network after install due to interface order change

** Tags removed: verification-done
** Tags added: verification-needed

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

Title:
  ISST-LTE: no network after install due to interface order change

Status in debian-installer package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2015-12-10 20:32:29 
==
  We use the network to install Ubuntu 14.04.4 version. The installation is 
successful but then there is no network after system reboot in post install. 
Checking the network and I saw the order of interface are changed. This is 
causing no network at all.

  There is 2 cards (Houston 4ports & Mellanox 2 ports). We are using the 
Mellanox interface for this installation.
  At the installation menu, we select this interface eth2 (mellanox card)

  ??? [!!] Configure the network 
    ? ?
    ? Your system has multiple network interfaces. Choose the one to use as   ?
    ? the primary network interface during the installation. If possible, ?
    ? the first connected network interface found has been selected.  ?
    ? ?
    ? Primary network interface:  ?
    ? ?
    ?   eth0: Emulex Corporation OneConnect NIC (Lancer)  ?
    ?   eth1: Emulex Corporation OneConnect NIC (Lancer)  ?
    ?   eth2: Mellanox Technologies MT27500 Family [ConnectX-3]   ?
    ?   eth3: Mellanox Technologies MT27500 Family [ConnectX-3]   ?
    ?   eth4: Emulex Corporation OneConnect NIC (Lancer)  ?
    ?   eth5: Emulex Corporation OneConnect NIC (Lancer)  ?
    ? ?
    ??
    ? ?
    ???

  After install,
  root@monklp3:~# ifconfig
  eth2  Link encap:Ethernet  HWaddr 00:00:c9:d1:be:28
    UP BROADCAST MULTICAST  MTU:1500  Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  loLink encap:Local Loopback
    inet addr:127.0.0.1  Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING  MTU:65536  Metric:1
    RX packets:32 errors:0 dropped:0 overruns:0 frame:0
    TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2368 (2.3 KB)  TX bytes:2368 (2.3 KB)
  root@monklp3:~# ifconfig -a|grep eth
  eth0  Link encap:Ethernet  HWaddr 00:00:c9:d1:be:26
  eth1  Link encap:Ethernet  HWaddr 00:00:c9:d1:be:27
  eth2  Link encap:Ethernet  HWaddr 00:00:c9:d1:be:28
  eth3  Link encap:Ethernet  HWaddr 00:02:c9:b7:60:b0
  eth4  Link encap:Ethernet  HWaddr 00:02:c9:b7:60:b1
  eth5  Link encap:Ethernet  HWaddr 00:00:c9:d1:be:29
  root@monklp3:~# cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto eth2
  iface eth2 inet dhcp
  root@monklp3:~# dmesg |grep "eth"
  [0.950725] ibmveth: IBM Power Virtual Ethernet Driver 1.05
  [0.950735] ehea: IBM eHEA ethernet device driver (Release EHEA_0107)
  [9.810472] mlx4_en: eth3: Link Up
  [   40.554271] be2net 0001:80:00.2 eth2: Link is Down
  [   40.560738] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
  root@monklp3:~#

  The mellanox inteface is now on eth3 but on the /etc/network/interface
  file, it is set on eth2.

  SRU TEST CASE:
  --
   * Do a netboot install in a VM or machine with more than one NIC. If you use 
a VM, take care to not use the default MAC addresses as they are blacklisted 
from the persistent net generator. E. g. use "-net 
nic,model=virtio,macaddr=A4:4E:31:12:34:XX" with QEMU.
   * In the d-i environment, switch to a console with Alt+F2 after the base 
system got installed.
   * With current trusty, there is no /etc/udev/rules.d/70-persistent-net.rules 
and thus it also does not exist in /t

[Touch-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

2016-02-04 Thread Marsh

Worked for me. Updated nl libs as well. Worked even after reboot.

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

Title:
network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Trusty:
Fix Committed

Bug description:
[Triage Notes]

[Impact]

This affects the 0.98 release of NetworkManager and has already
been fixed in newer releases.

* Backporting fixes from upstream release is required to prevent
NetworkManager from faulting which breaks networking on most
Desktop releases.

* All patches applied are already accepted upstream and newer Ubuntu
releases are not affected.

* Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating
libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing.

[Test Case]

[Regression Potential]

* NetworkManager is a highly visible package, so testing NetworkManager
functionality is critical. The patch does address the crash specificly
introduced by the updated libnl SRU.

* We need to ensure that users have installed this NetworkManager
update before installing libnl3 update (special phasing needed).

[Original Description]
Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

After installing updated libnl3 and restarting networkmanager, NM
crashes with:

The bug has been fixed in upstream 0.98 with these patches:

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

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

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

[Touch-packages] [Bug 1271704] Re: Screen Flickering and display problems

2016-02-04 Thread Jose Luis Rivitti

I reinstalled Ubutu 15.10 from a iso on DVD. Problem fixed. 
Linux toshibaS75 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Screen Flickering and display problems

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Same Bug #1249468.
  Toshiba Satellite S75-A7334, i7-4700MQ.
  Ubuntu 13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jan 22 17:53:20 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fa82]
  InstallationDate: Installed on 2014-01-21 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite S75-A
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic.efi.signed 
root=UUID=77175de3-8261-4605-82db-9b3e72a5b62e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd09/23/2013:svnTOSHIBA:pnSatelliteS75-A:pvrPSKNAU-00R04Y:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S75-A
  dmi.product.version: PSKNAU-00R04Y
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Jan 22 17:31:23 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   20555 
   vendor SEC
  xserver.version: 2:1.14.5-1ubuntu2~saucy1

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

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

[Touch-packages] [Bug 1515712] Re: maliit-server becomes deadlocked

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

** Changed in: maliit-framework (Ubuntu)
   Status: New => Confirmed

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

Title:
  maliit-server becomes deadlocked

Status in Canonical System Image:
  Incomplete
Status in maliit-framework package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  on krillin, rc-proposed 175

  I'm experiencing keyboard not popping up on any application. Can't
  remember if this was after a reboot or if it was working for a while
  and then stopped. I believe it's after a reboot.

  Upon inspection, it appears maliit-server process is deadlocked (see
  thread dump below). Also, there is no log in .cache/upstart/maliit-
  server.log only old logs maliit-server.log.1.gz etc, which leads me to
  believe this problem happens after reboot.

  Seems that some QNetwork initialization is happening and this is
  causing an issue (see Threads 3, 2, and 1). We should figure out why
  we are even doing any network stuff at all, as we probably shouldn't
  be.

  (gdb) t a a bt

  Thread 14 (Thread 0xb2cc2440 (LWP 2844)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb3d03cdc in ?? () from /usr/lib/arm-linux-gnueabihf/libmircommon.so.5
  #2  0xb3d04c96 in ?? () from /usr/lib/arm-linux-gnueabihf/libmircommon.so.5
  #3  0xb67ec2a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6010490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #5  0xb66e0c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 13 (Thread 0xb2197440 (LWP 3128)):
  #0  0xb435a840 in ?? ()
  #1  0xb436e29c in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 12 (Thread 0xb240fb40 (LWP 3129)):
  #0  0xb5c61836 in ?? () from /lib/arm-linux-gnueabihf/librt.so.1
  #1  0xb5c618a4 in ?? () from /lib/arm-linux-gnueabihf/librt.so.1
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 11 (Thread 0xb1976440 (LWP 3130)):
  #0  0xb6018d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb60146b0 in pthread_cond_wait@@GLIBC_2.4 () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb225e0a8 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 10 (Thread 0xb1176440 (LWP 3131)):
  ---Type  to continue, or q  to quit---
  #0  0xb6018d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #1  0xb60146b0 in pthread_cond_wait@@GLIBC_2.4 () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #2  0xb225e0a8 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 9 (Thread 0xb0697440 (LWP 3143)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 8 (Thread 0xafcff440 (LWP 3144)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 7 (Thread 0xaeaff440 (LWP 3146)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 6 (Thread 0xae1ff440 (LWP 3148)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5cac0d8 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 5 (Thread 0xacb49440 (LWP 3167)):
  #0  0xb66e1132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
  ---Type  to continue, or q  to quit---
  #1  0xb3b62312 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #2  0xb3b642ea in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #3  0xb3b6484a in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #4  0xb3b4d678 in core::dbus::Bus::run() () from 
/usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #5  0xb67ec2a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6010490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #7  0xb66e0c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 4 (Thread 0xac349440 (LWP 3169)):
  #0  0xb66da4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xad94c0a6 in ?? () from /usr/lib/arm-linux-gnueabihf

[Touch-packages] [Bug 1542049] Re: lxc: ADT exercise test failing with linux-4.4.0-3.17

2016-02-04 Thread Andy Whitcroft

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

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

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

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

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

Title:
  lxc: ADT exercise test failing with linux-4.4.0-3.17

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  New

Bug description:
  We have an ADT test failure with linux-4.4.0-3.17:

  adt-run [14:48:58]: test exercise: [---
  PASS: lxc-tests: /usr/bin/lxc-test-apparmor
  adt-run [17:35:39]: ERROR: timed out on command "su -s /bin/bash root -c set 
-e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  . ~/.profile 
>/dev/null 2>&1 || true; 
buildtree="/tmp/adt-run.Z4dUgS/build.hyN/lxc-2.0.0~beta2"; mkdir -p -m 1777 -- 
"/tmp/adt-run.Z4dUgS/exercise-artifacts"; export 
ADT_ARTIFACTS="/tmp/adt-run.Z4dUgS/exercise-artifacts"; export ADTTMP=$(mktemp 
-d --tmpdir adttmp.XX); export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=$(grep -c ^processor 
/proc/cpuinfo | sed 's/^0$/1/'); unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME 
LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE 
LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/adt_test_script_pid; set -C; 
echo $$ > /tmp/adt_test_script_pid; set +C; trap "rm -rf $ADTTMP 
/tmp/adt_test_script_pid" EXIT INT QUIT PIPE; chmod 755 $ADTTMP; cd 
"$buildtree"; export 'ADT_TEST_TRIGGERS=linux-meta/4.4.0.3.2'; chmod +x 
/tmp/adt-run.Z4dUgS/bui
 ld.hyN/lxc-2.0.0~beta2/debian/tests/exercise; touch 
/tmp/adt-run.Z4dUgS/exercise-stdout /tmp/adt-run.Z4dUgS/exercise-stderr; 
/tmp/adt-run.Z4dUgS/build.hyN/lxc-2.0.0~beta2/debian/tests/exercise 2> >(tee -a 
/tmp/adt-run.Z4dUgS/exercise-stderr >&2) > >(tee -a 
/tmp/adt-run.Z4dUgS/exercise-stdout); " (kind: test)
  adt-run [17:35:39]: test exercise: ---]
  adt-run [17:35:40]: test exercise:  - - - - - - - - - - results - - - - - - - 
- - -
  exercise FAIL timed out
  adt-run [17:35:40]:  summary
  exercise FAIL timed out

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

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

[Touch-packages] [Bug 1542049] [NEW] lxc: ADT exercise test failing with linux-4.4.0-3.17

2016-02-04 Thread Andy Whitcroft

Public bug reported:

We have an ADT test failure with linux-4.4.0-3.17:

adt-run [14:48:58]: test exercise: [---
PASS: lxc-tests: /usr/bin/lxc-test-apparmor
adt-run [17:35:39]: ERROR: timed out on command "su -s /bin/bash root -c set 
-e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  . ~/.profile 
>/dev/null 2>&1 || true; 
buildtree="/tmp/adt-run.Z4dUgS/build.hyN/lxc-2.0.0~beta2"; mkdir -p -m 1777 -- 
"/tmp/adt-run.Z4dUgS/exercise-artifacts"; export 
ADT_ARTIFACTS="/tmp/adt-run.Z4dUgS/exercise-artifacts"; export ADTTMP=$(mktemp 
-d --tmpdir adttmp.XX); export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=$(grep -c ^processor 
/proc/cpuinfo | sed 's/^0$/1/'); unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME 
LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE 
LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/adt_test_script_pid; set -C; 
echo $$ > /tmp/adt_test_script_pid; set +C; trap "rm -rf $ADTTMP 
/tmp/adt_test_script_pid" EXIT INT QUIT PIPE; chmod 755 $ADTTMP; cd 
"$buildtree"; export 'ADT_TEST_TRIGGERS=linux-meta/4.4.0.3.2'; chmod +x 
/tmp/adt-run.Z4dUgS/build
 .hyN/lxc-2.0.0~beta2/debian/tests/exercise; touch 
/tmp/adt-run.Z4dUgS/exercise-stdout /tmp/adt-run.Z4dUgS/exercise-stderr; 
/tmp/adt-run.Z4dUgS/build.hyN/lxc-2.0.0~beta2/debian/tests/exercise 2> >(tee -a 
/tmp/adt-run.Z4dUgS/exercise-stderr >&2) > >(tee -a 
/tmp/adt-run.Z4dUgS/exercise-stdout); " (kind: test)
adt-run [17:35:39]: test exercise: ---]
adt-run [17:35:40]: test exercise:  - - - - - - - - - - results - - - - - - - - 
- -
exercise FAIL timed out
adt-run [17:35:40]:  summary
exercise FAIL timed out

** Affects: linux (Ubuntu)
 Importance: High
 Status: Confirmed

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

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

Title:
  lxc: ADT exercise test failing with linux-4.4.0-3.17

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  New

Bug description:
  We have an ADT test failure with linux-4.4.0-3.17:

  adt-run [14:48:58]: test exercise: [---
  PASS: lxc-tests: /usr/bin/lxc-test-apparmor
  adt-run [17:35:39]: ERROR: timed out on command "su -s /bin/bash root -c set 
-e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  . ~/.profile 
>/dev/null 2>&1 || true; 
buildtree="/tmp/adt-run.Z4dUgS/build.hyN/lxc-2.0.0~beta2"; mkdir -p -m 1777 -- 
"/tmp/adt-run.Z4dUgS/exercise-artifacts"; export 
ADT_ARTIFACTS="/tmp/adt-run.Z4dUgS/exercise-artifacts"; export ADTTMP=$(mktemp 
-d --tmpdir adttmp.XX); export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=$(grep -c ^processor 
/proc/cpuinfo | sed 's/^0$/1/'); unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME 
LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE 
LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/adt_test_script_pid; set -C; 
echo $$ > /tmp/adt_test_script_pid; set +C; trap "rm -rf $ADTTMP 
/tmp/adt_test_script_pid" EXIT INT QUIT PIPE; chmod 755 $ADTTMP; cd 
"$buildtree"; export 'ADT_TEST_TRIGGERS=linux-meta/4.4.0.3.2'; chmod +x 
/tmp/adt-run.Z4dUgS/bui
 ld.hyN/lxc-2.0.0~beta2/debian/tests/exercise; touch 
/tmp/adt-run.Z4dUgS/exercise-stdout /tmp/adt-run.Z4dUgS/exercise-stderr; 
/tmp/adt-run.Z4dUgS/build.hyN/lxc-2.0.0~beta2/debian/tests/exercise 2> >(tee -a 
/tmp/adt-run.Z4dUgS/exercise-stderr >&2) > >(tee -a 
/tmp/adt-run.Z4dUgS/exercise-stdout); " (kind: test)
  adt-run [17:35:39]: test exercise: ---]
  adt-run [17:35:40]: test exercise:  - - - - - - - - - - results - - - - - - - 
- - -
  exercise FAIL timed out
  adt-run [17:35:40]:  summary
  exercise FAIL timed out

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

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

[Touch-packages] [Bug 1542049] Re: lxc: ADT exercise test failing with linux-4.4.0-3.17

2016-02-04 Thread Andy Whitcroft

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/ppc64el/l/lxc/20160204_173552@/log.gz

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

Title:
  lxc: ADT exercise test failing with linux-4.4.0-3.17

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  New

Bug description:
  We have an ADT test failure with linux-4.4.0-3.17:

  adt-run [14:48:58]: test exercise: [---
  PASS: lxc-tests: /usr/bin/lxc-test-apparmor
  adt-run [17:35:39]: ERROR: timed out on command "su -s /bin/bash root -c set 
-e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  . ~/.profile 
>/dev/null 2>&1 || true; 
buildtree="/tmp/adt-run.Z4dUgS/build.hyN/lxc-2.0.0~beta2"; mkdir -p -m 1777 -- 
"/tmp/adt-run.Z4dUgS/exercise-artifacts"; export 
ADT_ARTIFACTS="/tmp/adt-run.Z4dUgS/exercise-artifacts"; export ADTTMP=$(mktemp 
-d --tmpdir adttmp.XX); export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=$(grep -c ^processor 
/proc/cpuinfo | sed 's/^0$/1/'); unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME 
LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE 
LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/adt_test_script_pid; set -C; 
echo $$ > /tmp/adt_test_script_pid; set +C; trap "rm -rf $ADTTMP 
/tmp/adt_test_script_pid" EXIT INT QUIT PIPE; chmod 755 $ADTTMP; cd 
"$buildtree"; export 'ADT_TEST_TRIGGERS=linux-meta/4.4.0.3.2'; chmod +x 
/tmp/adt-run.Z4dUgS/bui
 ld.hyN/lxc-2.0.0~beta2/debian/tests/exercise; touch 
/tmp/adt-run.Z4dUgS/exercise-stdout /tmp/adt-run.Z4dUgS/exercise-stderr; 
/tmp/adt-run.Z4dUgS/build.hyN/lxc-2.0.0~beta2/debian/tests/exercise 2> >(tee -a 
/tmp/adt-run.Z4dUgS/exercise-stderr >&2) > >(tee -a 
/tmp/adt-run.Z4dUgS/exercise-stdout); " (kind: test)
  adt-run [17:35:39]: test exercise: ---]
  adt-run [17:35:40]: test exercise:  - - - - - - - - - - results - - - - - - - 
- - -
  exercise FAIL timed out
  adt-run [17:35:40]:  summary
  exercise FAIL timed out

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

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

[Touch-packages] [Bug 1539016] Re: Remove /bin/running-in-container

** Branch linked: lp:cloud-init

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

Title:
  Remove /bin/running-in-container

Status in apparmor package in Ubuntu:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  In Progress
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in memtest86+ package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in grub2 package in Debian:
  Fix Committed

Bug description:
  We still have an ubuntu delta in init-system-helper that adds /bin
  /running-in-container. This is just a (currently over-complicated)
  wrapper around "systemd-detect-virt --container". That works under any
  init system and is what upstreams and some packages already use, so
  let's cut out that delta.

  I'm currently running an archive grep to find remaining users.

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

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

[Touch-packages] [Bug 1541532] Re: migrate UTC setting from /etc/default/rcS to adjtime

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

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

Title:
  migrate UTC setting from  /etc/default/rcS to adjtime

Status in installation-guide package in Ubuntu:
  Fix Released
Status in lupin package in Ubuntu:
  New
Status in mbr package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in sysvinit package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in mbr package in Debian:
  Unknown

Bug description:
  This has been an Ubuntu delta in systemd and perhaps other Ubuntu
  packages for a long time. But /etc/default/rcS is a SysV-ism, and no
  other setting in there is relevant. Steps:

   * Bump the version guard in systemd.conf for migrating the actual setting 
(keep until 16.04 LTS)
   * Ensure that we only look at the LOCAL setting during boot, and do no 
actual drift correction at boot, as the kernel does that by itself.
   * grep the archive for software which might directly look at or even write 
that file (Ubuntu specific config tools and the like).

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

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

[Touch-packages] [Bug 1542047] [NEW] visual cleanup for convergence

Public bug reported:

Information from design:

1) App should set preferred size to something that is good for desktop, i.e. 
that shows 2 columns width
2) in windowed mode - window decoration quickly switches between Contacts & 
Address Book in the naming on start of app 
3) clean up empty state text, leave right hand column blank, no text at all 
accoding to Ben
4) google logo in 1st panel, empty list: import contacts is disappearing when 
you open the bottom edge briefly - should stay there until bottom edge is 
committed
5) when bottom edge is triggered and the background darkens, a white line is 
visible seemingly dividing the header and header sections; the white line seems 
to float on top of the bottom edge view. Should get rid of this
6) Contacts > new contact: “Add Field” should be “Add field” in the New contact 
view
7) Contacts > New contact - Font size for name and surname appears too large, 
make smaller
8) selected state in contact list view is super orange…and the names are purple 
-> massive no go; list item text should be aligned with new sdk guidelines as 
well as list item selection - use the selection rectangles instead of 
highlighting that olivier is using from the sdk presentation: 
https://docs.google.com/presentation/d/1YUJgWpH7nNFshhNsHhvVnYOjSx_sRE7mPrtupB3-F7s/edit?ts=56aa1cdf#slide=id.gb5ac35bf4_0_0

- Settings: 
9) default “Addressbook” should be “Address book” from one word to two words
10) wrong icon in the default address book, seem not to use the SURU icon 
theme, are icons in the selector needed at all? ‘Option Selector’ used to 
select address book (‘default address book, etc’) - Miss-aligned assets (icon, 
label, chevron). usage of wrong component in address book settings for 
selecting a local address book, it should be a list item and then a 2nd screen 
listing available accounts. Check with Ben on this. At miminum fix the 
alignment issues he is talking about.


Lower priority:
11)Contacts > new contact: tags “home > work > other” should change to 
“private/personal>work>other” and Enter an email address’ & ‘home/work/other’ 
should read  ‘Email address’ & ‘Personal/Work/other’. Is this hard? Will it 
cause incompatibilities?
12) Settings panel in two column mode is wrong: contacts are still visible in 
left panel, should be list of settings in left hand panel with details in right 
panel

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

** Affects: address-book-app (Ubuntu)
 Importance: High
 Assignee: Renato Araujo Oliveira Filho (renatofilho)
 Status: Confirmed

** Changed in: address-book-app (Ubuntu)
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None => ww08-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

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

Title:
  visual cleanup for convergence

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  Information from design:

  1) App should set preferred size to something that is good for desktop, i.e. 
that shows 2 columns width
  2) in windowed mode - window decoration quickly switches between Contacts & 
Address Book in the naming on start of app 
  3) clean up empty state text, leave right hand column blank, no text at all 
accoding to Ben
  4) google logo in 1st panel, empty list: import contacts is disappearing when 
you open the bottom edge briefly - should stay there until bottom edge is 
committed
  5) when bottom edge is triggered and the background darkens, a white line is 
visible seemingly dividing the header and header sections; the white line seems 
to float on top of the bottom edge view. Should get rid of this
  6) Contacts > new contact: “Add Field” should be “Add field” in the New 
contact view
  7) Contacts > New contact - Font size for name and surname appears too large, 
make smaller
  8) selected state in contact list view is super orange…and the names are 
purple -> massive no go; list item text should be aligned with new sdk 
guidelines as well as list item selection - use the selection rectangles 
instead of highlighting that olivier is using from the sdk presentation: 
https://docs.google.com/presentation/d/1YUJgWpH7nNFshhNsHhvVnYOjSx_sRE7mPrtupB3-

[Touch-packages] [Bug 1541532] Re: migrate UTC setting from /etc/default/rcS to adjtime

This bug was fixed in the package installation-guide - 20160121ubuntu2

---
installation-guide (20160121ubuntu2) xenial; urgency=medium

  * en/appendix/chroot-install.xml: Revert Ubuntu delta about setting UTC in
/etc/default/rcS instead of /etc/adjtime. (LP: #1541532)

 -- Martin Pitt   Thu, 04 Feb 2016 22:15:31
+0100

** Changed in: installation-guide (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  migrate UTC setting from  /etc/default/rcS to adjtime

Status in installation-guide package in Ubuntu:
  Fix Released
Status in lupin package in Ubuntu:
  New
Status in mbr package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in sysvinit package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in mbr package in Debian:
  Unknown

Bug description:
  This has been an Ubuntu delta in systemd and perhaps other Ubuntu
  packages for a long time. But /etc/default/rcS is a SysV-ism, and no
  other setting in there is relevant. Steps:

   * Bump the version guard in systemd.conf for migrating the actual setting 
(keep until 16.04 LTS)
   * Ensure that we only look at the LOCAL setting during boot, and do no 
actual drift correction at boot, as the kernel does that by itself.
   * grep the archive for software which might directly look at or even write 
that file (Ubuntu specific config tools and the like).

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

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

[Touch-packages] [Bug 1541532] Re: migrate UTC setting from /etc/default/rcS to adjtime

** Changed in: util-linux (Ubuntu)
   Status: New => In Progress

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

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

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

Title:
  migrate UTC setting from  /etc/default/rcS to adjtime

Status in installation-guide package in Ubuntu:
  Fix Released
Status in lupin package in Ubuntu:
  New
Status in mbr package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in sysvinit package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in mbr package in Debian:
  Unknown

Bug description:
  This has been an Ubuntu delta in systemd and perhaps other Ubuntu
  packages for a long time. But /etc/default/rcS is a SysV-ism, and no
  other setting in there is relevant. Steps:

   * Bump the version guard in systemd.conf for migrating the actual setting 
(keep until 16.04 LTS)
   * Ensure that we only look at the LOCAL setting during boot, and do no 
actual drift correction at boot, as the kernel does that by itself.
   * grep the archive for software which might directly look at or even write 
that file (Ubuntu specific config tools and the like).

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

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

[Touch-packages] [Bug 1542025] Re: Show warning on upgrade if there are /etc/init/*.override files

OK. Packages don't have a good way of presenting such a warning, so this
would need to go into the release upgrader.

** Summary changed:

- Transition from upstart to systemd should honor /etc/init/*.override
+ Show warning on upgrade if there are /etc/init/*.override files

** Package changed: systemd (Ubuntu) => ubuntu-release-upgrader (Ubuntu)

** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Won't Fix => Triaged

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

Title:
Show warning on upgrade if there are /etc/init/*.override files

Status in ubuntu-release-upgrader package in Ubuntu:
Triaged

Bug description:
While upgrading from 14.04 to 16.04, I noticed that all of my
previously disabled services got started again.

I disabled them by putting "manual" in e.g. /etc/init/isc-dhcp-
server.conf - which is the "right" way I think. Luckily, there was no
harm in my case, but this can put many people in risk by e.g. letting
starting server services which are then accessible outside or even
disrupt networks (like dhcp-servers). So in my oppinion the transition
to systemd should honor "manual" flags in .override files - or at
least warn if there are .override files.

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

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

[Touch-packages] [Bug 1531928] Re: [Xenial] root=PARTUUID= is not recognized as valid syntax.

This bug was fixed in the package initramfs-tools - 0.122ubuntu1

---
initramfs-tools (0.122ubuntu1) xenial; urgency=medium

  * Merge with Debian v0.122, known to fix:
- root=PARTUUID= is not recognized as valid syntax
  (LP: #1531928)
  * Merge with Debian v0.122 (LP: #1541508), remaining changes:
- Set takeover=1 in update-initramfs.
- Drop hooks/keymap and associated code; console-setup takes care of
  this in Ubuntu.
- Add a new 'fixrtc' script that tries to set the system clock forward
  based on the last mount time of the root disk; without this kludge,
  systems without a working RTC will end up in a perpetual reboot loop.
- Set hostname at boot, for the benefit of mdadm autoassembly.
- Don't display "Loading, please wait..." message when 'quiet' is in
  /proc/cmdline.
- Ignore errors from iscan and iscan-data hooks.
- Allow scripts and hooks to specify OPTION=VAR, and unless VAR is set
  to something other than "n", the script will not be included.
- Restore the framebuffer hook and script, copying KMS and other
  framebuffer drivers into the initramfs, but make them optional; you
  need to set FRAMEBUFFER=y for these to be included.
- Add hwaddr= alias for BOOTIF= for compatibility.
- When receiving "recovery" on cmdline, start upstart with --startup-
  event=recovery (LP: #575469)
- Make /etc/mtab a symlink to /proc/mounts on startup, since e.g.
  current ntfs-3g doesn't work otherwise.
- Mount /dev with the default tmpfs size rather than sourcing udev.conf.
- Automatically blacklist vga16fb when vga= or video= specified on
  kernel command-line.
- Add Hyper-V paravirtualised device drivers to the initramfs to allow
  booting of stock images in a Hyper-V guest. (LP: #917135)
- Add mountroot failure support, to allow meaningful messages when no
  root device can be found.
- Retain netboot= compatibility option.
- Breaks: mountall (<< 2.0~)
- Retain cryptopts= compatibility option.
- Use busybox-initramfs for Depends.
- Add vfat modules to the initramfs.
- Maintain compatibility with pre- /run configurations
- Use gzip from busybox instead of klibc.  Depend on busybox-initramfs
  (>= 1:1.13.3-1ubuntu5) to ensure that we have it.
- Sync the mount options for /run from /lib/init/fstab (LP: #1152744)
- Increase rootdelay to 180s on powerpc/ppc64/ppc64el (LP: #1326199)
- fixrtc: wait for udev to settle to expose device symlinks
- fixrtc: handle hwclock -s failures safely
- fixrtc: support busybox, handle last mount time on system partition,
  expose fs create time (LP: #1420473)
- fixrtc: avoid using xargs, wait-for-root before examining
- fixrtc: suppress /dev/ram as a root when using systempart (LP:
  #1443329)
- ppc64el: enable PowerPC NX Crypto Coprocessor
- resume: only resume when the partition contains a resume image
- resume: announce resume via plymouth if available
- Don't load keymaps unless we're loading a framebuffer; but set the
  keymap before giving a root shell.
- Add new initramfs-tools-bin package containing a binary that uses
  libudev to wait for udev to create the udev device, or wait for udev
  to finish processing if we catch it in the act, and returns the
  filesystem type as already probed by udev.
- Incorporate rzscontrol from compcache so that we can control current
  ramzswap devices.
- Support loading compcache from the initramfs.
- debian/control: update Vcs-* links for Ubuntu.
- hook-functions: fix PowerPC NX Crypto Coprocessor support (LP:
  #1454687)
- Drop: Maintain compatibility with pre- /run configurations (LP:
  #1485752)
- Drop: Ignore errors from iscan and iscan-data hooks (LP: #1485562)
- init: Mount /dev with "nosuid" Thanks to Daniel (LP: #1450960)
- import direct archive upload 0.120ubuntu6
- add squashfs to list of 'most' modules (LP: #1501834)
- drop Breaks: against upstart as we use it in user sessions.
- support mounting of loopback devices via loop*= parameters
- local_device_setup: use wait-for-root if it supports the device
  alias type

 -- Andy Whitcroft   Mon, 25 Jan 2016 16:08:12 +

** Changed in: initramfs-tools (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Xenial] root=PARTUUID=  is not recognized as valid syntax.

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  As per kernel source init/do_mounts.c root=PARTUUID= is acceptable 
format to pass root= option on command line to boot a system. But due to a bug 
in initramfs-tools this syntax does not work 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801154

  /*

[Touch-packages] [Bug 1541508] Re: initramfs-tools: merge debian v0.122

This bug was fixed in the package initramfs-tools - 0.122ubuntu1

---
initramfs-tools (0.122ubuntu1) xenial; urgency=medium

  * Merge with Debian v0.122, known to fix:
- root=PARTUUID= is not recognized as valid syntax
  (LP: #1531928)
  * Merge with Debian v0.122 (LP: #1541508), remaining changes:
- Set takeover=1 in update-initramfs.
- Drop hooks/keymap and associated code; console-setup takes care of
  this in Ubuntu.
- Add a new 'fixrtc' script that tries to set the system clock forward
  based on the last mount time of the root disk; without this kludge,
  systems without a working RTC will end up in a perpetual reboot loop.
- Set hostname at boot, for the benefit of mdadm autoassembly.
- Don't display "Loading, please wait..." message when 'quiet' is in
  /proc/cmdline.
- Ignore errors from iscan and iscan-data hooks.
- Allow scripts and hooks to specify OPTION=VAR, and unless VAR is set
  to something other than "n", the script will not be included.
- Restore the framebuffer hook and script, copying KMS and other
  framebuffer drivers into the initramfs, but make them optional; you
  need to set FRAMEBUFFER=y for these to be included.
- Add hwaddr= alias for BOOTIF= for compatibility.
- When receiving "recovery" on cmdline, start upstart with --startup-
  event=recovery (LP: #575469)
- Make /etc/mtab a symlink to /proc/mounts on startup, since e.g.
  current ntfs-3g doesn't work otherwise.
- Mount /dev with the default tmpfs size rather than sourcing udev.conf.
- Automatically blacklist vga16fb when vga= or video= specified on
  kernel command-line.
- Add Hyper-V paravirtualised device drivers to the initramfs to allow
  booting of stock images in a Hyper-V guest. (LP: #917135)
- Add mountroot failure support, to allow meaningful messages when no
  root device can be found.
- Retain netboot= compatibility option.
- Breaks: mountall (<< 2.0~)
- Retain cryptopts= compatibility option.
- Use busybox-initramfs for Depends.
- Add vfat modules to the initramfs.
- Maintain compatibility with pre- /run configurations
- Use gzip from busybox instead of klibc.  Depend on busybox-initramfs
  (>= 1:1.13.3-1ubuntu5) to ensure that we have it.
- Sync the mount options for /run from /lib/init/fstab (LP: #1152744)
- Increase rootdelay to 180s on powerpc/ppc64/ppc64el (LP: #1326199)
- fixrtc: wait for udev to settle to expose device symlinks
- fixrtc: handle hwclock -s failures safely
- fixrtc: support busybox, handle last mount time on system partition,
  expose fs create time (LP: #1420473)
- fixrtc: avoid using xargs, wait-for-root before examining
- fixrtc: suppress /dev/ram as a root when using systempart (LP:
  #1443329)
- ppc64el: enable PowerPC NX Crypto Coprocessor
- resume: only resume when the partition contains a resume image
- resume: announce resume via plymouth if available
- Don't load keymaps unless we're loading a framebuffer; but set the
  keymap before giving a root shell.
- Add new initramfs-tools-bin package containing a binary that uses
  libudev to wait for udev to create the udev device, or wait for udev
  to finish processing if we catch it in the act, and returns the
  filesystem type as already probed by udev.
- Incorporate rzscontrol from compcache so that we can control current
  ramzswap devices.
- Support loading compcache from the initramfs.
- debian/control: update Vcs-* links for Ubuntu.
- hook-functions: fix PowerPC NX Crypto Coprocessor support (LP:
  #1454687)
- Drop: Maintain compatibility with pre- /run configurations (LP:
  #1485752)
- Drop: Ignore errors from iscan and iscan-data hooks (LP: #1485562)
- init: Mount /dev with "nosuid" Thanks to Daniel (LP: #1450960)
- import direct archive upload 0.120ubuntu6
- add squashfs to list of 'most' modules (LP: #1501834)
- drop Breaks: against upstart as we use it in user sessions.
- support mounting of loopback devices via loop*= parameters
- local_device_setup: use wait-for-root if it supports the device
  alias type

 -- Andy Whitcroft   Mon, 25 Jan 2016 16:08:12 +

** Changed in: initramfs-tools (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  initramfs-tools: merge debian v0.122

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Merge up with Debian v0.122 release.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubsc

[Touch-packages] [Bug 1542025] Re: Transition from upstart to systemd should honor /etc/init/*.override

Sorry, I think you missunterstood me ;-)

I meant NO reading upstart scripts from systemd, I meant a "big fat
warning" during the system upgrade(!) if there are .override files - and
perhaps a knob which disables services which were disabled in upstart.
But the most important is the "big fat warning".

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

Title:
  Transition from upstart to systemd should  honor /etc/init/*.override

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  While upgrading from 14.04 to 16.04, I noticed that all of my
  previously disabled services got started again.

  I disabled them by putting "manual" in e.g. /etc/init/isc-dhcp-
  server.conf - which is the "right" way I think. Luckily, there was no
  harm in my case, but this can put many people in risk by e.g. letting
  starting server services which are then accessible outside or even
  disrupt networks (like dhcp-servers). So in my oppinion the transition
  to systemd should honor "manual" flags in .override files - or at
  least warn if there are .override files.

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

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

[Touch-packages] [Bug 1534682] Re: Not requesting desktop content when connected to monitor

2016-02-04 Thread Michał Sawicz

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

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

Title:
  Not requesting desktop content when connected to monitor

Status in Canonical System Image:
  Triaged
Status in Canonical Pocket Desktop:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The ua string is supposed to change based on screensize and other
  hueristics, but this is not happening. Getting mobile ua string
  always, even when connected to monitor via slimport

  using this build:
  (r112) ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu-pd

  Not seeing any messages in the browser log when I plug/unplug the
  monitor

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

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

[Touch-packages] [Bug 1534682] Re: Not requesting desktop content when connected to monitor

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => ww04-2016

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

Title:
  Not requesting desktop content when connected to monitor

Status in Canonical System Image:
  Triaged
Status in Canonical Pocket Desktop:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The ua string is supposed to change based on screensize and other
  hueristics, but this is not happening. Getting mobile ua string
  always, even when connected to monitor via slimport

  using this build:
  (r112) ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu-pd

  Not seeing any messages in the browser log when I plug/unplug the
  monitor

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

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

[Touch-packages] [Bug 1532868] Re: [Avila] OSK generates random touch events after switching from physical keyboard

** No longer affects: canonical-devices-system-image

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

Title:
  [Avila] OSK generates random touch events after switching from
  physical keyboard

Status in The Avila project:
  Invalid
Status in Canonical Pocket Desktop:
  Invalid
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Steps:
  connect a USB keyboard 
  Use for a bit
  Disconnect keyboard
  try using the onboard keyboard

  Result:
  The keyboard starts producing random touch events as soon as you try to use 
it.

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

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

[Touch-packages] [Bug 1538591] Re: Add a control to toggle between windowed and staged modes

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

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

Title:
  Add a control to toggle between windowed and staged modes

Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in Ubuntu UX:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  A new toggle will be added to the rotation (to be display) indicator
  to allow the user to switch between windowed (for desktop) and staged
  (for phone and tablet)

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

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

[Touch-packages] [Bug 1535377] Re: /usr/bin/unity8-dash:11:std::__shared_count:std::__shared_ptr:std::shared_ptr:ResultsMap::rebuild:scopes_ng::ResultsModel::addUpdateResults

** Branch linked: lp:~chihchun/unity-scopes-shell/lp1535377

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

Title:
  
/usr/bin/unity8-dash:11:std::__shared_count:std::__shared_ptr:std::shared_ptr:ResultsMap::rebuild:scopes_ng::ResultsModel::addUpdateResults

Status in unity-scopes-shell package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+16.04.20151208.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/17821ac9570b7bdcb4408aecef2d63a35e709dd9
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1535377/+subscriptions

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

[Touch-packages] [Bug 1534682] Re: Not requesting desktop content when connected to monitor

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

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

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

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

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

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

Title:
  Not requesting desktop content when connected to monitor

Status in Canonical System Image:
  Triaged
Status in Canonical Pocket Desktop:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The ua string is supposed to change based on screensize and other
  hueristics, but this is not happening. Getting mobile ua string
  always, even when connected to monitor via slimport

  using this build:
  (r112) ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu-pd

  Not seeing any messages in the browser log when I plug/unplug the
  monitor

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

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

[Touch-packages] [Bug 1536714] Re: Fix the user login experience on the greeter

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

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

Title:
  Fix the user login experience on the greeter

Status in The Avila project:
  New
Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in livecd-rootfs package in Ubuntu RTM:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  In Progress

Bug description:
  The current UX for tablets or when converged with a mouse attached is
  a bit of a placeholder showing the default phablet user.

  We need to support two modes of the greeter that scales according to
  the available input devices. The first one is one that works across
  mobile and tablet devices in non-mouse connected / touch-centric
  state. Unlocking with no mouse connected would be exactly as it is
  today on the phone, which displays the Infographic until you touch the
  screen, and then you get a message that says "swipe to unlock" If you
  don't have a pin code set, the screen unlocks. if you have a pincode
  set, the touch pincode-entry pad appears.

  If a mouse is connected, however, you get the more "desktop-friendly"
  greeter with the infographic, user-name and password entry field (just
  like what we have today) on tablet.  If the user taps or clicks into
  the password edit box, the OSK is popped up (unless an external
  keyboard is also attached). If no password or pincode has been set,
  then instead of the password entry field, you would instead have a
  "login" button that clears the greeter.

  On a tablet with mouse connected and no pincode set, the user could
  either swipe away the greeter or tap on the login button. If the user
  has a password/pincode set and attempts to swipe away the greeter, we
  should put up a hint message asking the user to enter their
  password/pincode to continue.

  This incremental enhancement to recognize the mouse is more consistent
  with convergence because tablets are mobile devices, and if no mouse
  is attached, we should follow a touch-centric approach. In a mouse-
  connected state, we can assume the user will be favoring that device.

  ===

  Immediate problem: "phablet" name on the greeter login list. A bigger
  refactoring of the greeter for bigger screens will follow.

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

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

[Touch-packages] [Bug 1534682] Re: Not requesting desktop content when connected to monitor

** No longer affects: canonical-devices-system-image

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

Title:
  Not requesting desktop content when connected to monitor

Status in Canonical System Image:
  Triaged
Status in Canonical Pocket Desktop:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The ua string is supposed to change based on screensize and other
  hueristics, but this is not happening. Getting mobile ua string
  always, even when connected to monitor via slimport

  using this build:
  (r112) ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu-pd

  Not seeing any messages in the browser log when I plug/unplug the
  monitor

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

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

[Touch-packages] [Bug 1486284] Re: /usr/bin/powerd:6:__gnu_cxx::__verbose_terminate_handler:cxxabiv1::terminate:std::terminate:std::thread::~thread:std::default_delete

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

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

Title:
  
/usr/bin/powerd:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:std::thread::~thread:std::default_delete

Status in Canonical System Image:
  Fix Committed
Status in powerd package in Ubuntu:
  In Progress

Bug description:
  Number 2 on errors.u.c over past week on rc-proposed. Frequency
  increased significantly with 0.16+15.04.20160111.1-0ubuntu1

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

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

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

[Touch-packages] [Bug 1541532] Re: migrate UTC setting from /etc/default/rcS to adjtime

> live-build: drop ubuntu-no-adjtime.patch

Actually, this isn't about setting UTC vs. LOCAL, just about the actual
time drift, so this can stay. Dropping task.

** Package changed: installation-guide (Debian) => mbr (Debian)

** Changed in: installation-guide (Ubuntu)
   Status: New => Fix Committed

** No longer affects: live-build (Ubuntu)

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

Title:
  migrate UTC setting from  /etc/default/rcS to adjtime

Status in installation-guide package in Ubuntu:
  Fix Committed
Status in lupin package in Ubuntu:
  New
Status in mbr package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Triaged
Status in sysvinit package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New
Status in mbr package in Debian:
  Unknown

Bug description:
  This has been an Ubuntu delta in systemd and perhaps other Ubuntu
  packages for a long time. But /etc/default/rcS is a SysV-ism, and no
  other setting in there is relevant. Steps:

   * Bump the version guard in systemd.conf for migrating the actual setting 
(keep until 16.04 LTS)
   * Ensure that we only look at the LOCAL setting during boot, and do no 
actual drift correction at boot, as the kernel does that by itself.
   * grep the archive for software which might directly look at or even write 
that file (Ubuntu specific config tools and the like).

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

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

[Touch-packages] [Bug 1541532] Re: migrate UTC setting from /etc/default/rcS to adjtime

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

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

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

Title:
  migrate UTC setting from  /etc/default/rcS to adjtime

Status in installation-guide package in Ubuntu:
  New
Status in live-build package in Ubuntu:
  New
Status in lupin package in Ubuntu:
  New
Status in mbr package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Triaged
Status in sysvinit package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New
Status in installation-guide package in Debian:
  Unknown

Bug description:
  This has been an Ubuntu delta in systemd and perhaps other Ubuntu
  packages for a long time. But /etc/default/rcS is a SysV-ism, and no
  other setting in there is relevant. Steps:

   * Bump the version guard in systemd.conf for migrating the actual setting 
(keep until 16.04 LTS)
   * Ensure that we only look at the LOCAL setting during boot, and do no 
actual drift correction at boot, as the kernel does that by itself.
   * grep the archive for software which might directly look at or even write 
that file (Ubuntu specific config tools and the like).

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

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

[Touch-packages] [Bug 1541985] Re: package udev 228-5ubuntu2 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1

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

** This bug has been marked a duplicate of bug 1540568
   package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has 
to be enabled to start service udev

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

Title:
  package udev 228-5ubuntu2 failed to install/upgrade: underprocessen
  installerade post-installation-skript gav felkod 1

Status in systemd package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 228-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb  4 19:45:28 2016
  ErrorMessage: underprocessen installerade post-installation-skript gav felkod 
1
  InstallationDate: Installed on 2016-01-29 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=afe7feaf-b274-43a5-b3a7-a6166ca11362 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: systemd
  Title: package udev 228-5ubuntu2 failed to install/upgrade: underprocessen 
installerade post-installation-skript gav felkod 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1542025] Re: Transition from upstart to systemd should honor /etc/init/*.override

Sorry, we are not  going to implement an upstart parser into systemd,
and there is not even an 1-to-1 correspondence between upstart jobs and
systemd units. So this can only ever be a heuristics, and "working in
some cases" is worse (because not predictable)  than "upstart overrides
don't affect systemd units".

The "right way" to disable something in an init system agnostic way is
"update-rc.d myservice disable". This will disable sysv init scripts,
upstart jobs, and systemd units. But it's not realistic to expect that
upstart and systemd can read each other's configuration files, sorry..

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

Title:
  Transition from upstart to systemd should  honor /etc/init/*.override

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  While upgrading from 14.04 to 16.04, I noticed that all of my
  previously disabled services got started again.

  I disabled them by putting "manual" in e.g. /etc/init/isc-dhcp-
  server.conf - which is the "right" way I think. Luckily, there was no
  harm in my case, but this can put many people in risk by e.g. letting
  starting server services which are then accessible outside or even
  disrupt networks (like dhcp-servers). So in my oppinion the transition
  to systemd should honor "manual" flags in .override files - or at
  least warn if there are .override files.

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

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

[Touch-packages] [Bug 1542033] [NEW] avahi-daemon doesn't start

Public bug reported:

While upgrading from 14.04 to 16.04 yesterday, I notived that avahi-
daemon doesn't start.

Log:
Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
-- Subject: Unit avahi-daemon.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit avahi-daemon.service has begun starting up.
Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" 
operation="open" profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" 
pid=13101 comm="avahi-daemon" requested_mask="r" denied_ma
Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 
audit(1454619615.281:301): apparmor="DENIED" operation="open" 
profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" pid=13101 
comm="avahi-da
Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 
audit(1454619615.285:302): apparmor="DENIED" operation="chown" 
profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" pid=13101 
comm="avahi-d
Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" 
operation="chown" profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" 
pid=13101 comm="avahi-daemon" requested_mask="w" denied_m
Feb 04 22:00:15 michis-ibm-haupt avahi-daemon[13101]: Failed to create runtime 
directory /var/run/avahi-daemon/.
Feb 04 22:00:15 michis-ibm-haupt systemd[1]: avahi-daemon.service: Main process 
exited, code=exited, status=255/n/a
Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Failed to start Avahi mDNS/DNS-SD 
Stack.

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

** Package changed: ubuntu => avahi (Ubuntu)

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

Title:
  avahi-daemon doesn't start

Status in avahi package in Ubuntu:
  New

Bug description:
  While upgrading from 14.04 to 16.04 yesterday, I notived that avahi-
  daemon doesn't start.

  Log:
  Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Starting Avahi mDNS/DNS-SD 
Stack...
  -- Subject: Unit avahi-daemon.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit avahi-daemon.service has begun starting up.
  Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" 
operation="open" profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" 
pid=13101 comm="avahi-daemon" requested_mask="r" denied_ma
  Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 
audit(1454619615.281:301): apparmor="DENIED" operation="open" 
profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" pid=13101 
comm="avahi-da
  Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 
audit(1454619615.285:302): apparmor="DENIED" operation="chown" 
profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" pid=13101 
comm="avahi-d
  Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" 
operation="chown" profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" 
pid=13101 comm="avahi-daemon" requested_mask="w" denied_m
  Feb 04 22:00:15 michis-ibm-haupt avahi-daemon[13101]: Failed to create 
runtime directory /var/run/avahi-daemon/.
  Feb 04 22:00:15 michis-ibm-haupt systemd[1]: avahi-daemon.service: Main 
process exited, code=exited, status=255/n/a
  Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Failed to start Avahi 
mDNS/DNS-SD Stack.

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

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

[Touch-packages] [Bug 1475678] Re: Unity8 not informing clients that they are not visible and thus can stop rendering

2016-02-04 Thread Michał Sawicz

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

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

Title:
  Unity8 not informing clients that they are not visible and thus can
  stop rendering

Status in Canonical System Image:
  In Progress
Status in QtMir:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Currently on the phone, apps stop rendering when shell hides them,
  because shell also lifecycle stops the app. App isn't actually told it
  should stop rendering, we just SIGSTOP its process.

  But some apps are not lifecycle stopped, e.g. music. So we should have
  unity8 tell the app to stop rendering.

  
  This will be a multi-step process:
  1. Qtubuntu
  Mir has a attribute to set on surfaces to tell them they are 
visible/occluded: (see mir/include/common/mir_toolkit/common.h)
  mir_surface_attrib_visibility - part of the MirSurfaceAttrib enum. 

  This indicates these possible values:
  typedef enum MirSurfaceVisibility
  {
  mir_surface_visibility_occluded = 0,
  mir_surface_visibility_exposed
  } MirSurfaceVisibility;

  On the client side (qtubuntu), you need to listen for this attribute change, 
and connect it to QWindowSystemInterface::handleExposeEvent() which tells Qt 
how much of a QWindow is being drawn.
  Note there is also a QWindowSystemInterface::handleWindowStateChanged() 
handler, which use use to explicitly set QWindow show/hide, but Qt tends to 
release its GL context on hide, which we may not desire. It may not hurt, worth 
a look.

  2. QtMir
  There are methods on mir::scene::Surface to set and get the MirSurfaceAttrib 
attributes. I think it would make sense to use the pre-existing 
MirSurfaceItem::visible property, so that if a surface is marked visible=false, 
then that will dispatch the mir_surface_visibility_occluded event to the 
client, so it will stop drawing.

  3. Unity8
  Correctly set visible=false when an application surface is occluded, and true 
when visible. QML has no automatic way of doing that (i.e. occlusion detection)

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

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

[Touch-packages] [Bug 1542033] [NEW] avahi-daemon doesn't start

You have been subscribed to a public bug:

While upgrading from 14.04 to 16.04 yesterday, I notived that avahi-
daemon doesn't start.

Log:
Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
-- Subject: Unit avahi-daemon.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit avahi-daemon.service has begun starting up.
Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" 
operation="open" profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" 
pid=13101 comm="avahi-daemon" requested_mask="r" denied_ma
Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 
audit(1454619615.281:301): apparmor="DENIED" operation="open" 
profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" pid=13101 
comm="avahi-da
Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 
audit(1454619615.285:302): apparmor="DENIED" operation="chown" 
profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" pid=13101 
comm="avahi-d
Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" 
operation="chown" profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" 
pid=13101 comm="avahi-daemon" requested_mask="w" denied_m
Feb 04 22:00:15 michis-ibm-haupt avahi-daemon[13101]: Failed to create runtime 
directory /var/run/avahi-daemon/.
Feb 04 22:00:15 michis-ibm-haupt systemd[1]: avahi-daemon.service: Main process 
exited, code=exited, status=255/n/a
Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Failed to start Avahi mDNS/DNS-SD 
Stack.

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

-- 
avahi-daemon doesn't start
https://bugs.launchpad.net/bugs/1542033
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to avahi in Ubuntu.

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

[Touch-packages] [Bug 1541959] Re: implement a software Updater

2016-02-04 Thread Emanuele Antonio Faraone

See this bug

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

Title:
  implement a software Updater

Status in unity8 package in Ubuntu:
  New

Bug description:
  implement an updater software, such as the one in unity 7, in order to update 
the diirettamente packages unity 8 without having to go to unity 7 to upgrade 
packages on unity 8 making it self
  Using: 8.11+16.04.20160129-0ubuntu1

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

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

[Touch-packages] [Bug 953875] Re: Encrypted swap no longer mounted at bootup

2016-02-04 Thread Jason Gerard DeRose

I get the impression this is known and expected, but this problem still
exists in the latest 14.04.4 daily ISOs (which have proposed enabled).

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

Title:
  Encrypted swap no longer mounted at bootup

Status in eCryptfs:
  Fix Released
Status in systemd:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Trusty:
  Triaged
Status in ubiquity source package in Trusty:
  Triaged
Status in ecryptfs-utils source package in Vivid:
  Fix Released
Status in systemd source package in Vivid:
  Fix Released
Status in ubiquity source package in Vivid:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  SUMMARY
  ===
  During installation with "encrypt my home folder" mode, a broken 
/etc/crypttab gets created which defines a non-existing swap device (usually 
"cryptswap1") with a UUID. This will also be put into /etc/fstab. As after 
installation the UUID does not exist, such systems don't have any actual swap.

  UPGRADE FIX
  ===
  An upgrade to Ubuntu 15.04 ("vivid") will detect and comment out these broken 
swap devices from /etc/fstab and /etc/crypttab. If you actually want  to use 
those, do these steps:

   - Find the swap device that was meant to be used in "sudo fdisk -l" (it 
should say "Linux swap" in the last column), remember the device name 
(something like "/dev/sda5")
   - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=)
   - Run "sudo mkswap -U 1234... /dev/sda5", replacing "1234" with the above 
UUID, and /dev/sda5 with the device name from step 1.
   - Edit /etc/crypttab to append ",offset=1024" in the fourth (last) column of 
the cryptswap1 line; ensure that there is *no space* between the 
"cipher=aes-cbc-essiv:sha256" and the appended option. If there is a leading 
"#" in the file, remove that too.
   - If there is a leading "#" in /etc/fstab in the line starting with 
/dev/mapper/cryptswap1 line, remove that.
   - Run "sudo update-initramfs -u".

  
  ORIGINAL REPORT
  ===

  Clean install of 12.04 and with encrypted home for my user. Did all
  updates and now the bootup hangs waiting for swap to become available
  and it never seems to ever finish. The 200GB SSD below is my boot
  drive and root filesystem.

  alan@mesh:~$ sudo swapon -a
  [sudo] password for alan:
  swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory

  alan@mesh:~$ grep swap /etc/fstab
  # swap was on /dev/sdg5 during installation
  #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 
 0   0
  /dev/mapper/cryptswap1 none swap sw 0 0

  alan@mesh:~$ sudo fdisk -l

  Disk /dev/sda: 115.0 GB, 115033153536 bytes
  255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x000ba2ed

     Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  206847  1024007  HPFS/NTFS/exFAT
  /dev/sda2  206848   224671743   1122324487  HPFS/NTFS/exFAT

  Disk /dev/sdb: 200.0 GB, 200049647616 bytes
  255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0xf0fa0806

     Device Boot  Start End  Blocks   Id  System
  /dev/sdb12048   349304831   1746513927  HPFS/NTFS/exFAT
  /dev/sdb2   374722558   390721535 79994895  Extended
  /dev/sdb3   *   349304832   37472051112707840   83  Linux
  /dev/sdb5   374722560   390721535 7999488   82  Linux swap / Solaris

  Partition table entries are not in disk order

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libecryptfs0 96-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 13 09:56:56 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120215)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ecryptfs-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1542025] [NEW] Transition from upstart to systemd should honor /etc/init/*.override

Public bug reported:

While upgrading from 14.04 to 16.04, I noticed that all of my previously
disabled services got started again.

I disabled them by putting "manual" in e.g. /etc/init/isc-dhcp-
server.conf - which is the "right" way I think. Luckily, there was no
harm in my case, but this can put many people in risk by e.g. letting
starting server services which are then accessible outside or even
disrupt networks (like dhcp-servers). So in my oppinion the transition
to systemd should honor "manual" flags in .override files - or at least
warn if there are .override files.

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

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

Title:
  Transition from upstart to systemd should  honor /etc/init/*.override

Status in systemd package in Ubuntu:
  New

Bug description:
  While upgrading from 14.04 to 16.04, I noticed that all of my
  previously disabled services got started again.

  I disabled them by putting "manual" in e.g. /etc/init/isc-dhcp-
  server.conf - which is the "right" way I think. Luckily, there was no
  harm in my case, but this can put many people in risk by e.g. letting
  starting server services which are then accessible outside or even
  disrupt networks (like dhcp-servers). So in my oppinion the transition
  to systemd should honor "manual" flags in .override files - or at
  least warn if there are .override files.

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

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

[Touch-packages] [Bug 1542021] [NEW] ibtinyxml2.6.2v5 replaces libtinyxml2.6.2, but doesn't provide it