[Touch-packages] [Bug 1511525] Re: Can't transfer file using bluetooth OBEX

[Yuan-Chen Cheng]

** Summary changed:

- Can't transfer file using bluetooth
+ Can't transfer file using bluetooth OBEX

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

Title:
  Can't transfer file using bluetooth OBEX

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Hi all
  On my BQ E4.5 I can't send or recive files using bluetooth. It looks strange 
for me that nobody reported this before so I decided to open this question.
  Thanks all

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

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Martin Pitt]

Moving to ifupdown. systemd does not configure the network (unless you
set them up in networkd, but we don't do that anywhere automatically and
there's no evidence that you did, and it's networking.service that
hangs).

I also don't see much wrong about this, except maybe that
interfaces.d/50-cloud-init.cfg and interfaces.d/eth0 both configure
eth0. But the latter (created by cloud-init I suppose) is a dead file as
/e/n/interfaces only includes *.cfg files, so that shouldn't matter.

** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu)

** Summary changed:

- systemctl wants to configure interfaces it shouldn't (lxdbr0)
+ ifupdown wants to configure interfaces it shouldn't (lxdbr0)

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

Title:
  ifupdown wants to configure interfaces it shouldn't (lxdbr0)

Status in ifupdown package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1566172] Re: [SUGGESTION] Use the space bar for moving the text cursor

[Kugi Eusebio]

I created a little hack and uploaded it in launchpad [1].
It can be used to see how this can be implemented and how useful it can be in 
different use cases.
For now, I'm enjoying this feature on my phone/tablet  :)


[1] https://launchpad.net/spacekey-cursor

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

Title:
  [SUGGESTION] Use the space bar for moving the text cursor

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

Bug description:
  I have an idea which maybe considered to be implemented.
  What if we use the space bar for moving the text cursor horizontally or even 
vertically.
  Currently, moving the cursor is quite hard and inaccurate.
  Space bar is quite big and makes it a good place to swipe to move the cursor.
  With this approach, we're not using more space and instead use a big part of 
the keyboard that is only there mostly for inserting spaces. The sensitivity is 
critical though because you don't want unintended movement of the cursor but I 
think it's very much doable.

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

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

[Touch-packages] [Bug 1568817] Re: uitk gles package upgrade not working

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-ui-toolkit-gles -
1.3.1918+16.04.20160404-0ubuntu3

---
ubuntu-ui-toolkit-gles (1.3.1918+16.04.20160404-0ubuntu3) xenial; urgency=medium

  * debian/qml-module-components-gles.install: don't provide overlapping files.
(LP: #1568817)

 -- Timo Jyrinki   Mon, 11 Apr 2016 13:52:46
+

** Changed in: ubuntu-ui-toolkit-gles (Ubuntu)
   Status: New => Fix Released

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

Title:
  uitk gles package upgrade not working

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit-gles package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  In Progress

Bug description:
  Trying to upgrade to xenial-proposed UITK - the gles version - is
  currently not working. Both normal and gles saw a complex split into
  several qml module packages and a rename.

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

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Serge Hallyn]

Tried adding lxdbr0 to the EXCLUDE_INTERFACES.  Works on a kvm vm;  but
the openstack instance ends up with *only* lxdbr0 configured.  Voodoo.

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1569151] Re: sudo crashed with SIGABRT in kill()

[Apport retracing service]

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

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 #1565332, 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/1569151/+attachment/4633566/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  sudo crashed with SIGABRT in kill()

Status in sudo package in Ubuntu:
  New

Bug description:
  ошибка при запуске системы.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 11 23:17:53 2016
  ExecutablePath: /usr/bin/sudo
  ExecutableTimestamp: 1459367833
  InstallationDate: Installed on 2014-12-18 (480 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/sudo -H -S -p GNOME_SUDO_PASS -u root -- bleachbit
  ProcCwd: /home/karen
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: sudo
  StacktraceTop:
   kill () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   __libc_start_main (main=0x561298df3a20, argc=9, argv=0x7ffe05892918, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe05892908) at ../csu/libc-start.c:291
   ?? ()
  Title: sudo crashed with SIGABRT in kill()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1568817] Re: uitk gles package upgrade not working

[Timo Jyrinki]

