Re: [Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-10-10 Thread Luke Yelavich
Ok, I am pretty sure it is patch 0502 in the bluez5 patch set. If I
enable only 0501 and 0502, and move some code required by 0502 from 0506
and build pulse, enabling 0502 causes Pulse to assert as previously
logged. Am in the process of digging through that patch to work out how
it changes things such that things don't work as they should... And I
don't think its just one patch hunk either. I will update when I have
more info.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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


[Touch-packages] [Bug 1631955] Re: Update e-d-s to 3.22.1

2016-10-10 Thread Jeremy Bicha
I installed the evolution-data-server packages from yakkety-proposed. I then 
rebooted (because e-d-s sometimes keeps services running even after log out?). 
I tried these apps and they appeared to work as well as before:
- evolution
- gnome-calendar
- gnome-contacts
- gnome-shell and its built-in calendar

I set the block-proposed tag because I believe it would have
automatically been promoted to the regular yakkety archives today
without that tag. I'll let the release team decide if they want this
update now or would rather wait a few more days.

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

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

Title:
  Update e-d-s to 3.22.1

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  ==
  There's a new release of evolution-data-server (e-d-s) from the stable 3.22 
branch. This release
  - Update translations
  - Fixes some console warnings caused by search folders when quitting an app
  - Attempts to fix Google Authentication token expired issue. The bug was 
re-opened upstream because the fixes worked for one person but apparently 
weren't enough for another.
  I experienced the Google expired token bug myself but I haven't verified yet 
whether the update fixes the issue. See attached GNOME bug.

  Since e-d-s is an important library/service used by several apps and
  shipped on all Ubuntu desktop flavors (I think), I suggest we not try
  to rush this into yakkety at the last moment before release, but
  handle it like a regular SRU.

  The e-d-s update is required to update evolution from 3.22 to 3.22.1.

  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22
  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22

  Test Case
  =
  Check several of evolution-data-server's reverse-dependencies to ensure 
they're still working.

  $ reverse-depends src:evolution-data-server

  Regression Potential
  
  Basically only search folders and Google authentication were touched in this 
update, so check those for problems. The Evolution stack is big and complex but 
this is a fairly minor stable release update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evolution-data-server 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 09:23:02 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1631955/+subscriptions

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


[Touch-packages] [Bug 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2016-10-10 Thread Daniel van Vugt
** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

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

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

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

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


[Touch-packages] [Bug 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2016-10-10 Thread mir-ci-bot
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0

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

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

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

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

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

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

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


[Touch-packages] [Bug 125734] Re: Firefox scrollbar doesn't use the "infinite size" usability effect

2016-10-10 Thread Hans109h
Nick Welch, your soultion helped me out a lot, however I'm also having
the same problem with Thunderbird.  Any solution there?

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

Title:
  Firefox scrollbar doesn't use the "infinite size" usability effect

Status in firefox package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Invalid

Bug description:
  Note that this is a regression - I'm pretty sure that previous
  versions of Ubuntu and/or Firefox had this right.

  Description of the problem:

  In user interface design (unfortunately not among mist Open Source
  developers ) it's a wide known fact that objects that are located at a
  screen edge are easier to target with the mouse - this is the main
  reason that MacOS menus are always at the top of the screen.

  That's because you can simply slam the mouse pointer in the general
  direction of an edge or corner of the screen and it will stop at the
  edge - then you can interact with the object by clicking dragging and
  so on.

  Locating UI objects at the edges of the screen is therefore a desired
  practice for most commonly used objects , so interacting with them
  takes less effort - it's a significant usability gain.

  In firefox's vertical scrollbar context it means one can easily target
  the scrollbar and scroll the page without precisely targeting the
  scrollbar - one simply moves the mouse far to the right and it's on
  the scollbar then.

  This hase definitely worked before. Now it doesn't - when I reach the
  screen edge, I have to retract the mouse at least one pixel back to
  the left to be able to drag the scollbar. It takes much more effort
  now and gives an uncomfortable feeling when I use Firefox. To be fair,
  Konqueror did never do this right, but there's a bug in their
  Bugzilla: https://bugs.kde.org/show_bug.cgi?id=96727

  This effect is known as "mile high menu bar" or "infinite size
  widget". To quote some experts:

  http://www.asktog.com/columns/022DesignedToGiveFitts.html

  "Remember that Fitts' Law states that access time is a function of
  distance and target size. If the target size is larger, then the time
  is reduced. It is reduced for a simple reason: the user need not slow
  down when approaching the target for fear of overshooting.

  Now consider the screen edge. How deep is the target? If it were
  really only the one pixel it appears, it would be very hard to hit.
  However, the screen edge is, for all practical purposes, infinitely
  deep. It doesn't matter how fast that mouse is going when it hits the
  screen edge, that pointer absolutely will not overshoot. Having to hit
  a pixel two pixels in from the screen edge takes much longer than
  hitting the edge itself. Use that edge. It is your friend."

  http://www.joelonsoftware.com/uibook/chapters/fog63.html

  "When the Macintosh was new, Bruce "Tog" Tognazzini wrote a column in Apple's
  developer magazine on UI. In his column, people wrote in with lots of 
interesting
  UI design problems, which he discussed. These columns continue to this day on
  his web site. They've also been collected and embellished in a couple of great
  books, like Tog on Software Design, which is a lot of fun and a great 
introduction
  to UI design. (Tog on Interface was even better, but it's out of print.)

  
  Tog invented the concept of the mile high menu bar to explain why the menu bar
  on the Macintosh, which is always glued to the top of the physical screen, is
  so much easier to use than menu bars on Windows, which appear inside each 
application
  window. When you want to point to the File menu on Windows, you have a target
  about half an inch wide and a quarter of an inch high to acquire. You must 
move
  and position the mouse fairly precisely in both the vertical and the 
horizontal
  dimensions.

  
  But on a Macintosh, you can slam the mouse up to the top of the screen, 
without
  regard to how high you slam it, and it will stop at the physical edge of the
  screen - the correct vertical position for using the menu. So, effectively,
  you have a target that is still half an inch wide, but a mile high. Now you
  only need to worry about positioning the cursor horizontally, not vertically,
  so the task of clicking on a menu item is that much easier.

  
  Based on this principle, Tog has a pop quiz: what are the five spots on the
  screen that are easiest to acquire (point to) with the mouse? The answer: all
  four corners of the screen (where you can literally slam the mouse over there
  in one fell swoop without any pointing at all), plus, the current position of
  the mouse, because it's already there."

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1612191] Re: net-tools upstream package is outdated ?

2016-10-10 Thread Launchpad Bug Tracker
[Expired for net-tools (Ubuntu) because there has been no activity for
60 days.]

** Changed in: net-tools (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  net-tools upstream package is outdated ?

Status in net-tools package in Ubuntu:
  Expired

Bug description:
  Hello,
  while looking to the netstat man page i found out that apparently ubuntu is 
still using an old version of net tools upstream package, which is still 
pointing to berlios.de . As far as i know berlios.de is now closed and the 
packages have been moved to sourceforge.net where they are still maintained: 
https://sourceforge.net/projects/net-tools/

  Could you please clarify me the reason behind having what it appears
  to be an outdated upstream package?

  
  Many thanks
  Samuele

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

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


[Touch-packages] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

2016-10-10 Thread Daniel van Vugt
** No longer affects: lightdm (Ubuntu)

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

Title:
  modesetting driver unbearably slow on intel graphics

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkey, I found the graphics performance of my
  MacBookPro12,1 (13", 2015, retina/hidpi display) became unbearably
  slow - switching workspaces, playing games, even just scrolling web
  browser tabs was visibly slower. The computer became constantly warm,
  and battery life dropped.

  Switching from using from modesetting back to the intel driver fixed
  these problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 11 11:47:47 2016
  DistUpgraded: 2016-10-05 14:48:30,702 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f]
  InstallationDate: Installed on 2015-07-22 (446 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-21-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
i915.fastboot=1 vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (5 days ago)
  dmi.bios.date: 09/28/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B14.1509281135
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B14.1509281135:bd09/28/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

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


Re: [Touch-packages] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

2016-10-10 Thread Michael Gratton
On Tue, Oct 11, 2016 at 2:35 PM, Daniel van Vugt 
 wrote:
> I have two theories at least:
> 1. modesetting can't deal with hiDPI very well; or
> 2. compiz/unity7 is falling back to software rendering under the 
> modesetting driver.
> 
> Can you please test #2? Just tap the Super key to open the Unity7 
> dash.
> Is it translucent or solid coloured?
> 
> Also, failure to set correct permissions for /dev/dri/* I think is
> lightdm's problem. So adding lightdm here.

Ah, apologies, this is on Ubuntu GNOME, so I'm running gnome-shell and 
gdm.

-- 
⊨ Michael Gratton, Percept Wrangler.
⚙ 

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

Title:
  modesetting driver unbearably slow on intel graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkey, I found the graphics performance of my
  MacBookPro12,1 (13", 2015, retina/hidpi display) became unbearably
  slow - switching workspaces, playing games, even just scrolling web
  browser tabs was visibly slower. The computer became constantly warm,
  and battery life dropped.

  Switching from using from modesetting back to the intel driver fixed
  these problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 11 11:47:47 2016
  DistUpgraded: 2016-10-05 14:48:30,702 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f]
  InstallationDate: Installed on 2015-07-22 (446 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-21-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
i915.fastboot=1 vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (5 days ago)
  dmi.bios.date: 09/28/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B14.1509281135
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B14.1509281135:bd09/28/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

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


[Touch-packages] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

2016-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  modesetting driver unbearably slow on intel graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkey, I found the graphics performance of my
  MacBookPro12,1 (13", 2015, retina/hidpi display) became unbearably
  slow - switching workspaces, playing games, even just scrolling web
  browser tabs was visibly slower. The computer became constantly warm,
  and battery life dropped.

  Switching from using from modesetting back to the intel driver fixed
  these problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 11 11:47:47 2016
  DistUpgraded: 2016-10-05 14:48:30,702 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f]
  InstallationDate: Installed on 2015-07-22 (446 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-21-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
i915.fastboot=1 vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (5 days ago)
  dmi.bios.date: 09/28/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B14.1509281135
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B14.1509281135:bd09/28/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

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


[Touch-packages] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

2016-10-10 Thread Daniel van Vugt
I have two theories at least:
1. modesetting can't deal with hiDPI very well; or
2. compiz/unity7 is falling back to software rendering under the modesetting 
driver.

Can you please test #2? Just tap the Super key to open the Unity7 dash.
Is it translucent or solid coloured?

Also, failure to set correct permissions for /dev/dri/* I think is
lightdm's problem. So adding lightdm here.

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

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

Title:
  modesetting driver unbearably slow on intel graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkey, I found the graphics performance of my
  MacBookPro12,1 (13", 2015, retina/hidpi display) became unbearably
  slow - switching workspaces, playing games, even just scrolling web
  browser tabs was visibly slower. The computer became constantly warm,
  and battery life dropped.

  Switching from using from modesetting back to the intel driver fixed
  these problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 11 11:47:47 2016
  DistUpgraded: 2016-10-05 14:48:30,702 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f]
  InstallationDate: Installed on 2015-07-22 (446 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-21-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
i915.fastboot=1 vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (5 days ago)
  dmi.bios.date: 09/28/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B14.1509281135
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B14.1509281135:bd09/28/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

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


[Touch-packages] [Bug 1612863] Re: Intel graphics drivers on 16.10 , choppy and not smooth

2016-10-10 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1632165 ***
https://bugs.launchpad.net/bugs/1632165

Confirmed by duplicate.

But see also Chrome bug 1615871.

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

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

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Intel  graphics drivers on 16.10 , choppy and not smooth
+ Modesetting driver on intel in 16.10 is choppy and not smooth

** Tags added: performance

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

Title:
  Modesetting driver on intel in 16.10 is choppy and not smooth

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Upgraded a working version of 16.04 to 16.10 Ubuntu . Intel graphics chip 
(details to arrive later ) 
   When running gfx gears fps is a healthy 48-58 fps , but when other movements 
are made on screen this drops terrible . Chrome browser is extremely slow to 
use . Firefox also slow but faster that chrome .
   Installed latest Intel drivers & Mesa drivers ( version to arrive later) 
from compiled sourced .

   This is a i7 with 16 gig of ram 128 gig ssd and 1tb home dir .

   Wobberly Windows is rough and jerky . Other symptoms are opening
  terminal from unitity dock takes ages . And usining nautilus can
  freeze the screen for several seconds .

   Please advis On info required to help with this .

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

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


[Touch-packages] [Bug 1632077] Re: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()

2016-10-10 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1584894 ***
https://bugs.launchpad.net/bugs/1584894

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


** This bug has been marked a duplicate of bug 1584894
   unity-system-compositor crashes on start-up with "Mir fatal error: Failed to 
schedule page flip" on VirtualBox Graphics Adapter and QEMU

** Information type changed from Private to Public

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

Title:
  unity-system-compositor crashed with SIGABRT in
  mir::fatal_error_abort()

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  1) Ubuntu 16.10 ***
  2) unity-system-compositor 0.7.1+16.10.20160909.1-0ubuntu1 
  3) At login screen, I have tried to enter in Unity 8 session and I expected 
to enter in it.
  4) Bring back at login screen

  
  *** System virtualized under VirtualBox 5.1.6

  The issue report has appeared after a new login in a Unity 7 session.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.7.1+16.10.20160909.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Oct 10 21:11:22 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2015-12-22 (293 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   mir::fatal_error_abort(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.6
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGABRT in 
mir::fatal_error_abort()
  UpgradeStatus: Upgraded to yakkety on 2016-10-07 (3 days ago)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.70-1
  version.lightdm: lightdm 1.19.5-0ubuntu1
  version.mesa: libegl1-mesa-dev 12.0.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1632077/+subscriptions

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


[Touch-packages] [Bug 1575516] Re: Mir is just a black screen and mouse cursor on Nvidia GTX 900 (and sometimes "Failed to schedule page flip")

2016-10-10 Thread Daniel van Vugt
** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

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

Title:
  Mir is just a black screen and mouse cursor on Nvidia GTX 900 (and
  sometimes "Failed to schedule page flip")

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  Nvidia (using nouveau not binary drivers): Mir servers freeze on
  start-up for 30 seconds, and then you get just a black screen and
  mouse cursor (which at least moves).

  Using lp:mir r3480 ...

  [2016-04-27 15:20:19.369559] mirserver: Selected driver: mir:mesa-kms 
(version 0.22.0)
  nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -22
  [2016-04-27 15:20:51.934145] mirserver: Using hardware cursor
  [2016-04-27 15:20:51.937691] mirserver: Initial display configuration:
  [2016-04-27 15:20:51.937703] mirserver:   0.36: unused DVI-I
  [2016-04-27 15:20:51.937713] mirserver:   0.39: DVI-D 24.0" 520x320mm
  [2016-04-27 15:20:51.937722] mirserver: Current mode 1920x1200 59.95Hz
  [2016-04-27 15:20:51.937731] mirserver: Preferred mode 1920x1200 
59.95Hz
  [2016-04-27 15:20:51.937740] mirserver: Logical position +0+0
  [2016-04-27 15:20:51.937781] mirserver:   0.41: unused HDMI-A
  [2016-04-27 15:20:51.937799] mirserver:   0.43: unused DisplayPort
  [2016-04-27 15:20:51.937972] mircommon: Loading modules from: 
bin/../lib/server-modules/
  [2016-04-27 15:20:51.938015] mircommon: Loading module: 
bin/../lib/server-modules/graphics-android.so.9
  [2016-04-27 15:20:51.938107]  mircommon: Failed to load module: 
bin/../lib/server-modules/graphics-android.so.9 (error was:libhardware.so.2: 
cannot open shared object file: No such file or directory)
  [2016-04-27 15:20:51.938119] mircommon: Loading module: 
bin/../lib/server-modules/graphics-mesa-kms.so.9
  [2016-04-27 15:20:51.938142] mircommon: Loading module: 
bin/../lib/server-modules/server-mesa-x11.so.9
  [2016-04-27 15:20:51.938536] mircommon: Loading module: 
bin/../lib/server-modules/input-evdev.so.5
  [2016-04-27 15:20:51.955316] mirserver: Selected input driver: 
mir:evdev-input (version: 0.22.0)
  [2016-04-27 15:20:51.955500] mirserver: Mir version 0.22.0
  [2016-04-27 15:20:51.962627] GLRenderer: EGL vendor: Mesa Project
  [2016-04-27 15:20:51.962645] GLRenderer: EGL version: 1.4 (DRI2)
  [2016-04-27 15:20:51.962651] GLRenderer: EGL client APIs: OpenGL OpenGL_ES 
OpenGL_ES2 OpenGL_ES3
  [2016-04-27 15:20:51.962657] GLRenderer: EGL extensions: EGL_EXT_buffer_age 
EGL_EXT_image_dma_buf_import EGL_KHR_create_context 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context 
EGL_MESA_configless_context EGL_MESA_image_dma_buf_export
  [2016-04-27 15:20:51.962670] GLRenderer: GL vendor: VMware, Inc.
  [2016-04-27 15:20:51.962679] GLRenderer: GL renderer: Gallium 0.4 on llvmpipe 
(LLVM 3.8, 256 bits)
  [2016-04-27 15:20:51.962688] GLRenderer: GL version: OpenGL ES 3.0 Mesa 11.2.0
  [2016-04-27 15:20:51.962697] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00

  lspci:
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] 
(rev a1)

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

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


Re: [Touch-packages] [Bug 1623763] Re: GTK Inspector Statistics tab non-functional

2016-10-10 Thread Michael Gratton
On Tue, Oct 11, 2016 at 2:37 AM, Sebastien Bacher  
wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. The issue you are reporting is an upstream one and it
> would be nice if somebody having it could send the bug to the 
> developers
> of the software by following the instructions at
> https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, 
> please
> tell us the number of the upstream bug (or the link), so we can add a
> bugwatch that will inform us about its status. Thanks in advance.


Hi, what makes you think it's an upstream problem?

As I mentioned, it works fine for apps run via Flatpak on the same 
computer, so this very much sounds like an Ubuntu/Debian specific issue.

//Mike

-- 
⊨ Michael Gratton, Percept Wrangler.
⚙ 

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

Title:
  GTK Inspector Statistics tab non-functional

Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Running a GTK+ 3 app with GOBJECT_DEBUG=instance-count enables the
  Statistics tab in GTK Inspector, but after clicking the Record button
  it never starts collecting statistics. This makes it difficult to
  develop and debug memory leaks in GTK programs on Ubuntu.

  To reproduce:

  1. Start an app with the Inspector and GOBJECT_DEBUG=instance-count
  set, e.g.:

  > GOBJECT_DEBUG=instance-count GTK_DEBUG=interactive gnome-calculator

  2. Click the Statistics tab
  3. Click the Record button
  4. Click around the app a bit

  Expected: Object counts go up, pretty graphs showing things
  Actual: Object counts stay at 0, pretty graphs showing flat lines

  This seems like it is Ubuntu-specific, since when running GTK+
  programs installed via Flatpak (and hence using the Flatpak runtime),
  the above works fine on the same system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-dev 3.20.8-1ubuntu0~ppa1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 15 13:05:19 2016
  InstallationDate: Installed on 2015-07-22 (421 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (196 days ago)

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

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


[Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected

2016-10-10 Thread Mathieu Trudel-Lapierre
I managed to reproduce it once trying to move from the on-laptop miniDP
connector to the dock's full-size DP connector -- then I had a black
background (well, no backgound) and the window trails.

It looks to me like an issue in compiz, but it might really be X. In
doubt, I'm not going to change this and let someone more knowledgeable
than me investigate this further.

If anything needs to be attempted, my X230 doesn't ever run anything
important (I use it for running installer tests, etc.), so I can do
further testing (and reinstalls).

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

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

Title:
  No X on boot with external monitor connected

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting from today's (201610907) daily yakkety livecd with an
  external display attached X does not start.

  If the external monitor is attached after X has started I can boot to
  the desktop using only using the laptop's LCD (ThinkPad x230, intel
  graphics).  The attaching a 1920x1080 LCD via miniDP extends the
  desktop but windows moved around produce a trail of windows that
  persist even after the window is closed.

  This is a regression from Xenial.

  $ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct  7 20:23:46 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
  MachineType: LENOVO 2306CTO
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Fri Oct  7 20:18:12 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected

2016-10-10 Thread Robert C Jennings
These are working with 16.04 perfectly, I updated to 16.10 and had to
restore from backups to get back to 16.10.  Then I booted from the live-
cd to capture this bug.

Scenarios:
 1. mDP to HDMI cable connected to a 1080p monitor (Dell E248Wfp); that is the 
simple example and they all fail with the same result.
 2. same Dell via DP2 on the doc using a DP to single-link DVI adapter (like 
http://www.monoprice.com/product?c_id=104_id=10428_id=1042801_id=4827)
 3. DP2 on the doc connected to a Shimian LCD running at 2560x1440 connected 
via a Dell (BizLink) DisplayPort to DVI Dual Link Adapter (like 
https://www.amazon.com/Dell-BIZLINK-DisplayPort-Adapter-Powered/dp/B003XYBA72). 
 But I didn't want to confuse the issue with that more niche bit of hardware.

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

Title:
  No X on boot with external monitor connected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When booting from today's (201610907) daily yakkety livecd with an
  external display attached X does not start.

  If the external monitor is attached after X has started I can boot to
  the desktop using only using the laptop's LCD (ThinkPad x230, intel
  graphics).  The attaching a 1920x1080 LCD via miniDP extends the
  desktop but windows moved around produce a trail of windows that
  persist even after the window is closed.

  This is a regression from Xenial.

  $ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct  7 20:23:46 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
  MachineType: LENOVO 2306CTO
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Fri Oct  7 20:18:12 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected

2016-10-10 Thread Robert C Jennings
Also, the bug was opened with the system running BIOS version 2.57:
  dmi.bios.version: G2ET97WW (2.57 )
I have upgraded to the latest version and recreated there as well:
  Version: G2ETA7WW (2.67 )

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

Title:
  No X on boot with external monitor connected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When booting from today's (201610907) daily yakkety livecd with an
  external display attached X does not start.

  If the external monitor is attached after X has started I can boot to
  the desktop using only using the laptop's LCD (ThinkPad x230, intel
  graphics).  The attaching a 1920x1080 LCD via miniDP extends the
  desktop but windows moved around produce a trail of windows that
  persist even after the window is closed.

  This is a regression from Xenial.

  $ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct  7 20:23:46 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
  MachineType: LENOVO 2306CTO
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Fri Oct  7 20:18:12 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

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


Re: [Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected

2016-10-10 Thread Robert C Jennings
I have tried two monitors of different brands and a random television.  The
resolution selected is 1920x1080.

On Mon, Oct 10, 2016 at 7:19 PM, Mathieu Trudel-Lapierre <
mathieu...@gmail.com> wrote:

> Could you please try with a different monitor or share more of the
> details of how you are using this, such as which resolution is picked?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1631519
>
> Title:
>   No X on boot with external monitor connected
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When booting from today's (201610907) daily yakkety livecd with an
>   external display attached X does not start.
>
>   If the external monitor is attached after X has started I can boot to
>   the desktop using only using the laptop's LCD (ThinkPad x230, intel
>   graphics).  The attaching a 1920x1080 LCD via miniDP extends the
>   desktop but windows moved around produce a trail of windows that
>   persist even after the window is closed.
>
>   This is a regression from Xenial.
>
>   $ lsb_release -rd
>   Description:  Ubuntu Yakkety Yak (development branch)
>   Release:  16.10
>
>   $ apt-cache policy xorg
>   xorg:
> Installed: 1:7.7+13ubuntu4
> Candidate: 1:7.7+13ubuntu4
> Version table:
>*** 1:7.7+13ubuntu4 500
>   500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
>   100 /var/lib/dpkg/status
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: xorg 1:7.7+13ubuntu4
>   ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
>   Uname: Linux 4.8.0-19-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.3-0ubuntu7
>   Architecture: amd64
>   CasperVersion: 1.379
>   CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Fri Oct  7 20:23:46 2016
>   DistUpgraded: Fresh install
>   DistroCodename: yakkety
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation 3rd Gen Core processor Graphics Controller
> [8086:0166] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
> [17aa:21fa]
>   LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
>   MachineType: LENOVO 2306CTO
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
> file=/cdrom/preseed/username.seed boot=casper quiet splash ---
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/25/2013
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G2ET97WW (2.57 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 2306CTO
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:
> pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:
> rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 2306CTO
>   dmi.product.version: ThinkPad X230
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.70-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.2-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160706-1ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-2
>   xserver.bootTime: Fri Oct  7 20:18:12 2016
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.18.4-1ubuntu6
>   xserver.video_driver: modeset
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions
>

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

Title:
  No X on boot with external monitor connected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When booting from today's (201610907) daily yakkety livecd with an
  external display attached X does not start.

  If the 

[Touch-packages] [Bug 1631365] Re: unity8 greeter does not save the last used session

2016-10-10 Thread Michał Sawicz
@Paul note there is a new greeter available now - in the unity8-greeter
package, coming from unity8.

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

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

Title:
  unity8 greeter does not save the last used session

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:
   * Have both unity7 and unity8 sessions installed
   * Log in to unity8
   * Log out
   * The greeter suggests unity7 as the session to log in 

  It should save the last session and suggest that one.

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

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


[Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected

2016-10-10 Thread Mathieu Trudel-Lapierre
I've tried this on my own Lenovo Thinkpad X230 (also a 2306CTO), and I
can't reproduce the issue at all. I've tried both the dock's full-sized
DP connector and miniDP on the laptop itself (undocked), both work with
no issues at all, and no artifacts on the external screen (or the panel,
for that matter).

I have no idea what causes this. Perhaps we're dealing with a monitor
that claims to support some resolutions it doesn't really like? The
monitor I use is a fairly good Dell P2210, but doesn't apparently
confirm to EDID 1.3 (but still works correctly).

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

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

Title:
  No X on boot with external monitor connected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When booting from today's (201610907) daily yakkety livecd with an
  external display attached X does not start.

  If the external monitor is attached after X has started I can boot to
  the desktop using only using the laptop's LCD (ThinkPad x230, intel
  graphics).  The attaching a 1920x1080 LCD via miniDP extends the
  desktop but windows moved around produce a trail of windows that
  persist even after the window is closed.

  This is a regression from Xenial.

  $ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct  7 20:23:46 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
  MachineType: LENOVO 2306CTO
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Fri Oct  7 20:18:12 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1631519] Re: No X on boot with external monitor connected

2016-10-10 Thread Mathieu Trudel-Lapierre
Could you please try with a different monitor or share more of the
details of how you are using this, such as which resolution is picked?

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

Title:
  No X on boot with external monitor connected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When booting from today's (201610907) daily yakkety livecd with an
  external display attached X does not start.

  If the external monitor is attached after X has started I can boot to
  the desktop using only using the laptop's LCD (ThinkPad x230, intel
  graphics).  The attaching a 1920x1080 LCD via miniDP extends the
  desktop but windows moved around produce a trail of windows that
  persist even after the window is closed.

  This is a regression from Xenial.

  $ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct  7 20:23:46 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
  MachineType: LENOVO 2306CTO
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Fri Oct  7 20:18:12 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1631365] [NEW] unity8 greeter does not save the last used session

2016-10-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

How to reproduce:
 * Have both unity7 and unity8 sessions installed
 * Log in to unity8
 * Log out
 * The greeter suggests unity7 as the session to log in 

It should save the last session and suggest that one.

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


** Tags: iso-testing yakkety
-- 
unity8 greeter does not save the last used session
https://bugs.launchpad.net/bugs/1631365
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity8 in Ubuntu.

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


[Touch-packages] [Bug 1495971] Re: Samsung ML-1250 prints only first job and then disconnects

2016-10-10 Thread Ricardo Biloti
I read this full issue report and replies and it seems I am experienced
an analogous problem. Should I report the details of my case here or
open a new issue?

Here are few initial information:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

uname -a:
Linux mangue 4.4.0-42-generic #62-Ubuntu SMP Fri Oct 7 23:11:45 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

lsusb:
Bus 005 Device 025: ID 04e8:3301 Samsung Electronics Co., Ltd ML-1660 Series

/var/log/syslog: (the block below keeps popping out continuously)

Oct 10 20:11:27 mangue kernel: [ 1594.728192] usb 5-2: reset full-speed USB 
device number 40 using uhci_hcd
Oct 10 20:11:27 mangue kernel: [ 1594.885385] usb 5-2: USB disconnect, device 
number 40
Oct 10 20:11:27 mangue kernel: [ 1594.885804] usblp1: removed
Oct 10 20:11:27 mangue udev-configure-printer[6009]: remove 
/devices/pci:00/:00:1d.0/usb5/5-2
Oct 10 20:11:27 mangue kernel: [ 1595.98] usb 5-2: new full-speed USB 
device number 41 using uhci_hcd
Oct 10 20:11:28 mangue kernel: [ 1595.169199] usb 5-2: New USB device found, 
idVendor=04e8, idProduct=3301
Oct 10 20:11:28 mangue kernel: [ 1595.169209] usb 5-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Oct 10 20:11:28 mangue kernel: [ 1595.169216] usb 5-2: Product: ML-1660 Series
Oct 10 20:11:28 mangue kernel: [ 1595.169222] usb 5-2: Manufacturer: Samsung 
Electronics Co., Ltd.
Oct 10 20:11:28 mangue kernel: [ 1595.169227] usb 5-2: SerialNumber: 
Z5ASBDAZ809914N.
Oct 10 20:11:28 mangue kernel: [ 1595.176325] usblp 5-2:1.0: usblp1: USB 
Bidirectional printer dev 41 if 0 alt 0 proto 2 vid 0x04E8 pid 0x3301
Oct 10 20:11:28 mangue mtp-probe: checking bus 5, device 41: 
"/sys/devices/pci:00/:00:1d.0/usb5/5-2"
Oct 10 20:11:28 mangue mtp-probe: bus: 5, device: 41 was not an MTP device
Oct 10 20:11:28 mangue udev-configure-printer[5977]: no corresponding CUPS 
device found
Oct 10 20:11:28 mangue systemd[1]: Started Automatic USB/Bluetooth printer 
setup (-devices-pci:00-:00:1d.0-usb5-5\x2d2).
Oct 10 20:11:28 mangue systemd[1]: printer.target: Unit not needed anymore. 
Stopping.
Oct 10 20:11:28 mangue systemd[1]: Stopped target Printer.
Oct 10 20:11:28 mangue systemd[1]: Starting Automatic USB/Bluetooth printer 
setup (-devices-pci:00-:00:1d.0-usb5-5\x2d2)...
Oct 10 20:11:28 mangue systemd[1]: Reached target Printer.
Oct 10 20:11:28 mangue udev-configure-printer[6029]: add 
/devices/pci:00/:00:1d.0/usb5/5-2
Oct 10 20:11:28 mangue udev-configure-printer[6029]: device devpath is 
/devices/pci:00/:00:1d.0/usb5/5-2
Oct 10 20:11:28 mangue udev-configure-printer[6029]: MFG:Samsung MDL:ML-1660 
Series SERN:- serial:Z5ASBDAZ809914N.

I am using Unified Linux Driver, from Samsung's HP, since the printer
was not able to print without it. After installing it, the printer was
automatically discovered and I could print one page. After that, the
printer goes automatically to disabled state. Re-enabling it does not
work, since it is disable few seconds later.

The printer used to work normally up to last week, when my computer was
still running Ubuntu 14.04 (and Samsung Linux Driver).

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

Title:
  Samsung ML-1250 prints only first job and then disconnects

Status in cups package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have:

  lsusb
  Bus 004 Device 009: ID 04e8:300e Samsung Electronics Co., Ltd Laser Printer

  Just connected printer and started to print first job:

  tail -f /var/log/syslog
  Sep 15 14:50:18 desktop udev-configure-printer: URI matches without serial 
number: usb://Samsung/ML-1250
  Sep 15 14:50:18 desktop udev-configure-printer: No serial number URI matches 
so using those without
  Sep 15 14:50:18 desktop udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1250, normalized: samsung ml 1250
  Sep 15 14:50:18 desktop udev-configure-printer: URI of print queue: 
usb://HP/LaserJet%201200?serial=00CNCF203187, normalized: laserjet 1200 serial 
00cncf203187
  Sep 15 14:50:18 desktop udev-configure-printer: About to add queue for 
usb://Samsung/ML-1250
  Sep 15 14:50:20 desktop udev-add-printer: add_queue: 
URIs=['usb://Samsung/ML-1250']
  Sep 15 14:50:20 desktop udev-add-printer: D-Bus method call failed: 
org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.redhat.NewPrinterNotification was not provided by any .service files
  Sep 15 14:50:23 desktop udev-add-printer: PPD: 
foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Samsung-ML-1250-pxlmono.ppd; 
Status: 0
  Sep 15 14:50:24 desktop colord: Profile added: ML-1250-Gray..
  Sep 15 14:50:24 desktop colord: Device added: cups-ML-1250
  Sep 15 14:53:51 desktop kernel: [22676.268686] usblp0: removed
  Sep 15 

[Touch-packages] [Bug 1632144] [NEW] SRU of LXC 2.0.5 (upstream bugfix release)

2016-10-10 Thread Stéphane Graber
Public bug reported:

LXC upstream released LXC 2.0.5 as a bugfix release with following changelog:
  - Fix .gitignore after /tools/ split
  - Add lxc-test-utils to .gitignore
  - bdev: use correct overlay module name
  - cleanup: tools: remove --name from lxc-top usage message
  - cleanup: whitespaces in option alignment for lxc-execute
  - Use full GPG fingerprint instead of long IDs.
  - tools: move --rcfile to the common options list
  - tools: set configfile after load_config
  - doc: add --rcfile to common opts
  - doc: Update Korean lxc-attach(1)
  - doc: Add --rcfile to Korean common opts
  - doc: Add --rcfile to Japanese common opts
  - tools: use exit(EXIT_*) everywhere
  - tools: unify exit() calls outside of main()
  - utils: Add mips signalfd syscall numbers
  - seccomp: Implement MIPS seccomp handling
  - seccomp: Add mips and mips64 entries to lxc_config_parse_arch
  - seccomp: fix strerror()
  - confile: add more archs to lxc_config_parse_arch()
  - seccomp: add support for s390x
  - seccomp: remove double include and order includes
  - seccomp: non functional changes
  - templates: use fd 9 instead of 200
  - templates: fedora requires openssl binary
  - tools: use boolean for ret in lxc_device.c
  - c/r: use /proc/self/tid/children instead of pidfile
  - c/r: Fix pid_t on some arches
  - templates: Add mips hostarch detection to debian
  - cleanup: replace tabs wth spaces in usage strings
  - remove extra 'ret'
  - c/r: write status only after trying to parse the pid
  - set FULL_PATH_NAMES=NO in doc/api/Doxyfile
  - templates: rm halt.target -> sigpwr.target symlink
  - templates: remove creation of bogus directory
  - console: use correct log name
  - configure: add --disable-werror
  - tests: fix get_item tests
  - templates: use correct cron version in alpine template
  - c/r: zero a smaller than known migrate_opts struct
  - lxczfs: small fixes
  - c/r: free valid_opts if necessary
  - make rsync deal with sparse files efficiently
  - lxc-create -t debian fails on ppc64el arch
  - c/r: fix typo in comment
  - cgroup: add new functions for interacting with hierachies
  - utils: add lxc_deslashify
  - c/r: pass --cgroup-roots on checkpoint
  - cgroup: get rid of weird hack in cgfsng_escape
  - cgroup: drop cgroup_canonical_path
  - c/r: check that cgroup_num_hierarchies > 0
  - tools: do not add trailing spaces on lxc-ls -1
  - conf: retrieve mtu from netdev->link
  - conf: try to retrieve mtu from veth
  - c/r: detatch from controlling tty on restore
  - Fix null derefence if attach is called without access to any tty
  - utils: fix lxc_string_split()
  - tools: lxc_deslashify() handle special cases
  - tests: add unit tests for lxc_deslashify()
  - Fix for ALTLinux container creation in all branches
  - utils: lxc_deslashify() free memory
  - Fix spelling of CentOS in the templates
  - Define LXC_DEVEL to detect development releases
  - tools: lxc-checkconfig conditionalize devpts check

Just like Ubuntu itself, upstream releases long term support releases,
as is 2.0 and then periodic point releases including all the accumulated
bugfixes.

Only the latest upstream release gets full support from the upstream
developers, everyone else is expected to first update to it before
receiving any kind of support.

This bugfix release has already been uploaded to Yakkety and
automatically backported in the upstream PPAs for all Ubuntu releases.
So far without any reported regression.

This should qualify under the minor upstream bugfix release allowance of
the SRU policy, letting us SRU this without paperwork for every single
change included in this upstream release.

Once the SRU hits -updates, we will be backporting this to trusty-
backports as well, making sure we have the same version everywhere.

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: lxc (Ubuntu Trusty)
 Importance: Undecided
 Assignee: Stéphane Graber (stgraber)
 Status: Triaged

** Affects: lxc (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

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

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

** Also affects: lxc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Changed in: lxc (Ubuntu Trusty)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxc (Ubuntu Xenial)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

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

Title:
  SRU of LXC 2.0.5 (upstream bugfix release)

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

[Touch-packages] [Bug 1615099] Re: SRU of LXC 2.0.4 (upstream bugfix release)

2016-10-10 Thread Stéphane Graber
** Changed in: lxc (Ubuntu Trusty)
   Status: Triaged => Fix Released

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

Title:
  SRU of LXC 2.0.4 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  LXC upstream released LXC 2.0.4 as a bugfix release with following changelog:
  - core: Add a prefix to the lxc.pc
  - core: Add flag in mount_entry to skip NODEV in case of a
persistent dev entry
  - core: Add missing cgroup namespace to ns_info struct
  - core: attach: setns instead of unshare in lxc-attach
  - core: bdev: Add subdirectories to search path
  - core: bdev: Be smarter about btrfs subvolume detection
  - core: cgfsng: Don't pre-calculate path
  - core: cgfsng: Fix is_lxcfs() and is_cgroupfs()
  - core: cgroups: Move cgroup files to common subfolder
  - core: conf: Set pty_info to NULL after free
  - core: Detect if we should send SIGRTMIN+3
  - core: Replace readdir_r() with readdir()
  - core: Set up MTU for vlan-type interfaces.
  - core: tools, tests: Reorganize repo
  - c/r: Add support for CRIU's --action-script
  - c/r: Add support for ghost-limit in CRIU
  - c/r: Drop in-flight connections during CRIU dump
  - c/r: Initialize migrate_opts properly
  - c/r: Make local function static
  - c/r: Replace tmpnam() with mkstemp()
  - c/r: Store criu version
  - c/r: Use PRIu64 format specifier
  - doc: Fix typo found by lintian
  - doc: Update Japanese lxc-attach(1)
  - doc: Update lxc-attach(1)
  - lxc-attach: Add -f option (rcfile)
  - lxc-attach: Cleanup whitespaces
  - lxc-create: Add missing newline in output
  - lxc-ls: Use correct runtime path
  - templates: alpine: Add support for new arch
  - templates: alpine: Mount tmpfs under /run
  - templates: debian: Add more quotes to variables (at least $rootfs
should now be covered)
  - templates: debian: Avoid noisy perl warnings caused by missing locales
  - templates: debian: fix regression when creating wheezy containers
  - templates: debian: Make shellcheck (Ubuntu: 0.3.7-5 amd64) most
possible happy
  - tests: Add unit tests for lxc_string_in_array()
  - tests: Add unit tests for lxc_string_replace()

  
  Just like Ubuntu itself, upstream releases long term support releases, as is 
2.0 and then periodic point releases including all the accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Yakkety and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

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

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


[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

2016-10-10 Thread Stéphane Graber
Marking this bug fix released as all the bits we wanted done here have
been done.

We still have a separate bug open for the dependency on squashfuse and
its SRU to xenial.

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

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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


[Touch-packages] [Bug 1002454] Re: IPv4 DNS preferred over IPv6 ones

2016-10-10 Thread Solarus
This bug is still present in Ubuntu 16.04.

Wireshark's captures show that IPv4 resolvers are preferred to IPv6 resolvers.
It also show the local machine sometimes directly contacting the root server's, 
that's weird.

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

Title:
  IPv4 DNS preferred over IPv6 ones

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

Bug description:
  The Network Manager always prefers IPv4 DNS over IPv6 ones. The issue
  occurs both when DNSs are statically configured and when they're
  acquired via DHCPv4/DHCPv6.

  Network Manager puts IPv4 DNSs before IPv6 ones in the /var/run/nm-
  dns-dnsmasq.conf so Dnsmasq resolves names using IPv4 DNSs before
  using IPv6 ones.

  If I disable Dnsmasq, DNS servers are put in the wrong way in
  /etc/resolv.conf file.

  The system shoud prefer IPv6 DNSs in any case.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager-gnome 0.9.4.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon May 21 21:05:59 2012
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.217  metric 
1 
   192.168.36.0/24 dev vmnet1  proto kernel  scope link  src 192.168.36.1 
   192.168.70.0/24 dev vmnet8  proto kernel  scope link  src 192.168.70.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to precise on 2012-05-02 (18 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   eth0-Static   0bcb2b9f-a2c0-46f9-a6b1-59f66e383264   
802-3-ethernet1337627018   lun 21 mag 2012 21:03:38 CEST  yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

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

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


[Touch-packages] [Bug 1434115] Re: apparently broken dependency resolution

2016-10-10 Thread Raphaël Droz
On production machine which most probably using php5-fpm + event or worker 
Apache2 MPM, this bug forcefully reinstall libapache2-mod-php5 after 
(unattended = minor) PHP5 update.
The direct effect of this is reinstalling mpm_prefork !

Simply stated: unattended-upgrades breaks LAMP installation by not resolving 
dependencies correctly.
Could maintainer have a look on this please?
I've been hit every time php5 package is updated.


Current workaround:
```
  Package: libapache2-mod-php5 libapache2-mod-php5filter
  Pin: origin ""
  Pin-Priority: -1
```
Note: may add php5-cgi, since the auto-installation of this package is not as 
disastrous.
Note: it's hard to *debug* this bug (unless setting XUUPOPT="-d" inside 
/etc/cron.daily/apt) and may well be left unnoticed in some case... until 
website traffic increases implying the prefork MPM extra-load.


Side question: why would unattended-upgrades provide its own (not-apt-based) 
resolution mechanism in the first place?


** Attachment added: "sample debug unattended-upgrade php5 log"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1434115/+attachment/4759001/+files/auto-upgrade.log

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

Title:
  apparently broken dependency resolution

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  It looks as though unattended upgrades' dependency resolution is a
  little broken when there are multiple alternatives and when the
  dependency is currently satisfied by a package other than the first
  alternative.

  In this case, package php5 was upgraded.  php5 depends:

  $ dpkg -s php5|grep Depends
  Depends: libapache2-mod-php5 (>= 5.5.9+dfsg-1ubuntu4.7) | 
libapache2-mod-php5filter (>= 5.5.9+dfsg-1ubuntu4.7) | php5-cgi (>= 
5.5.9+dfsg-1ubuntu4.7) | php5-fpm (>= 5.5.9+dfsg-1ubuntu4.7), php5-common (>= 
5.5.9+dfsg-1ubuntu4.7)

  I use php5-fpm, and specifically do not want libapache2-mod-php5
  installed (not least because it breaks my FPM config).  After manually
  purging libapache2-mod-php5:

  $ dpkg -l $(dpkg -s php5|grep Depends|perl -npe 's/Depends://; 
s/[,|]/\n/g'|cut -f 2 -d\ )|grep ^[a-z]
  un  libapache2-mod-php5 
  (no description available)
  un  libapache2-mod-php5filter   
  (no description available)
  un  php5-cgi
  (no description available)
  ii  php5-common 5.5.9+dfsg-1ubuntu4.7 
   amd64Common files for packages built from the php5 source
  ii  php5-fpm5.5.9+dfsg-1ubuntu4.7 
   amd64server-side, HTML-embedded scripting language (FPM-CGI 
binary)

  note that:
  • php5-fpm is installed and therefore that dependency of php5 was already 
satisfied
  • php5-cgi and libapache2-mod-php5filter are alternative dependencies along 
with libapache2-mod-php5, yet neither got installed in the way that 
libapache2-mod-php5 did.

  
  For completeness' sake, here's an excerpt of the unattended upgrade log (full 
log attached) showing that it was this morning's upgrade run that installed 
libapache2-mod-php5:

  Selecting previously unselected package libapache2-mod-php5.
  Preparing to unpack .../libapache2-mod-php5_5.5.9+dfsg-1ubuntu4.7_amd64.deb 
...
  Unpacking libapache2-mod-php5 (5.5.9+dfsg-1ubuntu4.7) ...
  Preparing to unpack .../php5_5.5.9+dfsg-1ubuntu4.7_all.deb ...
  Unpacking php5 (5.5.9+dfsg-1ubuntu4.7) over (5.5.9+dfsg-1ubuntu4.6) ...

  Other requested information:

  $ lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.82.1ubuntu2.1
Candidate: 0.82.1ubuntu2.1
Version table:
   *** 0.82.1ubuntu2.1 0
  500 http://ubuntu.orion.retrosnub.co.uk/ubuntu/ trusty-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   0.82.1ubuntu2 0
  500 http://ubuntu.orion.retrosnub.co.uk/ubuntu/ trusty/main amd64 
Packages

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

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


[Touch-packages] [Bug 1631988] Re: Web browser didn't appear when 'Report a problem...' asked if I could add more info to a bug report that would come up in a web browser window

2016-10-10 Thread Ads20000
$ xdg-open www.ubuntu.com
gvfs-open: www.ubuntu.com: error opening location: Error when getting 
information for file '/home/ubuntu/www.ubuntu.com': No such file or directory

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

Title:
  Web browser didn't appear when 'Report a problem...' asked if I could
  add more info to a bug report that would come up in a web browser
  window

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  I tried loading Checkbox in the live session, the 'Report a
  Problem...' dialogue came up and told me that the problem had already
  reported and asked if I could add more detail to the bug when it came
  up in the web browser, but the web browser didn't load.

  Computer info:
  VirtualBox Graphical User Interface Version 5.0.24_Ubuntu r108355
  (I don't have access to spare hardware to test on at the moment)
  Allocated 2GB RAM
  Host OS: Ubuntu 16.04 LTS 64-bit
  Lenovo ThinkPad X201

  Live session from the Ubuntu 16.10 20161008 ISO

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport 2.20.3-0ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportLog:
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: called for pid 7616, 
signal 11, core limit 0
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: executable: 
/usr/bin/webapp-container (command line "webapp-container 
--app-id=ubuntu-amazon-default --webapp --enable-back-forward 
http://www.amazon.com/?tag=u1webapp-20;)
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 7682) Mon Oct 10 15:55:12 2016: wrote report 
/var/crash/_usr_bin_webapp-container.999.crash
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CrashReports:
   644:999:123:0:2016-10-10 15:55:49.656395711 +0100:2016-10-10 
15:55:49.656395711 +0100:/var/crash/_usr_bin_webapp-container.999.upload
   600:115:123:0:2016-10-10 15:55:53.524429871 +0100:2016-10-10 
15:55:53.524429871 +0100:/var/crash/_usr_bin_webapp-container.999.uploaded
   640:999:123:15139136:2016-10-10 15:55:48.040390253 +0100:2016-10-10 
15:55:49.040390253 +0100:/var/crash/_usr_bin_webapp-container.999.crash
  CurrentDesktop: Unity
  Date: Mon Oct 10 15:57:49 2016
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default

2016-10-10 Thread Anders Kaseorg
The 8.8.8.8 fallback is not only used on misconfigured systems!  It’s
also used for a short period while initially connecting or reconnecting
to totally healthy networks with DHCP.  So the excuse that privacy-
conscious users should just use DHCP holds no water.

https://github.com/systemd/systemd/issues/4175#issuecomment-252571482

** Bug watch added: github.com/systemd/systemd/issues #4175
   https://github.com/systemd/systemd/issues/4175

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

Title:
  systemd-resolved: please do not use Google public DNS by default

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.)
  in the absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf 
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.


  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  
  Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS 
parameter.

  
  This issue has been discussed in the Debian BTS 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My interpretation 
of the Debian package maintainer's position is that a user concerned with the 
privacy implications shouldn't let systemd get into a state where it uses the 
fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf 
file or use DHCP").  I would argue that it's safest not to have fallback DNS 
servers configured at all by default.

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

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


[Touch-packages] [Bug 1611680] Re: Scrolling on www.ceskenoviny.cz is very slow

2016-10-10 Thread Launchpad Bug Tracker
** Branch linked: lp:~phablet-team/webbrowser-app/staging

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

Title:
  Scrolling on  www.ceskenoviny.cz is very slow

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Hello,
  the Czech news site I am reading quite often was recently updated to a new 
design and as of this update scrolling on the site gets quite tricky. On some 
articles scrolling is almost impossible.

  Now this is not the first site I find difficult to scroll on with an
  Ubuntu's web browser unfortunately, though it is usually the case of
  some heavy javascript ballast on the site I am sure.

  The worst experience I am getting so far is on this article:
  http://www.ceskenoviny.cz/zpravy/francouzska-justice-obvinila-16letou-
  divku-z-planovani-teroru/1379685 where scrolling is very laggy and
  more or less only gets me either to the absolute top or the absolute
  bottom of the article, not anywhere in the middle. Slow scrolling
  won't help the issue.

  Other articles like this one http://www.ceskenoviny.cz/zpravy/ceske-
  drahy-dostaly-pokutu-150-000-kc-za-chybejici-ceniky/1380181 feels only
  very laggy but not that bad from my experience.

  I've been testing this on my Meizu MX4 with rc-proposed. Maybe this is
  only the device issue though I doubt it.

  Is there something you can do about it?
  Thank you very much.

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

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


[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-10-10 Thread Launchpad Bug Tracker
** Branch linked: lp:~phablet-team/webbrowser-app/staging

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Fix Committed
Status in ubuntu-terminal-app package in Ubuntu:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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


[Touch-packages] [Bug 1632096] Re: dhclient-script does not respect ip6_prefixlen

2016-10-10 Thread LaMont Jones
*** This bug is a duplicate of bug 1609898 ***
https://bugs.launchpad.net/bugs/1609898

The DHCP v6 protocol does not include prefixlen: On-link indication
comes from router-advertisements, only.

So it's not so much that the script is ignoring it, as it is that
dhclient is making up answers.

** This bug has been marked a duplicate of bug 1609898
   dhclient incorrectly assumes a /64 ipv6 prefix

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

Title:
  dhclient-script does not respect ip6_prefixlen

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  /sbin/dhclient-script does not seem to pay any attention to the prefixlen 
that is provided.
  The result is that:
  $ dhclient -6 -1 -v eth0
  results in network configuration like this:

  
  2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
  inet6 fd42:83bb:a360:8010:2527:abdf:95cb:5e55/128 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe12:3456/64 scope link 
 valid_lft forever preferred_lft forever

  when it should have a /64 on the fd42 address, and subsequently no
  ability to reach other hosts on that network.

  The fix seems simple enough:
ip -6 addr add ${new_ip6_address}${new_ip6_prefixlen:+/${new_ip6_prefixlen}}
   dev ${interface} scope global

  Ie, we just have to add '/${new_ip6_prefixlen}' if it is set.

  
  This link seems relevant:

  https://kb.isc.org/article/AA-01141/0/How-to-workaround-IPv6-prefix-
  length-issues-with-ISC-DHCP-clients.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Oct 10 20:23:42 2016
  DhclientLeases:
   
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1624738] Re: Firefox search and location boxes have black borders when unselected

2016-10-10 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-mate-artwork - 16.10.9

---
ubuntu-mate-artwork (16.10.9) yakkety; urgency=medium

  * Fix Firefox download progress bars. (LP: #1630224)
  * Fix Unlock button for Time and Date Settings. (LP: #1630910)
  * Fix Back/Forward navigation buttons in Yelp. (LP: #1624574)
  * Fix Firefox Search/Location entry box borders. (LP: #1624738)
  * Fix Firefox menu items.

 -- Martin Wimpress   Sun, 09 Oct 2016 20:42:40
+0100

** Changed in: ubuntu-mate-artwork (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 ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1624738

Title:
  Firefox search and location boxes have black borders when unselected

Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  As seen in the attached screen shot the borders around Firefox
  location and search entry boxes are black when unselected, but they
  should be grey.

  The black borders are inconsistent with the rest of the Ubuntu theming
  and it looks jarring.

  The issue is resolved by styling the 'frame' selector, which Firefox
  uses to style the Search and Location entry boxes. Some overrides are
  then applied to prevent frames incorrectly rendering borders in other
  applications.

  [Test Case]

  To observe the issue simply open Firefox and look at the Search or
  Location entry boxes while they are unselected, the borders will be
  black.

  After installing the patched theme doing to same will result in the
  borders being rendered using an appropriate shade of grey.

  [Regression Potential]

  It is possible that some GTK3+ applications may now render frames with
  a border where they previously did not. That said, the default
  applications in Ubuntu have been checked for this regression and the
  appropriate overrides have been added.

  The default installed applications in Ubuntu have been tested to
  ensure they do not regress in the manner described above.

  [Other Info]
   
  Should Firefox style the Search and Location entry boxes with a discrete 
selector in the future then the styling added to work around the black border 
could be removed/updated.

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

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


[Touch-packages] [Bug 1632094] [NEW] Black colour in console is actually dark grey

2016-10-10 Thread Mark
Public bug reported:

A default Ubuntu installation runs setvtrgb to set the console (virtual
terminal) palette to that specified in /etc/console-setup/vtrgb

/etc/console-setup/vtrgb is provided by the package console-setup-linux. Its 
contents look like this:
1,222,57,255,0,118,44,204,128,255,0,255,0,255,0,255
1,56,181,199,111,38,181,204,128,0,255,255,0,0,255,255
1,43,74,6,184,113,233,204,128,0,0,0,255,255,255,255

For some reason, the (should-be-black) background colour is set to
#010101, i.e. very dark grey. Is that by accident or was there some
rationale for doing that?

To fix it and make "black" *actually* black, edit /etc/console-setup/vtrgb, 
replacing the 1s at the start of each line with 0s:
0,222,57,255,0,118,44,204,128,255,0,255,0,255,0,255
0,56,181,199,111,38,181,204,128,0,255,255,0,0,255,255
0,43,74,6,184,113,233,204,128,0,0,0,255,255,255,255

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  A default Ubuntu installation runs setvtrgb to set the console (virtual
  terminal) palette to that specified in /etc/console-setup/vtrgb
  
- The contents of /etc/console-setup/vtrgb look like this:
+ /etc/console-setup/vtrgb is provided by the package console-setup-linux. Its 
contents look like this:
  1,222,57,255,0,118,44,204,128,255,0,255,0,255,0,255
  1,56,181,199,111,38,181,204,128,0,255,255,0,0,255,255
  1,43,74,6,184,113,233,204,128,0,0,0,255,255,255,255
  
  For some reason, the (should-be-black) background colour is set to
  #010101, i.e. very dark grey. Is that by accident or was there some
  rationale for doing that?
  
  To fix it and make "black" *actually* black, edit /etc/console-setup/vtrgb, 
replacing the 1s at the start of each line with 0s:
  0,222,57,255,0,118,44,204,128,255,0,255,0,255,0,255
  0,56,181,199,111,38,181,204,128,0,255,255,0,0,255,255
  0,43,74,6,184,113,233,204,128,0,0,0,255,255,255,255

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

Title:
  Black colour in console is actually dark grey

Status in console-setup package in Ubuntu:
  New

Bug description:
  A default Ubuntu installation runs setvtrgb to set the console
  (virtual terminal) palette to that specified in /etc/console-
  setup/vtrgb

  /etc/console-setup/vtrgb is provided by the package console-setup-linux. Its 
contents look like this:
  1,222,57,255,0,118,44,204,128,255,0,255,0,255,0,255
  1,56,181,199,111,38,181,204,128,0,255,255,0,0,255,255
  1,43,74,6,184,113,233,204,128,0,0,0,255,255,255,255

  For some reason, the (should-be-black) background colour is set to
  #010101, i.e. very dark grey. Is that by accident or was there some
  rationale for doing that?

  To fix it and make "black" *actually* black, edit /etc/console-setup/vtrgb, 
replacing the 1s at the start of each line with 0s:
  0,222,57,255,0,118,44,204,128,255,0,255,0,255,0,255
  0,56,181,199,111,38,181,204,128,0,255,255,0,0,255,255
  0,43,74,6,184,113,233,204,128,0,0,0,255,255,255,255

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

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


[Touch-packages] [Bug 1632096] [NEW] dhclient-script does not respect ip6_prefixlen

2016-10-10 Thread Scott Moser
Public bug reported:

/sbin/dhclient-script does not seem to pay any attention to the prefixlen that 
is provided.
The result is that:
$ dhclient -6 -1 -v eth0
results in network configuration like this:


2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
inet6 fd42:83bb:a360:8010:2527:abdf:95cb:5e55/128 scope global 
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe12:3456/64 scope link 
   valid_lft forever preferred_lft forever

when it should have a /64 on the fd42 address, and subsequently no
ability to reach other hosts on that network.

The fix seems simple enough:
  ip -6 addr add ${new_ip6_address}${new_ip6_prefixlen:+/${new_ip6_prefixlen}}
 dev ${interface} scope global

Ie, we just have to add '/${new_ip6_prefixlen}' if it is set.


This link seems relevant:

https://kb.isc.org/article/AA-01141/0/How-to-workaround-IPv6-prefix-
length-issues-with-ISC-DHCP-clients.html

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: isc-dhcp-client 4.3.3-5ubuntu15
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Mon Oct 10 20:23:42 2016
DhclientLeases:
 
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images yakkety

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

Title:
  dhclient-script does not respect ip6_prefixlen

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  /sbin/dhclient-script does not seem to pay any attention to the prefixlen 
that is provided.
  The result is that:
  $ dhclient -6 -1 -v eth0
  results in network configuration like this:

  
  2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
  inet6 fd42:83bb:a360:8010:2527:abdf:95cb:5e55/128 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe12:3456/64 scope link 
 valid_lft forever preferred_lft forever

  when it should have a /64 on the fd42 address, and subsequently no
  ability to reach other hosts on that network.

  The fix seems simple enough:
ip -6 addr add ${new_ip6_address}${new_ip6_prefixlen:+/${new_ip6_prefixlen}}
   dev ${interface} scope global

  Ie, we just have to add '/${new_ip6_prefixlen}' if it is set.

  
  This link seems relevant:

  https://kb.isc.org/article/AA-01141/0/How-to-workaround-IPv6-prefix-
  length-issues-with-ISC-DHCP-clients.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Oct 10 20:23:42 2016
  DhclientLeases:
   
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1632088] Re: mirror crashed with SIGSEGV in __dynamic_cast()

2016-10-10 Thread Apport retracing service
*** This bug is a duplicate of bug 1620022 ***
https://bugs.launchpad.net/bugs/1620022

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1620022

** Tags removed: need-amd64-retrace

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

Title:
  mirror crashed with SIGSEGV in __dynamic_cast()

Status in apt package in Ubuntu:
  New

Bug description:
  On first reboot right after installing Ubuntu 16.10

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Oct 10 22:01:16 2016
  ExecutablePath: /usr/lib/apt/methods/mirror
  InstallationDate: Installed on 2014-11-25 (684 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/lib/apt/methods/mirror
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  Signal: 11
  SourcePackage: apt
  StacktraceTop:
   __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   pkgSystem::ArchitecturesSupported[abi:cxx11]() const () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   APT::Configuration::getArchitectures[abi:cxx11](bool const&) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
  Title: mirror crashed with SIGSEGV in __dynamic_cast()
  UpgradeStatus: Upgraded to yakkety on 2016-10-10 (0 days ago)
  UserGroups:

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

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


[Touch-packages] [Bug 1502173] Re: Python warnings: modules imported without specifying a version first

2016-10-10 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.3-0ubuntu8

---
apport (2.20.3-0ubuntu8) yakkety; urgency=medium

  * Prefer pycodestyle build dependency over pep8.
  * debian/tests/upstream-system: Create and export $GNUPGHOME, to work with
gnupg2.
  * apport-gtk: Specify module version with GI imports to avoid warnings.
Thanks Anatoly Techtonik. (LP: #1502173)
  * Disable Launchpad crash upload for final Ubuntu 16.10.

 -- Martin Pitt   Mon, 10 Oct 2016 14:28:17
+0200

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

Title:
  Python warnings: modules imported without specifying a version first

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  here is the problem:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apport-gtk 2.19-0ubuntu1
  Uname: Linux 4.2.2-040202-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Oct  2 16:17:14 2015
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)

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

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


[Touch-packages] [Bug 1632088] [NEW] mirror crashed with SIGSEGV in __dynamic_cast()

2016-10-10 Thread J.
*** This bug is a duplicate of bug 1620022 ***
https://bugs.launchpad.net/bugs/1620022

Public bug reported:

On first reboot right after installing Ubuntu 16.10

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: apt 1.3.1
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Mon Oct 10 22:01:16 2016
ExecutablePath: /usr/lib/apt/methods/mirror
InstallationDate: Installed on 2014-11-25 (684 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: /usr/lib/apt/methods/mirror
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
Signal: 11
SourcePackage: apt
StacktraceTop:
 __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 pkgSystem::ArchitecturesSupported[abi:cxx11]() const () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
 APT::Configuration::getArchitectures[abi:cxx11](bool const&) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
 ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
 ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
Title: mirror crashed with SIGSEGV in __dynamic_cast()
UpgradeStatus: Upgraded to yakkety on 2016-10-10 (0 days ago)
UserGroups:

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


** Tags: amd64 apport-crash yakkety

** Information type changed from Private to Public

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

Title:
  mirror crashed with SIGSEGV in __dynamic_cast()

Status in apt package in Ubuntu:
  New

Bug description:
  On first reboot right after installing Ubuntu 16.10

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Oct 10 22:01:16 2016
  ExecutablePath: /usr/lib/apt/methods/mirror
  InstallationDate: Installed on 2014-11-25 (684 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/lib/apt/methods/mirror
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  Signal: 11
  SourcePackage: apt
  StacktraceTop:
   __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   pkgSystem::ArchitecturesSupported[abi:cxx11]() const () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   APT::Configuration::getArchitectures[abi:cxx11](bool const&) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
  Title: mirror crashed with SIGSEGV in __dynamic_cast()
  UpgradeStatus: Upgraded to yakkety on 2016-10-10 (0 days ago)
  UserGroups:

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

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


[Touch-packages] [Bug 1597280] Re: [SVS1512Z9EB, Realtek ALC275, Black Headphone Out, Left] volume slider problem

2016-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [SVS1512Z9EB, Realtek ALC275, Black Headphone Out, Left] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Very low sound level. Alsamixer and pavucontrol did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hoofoo 1877 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jun 29 13:37:49 2016
  InstallationDate: Installed on 2016-06-18 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Volume slider, or mixer problems
  Title: [SVS1512Z9EB, Realtek ALC275, Black Headphone Out, Left] volume slider 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0081C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0081C8:bd09/18/2012:svnSonyCorporation:pnSVS1512Z9EB:pvrC60B4TX4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1512Z9EB
  dmi.product.version: C60B4TX4
  dmi.sys.vendor: Sony Corporation
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-06-29T12:57:00.907312

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

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


[Touch-packages] [Bug 1611466] Re: Calendar crashes on ESC typing.

2016-10-10 Thread Emerson Lima
Sorry the delay.
I'm using the follow version.
Distributor ID: Ubuntu
Description:Ubuntu 15.04
Release:15.04
Codename:   vivid

I don't know if some update solve the problem, but right now the problem is not 
more occurring.
Any forther information, please tell me.

** Changed in: indicator-datetime (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Calendar crashes on ESC typing.

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  When you click on date, it opens the calendar, if you type the ESC
  button on keyboard, the graphical interface crashes and in a few
  seconds it restart. During this few seconds or a minute, all the
  system stay frozen.

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

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


[Touch-packages] [Bug 1631988] Re: Web browser didn't appear when 'Report a problem...' asked if I could add more info to a bug report that would come up in a web browser window

2016-10-10 Thread Brian Murray
Could you try using xdg-open www.ubuntu.com and report back about what
happens?  Thanks in advance!

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

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

Title:
  Web browser didn't appear when 'Report a problem...' asked if I could
  add more info to a bug report that would come up in a web browser
  window

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  I tried loading Checkbox in the live session, the 'Report a
  Problem...' dialogue came up and told me that the problem had already
  reported and asked if I could add more detail to the bug when it came
  up in the web browser, but the web browser didn't load.

  Computer info:
  VirtualBox Graphical User Interface Version 5.0.24_Ubuntu r108355
  (I don't have access to spare hardware to test on at the moment)
  Allocated 2GB RAM
  Host OS: Ubuntu 16.04 LTS 64-bit
  Lenovo ThinkPad X201

  Live session from the Ubuntu 16.10 20161008 ISO

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport 2.20.3-0ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportLog:
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: called for pid 7616, 
signal 11, core limit 0
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: executable: 
/usr/bin/webapp-container (command line "webapp-container 
--app-id=ubuntu-amazon-default --webapp --enable-back-forward 
http://www.amazon.com/?tag=u1webapp-20;)
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 7682) Mon Oct 10 15:55:12 2016: wrote report 
/var/crash/_usr_bin_webapp-container.999.crash
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CrashReports:
   644:999:123:0:2016-10-10 15:55:49.656395711 +0100:2016-10-10 
15:55:49.656395711 +0100:/var/crash/_usr_bin_webapp-container.999.upload
   600:115:123:0:2016-10-10 15:55:53.524429871 +0100:2016-10-10 
15:55:53.524429871 +0100:/var/crash/_usr_bin_webapp-container.999.uploaded
   640:999:123:15139136:2016-10-10 15:55:48.040390253 +0100:2016-10-10 
15:55:49.040390253 +0100:/var/crash/_usr_bin_webapp-container.999.crash
  CurrentDesktop: Unity
  Date: Mon Oct 10 15:57:49 2016
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1629428] Re: [2522AC1, Conexant CX20585, Black Mic, Right] Recording problem. Mic Unplugged however responds to internal mic

2016-10-10 Thread Xalek
Is there any further information I can provide to help?

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

Title:
  [2522AC1, Conexant CX20585, Black Mic, Right] Recording problem. Mic
  Unplugged however responds to internal mic

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The internal microphone on this T410 works.

  I have a splitter cable in order to use the combo audio jack with a
  dedicated external microphone. This setup works on a Windows7
  installation.

  When viewing the information in sound settings in xubuntu, I have

  Internal Microphone
  Microphone (Unplugged)
  Dock Microphone (Unplugged)

  The internal Microphone works as expected, gains controllable.

  When I select Microphone (Unplugged), with my external microphone
  connected, I don't appear to get an output. However, if I tap the
  screen, where the internal Mic is, the volume levels are off the
  chart. If I unplug the external microphone, the same result can be
  observed.

  It appears both 'Internal Mic', and 'Microphone (Unplugged)' are
  grabbing audio from the same source (The internal microphone), just
  applying a different gain to it.

  Best Wishes

  Xalek

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   xander 1205 F...m pulseaudio
   /dev/snd/pcmC0D0p:   xander 1205 F...m pulseaudio
   /dev/snd/controlC0:  xander 1205 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Sep 30 20:07:14 2016
  InstallationDate: Installed on 2016-08-21 (40 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Black Mic, Right
  Symptom_Type: Only some of inputs are working
  Title: [2522AC1, Conexant CX20585, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2522AC1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2522AC1:pvrThinkPadT410:rvnLENOVO:rn2522AC1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2522AC1
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-09-30T13:48:19.621569

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

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


[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-10-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.13.0-98.145

---
linux (3.13.0-98.145) trusty; urgency=low

  * Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.

  * CVE-2016-7039
- SAUCE: net: add recursion limit to GRO

linux (3.13.0-97.144) trusty; urgency=low

  [ Joseph Salisbury ]

  * Release Tracking Bug
- LP: #1626604

  * Altering use_tempaddr drops all IPv6 addresses (LP: #994931)
- Revert "UBUNTU: SAUCE: (no-up) ipv6: Fix net.ipv6.conf.all.use_tempaddr
  sysctl"
- Revert "UBUNTU: SAUCE: (no-up) ipv6: make the 
net.ipv6.conf.all.use_tempaddr
  sysctl propagate to interface settings"
- neigh: convert parms to an array
- neigh: wrap proc dointvec functions
- neigh: use tbl->family to distinguish ipv4 from ipv6
- neigh: restore old behaviour of default parms values
- neigh: ipv6: respect default values set before an address is assigned to
  device

  * PCI quirk required for correct access to configuration space of NFP
4000/6000 (LP: #1624267)
- PCI: Support PCIe devices with short cfg_size
- PCI: Add Netronome vendor and device IDs
- PCI: Limit config space size for Netronome NFP6000 family
- PCI: Add Netronome NFP4000 PF device ID
- PCI: Limit config space size for Netronome NFP4000

  * CVE-2016-6136
- audit: fix a double fetch in audit_log_single_execve_arg()

  * CVE-2016-6480
- aacraid: Check size values after double-fetch from user

  * CVE-2016-6828
- tcp: fix use after free in tcp_xmit_retransmit_queue()

  * IPv6 with LVS Performance issue in latest 3.13LTS kernels (LP: #1618299)
- ipv6: remove prune parameter for fib6_clean_all
- ipv6: remove rt6i_genid

  * lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
(LP: #1619918)
- btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in
  btrfs_ioctl

  * Miscellaneous upstream changes
- powerpc/pseries: use pci_host_bridge.release_fn() to kfree(phb)

 -- Seth Forshee   Fri, 07 Oct 2016 20:08:32
-0500

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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


[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-10-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.19.0-71.79

---
linux (3.19.0-71.79) vivid; urgency=low

  * Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of FOU/GUE

  * CVE-2016-7039
- SAUCE: net: add recursion limit to GRO

linux (3.19.0-70.78) vivid; urgency=low

  [ Joseph Salisbury ]

  * Release Tracking Bug
- LP: #1625788

  * CVE-2016-6136
- audit: fix a double fetch in audit_log_single_execve_arg()

  * CVE-2016-6480
- aacraid: Check size values after double-fetch from user

  * CVE-2016-6828
- tcp: fix use after free in tcp_xmit_retransmit_queue()

  * lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
(LP: #1619918)
- btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in
  btrfs_ioctl

 -- Seth Forshee   Fri, 07 Oct 2016 20:11:52
-0500

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

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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


[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-10-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.19.0-71.79

---
linux (3.19.0-71.79) vivid; urgency=low

  * Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of FOU/GUE

  * CVE-2016-7039
- SAUCE: net: add recursion limit to GRO

linux (3.19.0-70.78) vivid; urgency=low

  [ Joseph Salisbury ]

  * Release Tracking Bug
- LP: #1625788

  * CVE-2016-6136
- audit: fix a double fetch in audit_log_single_execve_arg()

  * CVE-2016-6480
- aacraid: Check size values after double-fetch from user

  * CVE-2016-6828
- tcp: fix use after free in tcp_xmit_retransmit_queue()

  * lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
(LP: #1619918)
- btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in
  btrfs_ioctl

 -- Seth Forshee   Fri, 07 Oct 2016 20:11:52
-0500

** Changed in: linux (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6136

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6480

** Changed in: linux (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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


[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-10-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.4.0-42.62

---
linux (4.4.0-42.62) xenial; urgency=low

  * Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of FOU/GUE

  * CVE-2016-7039
- SAUCE: net: add recursion limit to GRO

linux (4.4.0-41.61) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1628204

  * nvme drive probe failure (LP: #1626894)
- (fix) NVMe: Don't unmap controller registers on reset

linux (4.4.0-40.60) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1627074

  * Permission denied in CIFS with kernel 4.4.0-38 (LP: #1626112)
- Fix memory leaks in cifs_do_mount()
- Compare prepaths when comparing superblocks
- SAUCE: Fix regression which breaks DFS mounting

  * Backlight does not change when adjust it higher than 50% after S3
(LP: #1625932)
- SAUCE: i915_bpo: drm/i915/backlight: setup and cache pwm alternate
  increment value
- SAUCE: i915_bpo: drm/i915/backlight: setup backlight pwm alternate
  increment on backlight enable

linux (4.4.0-39.59) xenial; urgency=low

  [ Joseph Salisbury ]

  * Release Tracking Bug
- LP: #1625303

  * thunder: chip errata w/ multiple CQEs for a TSO packet (LP: #1624569)
- net: thunderx: Fix for issues with multiple CQEs posted for a TSO packet

  * thunder: faulty TSO padding (LP: #1623627)
- net: thunderx: Fix for HW issue while padding TSO packet

  * CVE-2016-6828
- tcp: fix use after free in tcp_xmit_retransmit_queue()

  * Sennheiser Officerunner - cannot get freq at ep 0x83 (LP: #1622763)
- SAUCE: (no-up) ALSA: usb-audio: Add quirk for sennheiser officerunner

  * Backport E3 Skylake Support in ie31200_edac to Xenial (LP: #1619766)
- EDAC, ie31200_edac: Add Skylake support

  * Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices (LP: #1602724)
- SAUCE: nvme: Don't suspend admin queue that wasn't created

  * ISST-LTE:pNV: system ben is hung during ST (nvme) (LP: #1620317)
- blk-mq: Allow timeouts to run while queue is freezing
- blk-mq: improve warning for running a queue on the wrong CPU
- blk-mq: don't overwrite rq->mq_ctx

  * lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
(LP: #1619918)
- btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in
  btrfs_ioctl

  * radeon: monitor connected to onboard VGA doesn't work with Xenial
(LP: #1600092)
- drm/radeon/dp: add back special handling for NUTMEG

  * initramfs includes qle driver, but not firmware (LP: #1623187)
- qed: add MODULE_FIRMWARE()

  * [Hyper-V] Rebase Hyper-V to 4.7.2 (stable) (LP: #1616677)
- hv_netvsc: Implement support for VF drivers on Hyper-V
- hv_netvsc: Fix the list processing for network change event
- Drivers: hv: vmbus: Introduce functions for estimating room in the ring
  buffer
- Drivers: hv: vmbus: Use READ_ONCE() to read variables that are volatile
- Drivers: hv: vmbus: Export the vmbus_set_event() API
- lcoking/barriers, arch: Use smp barriers in smp_store_release()
- asm-generic: guard smp_store_release/load_acquire
- x86: reuse asm-generic/barrier.h
- asm-generic: add __smp_xxx wrappers
- x86: define __smp_xxx
- asm-generic: implement virt_xxx memory barriers
- Drivers: hv: vmbus: Move some ring buffer functions to hyperv.h
- Drivers: hv: vmbus: Implement APIs to support "in place" consumption of
  vmbus packets
- drivers:hv: Lock access to hyperv_mmio resource tree
- drivers:hv: Make a function to free mmio regions through vmbus
- drivers:hv: Track allocations of children of hv_vmbus in private resource
  tree
- drivers:hv: Separate out frame buffer logic when picking MMIO range
- Drivers: hv: vmbus: handle various crash scenarios
- Drivers: hv: balloon: don't crash when memory is added in non-sorted order
- Drivers: hv: balloon: reset host_specified_ha_region
- tools: hv: lsvmbus: add pci pass-through UUID
- hv_netvsc: move start_remove flag to net_device_context
- hv_netvsc: use start_remove flag to protect netvsc_link_change()
- hv_netvsc: untangle the pointer mess
- hv_netvsc: get rid of struct net_device pointer in struct netvsc_device
- hv_netvsc: synchronize netvsc_change_mtu()/netvsc_set_channels() with
  netvsc_remove()
- hv_netvsc: set nvdev link after populating chn_table
- hv_netvsc: Fix VF register on vlan devices
- hv_netvsc: remove redundant assignment in netvsc_recv_callback()
- hv_netvsc: introduce {net, hv}_device_to_netvsc_device() helpers
- hv_netvsc: pass struct netvsc_device to rndis_filter_{open, close}()
- hv_netvsc: pass struct net_device to rndis_filter_set_device_mac()
- hv_netvsc: pass struct net_device to rndis_filter_set_offload_params()
- netvsc: get 

[Touch-packages] [Bug 1626454] Re: can't connect with owncloud calendars

2016-10-10 Thread slash
To sort out my issue, I've:
- Create a new user with a weaker password,
- share my calendar to this new user,
- connect the ubuntu owncloud account to this new user.

Rgds

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

Title:
  can't connect with owncloud calendars

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu Calendar App:
  New
Status in account-plugins package in Ubuntu:
  Fix Released

Bug description:
  Running my own ownCloud (v9.1.1). Tried to connect Aquarius 4.5 with Calendar 
App
  The httpS certificate is official, up to date and not self-signed
  I use 7 calendars in my ownCloud-calendar-app.
  (yes, username and password is correct)

  This I tried:

  https://mydomain/owncloud/(suggested minimal path on the phone)
  Error message: Invalid username or password

  https://mydomain/owncloud/remote.php/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/   --> (This is the primary caldav 
address suggested by ownCloud calendar-app)
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/
  Error message: Invalid host URL

  
  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/MYCALENDARNAME/
  Error message: Invalid host URL
  --> This direct path to one of my calendars I use for example to connect my 
different calendars with Thunderbird lightning (its working)

  I tried all with and without ending "/"

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

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


[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-10 Thread Jason Gerard DeRose
@chiluk - the package in your PPA fixes it from my use case, thanks!

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Confirmed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
 networking.

   * Discover that the device never comes up because, networking is not
  conifgured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.

  [Other Info]
   
   * There are a number of other issues in this code base that are not solved 
by this fix.
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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


[Touch-packages] [Bug 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI

2016-10-10 Thread Olivier Tilloy
** Also affects: ubuntu-touch-session (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-touch-session (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

** Summary changed:

- 48 webbrowser_app autopilot test failures on krillin in CI
+ autopilot tests fail on newly flashed devices because GRID_UNIT_PX is not set

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

Title:
  autopilot tests fail on newly flashed devices because GRID_UNIT_PX is
  not set

Status in ubuntu-touch-session package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The autopilot tests for webbrowser_app have been failing in CI (system-apps 
jenkins instance) for about a month.
  Before that they reliably passed.
  They are being run on a krillin device that is being flashed anew for every 
single run. The device hasn’t changed.

  The last known successful run was on August 10:
  https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/.

  The next run on a webbrowser-app branch didn’t happen until August 27,
  and it failed: https://jenkins.canonical.com/system-
  apps/job/test-0-autopkgtest/308/.

  Something happened in between those two dates that broke the tests.
  It might be something in the infrastructure rather than in webbrowser-app 
itself, given that the tests all pass when run on my krillin at home.

  I am attaching the full log for the first failing run on August 27.

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

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


[Touch-packages] [Bug 1630969] Re: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

2016-10-10 Thread Brian Murray
I tried an upgrade from Xenial to Yakkety today and did not encounter
this error.  Perhaps this change fixed it?

android-tools (5.1.1r36+git20160322-0ubuntu5) yakkety; urgency=medium

  [ You-Sheng Yang ]
  * debian/rules, debian/control, debian/android-tools-adbd.*:
- Install systemd service files

 -- Łukasz 'sil2100' Zemczak   Wed, 05 Oct
2016 13:32:02 +0200

** Changed in: android-tools (Ubuntu)
   Importance: Undecided => High

** Changed in: android-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 5

Status in android-tools package in Ubuntu:
  Incomplete

Bug description:
  that package is not upgadable, that is all i can say, sorry)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Oct  6 04:03:47 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 5
  InstallationDate: Installed on 2016-09-23 (13 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160726)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: android-tools
  Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1630969] Re: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

2016-10-10 Thread Dan Attwood
I can confirm that this also works for me.

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

Title:
  package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 5

Status in android-tools package in Ubuntu:
  Incomplete

Bug description:
  that package is not upgadable, that is all i can say, sorry)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Oct  6 04:03:47 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 5
  InstallationDate: Installed on 2016-09-23 (13 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160726)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: android-tools
  Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1631575] Re: Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service not loaded.

2016-10-10 Thread Brian Murray
*** This bug is a duplicate of bug 1630969 ***
https://bugs.launchpad.net/bugs/1630969

VarLogDistUpgradeAttermlog.txt actually show
5.1.1r36+git20160322-ubuntu4 not ubuntu5 as listed in the description.

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

Title:
  Failed to stop android-tools-adbd.service: Unit android-tools-
  adbd.service not loaded.

Status in android-tools package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  dist=upgrade fails with:

  
  Preparing to unpack 
.../android-tools-adbd_5.1.1r36+git20160322-0ubuntu5_amd64.deb ...
  Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service 
not loaded.
  invoke-rc.d: initscript android-tools-adbd, action "stop" failed.
  dpkg: warning: subprocess old pre-removal script returned error exit status 5
  dpkg: trying script from the new package instead ...
  Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service 
not loaded.
  dpkg: error processing archive 
/var/cache/apt/archives/android-tools-adbd_5.1.1r36+git20160322-0ubuntu5_amd64.deb
 (--unpack):

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.5
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Sat Oct  8 08:43:03 2016
  InstallationDate: Installed on 2015-04-10 (546 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-08-28 (40 days ago)
  VarLogDistupgradeTermlog:

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

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


[Touch-packages] [Bug 1631575] Re: Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service not loaded.

2016-10-10 Thread Brian Murray
*** This bug is a duplicate of bug 1630969 ***
https://bugs.launchpad.net/bugs/1630969

** Also affects: android-tools (Ubuntu)
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1630969
   package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5

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

Title:
  Failed to stop android-tools-adbd.service: Unit android-tools-
  adbd.service not loaded.

Status in android-tools package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  dist=upgrade fails with:

  
  Preparing to unpack 
.../android-tools-adbd_5.1.1r36+git20160322-0ubuntu5_amd64.deb ...
  Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service 
not loaded.
  invoke-rc.d: initscript android-tools-adbd, action "stop" failed.
  dpkg: warning: subprocess old pre-removal script returned error exit status 5
  dpkg: trying script from the new package instead ...
  Failed to stop android-tools-adbd.service: Unit android-tools-adbd.service 
not loaded.
  dpkg: error processing archive 
/var/cache/apt/archives/android-tools-adbd_5.1.1r36+git20160322-0ubuntu5_amd64.deb
 (--unpack):

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.5
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Sat Oct  8 08:43:03 2016
  InstallationDate: Installed on 2015-04-10 (546 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-08-28 (40 days ago)
  VarLogDistupgradeTermlog:

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

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


[Touch-packages] [Bug 1621824] Re: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap."

2016-10-10 Thread bugproxy
** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start
  Set console keymap."

Status in kbd package in Ubuntu:
  Fix Released
Status in kbd source package in Xenial:
  Fix Committed
Status in kbd source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  On ppc64el, console keyboard maps will not be set at boot time because of a 
bug in detecting which VT is "safe" to use for setting the map.  This problem 
does not affect amd64 purely by chance, or because of which toolchain version 
or toolchain options were used to build the binary on each architecture; a 
rebuild of the kbd package could also introduce the problem on amd64.

  [Test case]
  1. On ppc64el, run 'sudo loadkeys /etc/console-setup/cached.kmap.gz'
  2. Confirm that you are shown an error, "Couldn't get a file descriptor 
referring to the console".
  3. Install the kbd package from xenial-proposed.
  4. Run 'sudo loadkeys /etc/console-setup/cached.kmap.gz' again.
  5. Confirm that no error message is shown and the command exits with staus 0.
  6. Repeat steps 3-6 on amd64.

  [Regression potential]
  Since keymap settings are currently not being applied on ppc64el, it's 
possible that someone who has configured a non-default keymap on a ppc64el 
system will be surprised after upgrade that their keymap has changed.

  
  == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 ==
   State: Open by: knodelk on 23 August 2016 14:00:43 

  Seeing the following error message in the Ubuntu dmesg log following
  IPL to Ubuntu on system with Ubuntu 16.04.1 installed:

  # dmesg -T --level=alert,crit,err
  [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap.

  This appears to be something that can be ignored so manufacturing will
  be ignoring this message until directed otherwise.

  ==> all systemd related messages:
  # dmesg -T | grep systemd
  [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. 
(+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
  [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to .
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event 
daemon FIFOs.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to 
Wall Directory Watch.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl 
Compatibility Named Pipe.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log).
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name 
Lookups.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd 
communication Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon 
socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File 
System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required 
static device nodes for the current kernel...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information 
manager...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, 
snapshots etc. using dmeventd or progress polling...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice 
system-serial\x2dgetty.slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable 
File Formats File System Automount Point.
  [Tue Aug 23 09:20:12 2016] systemd[1]: 

[Touch-packages] [Bug 1471087] Re: Battery power indicator shows incorrect battery percentage when fully charged

2016-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-power (Ubuntu)
   Status: New => Confirmed

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

Title:
  Battery power indicator shows incorrect battery percentage when fully
  charged

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04

  
  indicator-power:
Installed: 12.10.6+15.04.20150402-0ubuntu1
Candidate: 12.10.6+15.04.20150402-0ubuntu1
Version table:
   *** 12.10.6+15.04.20150402-0ubuntu1 0
  500 http://kr.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Power indicator currently showing 70%, however, battery is fully charged and 
running on AC power.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-power 12.10.6+15.04.20150402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  2 22:14:47 2015
  InstallationDate: Installed on 2015-06-20 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1471087] Re: Battery power indicator shows incorrect battery percentage when fully charged

2016-10-10 Thread Luigi Filippo Pavan
In my case: even after unplugging charging cable it shows wrong
percentage (below 100%)

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

Title:
  Battery power indicator shows incorrect battery percentage when fully
  charged

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04

  
  indicator-power:
Installed: 12.10.6+15.04.20150402-0ubuntu1
Candidate: 12.10.6+15.04.20150402-0ubuntu1
Version table:
   *** 12.10.6+15.04.20150402-0ubuntu1 0
  500 http://kr.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Power indicator currently showing 70%, however, battery is fully charged and 
running on AC power.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-power 12.10.6+15.04.20150402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  2 22:14:47 2015
  InstallationDate: Installed on 2015-06-20 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI

2016-10-10 Thread Olivier Tilloy
It appears that the regression was introduced by the change to ubuntu-
touch-session: https://bazaar.launchpad.net/~phablet-team/ubuntu-touch-
session/trunk/revision/288.

If I set the value of GRID_UNIT_PX in ~/.profile on the device and
reboot, the tests pass again.

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

Title:
  48 webbrowser_app autopilot test failures on krillin in CI

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The autopilot tests for webbrowser_app have been failing in CI (system-apps 
jenkins instance) for about a month.
  Before that they reliably passed.
  They are being run on a krillin device that is being flashed anew for every 
single run. The device hasn’t changed.

  The last known successful run was on August 10:
  https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/.

  The next run on a webbrowser-app branch didn’t happen until August 27,
  and it failed: https://jenkins.canonical.com/system-
  apps/job/test-0-autopkgtest/308/.

  Something happened in between those two dates that broke the tests.
  It might be something in the infrastructure rather than in webbrowser-app 
itself, given that the tests all pass when run on my krillin at home.

  I am attaching the full log for the first failing run on August 27.

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

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


[Touch-packages] [Bug 1631981] Re: Unity 8 System Settings should not be accessible from Unity 7

2016-10-10 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1631981

** Tags added: iso-testing

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

Title:
  Unity 8 System Settings should not be accessible from Unity 7

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I have literally no idea what package would be responsible for this
  issue (well, perhaps unity, or ubuntu-meta, but I'm not sure), so
  please change that!

  ---

  It should not be possible to access Unity 8's System Settings from
  Unity 7, not from the Dash and not by default. It's confusing for
  users who don't understand what it is, because changing the Unity 7
  background with the application doesn't work - presumably it's not
  meant to. Changing the primary button of the mouse/touchpad doesn't
  work either.

  Perhaps the Unity 8 System Settings program should work on Unity 7, in
  which case I should report the background's issue as a bug? Do tell me
  if these are bugs in the application not in Ubuntu's meta decision.
  Thanks!

  Computer info:
  VirtualBox Graphical User Interface Version 5.0.24_Ubuntu r108355
  (I don't have access to spare hardware to test on at the moment)
  Allocated 2GB RAM
  Host OS: Ubuntu 16.04 LTS 64-bit
  Lenovo ThinkPad X201

  Live session from the Ubuntu 16.10 20161008 ISO

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

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


[Touch-packages] [Bug 1631988] Re: Web browser didn't appear when 'Report a problem...' asked if I could add more info to a bug report that would come up in a web browser window

2016-10-10 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1631988

** Tags added: iso-testing

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

Title:
  Web browser didn't appear when 'Report a problem...' asked if I could
  add more info to a bug report that would come up in a web browser
  window

Status in apport package in Ubuntu:
  New

Bug description:
  I tried loading Checkbox in the live session, the 'Report a
  Problem...' dialogue came up and told me that the problem had already
  reported and asked if I could add more detail to the bug when it came
  up in the web browser, but the web browser didn't load.

  Computer info:
  VirtualBox Graphical User Interface Version 5.0.24_Ubuntu r108355
  (I don't have access to spare hardware to test on at the moment)
  Allocated 2GB RAM
  Host OS: Ubuntu 16.04 LTS 64-bit
  Lenovo ThinkPad X201

  Live session from the Ubuntu 16.10 20161008 ISO

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport 2.20.3-0ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportLog:
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: called for pid 7616, 
signal 11, core limit 0
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: executable: 
/usr/bin/webapp-container (command line "webapp-container 
--app-id=ubuntu-amazon-default --webapp --enable-back-forward 
http://www.amazon.com/?tag=u1webapp-20;)
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 7682) Mon Oct 10 15:55:12 2016: wrote report 
/var/crash/_usr_bin_webapp-container.999.crash
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CrashReports:
   644:999:123:0:2016-10-10 15:55:49.656395711 +0100:2016-10-10 
15:55:49.656395711 +0100:/var/crash/_usr_bin_webapp-container.999.upload
   600:115:123:0:2016-10-10 15:55:53.524429871 +0100:2016-10-10 
15:55:53.524429871 +0100:/var/crash/_usr_bin_webapp-container.999.uploaded
   640:999:123:15139136:2016-10-10 15:55:48.040390253 +0100:2016-10-10 
15:55:49.040390253 +0100:/var/crash/_usr_bin_webapp-container.999.crash
  CurrentDesktop: Unity
  Date: Mon Oct 10 15:57:49 2016
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1532125] Re: lxc-clone: Use btrfs backing store if original container does

2016-10-10 Thread Christian Brauner
Fixed by https://github.com/lxc/lxc/pull/760.

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

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

Title:
  lxc-clone: Use btrfs backing store if original container does

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  lxc-clone documents the backingstore option as "Select a different
  backing store for the new container. By default the same as the
  original container's is used.". This sounds like if the original
  container uses btrfs, the cloned container should as well.

  I have the LXC data dir on btrfs, and did lxc-create -n adt-xenial -B
  best. This correctly selected btrfs backing store:

  ID 293 gen 16369 top level 5 path lxc/adt-xenial/rootfs

  However, cloning is slow:

  $ time sudo lxc-clone -o adt-xenial -n x1
  Created container x1 as copy of adt-xenial

  real  0m9.417s
  user  0m1.359s
  sys   0m4.436s

  It did create a new btrfs snapshot:
  ID 297 gen 16372 top level 5 path lxc/x1/rootfs

  but apparently not as a copy of the original  lxc/adt-xenial/rootfs
  one.

  If I explicitly select btrfs as backingstore, it works as intended:

  $ time sudo lxc-clone -B btrfs -o adt-xenial -n x1
  Created container x1 as copy of adt-xenial

  real  0m0.136s
  user  0m0.004s
  sys   0m0.012s

  However, for scripts this is impractical, as it's not quite obvious
  how to determine whether the original container uses btrfs backing
  store, and "-B best" (which works for lxc-create) does not work for
  lxc-clone. So it seems lxc-clone does not actually use "the same -B as
  the original container"?

  I haven't tested this for other backing stores.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 1.1.5-0ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  8 10:10:03 2016
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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


[Touch-packages] [Bug 1459751] Re: lxc-attach runs in wrong container directory

2016-10-10 Thread Christian Brauner
I don't think we can change this behavior since too many users might
rely on this.

** Changed in: lxc (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  lxc-attach runs in wrong container directory

Status in lxc package in Ubuntu:
  Won't Fix

Bug description:
  net8-rmt# lxc-attach -n test -- bash -c 'id && egrep ^root /etc/passwd && 
echo ~ && echo $HOME && pwd'
  uid=0(root) gid=0(root) groups=0(root)
  root:x:0:0:root:/root:/bin/bash
  /root
  /root
  /

  Notice pwd show / instead of /root which is incorrect + causes all
  manner of confusion when debugging path related problems.

  net8-rmt# uname -a
  Linux ns515383.ip-167-114-159.net 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 
18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  net8-rmt# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.04
  Release:  15.04
  Codename: vivid

  Same behavior with containers created with precise through wily
  releases.

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

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


[Touch-packages] [Bug 1543016] Re: lxc-destroy --quiet is not quiet

2016-10-10 Thread Christian Brauner
** Changed in: lxc (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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1543016

Title:
  lxc-destroy --quiet is not quiet

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Since version 2.0.0beta, lxc-destroy is now verbose even when calling
  with --quiet:

  $ sudo lxc-clone -o adt-xenial -n foo
  $ sudo lxc-destroy --quiet -n foo 
  Destroyed container foo

  Not a biggie, but it broke some expectation in autopkgtest. I'll work
  around it there, but this doesn't look intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0~beta2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: i3
  Date: Mon Feb  8 09:05:08 2016
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  dnsmasq.conf:
   enable-tftp
   tftp-root=/tmp/tftp
   dhcp-boot=pxelinux.0
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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


[Touch-packages] [Bug 1413343] Re: lxc-create debug output is broken or useless

2016-10-10 Thread Christian Brauner
This is now also documented on https://linuxcontainers.org/lxc/getting-
started/.

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

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

Title:
  lxc-create debug output is broken or useless

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Can't create container and debug output doesn't explain anything:

  $ lxc-create --logpriority=DEBUG -n buildbox -o here.log
  lxc-create: Error creating container buildbox
  $ cat here.log 
   lxc-create 1421867190.847 WARN lxc_log - lxc_log_init called with 
log already initialized
   lxc-create 1421867190.847 ERRORlxc_create_ui - Error creating 
container buildbox

  I doubt that --logpriority option is processed at all:

  $ lxc-create --logpriority=wat -n buildbox -o here.log
  lxc-create: Error creating container buildbox

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Jan 21 21:55:50 2015
  InstallationDate: Installed on 2012-03-12 (1045 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  KernLog:
   Jan 21 07:40:13 SONiC kernel: [82266.453659] type=1400 
audit(1421815213.422:96): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=17589 
comm="apparmor_parser"
   Jan 21 07:40:13 SONiC kernel: [82266.453673] type=1400 
audit(1421815213.422:97): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=17589 comm="apparmor_parser"
   Jan 21 07:40:13 SONiC kernel: [82266.454329] type=1400 
audit(1421815213.422:98): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=17589 comm="apparmor_parser"
  SourcePackage: lxc
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (277 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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


[Touch-packages] [Bug 1624331] Re: tst_listitem_focus.13.qml unit test failure

2016-10-10 Thread Tim Peeters
** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

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

Title:
  tst_listitem_focus.13.qml unit test failure

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

Bug description:
  FAIL!  : 
components::ListItemFocus::test_refocus_listview_on_last_focused_item(No 
content) 'Focus frame shown for the item' returned FALSE. ()
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_listitem_focus.13.qml(504)]

  
  See 
https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull

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

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


[Touch-packages] [Bug 1631955] Re: Update e-d-s to 3.22.1

2016-10-10 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/evolution-data-server/ubuntu

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

Title:
  Update e-d-s to 3.22.1

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  ==
  There's a new release of evolution-data-server (e-d-s) from the stable 3.22 
branch. This release
  - Update translations
  - Fixes some console warnings caused by search folders when quitting an app
  - Attempts to fix Google Authentication token expired issue. The bug was 
re-opened upstream because the fixes worked for one person but apparently 
weren't enough for another.
  I experienced the Google expired token bug myself but I haven't verified yet 
whether the update fixes the issue. See attached GNOME bug.

  Since e-d-s is an important library/service used by several apps and
  shipped on all Ubuntu desktop flavors (I think), I suggest we not try
  to rush this into yakkety at the last moment before release, but
  handle it like a regular SRU.

  The e-d-s update is required to update evolution from 3.22 to 3.22.1.

  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22
  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22

  Test Case
  =
  Check several of evolution-data-server's reverse-dependencies to ensure 
they're still working.

  $ reverse-depends src:evolution-data-server

  Regression Potential
  
  Basically only search folders and Google authentication were touched in this 
update, so check those for problems. The Evolution stack is big and complex but 
this is a fairly minor stable release update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evolution-data-server 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 09:23:02 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1631955/+subscriptions

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


[Touch-packages] [Bug 1271455] Re: lxc-create does not honor $HTTP_PROXY when using a cached base image

2016-10-10 Thread Christian Brauner
** Changed in: lxc (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  lxc-create does not honor $HTTP_PROXY when using a cached base image

Status in lxc:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I just learned that one can call lxc-create with $HTTP_PROXY set to
  configure an apt proxy in the container. However, this only seems to
  work when it actually downloads and creates a base image. When it's
  using a cache it doesn't work:

  $ sudo HTTP_PROXY=http://donald:3142 lxc-create -t ubuntu -n precise-i386 -- 
-r precise -a i386
  Checking cache download in /var/cache/lxc/precise/rootfs-i386 ... 
  Copy /var/cache/lxc/precise/rootfs-i386 to /scratch/lxc/precise-i386/rootfs 
... 
  Copying rootfs to /scratch/lxc/precise-i386/rootfs ...
  [...]

  $ ls -l /scratch/lxc/precise-i386/rootfs/etc/apt/apt.conf.d/
  insgesamt 16
  -rw-r--r-- 1 root root 350 Nov 15 16:35 01autoremove
  -rw-r--r-- 1 root root 372 Jan 22 10:08 01autoremove-kernels
  -rw-r--r-- 1 root root 123 Apr 20  2012 20changelog
  -rw-r--r-- 1 root root 182 Mär 15  2012 70debconf

  i. e. there is no 70proxy.

  When appending -F it works. However, 70proxy is *not* in the cache, so
  lxc-create does create that after creating the cache. Hence it should
  not be too difficult to also create 70proxy after copying an existing
  cache?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.0~beta2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 22 10:15:32 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-14 (100 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131013)
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /scratch/lxc

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

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


[Touch-packages] [Bug 1623763] Re: GTK Inspector Statistics tab non-functional

2016-10-10 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  GTK Inspector Statistics tab non-functional

Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Running a GTK+ 3 app with GOBJECT_DEBUG=instance-count enables the
  Statistics tab in GTK Inspector, but after clicking the Record button
  it never starts collecting statistics. This makes it difficult to
  develop and debug memory leaks in GTK programs on Ubuntu.

  To reproduce:

  1. Start an app with the Inspector and GOBJECT_DEBUG=instance-count
  set, e.g.:

  > GOBJECT_DEBUG=instance-count GTK_DEBUG=interactive gnome-calculator

  2. Click the Statistics tab
  3. Click the Record button
  4. Click around the app a bit

  Expected: Object counts go up, pretty graphs showing things
  Actual: Object counts stay at 0, pretty graphs showing flat lines

  This seems like it is Ubuntu-specific, since when running GTK+
  programs installed via Flatpak (and hence using the Flatpak runtime),
  the above works fine on the same system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-dev 3.20.8-1ubuntu0~ppa1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 15 13:05:19 2016
  InstallationDate: Installed on 2015-07-22 (421 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (196 days ago)

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

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


[Touch-packages] [Bug 1631002] Re: fwupd crashed with SIGSEGV in malloc_consolidate()

2016-10-10 Thread Sebastien Bacher
** Information type changed from Private to Public

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

Title:
  fwupd crashed with SIGSEGV in malloc_consolidate()

Status in fwupd package in Ubuntu:
  New
Status in libusb package in Ubuntu:
  New

Bug description:
  fwupd crashed with SIGSEGV in malloc_consolidate()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: fwupd 0.7.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Oct  6 19:48:13 2016
  ExecutablePath: /usr/lib/x86_64-linux-gnu/fwupd/fwupd
  InstallationDate: Installed on 2016-08-20 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/fwupd/fwupd
  ProcEnviron:
   
  Signal: 11
  SourcePackage: fwupd
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f8d3420) at malloc.c:4202
   _int_free (av=0x7f8d3420, p=0x7f8d34003b20, have_lock=0) at malloc.c:4110
   __GI___libc_free (mem=) at malloc.c:2982
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: fwupd crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (32 days ago)
  UserGroups:

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

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


[Touch-packages] [Bug 1583102] Re: Could not execute 'apt-key' to verify signature (is gnupg installed?)

2016-10-10 Thread Marty Ellis
My problem was caused by using vagrant.  Vagrant sets the tmp owner to
vagrant:vagrant.  @sgrimm -  I followed your advice and that resolved my
issue.

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

Title:
  Could not execute 'apt-key' to verify signature (is gnupg installed?)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04 I'm getting this error for all my apt
  sources.

  This seems different to both
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1524196 (since I
  don't get the "Couldn't create tempfiles for splitting up
  /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-
  updates_InRelease" errors) and
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1577926 (since apt-
  key run by itself fails too).

  Downgrading to apt=1.0.10.2ubuntu2 fixed the problem so it seems to be
  related to recent changes in apt.

  Thanks!

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

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


[Touch-packages] [Bug 1631491] Re: Can't change a configuration option with dconf CLI

2016-10-10 Thread Sebastien Bacher
Thanks but that's not a bug, see e.g
http://askubuntu.com/questions/487206/dconf-change-a-string-key

you should also probably use "gsettings set ..." instead

** Changed in: d-conf (Ubuntu)
   Importance: Undecided => Low

** Changed in: d-conf (Ubuntu)
   Status: New => Invalid

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

Title:
  Can't change a configuration option with dconf CLI

Status in d-conf package in Ubuntu:
  Invalid

Bug description:
  I'm trying to change a configuration option with dconf on command line
  (to make automatic after that) but always occurs an error:

  $ dconf write /org/gnome/desktop/interface/monospace-font-name "Noto Mono 10"
  error: 0-1:unknown keyword

  Usage:
dconf write KEY VALUE 
  ... (all the rest of usage message for write parameter)

  Works well using dconf-editor, so I think the problem is in the CLI
  itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dconf-cli 0.26.0-2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  7 16:11:51 2016
  InstallationDate: Installed on 2016-05-03 (157 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: d-conf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1631763] Re: Ubuntu needs a GPU accelerated browser

2016-10-10 Thread Alberto Salvia Novella
** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Low

** Changed in: firefox (Ubuntu)
   Importance: Undecided => Low

** Also affects: chromium-browser (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Ubuntu needs a GPU accelerated browser

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  We all know the Web support of an operating system is becoming more
  and more important for users.

  The situation right now in terms of browser Performance and power
  consumption of GNU/Linux is not really in a good shape compared to the
  2 other competitors : Windows and Mac OSX.

  Windows 10 : Microsoft has shown how its integrated browser is more
  efficient and less hungry on power consumption than other browsers.

  Mac OSX: Safari is also showing a great power consumption and
  integrated features.

  
  SO this bug is to track progress for an integrated browser for Ubuntu ( can 
be firefox, chromium, something else ) that would out of the box  : 

  
  - Use GPU for video decoding 

  - Use GPU for Web 3D rendering like webGL

  - integrate as much as possible EME HTML5 for DRM support (like
  firefox 49 for netflix)

  
  Please suggest other features in the comments

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

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


[Touch-packages] [Bug 1631763] Re: Ubuntu needs a GPU accelerated browser

2016-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu needs a GPU accelerated browser

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  We all know the Web support of an operating system is becoming more
  and more important for users.

  The situation right now in terms of browser Performance and power
  consumption of GNU/Linux is not really in a good shape compared to the
  2 other competitors : Windows and Mac OSX.

  Windows 10 : Microsoft has shown how its integrated browser is more
  efficient and less hungry on power consumption than other browsers.

  Mac OSX: Safari is also showing a great power consumption and
  integrated features.

  
  SO this bug is to track progress for an integrated browser for Ubuntu ( can 
be firefox, chromium, something else ) that would out of the box  : 

  
  - Use GPU for video decoding 

  - Use GPU for Web 3D rendering like webGL

  - integrate as much as possible EME HTML5 for DRM support (like
  firefox 49 for netflix)

  
  Please suggest other features in the comments

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

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


[Touch-packages] [Bug 1631763] Re: Ubuntu needs a GPU accelerated browser

2016-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Ubuntu needs a GPU accelerated browser

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  We all know the Web support of an operating system is becoming more
  and more important for users.

  The situation right now in terms of browser Performance and power
  consumption of GNU/Linux is not really in a good shape compared to the
  2 other competitors : Windows and Mac OSX.

  Windows 10 : Microsoft has shown how its integrated browser is more
  efficient and less hungry on power consumption than other browsers.

  Mac OSX: Safari is also showing a great power consumption and
  integrated features.

  
  SO this bug is to track progress for an integrated browser for Ubuntu ( can 
be firefox, chromium, something else ) that would out of the box  : 

  
  - Use GPU for video decoding 

  - Use GPU for Web 3D rendering like webGL

  - integrate as much as possible EME HTML5 for DRM support (like
  firefox 49 for netflix)

  
  Please suggest other features in the comments

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

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


[Touch-packages] [Bug 1631763] Re: Ubuntu needs a GPU accelerated browser

2016-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu needs a GPU accelerated browser

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  We all know the Web support of an operating system is becoming more
  and more important for users.

  The situation right now in terms of browser Performance and power
  consumption of GNU/Linux is not really in a good shape compared to the
  2 other competitors : Windows and Mac OSX.

  Windows 10 : Microsoft has shown how its integrated browser is more
  efficient and less hungry on power consumption than other browsers.

  Mac OSX: Safari is also showing a great power consumption and
  integrated features.

  
  SO this bug is to track progress for an integrated browser for Ubuntu ( can 
be firefox, chromium, something else ) that would out of the box  : 

  
  - Use GPU for video decoding 

  - Use GPU for Web 3D rendering like webGL

  - integrate as much as possible EME HTML5 for DRM support (like
  firefox 49 for netflix)

  
  Please suggest other features in the comments

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

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


[Touch-packages] [Bug 1631789] Re: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to install/upgrade: EOF on stdin at conffile prompt

2016-10-10 Thread ChristianEhrhardt
Hi,
thank you for your report.

I didn't see anything that would give me a hint - adding unattended-
upgrades in case they could see something in the logs. For sure they
have more experience in how it should behave properly.

** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to
  install/upgrade: EOF on stdin at conffile prompt

Status in ntp package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Looks like unattended-upgrades failed?

  I just ran the update again and it installed an altered config file.

  #> apt-get install ntpdate
  Setting up ntpdate (1:4.2.6.p5+dfsg-3ubuntu2.14.04.10) ...

  Configuration file '/etc/network/if-up.d/ntpdate'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** ntpdate (Y/I/N/O/D/Z) [default=N] ? y
  Installing new version of config file /etc/network/if-up.d/ntpdate ...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10
  ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-96-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  Date: Sun Oct  9 04:07:26 2016
  DpkgHistoryLog:
   Start-Date: 2016-10-09  04:07:05
   Upgrade: chromium-codecs-ffmpeg-extra:amd64 
(52.0.2743.116-0ubuntu0.14.04.1.1134, 53.0.2785.143-0ubuntu0.14.04.1.1142), 
chromium-browser-l10n:amd64 (52.0.2743.116-0ubuntu0.14.04.1.1134, 
53.0.2785.143-0ubuntu0.14.04.1.1142), chromium-browser:amd64 
(52.0.2743.116-0ubuntu0.14.04.1.1134, 53.0.2785.143-0ubuntu0.14.04.1.1142), 
ntpdate:amd64 (4.2.6.p5+dfsg-3ubuntu2.14.04.5, 4.2.6.p5+dfsg-3ubuntu2.14.04.10)
  DpkgTerminalLog: Log started: 2016-10-09  04:07:05
  ErrorMessage: EOF on stdin at conffile prompt
  InstallationDate: Installed on 2014-04-29 (894 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: ntp
  Title: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to 
install/upgrade: EOF on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1631980] Re: Steam not able to see network in yakkety

2016-10-10 Thread Martin Pitt
** No longer affects: systemd (Ubuntu)

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

Title:
  Steam not able to see network in yakkety

Status in steam package in Ubuntu:
  New

Bug description:
  Steam is unable to see the network in yakkety.  Downloads stall and
  don't do anything; and trying to update steam results in a "Fatal
  Error: Steam needs to be online to update.  Please confirm your
  network connection and try again" dialog box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: steam:i386 1:1.0.0.52-5ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 07:43:55 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: steam
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

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

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


[Touch-packages] [Bug 1631781] Re: package dnsmasq 2.75-1ubuntu0.16.04.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2016-10-10 Thread ChristianEhrhardt
Hi,
Thank you for your report.

It seems that someone manually deleted the dnsmasq config, that causes
it to fail on upgrade.

>From the report e.g.:
  modified.conffile..etc.default.dnsmasq: [deleted]

If deleted anyway you can just remove or purge dnsmasq package and be good.
If needed a reinstall afterwards will deploy fresh default configs that work.

So since this looks like a local configuration problem, rather than a
bug in Ubuntu.

You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration problems, I'm marking this bug as Invalid. This helps us
to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package dnsmasq 2.75-1ubuntu0.16.04.1 failed to install/upgrade: le
  sous-processus script post-installation installé a retourné une erreur
  de sortie d'état 1

Status in dnsmasq package in Ubuntu:
  Invalid

Bug description:
  impossible to install it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq 2.75-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   dnsmasq: Install
   dnsmasq: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Oct  9 19:18:29 2016
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2016-08-09 (61 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: dnsmasq
  Title: package dnsmasq 2.75-1ubuntu0.16.04.1 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.dnsmasq: [deleted]
  modified.conffile..etc.dnsmasq.conf: [deleted]
  modified.conffile..etc.init.d.dnsmasq: [deleted]
  modified.conffile..etc.insserv.conf.d.dnsmasq: [deleted]
  modified.conffile..etc.resolvconf.update.d.dnsmasq: [deleted]

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

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


[Touch-packages] [Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

2016-10-10 Thread Andres Rodriguez
** Changed in: maas
   Status: New => Triaged

** Changed in: maas
Milestone: None => 2.1.0

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

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  New
Status in ifupdown source package in Xenial:
  New

Bug description:
  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under
  us.

  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.

  Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1621507: ipv6 network boot does not work

  [Impact]

  With the changes from the above, the iscsi root (at least in the ipv6
  case) gets disconneceted prior to clean shutdown (ifdown downs the
  interface), resulting in a failure to enlist, commission, or deploy
  cleanly under MAAS. (and a failure to cleanly unmount the root
  filesystem when it is over iscsi.)

  [Test Case]

  Given a MAAS 2.0 installation, and the packages in the other bugs,
  attempt to enlist, commission, or deploy a host with xenial.

  [Regression potential]

  This restores the pre-xenial behavior of not shutting down the
  interface if there are network drives at the time that neworking is
  stopped (making it a no-op.)  The additional change is to detect
  "/dev/disk/by-path/*-iscsi-*" as a network disk, replacing the check
  for the existence of /etc/iscsi/iscsi.initramfs, which was only
  created by debian-installer (and maas until recently).

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

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


[Touch-packages] [Bug 1631983] Re: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: no package named 'libopencv-gpu2.4v5' is installed, cannot configure

2016-10-10 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 opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1631983

Title:
  package libopencv-gpu2.4v5 (not installed) failed to install/upgrade:
  no package named 'libopencv-gpu2.4v5' is installed, cannot configure

Status in opencv package in Ubuntu:
  New

Bug description:
  actualicé la versión de ubuntu y han salido muchos errores

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-gpu2.4v5 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Oct  8 18:40:24 2016
  DuplicateSignature:
   package:libopencv-gpu2.4v5:(not installed)
   Setting up python-opencv (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing package libopencv-gpu2.4v5 (--configure):
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  ErrorMessage: no package named 'libopencv-gpu2.4v5' is installed, cannot 
configure
  InstallationDate: Installed on 2016-05-05 (157 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: opencv
  Title: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: 
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (1 days ago)

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

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


[Touch-packages] [Bug 1631988] [NEW] Web browser didn't appear when 'Report a problem...' asked if I could add more info to a bug report that would come up in a web browser window

2016-10-10 Thread Ads20000
Public bug reported:

I tried loading Checkbox in the live session, the 'Report a Problem...'
dialogue came up and told me that the problem had already reported and
asked if I could add more detail to the bug when it came up in the web
browser, but the web browser didn't load.

Computer info:
VirtualBox Graphical User Interface Version 5.0.24_Ubuntu r108355
(I don't have access to spare hardware to test on at the moment)
Allocated 2GB RAM
Host OS: Ubuntu 16.04 LTS 64-bit
Lenovo ThinkPad X201

Live session from the Ubuntu 16.10 20161008 ISO

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apport 2.20.3-0ubuntu7
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
ApportLog:
 ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: called for pid 7616, signal 
11, core limit 0
 ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: executable: 
/usr/bin/webapp-container (command line "webapp-container 
--app-id=ubuntu-amazon-default --webapp --enable-back-forward 
http://www.amazon.com/?tag=u1webapp-20;)
 ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 7682) Mon Oct 10 15:55:12 2016: wrote report 
/var/crash/_usr_bin_webapp-container.999.crash
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CasperVersion: 1.379
CrashReports:
 644:999:123:0:2016-10-10 15:55:49.656395711 +0100:2016-10-10 
15:55:49.656395711 +0100:/var/crash/_usr_bin_webapp-container.999.upload
 600:115:123:0:2016-10-10 15:55:53.524429871 +0100:2016-10-10 
15:55:53.524429871 +0100:/var/crash/_usr_bin_webapp-container.999.uploaded
 640:999:123:15139136:2016-10-10 15:55:48.040390253 +0100:2016-10-10 
15:55:49.040390253 +0100:/var/crash/_usr_bin_webapp-container.999.crash
CurrentDesktop: Unity
Date: Mon Oct 10 15:57:49 2016
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Web browser didn't appear when 'Report a problem...' asked if I could
  add more info to a bug report that would come up in a web browser
  window

Status in apport package in Ubuntu:
  New

Bug description:
  I tried loading Checkbox in the live session, the 'Report a
  Problem...' dialogue came up and told me that the problem had already
  reported and asked if I could add more detail to the bug when it came
  up in the web browser, but the web browser didn't load.

  Computer info:
  VirtualBox Graphical User Interface Version 5.0.24_Ubuntu r108355
  (I don't have access to spare hardware to test on at the moment)
  Allocated 2GB RAM
  Host OS: Ubuntu 16.04 LTS 64-bit
  Lenovo ThinkPad X201

  Live session from the Ubuntu 16.10 20161008 ISO

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apport 2.20.3-0ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportLog:
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: called for pid 7616, 
signal 11, core limit 0
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: executable: 
/usr/bin/webapp-container (command line "webapp-container 
--app-id=ubuntu-amazon-default --webapp --enable-back-forward 
http://www.amazon.com/?tag=u1webapp-20;)
   ERROR: apport (pid 7682) Mon Oct 10 15:54:45 2016: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 7682) Mon Oct 10 15:55:12 2016: wrote report 
/var/crash/_usr_bin_webapp-container.999.crash
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CrashReports:
   644:999:123:0:2016-10-10 15:55:49.656395711 +0100:2016-10-10 
15:55:49.656395711 +0100:/var/crash/_usr_bin_webapp-container.999.upload
   600:115:123:0:2016-10-10 15:55:53.524429871 +0100:2016-10-10 
15:55:53.524429871 +0100:/var/crash/_usr_bin_webapp-container.999.uploaded
   640:999:123:15139136:2016-10-10 15:55:48.040390253 +0100:2016-10-10 
15:55:49.040390253 +0100:/var/crash/_usr_bin_webapp-container.999.crash
  CurrentDesktop: Unity
  Date: Mon Oct 10 15:57:49 2016
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1631983] [NEW] package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: no package named 'libopencv-gpu2.4v5' is installed, cannot configure

2016-10-10 Thread carlos
Public bug reported:

actualicé la versión de ubuntu y han salido muchos errores

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libopencv-gpu2.4v5 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sat Oct  8 18:40:24 2016
DuplicateSignature:
 package:libopencv-gpu2.4v5:(not installed)
 Setting up python-opencv (2.4.9.1+dfsg-1.5ubuntu1) ...
 dpkg: error processing package libopencv-gpu2.4v5 (--configure):
  no package named 'libopencv-gpu2.4v5' is installed, cannot configure
ErrorMessage: no package named 'libopencv-gpu2.4v5' is installed, cannot 
configure
InstallationDate: Installed on 2016-05-05 (157 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: opencv
Title: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: no 
package named 'libopencv-gpu2.4v5' is installed, cannot configure
UpgradeStatus: Upgraded to xenial on 2016-10-09 (1 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libopencv-gpu2.4v5 (not installed) failed to install/upgrade:
  no package named 'libopencv-gpu2.4v5' is installed, cannot configure

Status in opencv package in Ubuntu:
  New

Bug description:
  actualicé la versión de ubuntu y han salido muchos errores

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libopencv-gpu2.4v5 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Oct  8 18:40:24 2016
  DuplicateSignature:
   package:libopencv-gpu2.4v5:(not installed)
   Setting up python-opencv (2.4.9.1+dfsg-1.5ubuntu1) ...
   dpkg: error processing package libopencv-gpu2.4v5 (--configure):
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  ErrorMessage: no package named 'libopencv-gpu2.4v5' is installed, cannot 
configure
  InstallationDate: Installed on 2016-05-05 (157 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: opencv
  Title: package libopencv-gpu2.4v5 (not installed) failed to install/upgrade: 
no package named 'libopencv-gpu2.4v5' is installed, cannot configure
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (1 days ago)

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

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


[Touch-packages] [Bug 1631980] Re: Steam not able to see network in yakkety

2016-10-10 Thread Joe Barnett
possibly caused by switch to systemd-resolved?

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

Title:
  Steam not able to see network in yakkety

Status in steam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Steam is unable to see the network in yakkety.  Downloads stall and
  don't do anything; and trying to update steam results in a "Fatal
  Error: Steam needs to be online to update.  Please confirm your
  network connection and try again" dialog box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: steam:i386 1:1.0.0.52-5ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 07:43:55 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: steam
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

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

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


[Touch-packages] [Bug 1631981] [NEW] Unity 8 System Settings should not be accessible from Unity 7

2016-10-10 Thread Ads20000
Public bug reported:

I have literally no idea what package would be responsible for this
issue (well, perhaps unity, or ubuntu-meta, but I'm not sure), so please
change that!

---

It should not be possible to access Unity 8's System Settings from Unity
7, not from the Dash and not by default. It's confusing for users who
don't understand what it is, because changing the Unity 7 background
with the application doesn't work - presumably it's not meant to.
Changing the primary button of the mouse/touchpad doesn't work either.

Perhaps the Unity 8 System Settings program should work on Unity 7, in
which case I should report the background's issue as a bug? Do tell me
if these are bugs in the application not in Ubuntu's meta decision.
Thanks!

Computer info:
VirtualBox Graphical User Interface Version 5.0.24_Ubuntu r108355
(I don't have access to spare hardware to test on at the moment)
Allocated 2GB RAM
Host OS: Ubuntu 16.04 LTS 64-bit
Lenovo ThinkPad X201

Live session from the Ubuntu 16.10 20161008 ISO

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

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

Title:
  Unity 8 System Settings should not be accessible from Unity 7

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I have literally no idea what package would be responsible for this
  issue (well, perhaps unity, or ubuntu-meta, but I'm not sure), so
  please change that!

  ---

  It should not be possible to access Unity 8's System Settings from
  Unity 7, not from the Dash and not by default. It's confusing for
  users who don't understand what it is, because changing the Unity 7
  background with the application doesn't work - presumably it's not
  meant to. Changing the primary button of the mouse/touchpad doesn't
  work either.

  Perhaps the Unity 8 System Settings program should work on Unity 7, in
  which case I should report the background's issue as a bug? Do tell me
  if these are bugs in the application not in Ubuntu's meta decision.
  Thanks!

  Computer info:
  VirtualBox Graphical User Interface Version 5.0.24_Ubuntu r108355
  (I don't have access to spare hardware to test on at the moment)
  Allocated 2GB RAM
  Host OS: Ubuntu 16.04 LTS 64-bit
  Lenovo ThinkPad X201

  Live session from the Ubuntu 16.10 20161008 ISO

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

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


[Touch-packages] [Bug 1631980] [NEW] Steam not able to see network in yakkety

2016-10-10 Thread Joe Barnett
Public bug reported:

Steam is unable to see the network in yakkety.  Downloads stall and
don't do anything; and trying to update steam results in a "Fatal Error:
Steam needs to be online to update.  Please confirm your network
connection and try again" dialog box.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: steam:i386 1:1.0.0.52-5ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 10 07:43:55 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-21 (416 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
PackageArchitecture: i386
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: steam
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

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

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


** Tags: apport-bug i386 yakkety

** Also 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/1631980

Title:
  Steam not able to see network in yakkety

Status in steam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Steam is unable to see the network in yakkety.  Downloads stall and
  don't do anything; and trying to update steam results in a "Fatal
  Error: Steam needs to be online to update.  Please confirm your
  network connection and try again" dialog box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: steam:i386 1:1.0.0.52-5ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 07:43:55 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: steam
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

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

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


[Touch-packages] [Bug 1547953] Re: timeanddate calendar shows events from google calendar that are not mine

2016-10-10 Thread Renato Araujo Oliveira Filho
Please fell free to re-open the bug if this is does not solve your
problem.

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

Title:
  timeanddate calendar shows events from google calendar that are not
  mine

Status in account-plugins package in Ubuntu:
  Invalid

Bug description:
  I have multiple calendars shared (of other users) that I have by
  default turned off in Google Calendar and check them only from time to
  time, when needed.

  However, connecting Google account to Ubuntu automatically downloads
  also events that are not from my calendar and belong to other (shared)
  calendars.

  This should not happen by default or rather user should be able to
  disabled listing calendar events from the calendars  he is not
  interested in!

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

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


[Touch-packages] [Bug 1442670] Re: Ubuntu Phone BQ: Camera makes blur images

2016-10-10 Thread Eran Uzan
I have the  same issue on PRO 5, sometimes it seems that  for  some
pictures  the camera just don't want to fcous

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

Title:
  Ubuntu Phone BQ: Camera makes blur images

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

Bug description:
  Hi!
  A lot of times the camera is getting a really bad images (blur effect) in all 
resolutions.

  And yes, I click previously for a focus.

  I'm sending you an example: That picture looked perfect in the mobile,
  but in the PC is really bad :(

  Thanks in advance!

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

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


[Touch-packages] [Bug 1547953] Re: timeanddate calendar shows events from google calendar that are not mine

2016-10-10 Thread Renato Araujo Oliveira Filho
You can disable (hide the calendar from app and indicator) calendars on
calendar-app settings pages. Just uncheck the calendar that you are not
interested.

** Changed in: account-plugins (Ubuntu)
   Status: New => Invalid

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

Title:
  timeanddate calendar shows events from google calendar that are not
  mine

Status in account-plugins package in Ubuntu:
  Invalid

Bug description:
  I have multiple calendars shared (of other users) that I have by
  default turned off in Google Calendar and check them only from time to
  time, when needed.

  However, connecting Google account to Ubuntu automatically downloads
  also events that are not from my calendar and belong to other (shared)
  calendars.

  This should not happen by default or rather user should be able to
  disabled listing calendar events from the calendars  he is not
  interested in!

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

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


[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

2016-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Confirmed

Bug description:
  [Impact]

   * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
  ip=dhcp or ip=:eth0:dhcp

   * Regression-updates

   * The fix better parses the ip= command line argument.

  [Test Case]

   * Create a machine that boots using an nfsroot.

   * Use ip=:eth0:dhcp on the kernel command line.  To set up
 networking.

   * Discover that the device never comes up because, networking is not
  conifgured correctly.

  [Regression Potential]

   * Regressions potential is limited to machines using
  ip={""|*|on|any|dhcp} on the kernel command line.  As this is
  already broken regression potential is minimal.

  [Other Info]
   
   * There are a number of other issues in this code base that are not solved 
by this fix.
   * The networking configuration does not strictly follow the kernel 
documentation as described 
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This 
should be fixed.

  Original Bug Description Follows==

  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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

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


[Touch-packages] [Bug 1631955] Re: Update e-d-s to 3.22.1

2016-10-10 Thread Martin Pitt
Hello Jeremy, or anyone else affected,

Accepted evolution-data-server into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/evolution-data-server/3.22.1-0ubuntu1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: evolution-data-server (Ubuntu Yakkety)
   Importance: Medium
   Status: In Progress

** Changed in: evolution-data-server (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Update e-d-s to 3.22.1

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  ==
  There's a new release of evolution-data-server (e-d-s) from the stable 3.22 
branch. This release
  - Update translations
  - Fixes some console warnings caused by search folders when quitting an app
  - Attempts to fix Google Authentication token expired issue. The bug was 
re-opened upstream because the fixes worked for one person but apparently 
weren't enough for another.
  I experienced the Google expired token bug myself but I haven't verified yet 
whether the update fixes the issue. See attached GNOME bug.

  Since e-d-s is an important library/service used by several apps and
  shipped on all Ubuntu desktop flavors (I think), I suggest we not try
  to rush this into yakkety at the last moment before release, but
  handle it like a regular SRU.

  The e-d-s update is required to update evolution from 3.22 to 3.22.1.

  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22
  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22

  Test Case
  =
  Check several of evolution-data-server's reverse-dependencies to ensure 
they're still working.

  $ reverse-depends src:evolution-data-server

  Regression Potential
  
  Basically only search folders and Google authentication were touched in this 
update, so check those for problems. The Evolution stack is big and complex but 
this is a fairly minor stable release update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evolution-data-server 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 09:23:02 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1631955/+subscriptions

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


[Touch-packages] [Bug 1631968] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

2016-10-10 Thread Claudia C
Public bug reported:

I was trying to update to latest Ubuntu and the upgrade failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Oct 10 06:01:50 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2014-10-26 (714 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-10-10 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I was trying to update to latest Ubuntu and the upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 10 06:01:50 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-10-26 (714 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-10-10 (0 days ago)

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

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


[Touch-packages] [Bug 1631968] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

2016-10-10 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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1631968

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I was trying to update to latest Ubuntu and the upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 10 06:01:50 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-10-26 (714 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-10-10 (0 days ago)

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

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


[Touch-packages] [Bug 1378814] Re: greeter does not properly update infographic after unlock

2016-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  greeter does not properly update infographic after unlock

Status in Band-aids for Ubuntu Phone:
  In Progress
Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This bug has been here since forever, but really needs to get cleaned
  up for rtm.

  Steps to reproduce:
  - send 2 text messages
  - lock your phone
  - unlock your phone
  - confirm infographic says "2 text messages sent today"
  - lock your phone for the night and go to sleep
  - unlock your phone the next day

  Expected results:
  - infographic should be cleared, or show relevant information for today

  Actual results:
  - infographic still says "2 text messages sent today"

  When the phone is unlocked the greeter should update the infographic
  text

To manage notifications about this bug go to:
https://bugs.launchpad.net/band-aids-uphone/+bug/1378814/+subscriptions

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


[Touch-packages] [Bug 1608116] Re: (Pro 5) slow start up camera app

2016-10-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  (Pro 5) slow start up camera app

Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  After OTA12 the startup time for camera app has gone from 3 s to 25 s.
  Also the scopes randomly freezes for 5-10 s

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

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


[Touch-packages] [Bug 1630337] Re: Need DBus API to get current co-ordinates of the Pointer

2016-10-10 Thread Omer Akram
There are a few points that I would like to point here that I and
mzanetti discussed.

Mike wanted for us to talk to the unity8 proxy object to get details of
the pointer co-ordinates to screen orientation but there are a few
reasons that I believe we should not be going by that path.

1. The tool i.e. Autopilot should only rely on APIs and not on internal details 
of the unity8 server.
2. We don't want to restart unity8 to enable testability for autopilot to work. 
Restarting unity8 would only make sense if we were testing unity8 itself.

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

Title:
  Need DBus API to get current co-ordinates of the Pointer

Status in unity8 package in Ubuntu:
  New

Bug description:
  The autopilot tool(using evdev) moves the mouse cursor on screen
  relative to its current position. This works fine in X11 as there are
  ways to easily get the co-ordinates of the cursor, but under Mir that
  does not work as we have no way to get the pointer' co-ordinates.

  We need this API to port autopilot to work under Mir based desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  Uname: Linux 4.7.0-040700-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Oct  4 22:42:50 2016
  InstallationDate: Installed on 2016-09-21 (12 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1547953] Re: timeanddate calendar shows events from google calendar that are not mine

2016-10-10 Thread Bill Filler
** Changed in: account-plugins (Ubuntu)
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Changed in: account-plugins (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  timeanddate calendar shows events from google calendar that are not
  mine

Status in account-plugins package in Ubuntu:
  New

Bug description:
  I have multiple calendars shared (of other users) that I have by
  default turned off in Google Calendar and check them only from time to
  time, when needed.

  However, connecting Google account to Ubuntu automatically downloads
  also events that are not from my calendar and belong to other (shared)
  calendars.

  This should not happen by default or rather user should be able to
  disabled listing calendar events from the calendars  he is not
  interested in!

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

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


[Touch-packages] [Bug 1631955] [NEW] Update e-d-s to 3.22.1

2016-10-10 Thread Jeremy Bicha
Public bug reported:

Impact
==
There's a new release of evolution-data-server (e-d-s) from the stable 3.22 
branch. This release
- Update translations
- Fixes some console warnings caused by search folders when quitting an app
- Attempts to fix Google Authentication token expired issue. The bug was 
re-opened upstream because the fixes worked for one person but apparently 
weren't enough for another.
I experienced the Google expired token bug myself but I haven't verified yet 
whether the update fixes the issue. See attached GNOME bug.

Since e-d-s is an important library/service used by several apps and
shipped on all Ubuntu desktop flavors (I think), I suggest we not try to
rush this into yakkety at the last moment before release, but handle it
like a regular SRU.

The e-d-s update is required to update evolution from 3.22 to 3.22.1.

https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22
https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22

Test Case
=
Check several of evolution-data-server's reverse-dependencies to ensure they're 
still working.

$ reverse-depends src:evolution-data-server

Regression Potential

Basically only search folders and Google authentication were touched in this 
update, so check those for problems. The Evolution stack is big and complex but 
this is a fairly minor stable release update.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: evolution-data-server 3.22.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 10 09:23:02 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-11 (59 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
SourcePackage: evolution-data-server
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution-data-server (Ubuntu)
 Importance: Medium
 Status: In Progress


** Tags: amd64 apport-bug block-proposed upgrade-software-version yakkety

** Description changed:

  Impact
  ==
- There's a new release of evolution-data-server from the stable 3.22 branch. 
This release
+ There's a new release of evolution-data-server (e-d-s) from the stable 3.22 
branch. This release
  - Update translations
  - Fixes some console warnings caused by search folders when quitting an app
  - Attempts to fix Google Authentication token expired issue. The bug was 
re-opened upstream because the fixes worked for one person but apparently 
weren't enough for another.
  I experienced the Google expired token bug myself but I haven't verified yet 
whether the update fixes the issue. See attached GNOME bug.
  
  Since e-d-s is an important library/service used by several apps and
  shipped on all Ubuntu desktop flavors (I think), I suggest we not try to
  rush this into yakkety at the last moment before release, but handle it
  like a regular SRU.
+ 
+ The e-d-s update is required to update evolution from 3.22 to 3.22.1.
+ 
+ https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22
+ https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
  
  Test Case
  =
  Check several of evolution-data-server's reverse-dependencies to ensure 
they're still working.
  
  $ reverse-depends src:evolution-data-server
  
  Regression Potential
  
  Basically only search folders and Google authentication were touched in this 
update, so check those for problems. The Evolution stack is big and complex but 
this is a fairly minor stable release update.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evolution-data-server 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 09:23:02 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags added: block-proposed

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1631955/+attachment/4758667/+files/JournalErrors.txt

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

Title:
  Update e-d-s to 3.22.1

Status in evolution-data-server package in Ubuntu:
  In Progress

Bug description:
  Impact
  ==
  There's a new release of evolution-data-server (e-d-s) from the stable 3.22 
branch. This release
  - Update translations
  - Fixes some console warnings caused by search folders when quitting an app
  - 

[Touch-packages] [Bug 1631675] Re: unity8 crashed with SIGSEGV in XGetXCBConnection() from dri2_initialize_wayland_swrast()

2016-10-10 Thread Giovanni
I have reinstalled Ubuntu 16.10 and now seems to work fine.

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

Title:
  unity8 crashed with SIGSEGV in XGetXCBConnection() from
  dri2_initialize_wayland_swrast()

Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  unity8 crashed with SIGSEGV in XGetXCBConnection()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Sun Oct  9 02:08:31 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-03-10 (212 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160310)
  ProcCmdline: unity8 --mode=full-shell
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV in XGetXCBConnection()
  UpgradeStatus: Upgraded to yakkety on 2016-10-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1630906] Re: QML segfault on arm64 due to builder kernel change

2016-10-10 Thread Timo Jyrinki
I've now also asked on #ubuntu-kernel if CONFIG_ARM64_VA_BITS=48 is here
to stay for the 4.4 kernel or not, pointing to this bug. It sounds like
no-one is currently considering going back to the 4.2 kernel on the
arm64 builders at least.

Meanwhile I'm collecting rebuilds of qtdeclarative-abi-5-6-1 users to
the 2055 silo, although it won't help yakkety as such as it's being
released and the qtdeclarative update may not be SRU material.

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

Title:
  QML segfault on arm64 due to builder kernel change

Status in linux package in Ubuntu:
  Confirmed
Status in online-accounts-api package in Ubuntu:
  New
Status in qmenumodel package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Builders were changed from wily to xenial (4.4) kernel for arm64, and
  likely due to this the following kind of errors started happening:

  https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64
  .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz

  They happen when executing QML code.

  I've ruled out that reverting to previous qtbase and qtdeclarative
  versions don't affect this, so it's not coming from a Qt change. I've
  also verified there's no problem eg on our Bq tablet running the same
  tests on xenial+overlay. There are currently no found changes at least
  in Qt upstream to backport arm64 related fixes.

  Cause is unknown. But the same problem is there on vivid, xenial and yakkety 
builds:
  
https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz

  This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6,
  or glibc 2.21, 2.23 or 2.24.

  More logs from affected packages:
  
https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz

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

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


[Touch-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

2016-10-10 Thread GTriderXC
I see mentioned here only Nexus 4. I never experienced such a behaviour
on bq E4.5. The only thing that happened was a second alarm clock that
didn't ring. However it happened only once and I can not reproduce it.

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

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

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


  1   2   >