** Also affects: ubuntu-ui-toolkit-gles (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

- Trying to upgrade to xenial-proposed UITK is currently not working.
+ Trying to upgrade to xenial-proposed UITK - the gles version - is
+ currently not working. Both normal and gles saw a complex split into
+ several qml module packages and a rename.

** Changed in: ubuntu-ui-toolkit-gles (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: ubuntu-ui-toolkit (Ubuntu RTM)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: ubuntu-ui-toolkit (Ubuntu RTM)
   Status: New => In Progress

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

** Changed in: ubuntu-ui-toolkit-gles (Ubuntu)
   Importance: Critical => High

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

Title:
  uitk gles package upgrade not working

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit-gles package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  In Progress

Bug description:
  Trying to upgrade to xenial-proposed UITK - the gles version - is
  currently not working. Both normal and gles saw a complex split into
  several qml module packages and a rename.

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

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

[Touch-packages] [Bug 1543774] Re: [AV200 - Xonar DS, playback] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [AV200 - Xonar DS, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Hello!

  I installed Ubuntu 15.10 several times but the soundproblem it didnt
  solve.

  I disconneted the soundcard by hand an reinstalled ubuntu for using on-board
  sound. But there it didnt notice on-board sound device.

  I tried the steps in the ubuntuuseres sound problem-site without
  success.

  Can You help me please?

  I like using ubuntu very much but having a sound would give me a good
  fact for taking ubuntu to my main system.

  Thank you very much!

  Greetings Hannes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hannes 1324 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb  9 21:15:09 2016
  InstallationDate: Installed on 2016-02-08 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DS failed
  Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 66 (Xonar DS)) - Xonar DS
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hannes 1324 F pulseaudio
  Symptom_Type: No sound at all
  Title: [AV200 - Xonar DS, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: None
  dmi.board.name: Hi-Fi A85S3
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/22/2012:svnBIOSTARGroup:pnHi-FiA85S3:pvr:rvnBIOSTARGroup:rnHi-FiA85S3:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: Hi-Fi A85S3
  dmi.sys.vendor: BIOSTAR Group

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

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

[Touch-packages] [Bug 1004607] Re: pulseaudio switches microhpones randomly

[Launchpad Bug Tracker]

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

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  pulseaudio switches microhpones randomly

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Problem
  ===

  During Skype calls, pulseaudio switches input to front microphone
  randomly. I need to manually switch back to rear mic every time that
  happens.

  Expected
  ===

 I select the rear microphone as input (pavucontrol) and it stays
  that way.

  
  Workaround
  ==

  I disabled this module in /etc/pulse/default.pa:

  # load-module module-switch-on-port-available

  and then restarting pulseaudio obviously solves this.

  
  Ideal workaround
  ==

  Disable port switching for (selected?) input devices in pavucontrol.

  Or at least somehow honor my selection, e.g. if the input is marked as
  a fallback device, it shouldn't switch.

  
  Possible cause 1
  =

  After pulseaudio startup, pactl shows these lines:

  analog-input-microphone-front: Front Microphone (priority 8500, 
available: yes)
  analog-input-microphone-rear: Rear Microphone (priority 8200, available: 
no)

  Note: I don't use the front mic port at all.

  Possible cause 2
  =
  My sound card or ports may be creating noise that triggers "jack activation" 
events

  
  Possible cause 3
  =

  Bios, hardware related issues trigger jack activation events.

  
  Example of pulseaudio switching mics during Skype call:
  

  pulseaudio[32253]: [alsa-source] alsa-source.c: Calculated software volume: 
0: 100% 1: 100% (accurate-enough=yes)
  pulseaudio[32253]: [alsa-source] alsa-source.c:  in dB: 
0: 0.00 dB 1: 0.00 dB
  pulseaudio[32253]: [alsa-source] source.c: Volume not changing
  pulseaudio[32253]: [pulseaudio] module-suspend-on-idle.c: Source 
alsa_input.pci-_00_07.0.analog-stereo becomes busy.
  pulseaudio[32253]: [alsa-sink] ratelimit.c: 723 events suppressed
  pulseaudio[32253]: [alsa-sink] flist.c: pulsecore/memblockq.c: list_items 
flist is full (don't worry)
  pulseaudio[32253]: last message repeated 10 times
  pulseaudio[32253]: [pulseaudio] module-alsa-card.c: Jack 'Front Mic Jack' is 
now unplugged
  pulseaudio[32253]: [pulseaudio] device-port.c: Setting port 
analog-input-microphone-front to status no
  pulseaudio[32253]: [pulseaudio] module-switch-on-port-available.c: finding 
port analog-input-microphone-front
  pulseaudio[32253]: [pulseaudio] module-alsa-card.c: Jack 'Front Mic Jack' is 
now plugged in
  pulseaudio[32253]: [pulseaudio] device-port.c: Setting port 
analog-input-microphone-front to status yes
  pulseaudio[32253]: [pulseaudio] module-switch-on-port-available.c: finding 
port analog-input-microphone-front
  pulseaudio[32253]: [alsa-source] alsa-mixer.c: Activating path 
analog-input-microphone-front
  pulseaudio[32253]: [alsa-source] alsa-mixer.c: Path 
analog-input-microphone-front (Front Microphone), direction=2, priority=85, 
probed=yes, supported=yes, has_mute=yes, has_volume=yes, has_dB=yes, 
min_volume=0, max_volume=3, min_dB=-16.5, max_dB=60
  pulseaudio[32253]: [alsa-source] alsa-mixer.c: Element Front Mic Boost, 
direction=2, switch=0, volume=1, volume_limit=-1, enumeration=0, required=0, 
required_any=4, required_absent=0, mask=0x36f66, n_channels=2, 
override_map=yes
  pulseaudio[32253]: [alsa-source] alsa-mixer.c: Element Capture, direction=2, 
switch=1, volume=1, volume_limit=-1, enumeration=0, required=0, required_any=0, 
required_absent=0, mask=0x36f66, n_channels=2, override_map=yes
  pulseaudio[32253]: [alsa-source] alsa-mixer.c: Element Input Source, 
direction=2, switch=0, vol

  
  Note the line:  module-alsa-card.c: Jack 'Front Mic Jack' is now unplugged
  and instantly afterwards: module-switch-on-port-available.c: finding port 
analog-input-microphone-front

  Sound card
  =
  
  cat /proc/asound/card0/codec\#0|grep Codec
  Codec: Realtek ALC888

  
  Versions
  ===
  Ubuntu   12.04 LTS
  pulseaudio 1:1.1-0ubuntu1
  kernel 3.2.0-24-generic
  alsa-base1.0.25+dfsg-0u

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

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

[Touch-packages] [Bug 1569071] Re: /usr/bin/bat in alsa-utils conflicts with /usr/bin/bat in bacula-qt-console

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-utils - 1.1.0-0ubuntu4

---
alsa-utils (1.1.0-0ubuntu4) xenial; urgency=medium

  * Add patch from Upstream/Debian to rename the bat command to fix
package conflicts (LP: #1569071)

 -- Luke Yelavich   Tue, 12 Apr 2016 09:33:00 +1000

** Changed in: alsa-utils (Ubuntu)
   Status: New => Fix Released

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

Title:
  /usr/bin/bat in alsa-utils conflicts with /usr/bin/bat in bacula-qt-
  console

Status in alsa-utils package in Ubuntu:
  Fix Released

Bug description:
  Unpacking alsa-utils (1.1.0-0ubuntu3) over (1.1.0-0ubuntu2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/alsa-utils_1.1.0-0ubuntu3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/bat', which is also in package 
bacula-console-qt 7.0.5+dfsg-4build1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  I am assuming that /usr/bin/alsabat has been renamed /usr/bin/bat -
  this is in conflict with existing package bacula-qt-console.

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

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

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

[Mathieu Trudel-Lapierre]

I pinged pitti on IRC earlier today, and just subscribed him for
guidance on whether this can be fixed in systemd; which seems to be the
least intrusive way to handle this (aside from expecting users to know
about this limitation and renaming interfaces themselves).

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

** Changed in: iproute2 (Ubuntu)
   Status: Triaged => Confirmed

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

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

Title:
  RTNETLINK answers: Numerical result out of range for alias interface
  from a usb NIC

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

[Mathieu Trudel-Lapierre]

This isn't a simple problem at all.

The new naming scheme from systemd makes it so that these specific
devices (USB dongles) get their MAC address encoded in the device name,
which brings it up to a length of 15 characters + \0; so 16 bytes. This
happens to also be the size limit for interface names (set as IFNAMSIZ
to 16). Adding more characters to the end of this string makes it too
long to be allowed by {libnl3, kernel, iproute2}. This is because while
we're not strictly dealing with interface names here, we're dealing with
a label which is bound by the same sized buffer (limited to IFNAMSIZ
size).

There are a few possible avenues for a solution:
 - Rename the address yourself to something smaller. This should be possible 
using udev rules.
 - Fix systemd to pick a different naming method.
 - Fix ip addr to better deal with address labels, which may mean dropping some 
backward compatibility (more below)
 - Increasing the buffer size for address labels (which means changes in the 
kernel, libnl, iproute2 at the very least, and probably many more userland 
utilities).

For iproute2:
   label LABEL
  Each address may be tagged with a label string.  In order to 
preserve compatibility with Linux-2.0 net aliases, this string must coincide 
with the name of the device
  or must be prefixed with the device name followed by colon.
It may be possible to strip out anything before the colon if a label is passed 
in that format to hand to the netlink layer a shorter label, but I haven't 
looked more closely at what such a change might impact.

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

Title:
  RTNETLINK answers: Numerical result out of range for alias interface
  from a usb NIC

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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

[Touch-packages] [Bug 1539011] Re: [regression] Window resizing is very choppy and stutters (border does not smoothly follow the mouse)

[Daniel van Vugt]

** Description changed:

  Just tried Unity8 desktop for the first time since October and found
  some things don't work as well as before. One of them is window
  resizing, which is now every choppy and stuttering.
+ 
+ Please also see bug 1540702 so as to not confuse the two.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160122-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 28 18:39:38 2016
  InstallationDate: Installed on 2015-12-03 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8-dash.log: Attempted to deliver an event to a non-existent 
window, ignoring.

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

Title:
  [regression] Window resizing is very choppy and stutters (border does
  not smoothly follow the mouse)

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

Bug description:
  Just tried Unity8 desktop for the first time since October and found
  some things don't work as well as before. One of them is window
  resizing, which is now every choppy and stuttering.

  Please also see bug 1540702 so as to not confuse the two.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160122-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 28 18:39:38 2016
  InstallationDate: Installed on 2015-12-03 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8-dash.log: Attempted to deliver an event to a non-existent 
window, ignoring.

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

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Stéphane Graber]

Not seeing anything wrong with the files above, no subnet conflict or
other network error.

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1568985] Re: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()

[Daniel van Vugt]

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

I suspect this bug is not strictly a duplicate of bug 1553549 as you
don't seem to be using nvidia.

However the stack trace and system information available is too brief to
be able to do anything else with this bug report, sorry.

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

Title:
  unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()

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

Bug description:
  Installed 16.04. Tried Unity 8 LXR, also the MIR version,  and both
  hang on the login screen if that window managed is chosen. Only a
  shutdown is possible. Next Unity 7 login gives this error report.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Apr 11 19:54:56 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:146a]
  InstallationDate: Installed on 2016-01-18 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7fd8dc59ac3b:mov(%rsi),%rax
   PC (0x7fd8dc59ac3b) ok
   source "(%rsi)" (0x7fd8d62c0668) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __gxx_personality_v0 () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   _Unwind_RaiseException () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   _Unwind_Resume_or_Rethrow () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()
  UpgradeStatus: Upgraded to xenial on 2016-04-08 (3 days ago)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1
  version.lightdm: lightdm 1.18.1-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

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

[Cerberus]

It started working, I checked three times in a row and it was
successful, will track this further to see if updating continues working
properly.

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

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Fix Committed
Status in Today Scope:
  Invalid
Status in connectivity-api package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

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

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

  In all cases the log reports:

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

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

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

  One time I saw
  Connect to the Internet ...

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

  In all other cases Checking for updates never finished

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

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

[Touch-packages] [Bug 1568082] Re: Dash 'activity pulse' on bottom should be blue

[Launchpad Bug Tracker]

** Branch linked: lp:~josharenson/unity8/blue-activity-pluse

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

Title:
  Dash 'activity pulse' on bottom should be blue

Status in unity8 package in Ubuntu:
  New

Bug description:
  Per new design palette, blue is for activity. Currently that pulser is
  orange.

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

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

[Touch-packages] [Bug 1569099] [NEW] package systemd-sysv 229-4ubuntu1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[Christian Reis]

Public bug reported:

This was easily fixed via an apt-get -f install, and there was no
mention of libgcrypt20, so I don' t think it' s a dupe of but 1560797.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd-sysv 229-4ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Mon Apr 11 11:20:26 2016
ErrorMessage: pre-dependency problem - not installing systemd-sysv
InstallationDate: Installed on 2012-01-26 (1537 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10
SourcePackage: systemd
Title: package systemd-sysv 229-4ubuntu1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
UpgradeStatus: Upgraded to xenial on 2016-04-11 (0 days ago)

** Affects: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1569099

Title:
  package systemd-sysv 229-4ubuntu1 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  New

Bug description:
  This was easily fixed via an apt-get -f install, and there was no
  mention of libgcrypt20, so I don' t think it' s a dupe of but 1560797.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Mon Apr 11 11:20:26 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2012-01-26 (1537 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-04-11 (0 days ago)

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

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

[Touch-packages] [Bug 1462441] Re: apport hangs, wrong menu entries

[Launchpad Bug Tracker]

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

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

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

Title:
  apport hangs, wrong menu entries

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Well, two problems. First:

  if you start ubuntu-bug without parameter, it shows a dialog
  containing:

  Other Problem
   (a lot of options)
  Display (X.org)

  first and last item are swapped. If you click other (the first), you
  will get a list of display problems. If you click Display (the last
  one), you will get "You need to specify a package or a PID. See --help
  for more information."

  Second problem:
  if you click cancel on the display page, apport hangs forever.
  Maybe duplicate of #660024

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: reportbug (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jun  5 18:13:55 2015
  InstallationDate: Installed on 2013-10-25 (588 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: reportbug
  UpgradeStatus: Upgraded to vivid on 2015-05-19 (17 days ago)

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

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

[Touch-packages] [Bug 1462441] Re: apport hangs, wrong menu entries

[Ian Turner]

(That is, with apport 2.20.1-0ubuntu1)

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

Title:
  apport hangs, wrong menu entries

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Well, two problems. First:

  if you start ubuntu-bug without parameter, it shows a dialog
  containing:

  Other Problem
   (a lot of options)
  Display (X.org)

  first and last item are swapped. If you click other (the first), you
  will get a list of display problems. If you click Display (the last
  one), you will get "You need to specify a package or a PID. See --help
  for more information."

  Second problem:
  if you click cancel on the display page, apport hangs forever.
  Maybe duplicate of #660024

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: reportbug (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jun  5 18:13:55 2015
  InstallationDate: Installed on 2013-10-25 (588 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: reportbug
  UpgradeStatus: Upgraded to vivid on 2015-05-19 (17 days ago)

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

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

[Touch-packages] [Bug 1462441] Re: apport hangs, wrong menu entries

[Ian Turner]

I'm seeing this problem in Xenial.

** Tags added: xenial

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

Title:
  apport hangs, wrong menu entries

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Well, two problems. First:

  if you start ubuntu-bug without parameter, it shows a dialog
  containing:

  Other Problem
   (a lot of options)
  Display (X.org)

  first and last item are swapped. If you click other (the first), you
  will get a list of display problems. If you click Display (the last
  one), you will get "You need to specify a package or a PID. See --help
  for more information."

  Second problem:
  if you click cancel on the display page, apport hangs forever.
  Maybe duplicate of #660024

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: reportbug (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jun  5 18:13:55 2015
  InstallationDate: Installed on 2013-10-25 (588 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: reportbug
  UpgradeStatus: Upgraded to vivid on 2015-05-19 (17 days ago)

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

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

[Touch-packages] [Bug 1569094] [NEW] After upgrade to Xenial, apport-collect fails

[Ian Turner]

Public bug reported:

After upgrading wily -> Xenial, when I run apport-collect with no
arguments, this is what I get:

Mon Apr 11 19:53:52 vectro@mirian:~ $ sudo apport-collect
ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

This is with apport 2.20.1-0ubuntu1. I assume it is a packaging issue.

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


** Tags: kubuntu packaging xenial

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

Title:
  After upgrade to Xenial, apport-collect fails

Status in apport package in Ubuntu:
  New

Bug description:
  After upgrading wily -> Xenial, when I run apport-collect with no
  arguments, this is what I get:

  Mon Apr 11 19:53:52 vectro@mirian:~ $ sudo apport-collect
  ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

  This is with apport 2.20.1-0ubuntu1. I assume it is a packaging issue.

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

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

[Touch-packages] [Bug 1567037] Re: lxc-attach crashed with SIGSEGV in get_pty_on_host()

[Serge Hallyn]

No that should actually be ok, it's ../Zulu not ./Zulu.

Could you show the contents of

/var/lib/lxc/unity-lxc/config
/var/lib/lxc/unity-lxc/fstab

(I'll also be asking for contents of any files listed in lxc.include
lines)

** No longer affects: tzdata (Ubuntu)

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

Title:
  lxc-attach crashed with SIGSEGV in get_pty_on_host()

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Installed unity8-lxc, ran unity8-setup, then rebooted.
  Login to unity8 lxc session failed (somehow nothing happened), then I logged 
into Unity7 and the crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: lxc1 2.0.0~rc15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  6 20:11:34 2016
  ExecutablePath: /usr/bin/lxc-attach
  InstallationDate: Installed on 2015-12-03 (124 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151203)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic.efi.signed 
root=UUID=dccfbc3c-48bc-43ed-9881-36efaa2ef6c5 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x563ee5318994 : movl   $0x1,0x1c(%r14)
   PC (0x563ee5318994) ok
   source "$0x1" ok
   destination "0x1c(%r14)" (0x001c) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: lxc
  Stacktrace:
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  StacktraceTop: main ()
  ThreadStacktrace:
   .
   Thread 1 (Thread 0x7fe20540f840 (LWP 2993)):
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  Title: lxc-attach crashed with SIGSEGV in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  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/1567037/+subscriptions

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Serge Hallyn]

Removing the ipv4 configuration from /etc/default/lxd-bridge doesn't
help.

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1569071] Re: /usr/bin/bat in alsa-utils conflicts with /usr/bin/bat in bacula-qt-console

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-audio-dev/alsa-utils/ubuntu

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

Title:
  /usr/bin/bat in alsa-utils conflicts with /usr/bin/bat in bacula-qt-
  console

Status in alsa-utils package in Ubuntu:
  New

Bug description:
  Unpacking alsa-utils (1.1.0-0ubuntu3) over (1.1.0-0ubuntu2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/alsa-utils_1.1.0-0ubuntu3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/bat', which is also in package 
bacula-console-qt 7.0.5+dfsg-4build1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  I am assuming that /usr/bin/alsabat has been renamed /usr/bin/bat -
  this is in conflict with existing package bacula-qt-console.

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

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Serge Hallyn]

ip addr show:  http://paste.ubuntu.com/15769059/
ip route show: http://paste.ubuntu.com/15769063/
/etc/network/interfaces: http://paste.ubuntu.com/15769066/
/etc/network/interfaces.d/50-cloud-init.cfg: http://paste.ubuntu.com/15769068/
/etc/network/interfaces.d/eth0: http://paste.ubuntu.com/15769071/

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Serge Hallyn]

Note that adding an ipv4 address to the local uvt-kvm guest does *not*
make it fail, sadly :(  Getting the other info...

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

-- 
Mailing list: https://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 1516985] Re: Package update to 3.0

[extraym...@gmail.com]

Any chance this gets into final release?

2016-03-21 1:21 GMT+08:00 Mike Gogulski :

> The final beta freeze for Xenial is coming up on the 24th according to
> https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule
>
> *prays that someone picks this up and champions an exception*
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1516985
>
> Title:
>   Package update to 3.0
>
> Status in opencv package in Ubuntu:
>   Confirmed
> Status in opencv package in Debian:
>   Fix Released
>
> Bug description:
>   It would be nice to update opencv in the repo to 3.0 which is released
>   in 2015-06!
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1516985/+subscriptions
>

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

Title:
  Package update to 3.0

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

Bug description:
  It would be nice to update opencv in the repo to 3.0 which is released
  in 2015-06!

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

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

[Touch-packages] [Bug 1569082] Re: package libxxf86vm1 1:1.1.4-1 [modified: usr/share/doc/libxxf86vm1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxxf8

[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 libxxf86vm in Ubuntu.
https://bugs.launchpad.net/bugs/1569082

Title:
  package libxxf86vm1 1:1.1.4-1 [modified:
  usr/share/doc/libxxf86vm1/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libxxf86vm1/changelog.Debian.gz', which is different
  from other instances of package libxxf86vm1:i386

Status in libxxf86vm package in Ubuntu:
  New

Bug description:
  just tried install i386 version of opengl, that's all I know
  just following the process as presented by ubuntu ui

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libxxf86vm1 1:1.1.4-1 [modified: 
usr/share/doc/libxxf86vm1/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 11 19:03:51 2016
  DuplicateSignature: package:libxxf86vm1:1:1.1.4-1 [modified: 
usr/share/doc/libxxf86vm1/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libxxf86vm1/changelog.Debian.gz', which is different from other 
instances of package libxxf86vm1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libxxf86vm1/changelog.Debian.gz', which is different from other 
instances of package libxxf86vm1:i386
  InstallationDate: Installed on 2016-03-31 (11 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: libxxf86vm
  Title: package libxxf86vm1 1:1.1.4-1 [modified: 
usr/share/doc/libxxf86vm1/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libxxf86vm1/changelog.Debian.gz', 
which is different from other instances of package libxxf86vm1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1569082] [NEW] package libxxf86vm1 1:1.1.4-1 [modified: usr/share/doc/libxxf86vm1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxx

[ajanke]

Public bug reported:

just tried install i386 version of opengl, that's all I know
just following the process as presented by ubuntu ui

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libxxf86vm1 1:1.1.4-1 [modified: 
usr/share/doc/libxxf86vm1/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Mon Apr 11 19:03:51 2016
DuplicateSignature: package:libxxf86vm1:1:1.1.4-1 [modified: 
usr/share/doc/libxxf86vm1/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libxxf86vm1/changelog.Debian.gz', which is different from other 
instances of package libxxf86vm1:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libxxf86vm1/changelog.Debian.gz', which is different from other 
instances of package libxxf86vm1:i386
InstallationDate: Installed on 2016-03-31 (11 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: libxxf86vm
Title: package libxxf86vm1 1:1.1.4-1 [modified: 
usr/share/doc/libxxf86vm1/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libxxf86vm1/changelog.Debian.gz', 
which is different from other instances of package libxxf86vm1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-conflict wily

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

Title:
  package libxxf86vm1 1:1.1.4-1 [modified:
  usr/share/doc/libxxf86vm1/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libxxf86vm1/changelog.Debian.gz', which is different
  from other instances of package libxxf86vm1:i386

Status in libxxf86vm package in Ubuntu:
  New

Bug description:
  just tried install i386 version of opengl, that's all I know
  just following the process as presented by ubuntu ui

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libxxf86vm1 1:1.1.4-1 [modified: 
usr/share/doc/libxxf86vm1/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 11 19:03:51 2016
  DuplicateSignature: package:libxxf86vm1:1:1.1.4-1 [modified: 
usr/share/doc/libxxf86vm1/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libxxf86vm1/changelog.Debian.gz', which is different from other 
instances of package libxxf86vm1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libxxf86vm1/changelog.Debian.gz', which is different from other 
instances of package libxxf86vm1:i386
  InstallationDate: Installed on 2016-03-31 (11 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: libxxf86vm
  Title: package libxxf86vm1 1:1.1.4-1 [modified: 
usr/share/doc/libxxf86vm1/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libxxf86vm1/changelog.Debian.gz', 
which is different from other instances of package libxxf86vm1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Stéphane Graber]

Ok, the fact that this only happens when it does have an IP may point at
some kind of conflict.

Any chance you can (obviously before reboot), also post "ip addr show",
"ip route show" and the content of /etc/network/interfaces and any file
under /etc/network/interfaces.d/ ?

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

-- 
Mailing list: https://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 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Serge Hallyn]

Hm, so lxdbr0 has an ipv4 address in the openstack instance. In the
uvt-kvm instance where networking comes up fine, it does not.

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1561096] Re: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under Ubuntu 16.04 with added adapters (ibmveth)

[bugproxy]

--- Comment From cdead...@us.ibm.com 2016-04-11 18:44 EDT---
*** Bug 136973 has been marked as a duplicate of this bug. ***

** Tags added: bugnameltc-136930 severity-high

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

Title:
  STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under
  Ubuntu 16.04 with added adapters (ibmveth)

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  Problem Description : I had installed a fresh install of Ubuntu 16.04
  from an ISO image and had set up the partition as directed in the
  Wiki. I had set up the networking as directed in the WIKI and was able
  to ping "iofnim" and was able to perform updates and upgrades to the
  Ubuntu installation without issue.

  I had checked to make sure (by adding them to an existing AIX
  partition) that the Mason and Travis_EN adapters to be added were at
  the latest microcode levels.  I assigned them to the partition to be
  used (br16p05) and then shut down the partition and restarted it to
  allow the partition to activate the adapters.

  After the partition restarted, I attempted to build the network using
  build_net and during its run noticed that the output for the adapters
  was returning "Network is unreachable".  After it completed, I
  attempted to mount iofnim using the command:

  "mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock"

  which returned a "Failed" error message.

  I then ran "ifconfig -a" to check on the state of the network which
  had been working until I rebooted the partition after adding the
  adapters.

  I found the unconventional names for both the Mason and the Travis_EN
  adapters contained in the output from "ifconfig -a" but also found
  that "eth0", with which I had originally set up the network access for
  the partition during setupp, was no longer listed but instead "eth1"
  was now listed and none of the networking data including IP's reported
  from "ifconfig -a" were set.

  I consulted with Thiru and he asked I write it up and include a tar
  file created from /var/log which I have attached to the defect.

  As an additional note, I was able to go back into
  /etc/network/interfaces and modify the settings for "eth0" to now be
  set to "eth1" and after bringing the port down and back up, was able
  to again ping out and access the network.

  Please advise.

  == Comment: #7 - Kevin W. Rudd  - 2016-02-11 12:32:49 ==
  Thank you for the additional info.  This is not quite the same as the bug I 
referenced earlier.  It is actually a match for bug 122308 . 

  Canonical:

  This is the same basic issue as originally worked in LP Bug 1437375

  The ibmveth based devices are not associated with PCI bus locations,
  and still rely on the legacy eth? naming.  The problem here is that
  the 75-persistent-net-generator.rules file that used to set up the 70
  -persistent-net.rules file for these devices has been removed in 16.04

  This creates a name-slip problem for these ibmveth devices depending
  on the timing of other devices (where another NIC will temporarily be
  assigned a name like eth0 before it is renamed by udev).

  Please add back persistent-net-generator support for non-PCI-based
  devices like this.

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

-- 
Mailing list: https://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 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Serge Hallyn]

cat lxd-bridge: http://paste.ubuntu.com/15768875/
systemctl status lxd-bridge:  http://paste.ubuntu.com/15768890/

These are of course before the reboot.  I cannot get in after reboot.

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1569071] Re: /usr/bin/bat in alsa-utils conflicts with /usr/bin/bat in bacula-qt-console

[Lars Bahner]

http://packages.ubuntu.com/xenial/amd64/bareos-bat/filelist

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

Title:
  /usr/bin/bat in alsa-utils conflicts with /usr/bin/bat in bacula-qt-
  console

Status in alsa-utils package in Ubuntu:
  New

Bug description:
  Unpacking alsa-utils (1.1.0-0ubuntu3) over (1.1.0-0ubuntu2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/alsa-utils_1.1.0-0ubuntu3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/bat', which is also in package 
bacula-console-qt 7.0.5+dfsg-4build1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  I am assuming that /usr/bin/alsabat has been renamed /usr/bin/bat -
  this is in conflict with existing package bacula-qt-console.

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

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

[Touch-packages] [Bug 1569071] [NEW] /usr/bin/bat in alsa-utils conflicts with /usr/bin/bat in bacula-qt-console

[Lars Bahner]

Public bug reported:

Unpacking alsa-utils (1.1.0-0ubuntu3) over (1.1.0-0ubuntu2) ...
dpkg: error processing archive 
/var/cache/apt/archives/alsa-utils_1.1.0-0ubuntu3_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/bat', which is also in package bacula-console-qt 
7.0.5+dfsg-4build1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

I am assuming that /usr/bin/alsabat has been renamed /usr/bin/bat - this
is in conflict with existing package bacula-qt-console.

** Affects: alsa-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  /usr/bin/bat in alsa-utils conflicts with /usr/bin/bat in bacula-qt-
  console

Status in alsa-utils package in Ubuntu:
  New

Bug description:
  Unpacking alsa-utils (1.1.0-0ubuntu3) over (1.1.0-0ubuntu2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/alsa-utils_1.1.0-0ubuntu3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/bat', which is also in package 
bacula-console-qt 7.0.5+dfsg-4build1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  I am assuming that /usr/bin/alsabat has been renamed /usr/bin/bat -
  this is in conflict with existing package bacula-qt-console.

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

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

[Touch-packages] [Bug 1521299] Re: Please merge freetype 2.6.3-3 from Debian testing

[Steve Langasek]

I agree that it appears 2.6.3 would be preferable due to the fuzzing
fixes.  However, as freetype has a history of introducing behavior
regressions on a fairly regular basis, this is not a straightforward
change to make during feature freeze because it's not easy to
regression-test.  I don't believe I am in a position to drive this for
16.04.

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

Title:
  Please merge freetype 2.6.3-3 from Debian testing

Status in freetype package in Ubuntu:
  Triaged
Status in freetype package in Debian:
  Fix Released

Bug description:
  Please update the package to 2.6.3. There's quite a bit of interesting
  new features and stability fixes via fuzzing since 2.5.x.

  Have a look at www.freetype.org -> "More on the 2.6.2 release for users and 
developers".
  -

  freetype (2.6.3-3) unstable; urgency=medium

* Install the now-available-upstream manpages for freetype-demos.
  Closes: #131137.
* Register all of the HTML documentation with doc-base.  Closes: #451660.
* Suppress lintian warning about symbols file declaring dependency on
  other package, which is entirely by design.

   -- Steve Langasek   Tue, 01 Mar 2016 06:43:44
  +

  freetype (2.6.3-2) unstable; urgency=medium

* Adjust symbols file to actually produce invalid dependencies when
  internal symbols are used, as intended.

   -- Steve Langasek   Tue, 01 Mar 2016 03:29:18
  +

  freetype (2.6.3-1) unstable; urgency=medium

* New upstream release.  Closes: #812518, LP: #1521299
  - stem darkening now disabled by default.  Closes: #801370.
* Avoid marking private symbols as supported from 2.6.1 on.  Apparently
  dpkg-gensymbols doesn't do what I expected for this kind of declaration
  anyway, but we should at least avoid marking them wrong in the source.
* Update to Standards-Version 3.9.7.

   -- Steve Langasek   Tue, 01 Mar 2016 00:04:14
  +

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

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

[Touch-packages] [Bug 1561302] Re: gdm won't allow passwordless login

[Tim]

** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Tim (darkxst)

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

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

Title:
  gdm won't allow passwordless login

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in casper package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  New
Status in pam package in Ubuntu:
  Invalid

Bug description:
  The Live session user does not have a password set, however gdm won't
  allow login in this case since the "Sign In" button is disabled.

  Normally this should be too much of an issue, since the login screen
  should only be hit on logout from the live session, some people are
  reporting hitting the gdm login screen on boot due to ubiquity-dm
  failing to boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 24 13:55:19 2016
  InstallationDate: Installed on 2016-03-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Stéphane Graber]

Can you attach your /etc/default/lxd-bridge and "sudo systemctl status
lxd-bridge"?

Just confirming that everything looks sane on that front.

It does look like systemd triggers on the interface and expects ifupdown
to configure it, waiting forever for it to do so, despite the
possibility that the interface isn't ifupdown-managed at all and that
there is therefore no way for ifupdown to do anything about it.

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1569066] [NEW] /usr/bin/pulseaudio:*** stack smashing detected ***: /usr/bin/pulseaudio terminated

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding pulseaudio.  This problem was most recently seen with version
1:6.0-0ubuntu13, the problem page at
https://errors.ubuntu.com/problem/9a5d1c6212dac0a988685cb691fdb5f0e39d69a4
contains more details.

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


** Tags: precise quantal raring saucy trusty utopic vivid wily

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

Title:
  /usr/bin/pulseaudio:*** stack smashing detected ***:
  /usr/bin/pulseaudio terminated

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding pulseaudio.  This problem was most recently seen with
  version 1:6.0-0ubuntu13, the problem page at
  https://errors.ubuntu.com/problem/9a5d1c6212dac0a988685cb691fdb5f0e39d69a4
  contains more details.

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

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Launchpad Bug Tracker]

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

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

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1569064] Re: systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Launchpad Bug Tracker]

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

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

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

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1569064] [NEW] systemctl wants to configure interfaces it shouldn't (lxdbr0)

[Serge Hallyn]

Public bug reported:

The reproducer:

create a xenial vm.  There, run

lxc launch ubuntu:

leave that container running, and reboot.  If you're "lucky", networking
will never come up:

[[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
[[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s / 
5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
 A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] A 
start job is running for Raise network
interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job is 
running for Raise network interfaces (35
s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

(etc)

I can reproduce this 100% on serverstack (openstack) instances.  I
cannot reproduce it locally with uvt-kvm.

What appears to be happening is that lxd starts lxd-bridge which creates
lxdbr0 with no ipv4 address;  this racily happens before systemd does
its networking setup;  said network setup then sees lxdbr0 and wants to
configure it, so waits for it to have an ip address.  Plausible?

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

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

** Also affects: lxd (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/1569064

Title:
  systemctl wants to configure interfaces it shouldn't (lxdbr0)

Status in lxd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The reproducer:

  create a xenial vm.  There, run

  lxc launch ubuntu:

  leave that container running, and reboot.  If you're "lucky",
  networking will never come up:

  [[0;32m  OK  [0m] Found device /sys/subsystem/net/devices/lxdbr0.
  [[0m[0;31m* [0m] A start job is running for Raise network interfaces (32s 
/ 5min 11s)[K[[0;1;31m*[0m[0;31m*[0m]
   A start job is running for Raise network interfaces (33s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] A start job i
  s running for Raise network interfaces (34s / 5min 11s)[K[ 
[0;31m*[0;1;31m*[0m[0;31m*  [0m] A start job is running for
  Raise network interfaces (34s / 5min 11s)[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] 
A start job is running for Raise network
  interfaces (35s / 5min 11s)[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job 
is running for Raise network interfaces (35
  s / 5min 11s)[K[[0;31m*[0;1;31m*[0m] A start job is running for Raise 
network interfaces (36s / 5min 11s)[K[ [0
  ;31m*[0m] A start job is running for Raise network interfaces (37s / 5min 
11s)[K[[0;31m*[0;1;31m*[0m] A start job i

  (etc)

  I can reproduce this 100% on serverstack (openstack) instances.  I
  cannot reproduce it locally with uvt-kvm.

  What appears to be happening is that lxd starts lxd-bridge which
  creates lxdbr0 with no ipv4 address;  this racily happens before
  systemd does its networking setup;  said network setup then sees
  lxdbr0 and wants to configure it, so waits for it to have an ip
  address.  Plausible?

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

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

[Touch-packages] [Bug 1568849] Re: inconsistent disappearance of child scope on Today scope

[Michi Henning]

Added unity-scopes-shell because scopes-api just passes through what it
gets from the shell.

** Also affects: unity-scopes-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  inconsistent disappearance of child scope on Today scope

Status in Holidays Scope:
  New
Status in unity-scopes-api package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  The child scope shown on Today scope disappears frequently after a
  manual refresh (swipe down gesture) even when WiFi+location detection
  are turned on and nothing else changes on Today scope. Not even
  multiple manual refreshes bring the child scope back. The most
  efficient way of restoring the child scope is to turn off/turn on the
  option in settings of Today scope + manual refresh of Today scope
  afterwards, although this also doesn't work in 100 % of cases.

  Would be nice to have the child scope permanently visible on Today
  scope regardless of the location and WiFi settings.

  Using BQ 4.5 / OTA 10

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

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

[Touch-packages] [Bug 1561096] Re: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under Ubuntu 16.04 with added adapters (ibmveth)

[Martin Pitt]

Fixed:
  http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=4bd57cb
  http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=e9b0a

I'll upload a new package tomorrow. I tested this with some fake DEVPATH
and QEMU devices (DRIVER=="virtio_net"), but a full install/boot test on
a real ppc64el machine with ibmveth would be highly appreciated once
this lands, to make double-sure everything is correct.

Thanks! I'm happy about this solution, it keeps simple but predictable
and stable names and avoids all the overhead and brittleness of the old
generator.

** Changed in: systemd (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under
  Ubuntu 16.04 with added adapters (ibmveth)

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  Problem Description : I had installed a fresh install of Ubuntu 16.04
  from an ISO image and had set up the partition as directed in the
  Wiki. I had set up the networking as directed in the WIKI and was able
  to ping "iofnim" and was able to perform updates and upgrades to the
  Ubuntu installation without issue.

  I had checked to make sure (by adding them to an existing AIX
  partition) that the Mason and Travis_EN adapters to be added were at
  the latest microcode levels.  I assigned them to the partition to be
  used (br16p05) and then shut down the partition and restarted it to
  allow the partition to activate the adapters.

  After the partition restarted, I attempted to build the network using
  build_net and during its run noticed that the output for the adapters
  was returning "Network is unreachable".  After it completed, I
  attempted to mount iofnim using the command:

  "mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock"

  which returned a "Failed" error message.

  I then ran "ifconfig -a" to check on the state of the network which
  had been working until I rebooted the partition after adding the
  adapters.

  I found the unconventional names for both the Mason and the Travis_EN
  adapters contained in the output from "ifconfig -a" but also found
  that "eth0", with which I had originally set up the network access for
  the partition during setupp, was no longer listed but instead "eth1"
  was now listed and none of the networking data including IP's reported
  from "ifconfig -a" were set.

  I consulted with Thiru and he asked I write it up and include a tar
  file created from /var/log which I have attached to the defect.

  As an additional note, I was able to go back into
  /etc/network/interfaces and modify the settings for "eth0" to now be
  set to "eth1" and after bringing the port down and back up, was able
  to again ping out and access the network.

  Please advise.

  == Comment: #7 - Kevin W. Rudd  - 2016-02-11 12:32:49 ==
  Thank you for the additional info.  This is not quite the same as the bug I 
referenced earlier.  It is actually a match for bug 122308 . 

  Canonical:

  This is the same basic issue as originally worked in LP Bug 1437375

  The ibmveth based devices are not associated with PCI bus locations,
  and still rely on the legacy eth? naming.  The problem here is that
  the 75-persistent-net-generator.rules file that used to set up the 70
  -persistent-net.rules file for these devices has been removed in 16.04

  This creates a name-slip problem for these ibmveth devices depending
  on the timing of other devices (where another NIC will temporarily be
  assigned a name like eth0 before it is renamed by udev).

  Please add back persistent-net-generator support for non-PCI-based
  devices like this.

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

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

[Lampros Liontos]

Was there something else I needed to clarify?  According to the
developer of OpenAL (from what I understand), the PulseAudio stream
keeps its existing buffer, even though OpenAL sets it to 0 for manual
starting control.  I was just wondering what might have been causing
this.

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

Title:
  OpenAL Software Silent/Freezes

Status in openal-soft package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1561096] Re: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under Ubuntu 16.04 with added adapters (ibmveth)

[bugproxy]

** Tags removed: bugnameltc-136930 severity-high

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

Title:
  STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under
  Ubuntu 16.04 with added adapters (ibmveth)

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Problem Description : I had installed a fresh install of Ubuntu 16.04
  from an ISO image and had set up the partition as directed in the
  Wiki. I had set up the networking as directed in the WIKI and was able
  to ping "iofnim" and was able to perform updates and upgrades to the
  Ubuntu installation without issue.

  I had checked to make sure (by adding them to an existing AIX
  partition) that the Mason and Travis_EN adapters to be added were at
  the latest microcode levels.  I assigned them to the partition to be
  used (br16p05) and then shut down the partition and restarted it to
  allow the partition to activate the adapters.

  After the partition restarted, I attempted to build the network using
  build_net and during its run noticed that the output for the adapters
  was returning "Network is unreachable".  After it completed, I
  attempted to mount iofnim using the command:

  "mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock"

  which returned a "Failed" error message.

  I then ran "ifconfig -a" to check on the state of the network which
  had been working until I rebooted the partition after adding the
  adapters.

  I found the unconventional names for both the Mason and the Travis_EN
  adapters contained in the output from "ifconfig -a" but also found
  that "eth0", with which I had originally set up the network access for
  the partition during setupp, was no longer listed but instead "eth1"
  was now listed and none of the networking data including IP's reported
  from "ifconfig -a" were set.

  I consulted with Thiru and he asked I write it up and include a tar
  file created from /var/log which I have attached to the defect.

  As an additional note, I was able to go back into
  /etc/network/interfaces and modify the settings for "eth0" to now be
  set to "eth1" and after bringing the port down and back up, was able
  to again ping out and access the network.

  Please advise.

  == Comment: #7 - Kevin W. Rudd  - 2016-02-11 12:32:49 ==
  Thank you for the additional info.  This is not quite the same as the bug I 
referenced earlier.  It is actually a match for bug 122308 . 

  Canonical:

  This is the same basic issue as originally worked in LP Bug 1437375

  The ibmveth based devices are not associated with PCI bus locations,
  and still rely on the legacy eth? naming.  The problem here is that
  the 75-persistent-net-generator.rules file that used to set up the 70
  -persistent-net.rules file for these devices has been removed in 16.04

  This creates a name-slip problem for these ibmveth devices depending
  on the timing of other devices (where another NIC will temporarily be
  assigned a name like eth0 before it is renamed by udev).

  Please add back persistent-net-generator support for non-PCI-based
  devices like this.

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

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

[Touch-packages] [Bug 1561096] Re: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under Ubuntu 16.04 with added adapters (ibmveth)

[Martin Pitt]

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

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

Title:
  STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under
  Ubuntu 16.04 with added adapters (ibmveth)

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Problem Description : I had installed a fresh install of Ubuntu 16.04
  from an ISO image and had set up the partition as directed in the
  Wiki. I had set up the networking as directed in the WIKI and was able
  to ping "iofnim" and was able to perform updates and upgrades to the
  Ubuntu installation without issue.

  I had checked to make sure (by adding them to an existing AIX
  partition) that the Mason and Travis_EN adapters to be added were at
  the latest microcode levels.  I assigned them to the partition to be
  used (br16p05) and then shut down the partition and restarted it to
  allow the partition to activate the adapters.

  After the partition restarted, I attempted to build the network using
  build_net and during its run noticed that the output for the adapters
  was returning "Network is unreachable".  After it completed, I
  attempted to mount iofnim using the command:

  "mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock"

  which returned a "Failed" error message.

  I then ran "ifconfig -a" to check on the state of the network which
  had been working until I rebooted the partition after adding the
  adapters.

  I found the unconventional names for both the Mason and the Travis_EN
  adapters contained in the output from "ifconfig -a" but also found
  that "eth0", with which I had originally set up the network access for
  the partition during setupp, was no longer listed but instead "eth1"
  was now listed and none of the networking data including IP's reported
  from "ifconfig -a" were set.

  I consulted with Thiru and he asked I write it up and include a tar
  file created from /var/log which I have attached to the defect.

  As an additional note, I was able to go back into
  /etc/network/interfaces and modify the settings for "eth0" to now be
  set to "eth1" and after bringing the port down and back up, was able
  to again ping out and access the network.

  Please advise.

  == Comment: #7 - Kevin W. Rudd  - 2016-02-11 12:32:49 ==
  Thank you for the additional info.  This is not quite the same as the bug I 
referenced earlier.  It is actually a match for bug 122308 . 

  Canonical:

  This is the same basic issue as originally worked in LP Bug 1437375

  The ibmveth based devices are not associated with PCI bus locations,
  and still rely on the legacy eth? naming.  The problem here is that
  the 75-persistent-net-generator.rules file that used to set up the 70
  -persistent-net.rules file for these devices has been removed in 16.04

  This creates a name-slip problem for these ibmveth devices depending
  on the timing of other devices (where another NIC will temporarily be
  assigned a name like eth0 before it is renamed by udev).

  Please add back persistent-net-generator support for non-PCI-based
  devices like this.

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

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

[Touch-packages] [Bug 1567037] Re: lxc-attach crashed with SIGSEGV in get_pty_on_host()

[Serge Hallyn]

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

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

Title:
  lxc-attach crashed with SIGSEGV in get_pty_on_host()

Status in lxc package in Ubuntu:
  Fix Committed
Status in tzdata package in Ubuntu:
  New

Bug description:
  Installed unity8-lxc, ran unity8-setup, then rebooted.
  Login to unity8 lxc session failed (somehow nothing happened), then I logged 
into Unity7 and the crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: lxc1 2.0.0~rc15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  6 20:11:34 2016
  ExecutablePath: /usr/bin/lxc-attach
  InstallationDate: Installed on 2015-12-03 (124 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151203)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic.efi.signed 
root=UUID=dccfbc3c-48bc-43ed-9881-36efaa2ef6c5 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x563ee5318994 : movl   $0x1,0x1c(%r14)
   PC (0x563ee5318994) ok
   source "$0x1" ok
   destination "0x1c(%r14)" (0x001c) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: lxc
  Stacktrace:
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  StacktraceTop: main ()
  ThreadStacktrace:
   .
   Thread 1 (Thread 0x7fe20540f840 (LWP 2993)):
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  Title: lxc-attach crashed with SIGSEGV in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  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/1567037/+subscriptions

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

[Touch-packages] [Bug 1561096] Re: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under Ubuntu 16.04 with added adapters (ibmveth)

[Martin Pitt]

> The 3002 is likely what we'd want to bind to.

Thanks for pointing this out! This sounds like a very good solution,
much better than either of the above. If this is stable across reboots
and indeed a property of the (virtual) "hardware", then let's use this.

Thus an udev rule like this ought to work, e. g. in /lib/udev/rules.d/76
-ibmveth-naming.rules:

SUBSYSTEM=="net", NAME=="", DRIVERS=="ibmveth", PROGRAM="/bin/sh -ec
'D=${DEVPATH#*/vio/}; D=${D#3}; echo ${D/*} | sed s/^0*//",
NAME="ibmveth$result"

This will sort after any existing 70-persistent-net.rules, but before 80
-net-setup-link.rules.

So for your example the interface would be called "ibmveth2", and for a
device which breaks the "starts with 3" assumption and has e. g.
/devices/vio/503, it would then be named "ibmveth503". If this
(not starting with '3') "Should Not Happen™", that's fine, but I'd
rather be cautious.

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

Title:
  STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under
  Ubuntu 16.04 with added adapters (ibmveth)

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Problem Description : I had installed a fresh install of Ubuntu 16.04
  from an ISO image and had set up the partition as directed in the
  Wiki. I had set up the networking as directed in the WIKI and was able
  to ping "iofnim" and was able to perform updates and upgrades to the
  Ubuntu installation without issue.

  I had checked to make sure (by adding them to an existing AIX
  partition) that the Mason and Travis_EN adapters to be added were at
  the latest microcode levels.  I assigned them to the partition to be
  used (br16p05) and then shut down the partition and restarted it to
  allow the partition to activate the adapters.

  After the partition restarted, I attempted to build the network using
  build_net and during its run noticed that the output for the adapters
  was returning "Network is unreachable".  After it completed, I
  attempted to mount iofnim using the command:

  "mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock"

  which returned a "Failed" error message.

  I then ran "ifconfig -a" to check on the state of the network which
  had been working until I rebooted the partition after adding the
  adapters.

  I found the unconventional names for both the Mason and the Travis_EN
  adapters contained in the output from "ifconfig -a" but also found
  that "eth0", with which I had originally set up the network access for
  the partition during setupp, was no longer listed but instead "eth1"
  was now listed and none of the networking data including IP's reported
  from "ifconfig -a" were set.

  I consulted with Thiru and he asked I write it up and include a tar
  file created from /var/log which I have attached to the defect.

  As an additional note, I was able to go back into
  /etc/network/interfaces and modify the settings for "eth0" to now be
  set to "eth1" and after bringing the port down and back up, was able
  to again ping out and access the network.

  Please advise.

  == Comment: #7 - Kevin W. Rudd  - 2016-02-11 12:32:49 ==
  Thank you for the additional info.  This is not quite the same as the bug I 
referenced earlier.  It is actually a match for bug 122308 . 

  Canonical:

  This is the same basic issue as originally worked in LP Bug 1437375

  The ibmveth based devices are not associated with PCI bus locations,
  and still rely on the legacy eth? naming.  The problem here is that
  the 75-persistent-net-generator.rules file that used to set up the 70
  -persistent-net.rules file for these devices has been removed in 16.04

  This creates a name-slip problem for these ibmveth devices depending
  on the timing of other devices (where another NIC will temporarily be
  assigned a name like eth0 before it is renamed by udev).

  Please add back persistent-net-generator support for non-PCI-based
  devices like this.

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

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

[Touch-packages] [Bug 1566991] Re: software-properties-gtk crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: 'modinfo'

[Brian Murray]

You seem to have the package kmod installed, is '/sbin/modinfo'
available?

** Changed in: software-properties (Ubuntu)
   Status: New => Incomplete

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

Title:
  software-properties-gtk crashed with FileNotFoundError in
  _execute_child(): [Errno 2] No such file or directory: 'modinfo'

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.20
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  6 13:22:33 2016
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2016-03-23 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 
--toplevel 48234501
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', 
'--toplevel', '48234501']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with FileNotFoundError in 
_execute_child(): [Errno 2] No such file or directory: 'modinfo'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1567037] Re: lxc-attach crashed with SIGSEGV in get_pty_on_host()

[Philipp]

# ls -l /etc/localtime 
-rw-r--r-- 1 root root 2335 Apr 10 23:13 /etc/localtime

# ls -l /var/lib/lxc/unity8-lxc/rootfs/etc/localtime 
lrwxrwxrwx 1 root root 27 Apr 10 06:02 
/var/lib/lxc/unity8-lxc/rootfs/etc/localtime -> /usr/share/zoneinfo/Etc/UTC

# ls -l /usr/share/zoneinfo/Etc/UTC 
lrwxrwxrwx 1 root root 7 Apr 10 23:12 /usr/share/zoneinfo/Etc/UTC -> ../Zulu

# ls -l /usr/share/zoneinfo/Etc/Zulu 
lrwxrwxrwx 1 root root 7 Apr 10 23:12 /usr/share/zoneinfo/Etc/Zulu -> ../Zulu

Zulu seems to be a link on itself, that cant work I guess?

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

Title:
  lxc-attach crashed with SIGSEGV in get_pty_on_host()

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Installed unity8-lxc, ran unity8-setup, then rebooted.
  Login to unity8 lxc session failed (somehow nothing happened), then I logged 
into Unity7 and the crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: lxc1 2.0.0~rc15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  6 20:11:34 2016
  ExecutablePath: /usr/bin/lxc-attach
  InstallationDate: Installed on 2015-12-03 (124 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151203)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic.efi.signed 
root=UUID=dccfbc3c-48bc-43ed-9881-36efaa2ef6c5 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x563ee5318994 : movl   $0x1,0x1c(%r14)
   PC (0x563ee5318994) ok
   source "$0x1" ok
   destination "0x1c(%r14)" (0x001c) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: lxc
  Stacktrace:
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  StacktraceTop: main ()
  ThreadStacktrace:
   .
   Thread 1 (Thread 0x7fe20540f840 (LWP 2993)):
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  Title: lxc-attach crashed with SIGSEGV in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  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/1567037/+subscriptions

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

[Touch-packages] [Bug 1561647] Re: No mokutil prompt triggered when installing from additional drivers

[Brian Murray]

** Tags added: xenial

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

Title:
  No mokutil prompt triggered when installing from additional drivers

Status in software-properties package in Ubuntu:
  New

Bug description:
  STEPS:
  1. On a system with binary blobs
  2. Install xenial daily on a secureboot system
  3. In dash type additional
  4. Click on additional drivers
  5. Install the binary drivers

  EXPECTED:
  Like in the installer or using apt install (binary blob) I expect to see a 
warning telling me in disable secureboot

  ACTUAL:
  I get nothing and the binary modules are installed.

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

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

[Touch-packages] [Bug 1516403] Re: Upper angles of window not curved

[Christopher Kyle Horton]

I'm still getting the issue here, except in my case the corners are
white instead of black.

** Attachment added: "GNOME Calendar white corners in Ambiance under Unity"
   
https://bugs.launchpad.net/unity/+bug/1516403/+attachment/4633176/+files/Screenshot%20from%202016-04-11%2016-52-14.png

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

Title:
  Upper angles of window not curved

Status in Unity:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Released
Status in unity source package in Xenial:
  Fix Released

Bug description:
  Hallo
  The upper angles aren't curved as all the other windows, see attached 
screenshot.
  Best regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 15 17:21:04 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-11 (35 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151010)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1568857] Re: gallery-app should use QML api for content-hub

[Arthur Mello]

** Branch linked: lp:~artmello/gallery-app/gallery-app-qml_content_hub

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

Title:
  gallery-app should use QML api for content-hub

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

Bug description:
  current it uses c++ api which is not documented. it should use QML api
  like other apps.

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

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

[Touch-packages] [Bug 1567840] Re: tst_datepicker generates segfault

[Tim Peeters]

tst_adaptivepagelayout.qml can crash as well, see
http://pastebin.ubuntu.com/15767687/

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

Title:
  tst_datepicker generates segfault

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

Bug description:
  On my amd64 xenial laptop:

  tim@tim-mbp:~/dev/ubuntu-ui-toolkit/m/datepicker-
  segfault/tests/unit_x11/tst_components$ qmltestrunner -import
  ../../../qml/ -input tst_datepicker.qml

  * Start testing of qmltestrunner *
  Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.3.1 20160225)
  PASS   : qmltestrunner::DatePickerAPI::initTestCase()
  QWARN  : qmltestrunner::DatePickerAPI::test_0_date() [PERFORMANCE]: Last 
frame took 43 ms to render.
  PASS   : qmltestrunner::DatePickerAPI::test_0_date()
  PASS   : qmltestrunner::DatePickerAPI::test_0_locale()
  PASS   : qmltestrunner::DatePickerAPI::test_0_minimum_maximum()
  PASS   : qmltestrunner::DatePickerAPI::test_0_mode()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDate()
  QWARN  : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth() 
file:///home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/qml/Ubuntu/Components/Pickers/1.2/DatePicker.qml:374:5:
 QML DayModel: Binding loop detected for property "date"
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeLocale()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumAfterDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumBeforeDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeH()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHMS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeHS() cannot set mode 
to Hours|Minutes
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(194)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMinute()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled() unhandled 
mode flag should not pass
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(254)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeY()
  Segmentation fault (core dumped)

  Also segfaults on jenkins, blocking all merges, see
  https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/424/consoleFull

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

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

[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc

[Stéphane Graber]

That redhat bug shows a similar end result though I doubt the cause is
the same in Ubuntu's case. We wouldn't see such random occurrences of
the bug if it was something as simple as a package shipping a completely
broken binfmt snippet.

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

Title:
   Too many levels of symbolic links /proc/sys/fs/binfmt_misc

Status in binfmt-support package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  At first I thought this was an LXD issue, but it turns out the issue
  is in systemd

  https://github.com/lxc/lxd/issues/1727#issuecomment-194416558

  ls -l  /proc/sys/fs/binfmt_misc  fails with error:

  Too many levels of symbolic links

  
  I restarted binfmt manually by running:

  sudo /usr/sbin/update-binfmts --disable
  sudo /usr/sbin/update-binfmts --enable

  I think using systemd to do this would have also worked:

  sudo service binfmt-support restart

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

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

[Touch-packages] [Bug 1563026] Re: LXC/LXD installed by default on Ubuntu server

[Pete Cheslock]

I agree with both Tom and lightraven24, in that adding in packages that
are not asked for becomes overkill when your "container" is effectively
an amazon instance.  Having the ability to create a truely "minimal"
build of ubuntu in order to run on a cloud service provider is important
to reduce possible attack vectors by having in additional software you
never asked for in the first place.  I think a menu option for
"container services" that installs all necessary lxd related
dependencies would be ideal so at least the user could choose if they
want to include that.  Asking users to specifically go and uninstall a
bunch of services after deploy seems like a poor user experience.

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

Title:
  LXC/LXD installed by default on Ubuntu server

Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  When performing a new installation of Ubuntu server 16.04 Beta 2, LXC
  and LXD are included in the default packages even when "Virtual
  Server" is not selected as an installation task. This brings in all of
  the required dependencies as well, obviously, which seems like it is
  not the best default behavior to have.

  When installing from a non-UEFI boot, the user may select "minimal
  install" from the "F4" menu. This menu is not available from the UEFI
  grub environment, making it apparently impossible to select an
  installation that does not include the LXC and LXD suite by default.

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

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

[Touch-packages] [Bug 1565658] Re: Upgrade to 1.1.1 that was released in March 2016

[Pander]

Please, put it back to "Confirmed" Thanks

** Tags removed: xenial
** Tags added: 16.10

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

Title:
  Upgrade to 1.1.1 that was released in March 2016

Status in alsa-lib package in Ubuntu:
  Won't Fix

Bug description:
  Please, upgrade to 1.1.1 that was released end of March 2016.

  See also http://www.alsa-
  project.org/main/index.php/Changes_v1.1.0_v1.1.1

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

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

[Touch-packages] [Bug 1565659] Re: Upgrade to 1.1.1 that was released in March 2016

[Pander]

** Tags removed: xenial
** Tags added: 16.10

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

Title:
  Upgrade to 1.1.1 that was released in March 2016

Status in alsa-utils package in Ubuntu:
  Confirmed

Bug description:
  Please, upgrade to 1.1.1 that was released end of March 2016.

  See also http://www.alsa-
  project.org/main/index.php/Changes_v1.1.0_v1.1.1

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

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

[Touch-packages] [Bug 1565660] Re: Upgrade to 1.1.1 that was released in March 2016

[Pander]

** Tags removed: xenial
** Tags added: 16.10

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

Title:
  Upgrade to 1.1.1 that was released in March 2016

Status in alsa-plugins package in Ubuntu:
  Confirmed

Bug description:
  Please, upgrade to 1.1.1 that was released end of March 2016.

  See also http://www.alsa-
  project.org/main/index.php/Changes_v1.1.0_v1.1.1

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

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

[Touch-packages] [Bug 1561096] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From bjki...@us.ibm.com 2016-04-11 16:27 EDT---
It really seems like the right fix here might be to enhance the code generating 
the location name to better handle ibmveth. If we look at the information below:

P: /devices/vio/3002/net/eth1
E: DEVPATH=/devices/vio/3002/net/eth1
E: ID_NET_DRIVER=ibmveth
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enx46dee7232602
E: IFINDEX=3
E: INTERFACE=eth1
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth1
E: TAGS=:systemd:
E: USEC_INITIALIZED=829495

The 3002 is likely what we'd want to bind to. The first digit should
always be 3. Its the rightmost digits we are interested in, as they are
associated with the slot id selected in the HMC. In this case 2. So I
think what we want to do is figure out how best to reflect this physical
location in order for the existing code to just work...

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

Title:
  STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under
  Ubuntu 16.04 with added adapters (ibmveth)

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Problem Description : I had installed a fresh install of Ubuntu 16.04
  from an ISO image and had set up the partition as directed in the
  Wiki. I had set up the networking as directed in the WIKI and was able
  to ping "iofnim" and was able to perform updates and upgrades to the
  Ubuntu installation without issue.

  I had checked to make sure (by adding them to an existing AIX
  partition) that the Mason and Travis_EN adapters to be added were at
  the latest microcode levels.  I assigned them to the partition to be
  used (br16p05) and then shut down the partition and restarted it to
  allow the partition to activate the adapters.

  After the partition restarted, I attempted to build the network using
  build_net and during its run noticed that the output for the adapters
  was returning "Network is unreachable".  After it completed, I
  attempted to mount iofnim using the command:

  "mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock"

  which returned a "Failed" error message.

  I then ran "ifconfig -a" to check on the state of the network which
  had been working until I rebooted the partition after adding the
  adapters.

  I found the unconventional names for both the Mason and the Travis_EN
  adapters contained in the output from "ifconfig -a" but also found
  that "eth0", with which I had originally set up the network access for
  the partition during setupp, was no longer listed but instead "eth1"
  was now listed and none of the networking data including IP's reported
  from "ifconfig -a" were set.

  I consulted with Thiru and he asked I write it up and include a tar
  file created from /var/log which I have attached to the defect.

  As an additional note, I was able to go back into
  /etc/network/interfaces and modify the settings for "eth0" to now be
  set to "eth1" and after bringing the port down and back up, was able
  to again ping out and access the network.

  Please advise.

  == Comment: #7 - Kevin W. Rudd  - 2016-02-11 12:32:49 ==
  Thank you for the additional info.  This is not quite the same as the bug I 
referenced earlier.  It is actually a match for bug 122308 . 

  Canonical:

  This is the same basic issue as originally worked in LP Bug 1437375

  The ibmveth based devices are not associated with PCI bus locations,
  and still rely on the legacy eth? naming.  The problem here is that
  the 75-persistent-net-generator.rules file that used to set up the 70
  -persistent-net.rules file for these devices has been removed in 16.04

  This creates a name-slip problem for these ibmveth devices depending
  on the timing of other devices (where another NIC will temporarily be
  assigned a name like eth0 before it is renamed by udev).

  Please add back persistent-net-generator support for non-PCI-based
  devices like this.

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

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

[Touch-packages] [Bug 1567037] Re: lxc-attach crashed with SIGSEGV in get_pty_on_host()

[Serge Hallyn]

Could you please show the results of:

ls -l /etc/localtime
ls -l /var/lib/lxc/unity8-lxc/rootfs/etc/localtime

?

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

Title:
  lxc-attach crashed with SIGSEGV in get_pty_on_host()

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Installed unity8-lxc, ran unity8-setup, then rebooted.
  Login to unity8 lxc session failed (somehow nothing happened), then I logged 
into Unity7 and the crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: lxc1 2.0.0~rc15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  6 20:11:34 2016
  ExecutablePath: /usr/bin/lxc-attach
  InstallationDate: Installed on 2015-12-03 (124 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151203)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic.efi.signed 
root=UUID=dccfbc3c-48bc-43ed-9881-36efaa2ef6c5 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x563ee5318994 : movl   $0x1,0x1c(%r14)
   PC (0x563ee5318994) ok
   source "$0x1" ok
   destination "0x1c(%r14)" (0x001c) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: lxc
  Stacktrace:
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  StacktraceTop: main ()
  ThreadStacktrace:
   .
   Thread 1 (Thread 0x7fe20540f840 (LWP 2993)):
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  Title: lxc-attach crashed with SIGSEGV in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  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/1567037/+subscriptions

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

[Touch-packages] [Bug 1568485] Re: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13

[Launchpad Bug Tracker]

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

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

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

Title:
  kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Get this logged on a fully upgraded 64 desktop (proposed archive
  enabled)

  kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/sbin/dhclient" name="run/systemd/journal/dev-log"
  pid=1102 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0
  ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr 10 12:23:56 2016
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Annoying dialog "Authentication is required to change your own user
  data"

Status in accountsservice:
  Unknown
Status in accountsservice package in Ubuntu:
  Confirmed
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in policykit-1-gnome package in Ubuntu:
  Confirmed

Bug description:
  Every few days a dialog pops up saying "Authentication is required to change 
your own user data" with an entry field for a password. If I type my user's 
password the dialog will reappear with an empty entry field. If I click on the 
cross to close the window many times it will be gone, but reappear a few days 
later. I don't know what this window is for and it makes no difference whether 
I close it or leave it. I don't use the gnome keyring.
  This started with Ubuntu 15.04 or maybe with an earlier release, and is still 
there in Ubuntu 15.10, also on machines I did a fresh install.

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

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

[Touch-packages] [Bug 1568954] Re: lvmetad should not run in container

[Launchpad Bug Tracker]

This bug was fixed in the package lvm2 - 2.02.133-1ubuntu9

---
lvm2 (2.02.133-1ubuntu9) xenial; urgency=medium

  * Do not start when inside a container (LP: #1568954)

 -- Simon Deziel   Mon, 11 Apr 2016 18:21:59
+

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

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

Title:
  lvmetad should not run in container

Status in lvm2 package in Ubuntu:
  Fix Released

Bug description:
  lvmetad is IMHO unneeded in a container.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.133-1ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 11 12:23:27 2016
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1567840] Re: tst_datepicker generates segfault

[Tim Peeters]

with aggressive garbage collection the bug gets exposed in
tst_datepicker13.qml as well:

tim@tim-mbp:~/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components$
 export QV4_MM_AGGRESSIVE_GC=1
tim@tim-mbp:~/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components$
 qmltestrunner -import ../../../qml/ -input tst_datepicker13.qml 
* Start testing of qmltestrunner *
Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 shared 
(dynamic) release build; by GCC 5.3.1 20160330)
Segmentation fault (core dumped)

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

Title:
  tst_datepicker generates segfault

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

Bug description:
  On my amd64 xenial laptop:

  tim@tim-mbp:~/dev/ubuntu-ui-toolkit/m/datepicker-
  segfault/tests/unit_x11/tst_components$ qmltestrunner -import
  ../../../qml/ -input tst_datepicker.qml

  * Start testing of qmltestrunner *
  Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.3.1 20160225)
  PASS   : qmltestrunner::DatePickerAPI::initTestCase()
  QWARN  : qmltestrunner::DatePickerAPI::test_0_date() [PERFORMANCE]: Last 
frame took 43 ms to render.
  PASS   : qmltestrunner::DatePickerAPI::test_0_date()
  PASS   : qmltestrunner::DatePickerAPI::test_0_locale()
  PASS   : qmltestrunner::DatePickerAPI::test_0_minimum_maximum()
  PASS   : qmltestrunner::DatePickerAPI::test_0_mode()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDate()
  QWARN  : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth() 
file:///home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/qml/Ubuntu/Components/Pickers/1.2/DatePicker.qml:374:5:
 QML DayModel: Binding loop detected for property "date"
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeDateToNextMonth()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeLocale()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumAfterDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMaximumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumBeforeDate()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeMinimumInvalid()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeH()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHMS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeHS() cannot set mode 
to Hours|Minutes
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(194)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeHS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeM()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMD()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMS()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeMinute()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeS()
  XFAIL  : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled() unhandled 
mode flag should not pass
     Loc: 
[/home/tim/dev/ubuntu-ui-toolkit/m/datepicker-segfault/tests/unit_x11/tst_components/tst_datepicker.qml(254)]
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeUnhandled()
  PASS   : qmltestrunner::DatePickerAPI::test_1_changeModeY()
  Segmentation fault (core dumped)

  Also segfaults on jenkins, blocking all merges, see
  https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-
  amd64-devel/424/consoleFull

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

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

[Touch-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta

[Harm van Bakel]

@seb128, I just submitted Bug #1569022 that contains a backtrace of the
crash.

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

Title:
  [FFE] NetworkManager 1.2-beta

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-applet package in Ubuntu:
  Triaged
Status in network-manager-iodine package in Ubuntu:
  Triaged
Status in network-manager-openconnect package in Ubuntu:
  Triaged
Status in network-manager-openvpn package in Ubuntu:
  Triaged
Status in network-manager-pptp package in Ubuntu:
  Triaged
Status in network-manager-vpnc package in Ubuntu:
  Triaged

Bug description:
  We really should update NetworkManager to 1.2 (or some other updated
  stable release) for the LTS, this will allow us to better deal with
  any bugs that might come up post-release.

  This new release will also much improve interop with LXC, which has
  recently been an issue.

  Other FFEs will be opened for NM VPN plugins and for NetworkManager-
  applet.

  
  
  
  NetworkManager-1.2
  Overview of changes since NetworkManager-1.0
  

  This is a new stable release of NetworkManager.  Notable changes
  include:

  * Added an option to enable use of random MAC addresses for Wi-Fi access
  point scanning (defaults to disabled).  Controlled with
  'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key 
in
  ifcfg files).
  * Wi-Fi scanning now utilizes wpa_supplicant's AP list.
  * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg
  files.
  * Added support for creation of more types of software devices: tun & tap,
  macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6).
  * The software devices (bond, bridge, vlan, team, ...) can now be stacked
  arbitrarily.  The nmcli interface for creating master-slave relationships
  has been significantly improved by the use of 'master' argument to
  all link types.
  * RFC7217 stable privacy addressing is now used by default to protect from
  address-based host tracking. The IPv6 addressing mode is configured with
  IPV6_ADDR_GEN_MODE key in ifcfg files.
  * Improved route management code to avoid clashes between conflicting
  routes in multiple connections.
  * Refactored platform code resulting in more robust interface to platform,
  less overhead and reduced memory footprint.
  * Improved interoperability with other network management tools.  The
  externally created software devices are not managed until they're
  activated.
  * The Device instances now exist for all software connections and the platform
  devices are now only created when the device is activated.  This makes it
  possible for connections with device of same name not to clash unless
  they're activated concurrently.  The links are now not unnecessarily 
present
  unless the connection is active, avoiding pollution of the link namespace.
  * NetworkManager now correctly manages connectivity in namespace-based
  containers such as LXC and Docker.
  * Support for configuring ethernet Wake-On-Lan has been added.
  * Added LLDP listener functionality and related CLI client commands. Enabled 
via
  LLDP option in ifcfg files.
  * CLI secret agent has been extended with support for VPN secrets.
  * The command line client now utilizes colors for its output.
  * The command line client now sorts the devices and properties for better
  clarity.
  * Numerous improvements to Bash command completion for nmcli.
  * NetworkManager relies on less external libraries.  The use of dbus-glib
  has been replaced with gio's native D-Bus support and libnl-route is no
  longer used.
  * Dependency on avahi-autoipd has been dropped.  Native IPv4 link-local
  addressing configuration based on systemd network library is now used
  instead.
  * Hostname is now managed via systemd-hostnamed on systemd-based systems.
  * Management of resolv.conf management can be changed at runtime, private
  resolv.conf is always written in /run.
  * NetworkManager can now write DNS options to resolv.conf.
  * Updated version of systemd network library used for internal DHCP and
  IPv4 link-local support.
  * Support for event logging via audit subsystem has been added.
  * Support for native logging via systemd-journald has been added taking
  advantage of its structured logging.
  * Live reconfiguration of IP configuration after changing the settings without
  reactivation of the device with "nmcli device reapply" command and via
  D-Bus API.
  * The API for VPN plugins now supports multiple simultaneous connections.
  Most popular VPN plugins have been updated to support this functionality.
  * The libnm library now provides 

[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc

[Stéphane Graber]

Just found this report too
https://bugzilla.redhat.com/show_bug.cgi?id=986339

** Bug watch added: Red Hat Bugzilla #986339
   https://bugzilla.redhat.com/show_bug.cgi?id=986339

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

Title:
   Too many levels of symbolic links /proc/sys/fs/binfmt_misc

Status in binfmt-support package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  At first I thought this was an LXD issue, but it turns out the issue
  is in systemd

  https://github.com/lxc/lxd/issues/1727#issuecomment-194416558

  ls -l  /proc/sys/fs/binfmt_misc  fails with error:

  Too many levels of symbolic links

  
  I restarted binfmt manually by running:

  sudo /usr/sbin/update-binfmts --disable
  sudo /usr/sbin/update-binfmts --enable

  I think using systemd to do this would have also worked:

  sudo service binfmt-support restart

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

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

[Touch-packages] [Bug 1561096] Re: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under Ubuntu 16.04 with added adapters (ibmveth)

[Martin Pitt]

Timing wise, we'll enter final freeze this Thursday, so I'd like to
upload either solution tomorrow. Any final thoughts about which approach
to take? Thanks!

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

Title:
  STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under
  Ubuntu 16.04 with added adapters (ibmveth)

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Problem Description : I had installed a fresh install of Ubuntu 16.04
  from an ISO image and had set up the partition as directed in the
  Wiki. I had set up the networking as directed in the WIKI and was able
  to ping "iofnim" and was able to perform updates and upgrades to the
  Ubuntu installation without issue.

  I had checked to make sure (by adding them to an existing AIX
  partition) that the Mason and Travis_EN adapters to be added were at
  the latest microcode levels.  I assigned them to the partition to be
  used (br16p05) and then shut down the partition and restarted it to
  allow the partition to activate the adapters.

  After the partition restarted, I attempted to build the network using
  build_net and during its run noticed that the output for the adapters
  was returning "Network is unreachable".  After it completed, I
  attempted to mount iofnim using the command:

  "mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock"

  which returned a "Failed" error message.

  I then ran "ifconfig -a" to check on the state of the network which
  had been working until I rebooted the partition after adding the
  adapters.

  I found the unconventional names for both the Mason and the Travis_EN
  adapters contained in the output from "ifconfig -a" but also found
  that "eth0", with which I had originally set up the network access for
  the partition during setupp, was no longer listed but instead "eth1"
  was now listed and none of the networking data including IP's reported
  from "ifconfig -a" were set.

  I consulted with Thiru and he asked I write it up and include a tar
  file created from /var/log which I have attached to the defect.

  As an additional note, I was able to go back into
  /etc/network/interfaces and modify the settings for "eth0" to now be
  set to "eth1" and after bringing the port down and back up, was able
  to again ping out and access the network.

  Please advise.

  == Comment: #7 - Kevin W. Rudd  - 2016-02-11 12:32:49 ==
  Thank you for the additional info.  This is not quite the same as the bug I 
referenced earlier.  It is actually a match for bug 122308 . 

  Canonical:

  This is the same basic issue as originally worked in LP Bug 1437375

  The ibmveth based devices are not associated with PCI bus locations,
  and still rely on the legacy eth? naming.  The problem here is that
  the 75-persistent-net-generator.rules file that used to set up the 70
  -persistent-net.rules file for these devices has been removed in 16.04

  This creates a name-slip problem for these ibmveth devices depending
  on the timing of other devices (where another NIC will temporarily be
  assigned a name like eth0 before it is renamed by udev).

  Please add back persistent-net-generator support for non-PCI-based
  devices like this.

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

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

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

[Mathieu Trudel-Lapierre]

ifupdown handles the passed names correctly, but it looks like iproute2
is very unhappy about something in these long names like
"enx000be608397d:1"; when setting the label for the address. Since the
label must match the device and it otherwise works with "eth1:1", I'll
looking into the iproute2 code now.

** Package changed: ifupdown (Ubuntu) => iproute2 (Ubuntu)

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

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

Title:
  RTNETLINK answers: Numerical result out of range for alias interface
  from a usb NIC

Status in iproute2 package in Ubuntu:
  In Progress

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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

[Touch-packages] [Bug 1568667] Re: apport-collect 1568667, whoopsie-upload-all: error: unrecognized arguments: 1568667

[Pavlushka]

and some more,
the /etc/init/apport-noui.conf

description "Process error reports when automatic reporting is enabled"
author "Evan Dandrea "

start on (
file FILE=/var/crash/*.crash EVENT=create
)

instance $MATCH
script
[ -e /var/lib/apport/autoreport ] || exit 0
exec /usr/share/apport/whoopsie-upload-all
end script

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

Title:
  apport-collect 1568667, whoopsie-upload-all: error: unrecognized
  arguments: 1568667

Status in whoopsie package in Ubuntu:
  Incomplete

Bug description:
  apport-collect 1568660
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: 1568660

  apport-collect 1568663
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: 1568663

  apport-collect 1568667
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: 1568667

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: whoopsie 0.2.24.6ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  CrashReports: 600:0:124:176272:2016-04-11 06:26:33.478468407 +0600:2016-04-11 
06:26:36.014480956 +0600:/var/crash/initramfs-tools.0.crash
  CurrentDesktop: GNOME
  Date: Mon Apr 11 09:43:08 2016
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1568667] Re: apport-collect 1568667, whoopsie-upload-all: error: unrecognized arguments: 1568667

[Pavlushka]

Yes.

sudo dpkg -L apport-noui
/.
/etc
/etc/init
/etc/init/apport-noui.conf
/var
/var/lib
/var/lib/apport
/usr
/usr/share
/usr/share/doc
/usr/share/doc/apport-noui
/usr/share/doc/apport-noui/copyright
/usr/share/doc/apport-noui/changelog.Debian.gz

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

Title:
  apport-collect 1568667, whoopsie-upload-all: error: unrecognized
  arguments: 1568667

Status in whoopsie package in Ubuntu:
  Incomplete

Bug description:
  apport-collect 1568660
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: 1568660

  apport-collect 1568663
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: 1568663

  apport-collect 1568667
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: 1568667

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: whoopsie 0.2.24.6ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  CrashReports: 600:0:124:176272:2016-04-11 06:26:33.478468407 +0600:2016-04-11 
06:26:36.014480956 +0600:/var/crash/initramfs-tools.0.crash
  CurrentDesktop: GNOME
  Date: Mon Apr 11 09:43:08 2016
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1457974] Re: Coloured triangles on screen

[Tim Ritberg]

SOLVED.

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

Title:
  Coloured triangles on screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 14.10 to 15.04 the Xubuntu login screen is
  corrupted with triangles and colourful shades (see photo).

  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270] 
[1002:791f] (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Technology Solutions Device [1734:110a]
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: FUJITSU SIEMENS AMILO Pa 2510
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi initrd=/casper/initrd.lz 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Tags:  vivid ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/18/08
  dmi.bios.vendor: Phoenix Technologies LTD.
  dmi.bios.version: 1.08C
  dmi.board.name: F37
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.chassis.asset.tag: 000
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD.:bvr1.08C:bd01/18/08:svnFUJITSUSIEMENS:pnAMILOPa2510:pvr20:rvnFUJITSUSIEMENS:rnF37:rvr:cvnFUJITSUSIEMENS:ct10:cvr:
  dmi.product.name: AMILO Pa 2510
  dmi.product.version: 20
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sat May 23 22:34:02 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Eduardo Corral]

Same here. Crashed 3 times today

[ 13938.517] (EE) 
[ 13938.517] (EE) Backtrace:
[ 13938.517] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x561beda6968e]
[ 13938.517] (EE) 1: /usr/bin/X (0x561bed8b5000+0x1b89f9) [0x561beda6d9f9]
[ 13938.517] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f97eb45+0x352f0) 
[0x7f97eb4852f0]
[ 13938.517] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f97e7826000+0x4b07c) [0x7f97e787107c]
[ 13938.517] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f97e7826000+0x55d5a) [0x7f97e787bd5a]
[ 13938.517] (EE) 5: /usr/bin/X (0x561bed8b5000+0x13ddf8) [0x561bed9f2df8]
[ 13938.517] (EE) 6: /usr/bin/X (0x561bed8b5000+0x54a87) [0x561bed909a87]
[ 13938.517] (EE) 7: /usr/bin/X (0x561bed8b5000+0x5818f) [0x561bed90d18f]
[ 13938.518] (EE) 8: /usr/bin/X (0x561bed8b5000+0x5c34b) [0x561bed91134b]
[ 13938.518] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f97eb470a40]
[ 13938.518] (EE) 10: /usr/bin/X (_start+0x29) [0x561bed8fb6c9]
[ 13938.518] (EE) 
[ 13938.518] (EE) Segmentation fault at address 0x47048
[ 13938.518] (EE) 
Fatal server error:
[ 13938.518] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 13938.518] (EE) 
[ 13938.518] (EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
[ 13938.518] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
[ 13938.518] (EE) 
[ 13938.518] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 13938.816] (EE) Server terminated with error (1). Closing log file.

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics 

[Touch-packages] [Bug 1563590] Re: 1.25.4, xenial, init script install error race

[Martin Pitt]

Fix sent upstream in https://github.com/systemd/systemd/pull/3016 . This
is only cosmetical, thus setting importance to "Low".

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

** Changed in: juju-core
   Status: New => Invalid

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

Title:
  1.25.4, xenial, init script install error race

Status in juju-core:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Notice the error: "The unit files have no [Install] section. They are
  not meant to be enabled using systemctl."  And the long error message
  after it saying this could be for a number of reasons.  My only clue
  is perhaps some kind of race, since I get this only occasionally.

  Here is the contents of the systemd file:

  /etc/systemd/system/multi-user.target.wants/jujud-machine-1.service

  http://paste.ubuntu.com/1673/

  Note, it does have an [Install] section, so I think the error from
  systemd link is at best misleading.

  
  Mar 29 21:47:37 pascal cloud-init[4957]: + mkdir -p 
/var/lib/juju/tools/1.25.4-xenial-amd64
  Mar 29 21:47:37 pascal cloud-init[4957]: + echo Fetching tools: curl -sSfw 
'tools from %{url_effective} downloaded: HTTP %{http_code}; time 
%{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' 
--noproxy "*" --insecure -o $bin/tools.tar.gz <[
  Mar 29 21:47:37 pascal cloud-init[4957]: Fetching tools: curl -sSfw 'tools 
from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size 
%{size_download} bytes; speed %{speed_download} bytes/s ' --noproxy "*" 
--insecure -o $bin/tools.tar.gz <[https:/
  Mar 29 21:47:37 pascal cloud-init[4957]: + seq 5
  Mar 29 21:47:37 pascal cloud-init[4957]: + printf Attempt 1 to download tools 
from %s...\n https://10.1.101.81:17070/tools/1.25.4-xenial-amd64
  Mar 29 21:47:37 pascal cloud-init[4957]: Attempt 1 to download tools from 
https://10.1.101.81:17070/tools/1.25.4-xenial-amd64...
  Mar 29 21:47:37 pascal cloud-init[4957]: + curl -sSfw tools from 
%{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size 
%{size_download} bytes; speed %{speed_download} bytes/s  --noproxy * --insecure 
-o /var/lib/juju/tools/1.25.4-xenial-amd64/tools
  Mar 29 21:47:39 pascal cloud-init[4957]: tools from 
https://10.1.101.81:17070/tools/1.25.4-xenial-amd64 downloaded: HTTP 200; time 
2.408s; size 16602428 bytes; speed 6893479.000 bytes/s + echo Tools downloaded 
successfully.
  Mar 29 21:47:39 pascal cloud-init[4957]: Tools downloaded successfully.
  Mar 29 21:47:39 pascal cloud-init[4957]: + break
  Mar 29 21:47:39 pascal cloud-init[4957]: + sha256sum 
/var/lib/juju/tools/1.25.4-xenial-amd64/tools.tar.gz
  Mar 29 21:47:40 pascal cloud-init[4957]: + grep 
416c01467ac9ddd17907d3ab627631df10822c2a706631b86efead6f3f38d27b 
/var/lib/juju/tools/1.25.4-xenial-amd64/juju1.25.4-xenial-amd64.sha256
  Mar 29 21:47:40 pascal cloud-init[4957]: 
416c01467ac9ddd17907d3ab627631df10822c2a706631b86efead6f3f38d27b  
/var/lib/juju/tools/1.25.4-xenial-amd64/tools.tar.gz
  Mar 29 21:47:40 pascal cloud-init[4957]: + tar zxf 
/var/lib/juju/tools/1.25.4-xenial-amd64/tools.tar.gz -C 
/var/lib/juju/tools/1.25.4-xenial-amd64
  Mar 29 21:47:40 pascal cloud-init[4957]: + printf %s 
{"version":"1.25.4-xenial-amd64","url":"https://10.1.101.81:17070/environment/94a7eb52-f85f-4280-8b51-0f9c8cc07748/tools/1.25.4-xenial-amd64","sha256":"416c01467ac9ddd17907d3ab627631df10822c2a706631b86efead6f3f38d2
  Mar 29 21:47:40 pascal cloud-init[4957]: + mkdir -p 
/var/lib/juju/agents/machine-1
  Mar 29 21:47:40 pascal cloud-init[4957]: + cat
  Mar 29 21:47:40 pascal cloud-init[4957]: + chmod 0600 
/var/lib/juju/agents/machine-1/agent.conf
  Mar 29 21:47:40 pascal cloud-init[4957]: + ln -s 1.25.4-xenial-amd64 
/var/lib/juju/tools/machine-1
  Mar 29 21:47:40 pascal cloud-init[4957]: + echo Starting Juju machine agent 
(jujud-machine-1)
  Mar 29 21:47:40 pascal cloud-init[4957]: Starting Juju machine agent 
(jujud-machine-1)
  Mar 29 21:47:40 pascal cloud-init[4957]: + mkdir -p 
/var/lib/juju/init/jujud-machine-1
  Mar 29 21:47:40 pascal cloud-init[4957]: + cat
  Mar 29 21:47:40 pascal cloud-init[4957]: + chmod 0755 
/var/lib/juju/init/jujud-machine-1/exec-start.sh
  Mar 29 21:47:40 pascal cloud-init[4957]: + cat
  Mar 29 21:47:40 pascal cloud-init[4957]: + /bin/systemctl link 
/var/lib/juju/init/jujud-machine-1/jujud-machine-1.service
  Mar 29 21:47:40 pascal cloud-init[4957]: Created symlink from 
/etc/systemd/system/jujud-machine-1.service to 
/var/lib/juju/init/jujud-machine-1/jujud-machine-1.service.
  Mar 29 21:47:40 pascal systemd[1]: Reloading.
  Mar 29 21:47:40 pascal systemd[1]: Started ACPI event daemon.
  Mar 29 21:47:40 pascal cloud-init[4957]: + /bin/systemctl daemon-reload
  Mar 29 21:47:40 pascal systemd[1]: Reloading.
  Mar 29 21:47:40 pascal 

[Touch-packages] [Bug 1563858] Re: Cannot open camera controls in landscape mode

[Michael]

I can confirm this for vegetahd with camera app 3.0.0.644 . In the
probably mostly used landscape orientation the BottomEdge control cannot
be swiped because the manual touch focus gets active before.

Playing with the orientation I also found out for the first time that I
can swipe to the photo roll (with the very same settings control) but
only when I hold the phone upside-down in portrait mode.

That's completely non-obvious, is there already a bug report for this?

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

Title:
  Cannot open camera controls in landscape mode

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

Bug description:
  Test case.
  - Open camera app.
  - Move the device to landscape orientation.
  - Swipe and tap on the bottom button to open the camera controls.

  Expected result.
  - Camera controls are displayed.

  Actual result.
  - Camera controls are not opened.

  current build number: 298
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  Tested also in frieza.

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

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

[Touch-packages] [Bug 1569001] Re: jackd crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Apport retracing service]

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

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 #1548103, 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/1569001/+attachment/4633101/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  jackd crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

Status in jackd2 package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 11 20:09:39 2016
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2016-01-19 (82 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160117)
  ProcCmdline: /usr/bin/jackd -T -ndefault -T -d alsa
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libjackserver.so.0
  Title: jackd crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Touch-packages] [Bug 1568999] Re: Visualizzazione delle traduzioni per segnalazione di bug all'accensione del sistema, dove nella sessione precedente avevo scaricato molti pacchetti. Traduci invece s

[Apport retracing service]

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

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 #1351286, 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/1568999/+attachment/4633091/+files/CoreDump.gz

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

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

** This bug has been marked a duplicate of bug 1351286
   colord-sane assert failure: colord-sane: simple-watch.c:454: 
avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == 
STATE_DISPATCHED || s->state == STATE_FAILURE' failed.

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
Visualizzazione delle traduzioni per segnalazione di bug
  all'accensione del sistema, dove nella sessione precedente avevo
  scaricato molti pacchetti. Traduci invece segnalazione di bag
  all'accensione del sistema, dove nella sessione precedente avevo
  scaricato molti pacchetti. Bug when the system signaling, where in the
  previous session I had downloaded several packages.

Status in colord package in Ubuntu:
  New

Bug description:
   Bug when the system signaling, where in the previous session I had
  downloaded several packages. Linux 4.4.0-18-generic(i686), ubuntu
  xenial xerus (development branch) LXDE(lubuntu).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: colord 1.2.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic i686
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Mon Apr 11 20:29:06 2016
  ExecutablePath: /usr/lib/colord/colord-sane
  InstallationDate: Installed on 2016-02-21 (50 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160102)
  ProcCmdline: /usr/lib/colord/colord-sane
  Signal: 6
  SourcePackage: colord
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1562875] Re: Totem can't play H264 on fresh 16.04 beta install

[ike]

can confirm Bruce Arnold's latest statement. VLC plays fine. Totem will
not play videos even though all ubuntu restricted extras are installed

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

Title:
  Totem can't play H264 on fresh 16.04 beta install

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Totem can't play neither find the correct codec to play H264 *.mp4
  video in last 16.04 beta.

  Terminal says :

  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile)
  decoder|decoder-video/x-h264, stream-format=(string)avc,
  alignment=(string)au, level=(string)4, profile=(string)main, max-
  input-size=(int)51696, parsed=(boolean)true (H.264 (Main Profile)
  decoder)

  
  Totem tries to find the correct codec but fails, see attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 15:51:47 2016
  InstallationDate: Installed on 2016-03-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1562875/+subscriptions

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately

[mir-ci-bot]

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.22.0

** Changed in: mir
   Status: In Progress => 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/1549701

Title:
  Sometimes devices don't suspend - display turns back on immediately

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.21 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

  Steps to reproduce on arale:

  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button

  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail

  The touchscreen is handling the circular button and emits a key down event. 
When turning the screen of the touch screen device is turned off too. Mir is 
not aware of the touchscreen being off. So meanwhile the repeat handling kicks 
in and emits key events. This makes USC turn the screen back on again.
  The touchscreen driver does not notice that the circular button is still 
held. So still no release event is sent.

  We could fix this by:
  - fixing the touchscreen driver to release any touch contacts or buttons 
pressed, when the device is turned off (something the bluetooth stack seems to 
do on some devices)
  - sidestep the problem by making usc only react to press events as a wake 
trigger and make repeat and release events only reset the inactivity timer
  - give mir the knowledge that the disabled output also disables the 
touchscreen (a connection we need to be aware of to get the mapping of touch 
screen coordinates onto scene coordinates right), hence remove the device and 
thus turn of any repeat key handling attached to that device.

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

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

[Touch-packages] [Bug 1568346] Re: Scope Manager as Black background and black text color...

[Rodney Dawes]

** Package changed: unity-scope-click (Ubuntu) => unity-scopes-shell
(Ubuntu)

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

Title:
  Scope Manager as Black background and black text color...

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

Bug description:
  it is not possible to read anything: /

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

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

[Touch-packages] [Bug 1567377] Re: Select text popup not localized

[Łukasz Zemczak]

** Changed in: langpack-o-matic
   Status: In Progress => Fix Released

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

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

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

Title:
  Select text popup not localized

Status in Canonical System Image:
  Fix Committed
Status in langpack-o-matic:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Test case.
  - Switch the phone to Spanish.
  - Open webbrowser-app.
  - Go to slashdot.org
  - Select a text.

  Expected result.
  - The select text dialog is translated to Spanish.

  Actual result.
  - Dialog is in English.

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

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

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

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

[Cerberus]

This is happening to me on BQ Aquaris E4.5 with OTA-10 for a few days
now regardless of whether I use wifi or 3g, checking for updates never
finishes, I did a tracepath to system-image.ubuntu.com as recommended to
me on the IRC, and my network reaches Canonical server fine, but after
that nothing happens. To be precise tracepath reaches:

te2-1.jotunn.canonical.com

And then I get "no reply" over and over again. I removed Ubuntu One
account, readded it, rebooted the phone and nothing. I can install
applications from the Store, but checking for updates never finishes, or
to be more precise, it does "finish" (fails) after a long time with the
error message how I should connect to the Internet. Internet otherwise
works fine on the phone, phone is not made rw nor it has any special
modifications, I run vanilla OTA-10 with no tinkering whatsoever.

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

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Fix Committed
Status in Today Scope:
  Invalid
Status in connectivity-api package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

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

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

  In all cases the log reports:

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

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

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

  One time I saw
  Connect to the Internet ...

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

  In all other cases Checking for updates never finished

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

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

[Touch-packages] [Bug 1568954] Re: lvmetad should not run in container

[Simon Déziel]

** Patch added: "xenial-lp1568954.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1568954/+attachment/4633058/+files/xenial-lp1568954.debdiff

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

Title:
  lvmetad should not run in container

Status in lvm2 package in Ubuntu:
  New

Bug description:
  lvmetad is IMHO unneeded in a container.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.133-1ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 11 12:23:27 2016
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1568667] Re: apport-collect 1568667, whoopsie-upload-all: error: unrecognized arguments: 1568667

[Brian Murray]

Do you have the apport-noui package installed?

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

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

Title:
  apport-collect 1568667, whoopsie-upload-all: error: unrecognized
  arguments: 1568667

Status in whoopsie package in Ubuntu:
  Incomplete

Bug description:
  apport-collect 1568660
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: 1568660

  apport-collect 1568663
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: 1568663

  apport-collect 1568667
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: 1568667

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: whoopsie 0.2.24.6ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  CrashReports: 600:0:124:176272:2016-04-11 06:26:33.478468407 +0600:2016-04-11 
06:26:36.014480956 +0600:/var/crash/initramfs-tools.0.crash
  CurrentDesktop: GNOME
  Date: Mon Apr 11 09:43:08 2016
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1568346] [NEW] Scope Manager as Black background and black text color...

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

it is not possible to read anything: /

** Affects: unity-scopes-shell (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Scope Manager as Black background and black text color...
https://bugs.launchpad.net/bugs/1568346
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity-scopes-shell 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 1568985] Re: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()

[Apport retracing service]

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

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 #1553549, 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/1568985/+attachment/4633022/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1553549
   unity-system-compositor crashed with SIGSEGV in get_adjusted_ptr(), when 
proprietary Nvidia drivers are installed

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()

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

Bug description:
  Installed 16.04. Tried Unity 8 LXR, also the MIR version,  and both
  hang on the login screen if that window managed is chosen. Only a
  shutdown is possible. Next Unity 7 login gives this error report.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Apr 11 19:54:56 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:146a]
  InstallationDate: Installed on 2016-01-18 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7fd8dc59ac3b:mov(%rsi),%rax
   PC (0x7fd8dc59ac3b) ok
   source "(%rsi)" (0x7fd8d62c0668) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __gxx_personality_v0 () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   _Unwind_RaiseException () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   _Unwind_Resume_or_Rethrow () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()
  UpgradeStatus: Upgraded to xenial on 2016-04-08 (3 days ago)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1
  version.lightdm: lightdm 1.18.1-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1406810] Re: screen is garbled with 14.10 (was fine with 14.04)

[Nicolas Jungers]

I burned the iso from http://cdimage.ubuntu.com/daily-live/current
/xenial-desktop-amd64.iso downloaded yesterday. The image was from the
8th of April.

The boot gives a black screen as usual now that stay till the DVD become
quiet.

When editing the grub line and removing the "quiet splash" arguments to
casper, after an initial black period, white text flickers too fast for
my camera, I'd say a full screen or so, then black again till the end.

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

Title:
  screen is garbled with 14.10 (was fine with 14.04)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On a iMac Alu 2010, when upgrading from 14.04 desktop to 14.10 desktop
  or installing 10.10 server (SSH package only) the screen shows thin 
horizontal lines moving on a black background.

  /etc/X11/xorg.conf is absent (using default config),
  /var/log/Xorg.0.log doesn't show any error beside the lack of the
  fglrx module. But I doubt it's relevant with the symptoms appearing on
  the server install.

  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV770/M98L [Mobility Radeon HD 4850] 
[1002:944a] (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Device [106b:00b5]
  InstallationDate: Installed on 2015-01-01 (440 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  MachineType: Apple Inc. iMac11,1
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic 
root=UUID=f19c8f84-1553-4a36-889a-acfb8a13da9a ro
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-79-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 03/17/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM111.88Z.0034.B02.1003171314
  dmi.board.name: Mac-F2268DAE
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268DAE
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM111.88Z.0034.B02.1003171314:bd03/17/10:svnAppleInc.:pniMac11,1:pvr1.0:rvnAppleInc.:rnMac-F2268DAE:rvr:cvnAppleInc.:ct13:cvrMac-F2268DAE:
  dmi.product.name: iMac11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Mar 16 19:43:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1568912] Re: NM autopkgtests fail IPv6 validation for non-SLAAC cases

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.1.93-0ubuntu2

---
network-manager (1.1.93-0ubuntu2) xenial; urgency=medium

  * debian/tests/nm: NM defaults to stable-privacy addrgenmode for new
connections; in other words, it tells the kernel to do address generation
using stable privacy addresses (which aren't strictly EUI-64, and so don't
carry "fe:ff" in the middle). Adjust our IPv6 test case to allow for this.
(LP: #1568912)

 -- Mathieu Trudel-Lapierre   Mon, 11 Apr 2016
11:11:30 -0400

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

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

Title:
  NM autopkgtests fail IPv6 validation for non-SLAAC cases

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Only a single example:

  ==
  FAIL: test_manual_ip6_raonly_pubaddr (__main__.ColdplugEthernet)
  ethernet: manual connection, IPv6 with only RA, preferring public address
  --
  Traceback (most recent call last):
File 
"/tmp/adt-run.onjRP6/build.gYt/network-manager-1.1.93/debian/tests/nm", line 
631, in test_manual_ip6_raonly_pubaddr
  ip6_privacy=NetworkManager.SettingIP6ConfigPrivacy.PREFER_PUBLIC_ADDR)
File 
"/tmp/adt-run.onjRP6/build.gYt/network-manager-1.1.93/debian/tests/network_test_base.py",
 line 351, in wrapped
  args[0].wrap_process(fn, *args, **kwargs)
File 
"/tmp/adt-run.onjRP6/build.gYt/network-manager-1.1.93/debian/tests/network_test_base.py",
 line 255, in wrap_process
  self.fail(f.read())
  AssertionError: Traceback (most recent call last):
File 
"/tmp/adt-run.onjRP6/build.gYt/network-manager-1.1.93/debian/tests/network_test_base.py",
 line 244, in wrap_process
  fn(*args, **kwargs)
File 
"/tmp/adt-run.onjRP6/build.gYt/network-manager-1.1.93/debian/tests/nm", line 
701, in do_test
  self.check_low_level_config(self.dev_e_client, ipv6_mode, ip6_privacy)
File 
"/tmp/adt-run.onjRP6/build.gYt/network-manager-1.1.93/debian/tests/nm", line 
372, in check_low_level_config
  self.assert_iface_up(iface, expected_ip_a, unexpected_ip_a)
File 
"/tmp/adt-run.onjRP6/build.gYt/network-manager-1.1.93/debian/tests/nm", line 
211, in assert_iface_up
  self.assertRegex(out, r)
File "/usr/lib/python3.5/unittest/case.py", line 1289, in assertRegex
  raise self.failureException(msg)
  AssertionError: Regex didn't match: 'inet6 2600::[0-9a-f:]*ff:fe[0-9a-f:]+/64 
scope global (?:tentative )?(?:mngtmpaddr )?(?:noprefixroute )?dynamic' not 
found in '9: eth42@veth42:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000\nlink/ether a2:db:d3:21:09:7b brd 
ff:ff:ff:ff:ff:ff\ninet6 2600::16/128 scope global dynamic \n   
valid_lft 3590sec preferred_lft 3590sec\ninet6 2600::345d:fa96:28ff:40df/64 
scope global temporary dynamic \n   valid_lft 3589sec preferred_lft 
3589sec\ninet6 2600::ab06:f5a:2116:306/64 scope global mngtmpaddr 
noprefixroute dynamic \n   valid_lft 3590sec preferred_lft 3590sec\n
inet6 fe80::70a2:f5ce:e46c:42bd/64 scope link \n   valid_lft forever 
preferred_lft forever\n'

  
  See 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/network-manager/20160409_002439@/log.gz;
 failing autopkgtests for NM 1.1.93-0ubuntu1 upload to Xenial.

  NM autopkgtests need to account for the new use of stable-privacy as a
  default addrgenmode for new connections.

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

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

[Touch-packages] [Bug 1567037] Re: lxc-attach crashed with SIGSEGV in get_pty_on_host()

[Philipp]

** Attachment added: "unity8-lxc.log"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1567037/+attachment/4633045/+files/unity8-lxc.log

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

Title:
  lxc-attach crashed with SIGSEGV in get_pty_on_host()

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Installed unity8-lxc, ran unity8-setup, then rebooted.
  Login to unity8 lxc session failed (somehow nothing happened), then I logged 
into Unity7 and the crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: lxc1 2.0.0~rc15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  6 20:11:34 2016
  ExecutablePath: /usr/bin/lxc-attach
  InstallationDate: Installed on 2015-12-03 (124 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151203)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic.efi.signed 
root=UUID=dccfbc3c-48bc-43ed-9881-36efaa2ef6c5 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x563ee5318994 : movl   $0x1,0x1c(%r14)
   PC (0x563ee5318994) ok
   source "$0x1" ok
   destination "0x1c(%r14)" (0x001c) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: lxc
  Stacktrace:
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  StacktraceTop: main ()
  ThreadStacktrace:
   .
   Thread 1 (Thread 0x7fe20540f840 (LWP 2993)):
   #0  0x563ee5318994 in main ()
   No symbol table info available.
  Title: lxc-attach crashed with SIGSEGV in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  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/1567037/+subscriptions

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

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

[Mathieu Trudel-Lapierre]

Looks like at first glance ifupdown is confused by this naming format
together with the subif. I'll try to reproduce here, I do happen to have
a USB ethernet dongle that should show this problem.

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

Title:
  RTNETLINK answers: Numerical result out of range for alias interface
  from a usb NIC

Status in ifupdown package in Ubuntu:
  New

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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

[Touch-packages] [Bug 1543031] Re: Sometimes no notification when new OTA is available

[Nikola Srnec]

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

I am still stuck on OTA-8 update since december 2015.

I did not get any single OTA update notificaition after OTA-8, can
somebody help fix this issue?

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

Title:
  Sometimes no notification when new OTA is available

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  New
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  frieza 7

  I flashed build 7, there is build 8 on system-image.u.c but I didn't
  receive a notification. client.log and u-d-m attached.

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

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

[Touch-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe

[Jason Gerard DeRose]

So there seems to be a curious pattern with this bug (which might
provide an important hint): on desktop systems with 970 GTX or 980 GTX
cards, this bug always seems to happen when connected to a monitor over
DisplayPort, but does *not* seem to happen when connected to a monitor
over HDMI.

We'll investigate this more carefully as soon as there's a new Xenial
daily build available (with the 4.4.0-18-generic kernel).

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

Title:
  xenial: invalid opcode when using llvmpipe

Status in System76:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  Currently Unity on Xenial is unusable when the llvmpipe software
  fallback is used, at least on certain hardware.

  For example, from dmesg:

  [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 
sp:7ffccd914ea0 error:0
  [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 
sp:7ffe5ed737e0 error:0
  [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 
sp:7ffd55804020 error:0

  This definitely effects hardware we've tested with NVIDIA 970m and
  980m GPUs (when using the nouveau driver), and probably effects others
  as well.

  Although strangely, with some NVIDIA 900 series hardware we're not
  seeing this bug when using the nouveau driver. This will be
  investigated further.

  In the current state, it's not possible to install Xenial on effected
  hardware using recent daily desktop amd64 ISOs.

  Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in
  Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from
  ppa:canonical-x/x-staging. (The later test was done with the System76
  imaging system using an image with ppa:canonical-x/x-staging and
  nvidia-361 pre-installed, then removing nvidia-361 and rebooting).

  I'm kinda shooting in the dark here, but I did my best to rule out the
  kernel as a variable:

  (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and
  had no problems.

  (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they
  don't fix the problem.

  I'm not sure the underling bug is in compiz, but I'm filing it against
  compiz anyway because that's where the dmesg output is pointing me.

  Other likely culprits include nux, mesa, maybe even llvm, and probably
  others I'm not thinking of :)

  Also, I'm positive llvmpipe is being used when this invalid opcode is
  trapped because I added this to
  /etc/X11/Xsession.d/50_check_unity_support:

  /usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log

  That way I could figure out what renderer was being used from a VT (as
  the X session is darn near unusable in this state).

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

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

[Touch-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe

[Jason Gerard DeRose]

Oh, and another bit of information: our laptops all use embedded Display
Port for their connection to the internal screen, and in this case, this
bug always manifests.

So at least in our testing so far, both eDP and DP seem to be effected.

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

Title:
  xenial: invalid opcode when using llvmpipe

Status in System76:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  Currently Unity on Xenial is unusable when the llvmpipe software
  fallback is used, at least on certain hardware.

  For example, from dmesg:

  [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 
sp:7ffccd914ea0 error:0
  [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 
sp:7ffe5ed737e0 error:0
  [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 
sp:7ffd55804020 error:0

  This definitely effects hardware we've tested with NVIDIA 970m and
  980m GPUs (when using the nouveau driver), and probably effects others
  as well.

  Although strangely, with some NVIDIA 900 series hardware we're not
  seeing this bug when using the nouveau driver. This will be
  investigated further.

  In the current state, it's not possible to install Xenial on effected
  hardware using recent daily desktop amd64 ISOs.

  Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in
  Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from
  ppa:canonical-x/x-staging. (The later test was done with the System76
  imaging system using an image with ppa:canonical-x/x-staging and
  nvidia-361 pre-installed, then removing nvidia-361 and rebooting).

  I'm kinda shooting in the dark here, but I did my best to rule out the
  kernel as a variable:

  (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and
  had no problems.

  (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they
  don't fix the problem.

  I'm not sure the underling bug is in compiz, but I'm filing it against
  compiz anyway because that's where the dmesg output is pointing me.

  Other likely culprits include nux, mesa, maybe even llvm, and probably
  others I'm not thinking of :)

  Also, I'm positive llvmpipe is being used when this invalid opcode is
  trapped because I added this to
  /etc/X11/Xsession.d/50_check_unity_support:

  /usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log

  That way I could figure out what renderer was being used from a VT (as
  the X session is darn near unusable in this state).

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

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

[Touch-packages] [Bug 1567744] Re: RTNETLINK answers: Numerical result out of range for alias interface from a usb NIC

[Andres Rodriguez]

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

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

Title:
  RTNETLINK answers: Numerical result out of range for alias interface
  from a usb NIC

Status in ifupdown package in Ubuntu:
  New

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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

[Touch-packages] [Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed

[Sebastian Nohn]

Jarno Suni, OK. Too bad. My interpretation was, this is also fixed in
14.04. For some reason I don't know more header packages were installed
than image packages. My guess is this is because of some incomplete
manual kernel removal, I executed in the past.

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

Title:
  Autoupdater fills /boot and crashes because old kernel images are
  never removed

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1) Install Ubuntu with the default LVM encryption recipe
  2) Set Ubuntu to automatically install security updates on the background
  3) Use ubuntu for 5 months

  Actual results:
  The system automatically installs security updates for the kernel under 
/boot. It's never removes previous kernel images. After about five months, the 
/boot partition created by the install recipe (i.e. sized according to the 
judgment of Ubuntu developers—not me) fills up and the unattended updater 
crashes during the next kernel update.

  Expected results:
  Expected the unattended updater to leave the nearest kernel and the previous 
one on /boot and to automatically remove older kernel images. Expected the 
system installer to set up /boot such that it never runs out of space when the 
system updater operates automatically.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: update-manager 1:0.156.14.9
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Sun Sep 23 12:53:52 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1543031] Re: Sometimes no notification when new OTA is available

[Launchpad Bug Tracker]

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

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

** Changed in: ubuntu-download-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Sometimes no notification when new OTA is available

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  New
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  frieza 7

  I flashed build 7, there is build 8 on system-image.u.c but I didn't
  receive a notification. client.log and u-d-m attached.

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

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

[Touch-packages] [Bug 1567697] Re: libcurl is missing http2 support

[Brian Murray]

** Tags added: xenial

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

Title:
  libcurl is missing http2 support

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  libcurl supports HTTP/2.0 through libnghttp2, but the package on
  Ubuntu is not compiled with it.

  Alternatively, a libcurl4-(gnutls|openssl)-nghttp2 might be a good
  idea.

  See also: https://curl.haxx.se/docs/http2.html

  curl CLI tool should not need an update, as it already has the
  commandline switches, but when you use them it comes back with
  unsupported protocol.

  drwilco@eris:~$ curl --http2 www.google.com
  curl: (1) Unsupported protocol

  
  drwilco@eris:~$ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  root@eris:~# apt-cache policy libcurl3
  libcurl3:
Installed: 7.47.0-1ubuntu2
Candidate: 7.47.0-1ubuntu2
Version table:
   *** 7.47.0-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1518332] Re: FileManager should have option for viewing rather than exporting

[Andrew Hayzen]

This looks like a duplicate/linked to bug 1413821 [0], please see the 
discussion there as well where we stated that it needs to check if the path is 
within, for example for music.
/home/*/Music
/media/*/*/Music

Then use url-handler, otherwise use content-hub. This should be the same
for documents, music, photos, videos etc.

Or alternatively for music (possibly photos, videos) check if it is in
the MediaScanner store.

0 - https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1413821

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

Title:
  FileManager should have option for viewing rather than exporting

Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  In Progress
Status in Ubuntu File Manager App:
  New
Status in mediaplayer-app package in Ubuntu:
  Fix Released
Status in ubuntu-filemanager-app package in Ubuntu:
  Confirmed

Bug description:
  I would expect to be able to open a .MP4 video from the file manager,
  and have it play in Media Player... but the it seems that Media Player
  is not an option for playback, only Gallery, which is not terribly
  suitable.

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

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