date:20160912

// , [XPS L521X, Realtek ALC3260, Headphone Out] No sound from the
headphone jack, ever.

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

// , Similar issue: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1622844

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1622844] Re: [XPS L521X, Realtek ALC3260, Headphone Out] No sound from the headphone jack, ever.

// , Similar issue: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1523100?comments=all

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

Title:
  [XPS L521X, Realtek ALC3260, Headphone Out] No sound from the
  headphone jack, ever.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
// , Other sound works alright.

  This bug seems to affect my Dell XPS L521X Ubuntu laptop running
  Ubuntu Xenial 16.04:

  $ lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller (rev 04)
  01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller 
(rev ff)

  
  $ uname -a
  Linux nb-XPS-L521X 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 
18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  My headphone jack simply does not work with 16.04.

  It worked just fine with 14.04.

  I ran the following command to look at my audio packages:

  $ sudo apt list > apt_list_20160912.txt ; cat
  apt_list_20160912.txt | egrep 'audio|alsa|pulse'

  Results are at the following link:

  http://hastebin.com/kivayotucu.apache

  If you would like further details about this, or a gdb report, I'm at
  your service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   nb 3944 F...m pulseaudio
   /dev/snd/controlC0:  nb 3944 F pulseaudio
nb13118 F alsamixer
   /dev/snd/controlC1:  nb 3944 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 12 22:23:48 2016
  InstallationDate: Installed on 2016-09-11 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [XPS L521X, Realtek ALC3260, Black Headphone Out, Front] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0880F2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/01/2013:svnDellInc.:pnXPSL521X:pvrA15:rvnDellInc.:rn0880F2:rvrA00:cvnDellInc.:ct8:cvrA15:
  dmi.product.name: XPS L521X
  dmi.product.version: A15
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1622844] [NEW] [XPS L521X, Realtek ALC3260, Headphone Out] No sound from the headphone jack, ever.

Public bug reported:

  // , Other sound works alright.

This bug seems to affect my Dell XPS L521X Ubuntu laptop running Ubuntu
Xenial 16.04:

$ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller (rev 04)
01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller 
(rev ff)


$ uname -a
Linux nb-XPS-L521X 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

My headphone jack simply does not work with 16.04.

It worked just fine with 14.04.

I ran the following command to look at my audio packages:

$ sudo apt list > apt_list_20160912.txt ; cat
apt_list_20160912.txt | egrep 'audio|alsa|pulse'

Results are at the following link:

http://hastebin.com/kivayotucu.apache

If you would like further details about this, or a gdb report, I'm at
your service.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   nb 3944 F...m pulseaudio
 /dev/snd/controlC0:  nb 3944 F pulseaudio
  nb13118 F alsamixer
 /dev/snd/controlC1:  nb 3944 F pulseaudio
CurrentDesktop: Unity
Date: Mon Sep 12 22:23:48 2016
InstallationDate: Installed on 2016-09-11 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: Only some of outputs are working
Title: [XPS L521X, Realtek ALC3260, Black Headphone Out, Front] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/01/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0880F2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A15
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/01/2013:svnDellInc.:pnXPSL521X:pvrA15:rvnDellInc.:rn0880F2:rvrA00:cvnDellInc.:ct8:cvrA15:
dmi.product.name: XPS L521X
dmi.product.version: A15
dmi.sys.vendor: Dell Inc.

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


** Tags: alc3260 amd64 apport-bug audio xenial

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

Title:
  [XPS L521X, Realtek ALC3260, Headphone Out] No sound from the
  headphone jack, ever.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
// , Other sound works alright.

  This bug seems to affect my Dell XPS L521X Ubuntu laptop running
  Ubuntu Xenial 16.04:

  $ lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller (rev 04)
  01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller 
(rev ff)

  
  $ uname -a
  Linux nb-XPS-L521X 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 
18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  My headphone jack simply does not work with 16.04.

  It worked just fine with 14.04.

  I ran the following command to look at my audio packages:

  $ sudo apt list > apt_list_20160912.txt ; cat
  apt_list_20160912.txt | egrep 'audio|alsa|pulse'

  Results are at the following link:

  http://hastebin.com/kivayotucu.apache

  If you would like further details about this, or a gdb report, I'm at
  your service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   nb 3944 F...m pulseaudio
   /dev/snd/controlC0:  nb 3944 F pulseaudio
nb13118 F alsamixer
   /dev/snd/controlC1:  nb 3944 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Sep 12 22:23:48 2016
  InstallationDate: Installed on 2016-09-11 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [XPS L521X, Realtek ALC3260, Black Headphone Out, Front]

[Touch-packages] [Bug 1622742] Re: ActivityIndicator broken, likely due to Qt 5.6 update

2016-09-12 Thread Zsombor Egri

** Tags added: qt5.6

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

Title:
  ActivityIndicator broken, likely due to Qt 5.6 update

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

Bug description:
  QML ActivityIndicator: file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

  The indicator isn't displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 
1.3.2073+16.04.20160824build1~~xenialoverlay1~1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 12 22:31:21 2016
  InstallationDate: Installed on 2016-05-06 (128 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Enabling debugging I can't see anything EGL-related failing before the
errors start in unity8-dash.log. Although rendering appears to fail:

[2016-09-13:12:45:18.825] ubuntumirclient: Created surface with geometry: QRect(
0,24 510x712) title: "Scopes" role: 1
[2016-09-13:12:45:18.825] ubuntumirclient.graphics: Requested format: 
QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize 
8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize -1, stencilBufferSize 
8, samples -1, swapBehavior 2, swapInterval 1, profile  0) 
Actual format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 
24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, 
stencilBufferSize 8, samples 0, swapBehavior 0, swapInterval 1, profile  0) 
with associated Mir pixel format: XRGB
[2016-09-13:12:45:18.825] ubuntumirclient: UbuntuWindow(window=0x55e51c635990, s
creen=0x55e51c53cd80, input=0x55e51c53cbe0, surf=0x55e51ca3eae0) with title 'Sco
pes', role: '1'
[2016-09-13:12:45:18.825] ubuntumirclient: setVisible (window=0x55e51c635990, vi
sible=true)
[2016-09-13:12:45:18.825] ubuntumirclient: updateSurfaceState (window=0x55e51c63
5990, surfaceState=restored)
[2016-09-13:12:45:18.826] file:///usr/share/unity8//Dash/Dash.qml:39: ReferenceE
rror: window is not defined
[2016-09-13:12:45:18.826] file:///usr/share/unity8//Dash/GenericScopeView.qml:64
4: TypeError: Cannot read property 'activeFiltersCount' of null
[2016-09-13:12:45:18.826] file:///usr/share/unity8//Dash/GenericScopeView.qml:64
3: TypeError: Cannot read property 'filters' of null
[2016-09-13:12:45:18.826] file:///usr/share/unity8//Dash/Dash.qml:265: 
ReferenceError: scopeStyle is not defined
[2016-09-13:12:45:18.826] ubuntumirclient.input: 
customEvent(type=mir_event_type_surface_output)
[2016-09-13:12:45:18.826] User agent string: 
"release=16.10=1.0.6+16.10.20160617-0ubuntu1=0.5.7+16.10.20160624.2-0ubuntu2=8.14+16.10.20160831.3-0ubuntu1"
[2016-09-13:12:45:18.827] qt.scenegraph.renderloop: exposureChanged() 
QQuickWindowQmlImpl(0x55e51c635990)
[2016-09-13:12:45:18.827] qt.scenegraph.renderloop: handleExposure() 
QQuickWindowQmlImpl(0x55e51c635990)
[2016-09-13:12:45:18.827] qt.scenegraph.renderloop: - adding window to list
[2016-09-13:12:45:18.827] qt.scenegraph.renderloop: - starting render thread
[2016-09-13:12:45:18.829] ubuntumirclient.graphics: EGL vendor: Mesa Project
[2016-09-13:12:45:18.829] ubuntumirclient.graphics: EGL version: 1.4 (DRI2)
[2016-09-13:12:45:18.829] ubuntumirclient.graphics: EGL extensions: 
EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import EGL_KHR_create_context 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_reusable_sync 
EGL_KHR_surfaceless_context EGL_MESA_configless_context EGL_MESA_drm_image 
EGL_MESA_image_dma_buf_export 
[2016-09-13:12:45:18.829] ubuntumirclient.graphics: EGL configuration 
attributes:
[2016-09-13:12:45:18.829]   EGL_BUFFER_SIZE: 32
[2016-09-13:12:45:18.829]   EGL_ALPHA_SIZE: 8
[2016-09-13:12:45:18.829]   EGL_BLUE_SIZE: 8
[2016-09-13:12:45:18.829]   EGL_GREEN_SIZE: 8
[2016-09-13:12:45:18.829]   EGL_RED_SIZE: 8
[2016-09-13:12:45:18.829]   EGL_DEPTH_SIZE: 24
[2016-09-13:12:45:18.829]   EGL_STENCIL_SIZE: 8
[2016-09-13:12:45:18.829]   EGL_CONFIG_CAVEAT: 12344
[2016-09-13:12:45:18.829]   EGL_CONFIG_ID: 9
[2016-09-13:12:45:18.829]   EGL_LEVEL: 0
[2016-09-13:12:45:18.829]   EGL_MAX_PBUFFER_HEIGHT: 0
[2016-09-13:12:45:18.829]   EGL_MAX_PBUFFER_PIXELS: 0
[2016-09-13:12:45:18.829]   EGL_MAX_PBUFFER_WIDTH: 0
[2016-09-13:12:45:18.829]   EGL_NATIVE_RENDERABLE: 1
[2016-09-13:12:45:18.829]   EGL_NATIVE_VISUAL_ID: 0
[2016-09-13:12:45:18.829]   EGL_NATIVE_VISUAL_TYPE: 12344
[2016-09-13:12:45:18.829]   EGL_SAMPLES: 0
[2016-09-13:12:45:18.829]   EGL_SAMPLE_BUFFERS: 0
[2016-09-13:12:45:18.829]   EGL_SURFACE_TYPE: 4
[2016-09-13:12:45:18.829]   EGL_TRANSPARENT_TYPE: 12344
[2016-09-13:12:45:18.829]   EGL_TRANSPARENT_BLUE_VALUE: 0
[2016-09-13:12:45:18.829]   EGL_TRANSPARENT_GREEN_VALUE: 0
[2016-09-13:12:45:18.829]   EGL_TRANSPARENT_RED_VALUE: 0
[2016-09-13:12:45:18.829]   EGL_BIND_TO_TEXTURE_RGB: 0
[2016-09-13:12:45:18.829]   EGL_BIND_TO_TEXTURE_RGBA: 0
[2016-09-13:12:45:18.829]   EGL_MIN_SWAP_INTERVAL: 0
[2016-09-13:12:45:18.829]   EGL_MAX_SWAP_INTERVAL: 0
[2016-09-13:12:45:18.830] qt.scenegraph.renderloop: - OpenGL context created

...

[2016-09-13:12:45:18.831] qt.scenegraph.renderloop: - lock for sync
[2016-09-13:12:45:18.831] qt.scenegraph.renderloop: - wait for sync
[2016-09-13:12:45:18.846] qt.scenegraph.renderloop: (RT) 
--- begin processEvents()
[2016-09-13:12:45:18.846] qt.scenegraph.renderloop: (RT) 
WM_RequestSync
[2016-09-13:12:45:18.846] qt.scenegraph.renderloop: (RT) -

[Touch-packages] [Bug 1622826] Re: unity8-dash crashed with SIGSEGV in eglDestroyContext()

2016-09-12 Thread Apport retracing service

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

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 #1620994, 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/1622826/+attachment/4739612/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  unity8-dash crashed with SIGSEGV in eglDestroyContext()

Status in unity8 package in Ubuntu:
  New

Bug description:
  Todays image of 16.10, updated. login to unity8 gives pretty much unusable 
session & 3 crashes, this is one.
  (- nothing actually works except opening items in the launcher, the 
items/scopes don't work & can't be closed/quit directly, only from the launcher.

  Other 2 crashes -
  private - Bug #1620939  Bug #1622827

  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160831.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 13 00:00:49 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-09-13 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160910)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1fd51da3e:mov0x30(%rbp),%rax
   PC (0x7ff1fd51da3e) ok
   source "0x30(%rbp)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglDestroyContext () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QOpenGLContext::destroy() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGSEGV in eglDestroyContext()
  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/unity8/+bug/1622826/+subscriptions

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

[Touch-packages] [Bug 1503551] Re: Java segfaulted in i965 driver - lots of deleted mmapped files

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

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

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

Title:
  Java segfaulted in i965 driver - lots of deleted mmapped files

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Java encountered a segfault in the i965 driver while running
  Minecraft. A perusal of the dump report suggests that the issue is not
  due to Minecraft but due to heavy use of the graphics exacerbating a
  memory mapping leak in the driver - it seems that the mappings for
  /dev/drm/card0 and /dri objects are not properly freed.

  Note that I was running Optifine with Multi-Core loading, which causes
  multi-threaded use of the graphics driver.

  Important parts of the hs_err file are pasted below. However, I cut
  out a *lot* of the /drm mm object and /dev/dri/card0 mappings. There's
  a more than a hundred pages at 30 lines a page.

  ---

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f180efcc4e3, pid=31233, tid=139740657592064
  #
  # JRE version: OpenJDK Runtime Environment (7.0_79-b14) (build 1.7.0_79-b14)
  # Java VM: OpenJDK 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 
compressed oops)
  # Derivative: IcedTea 2.5.6
  # Distribution: Ubuntu 15.04, package 7u79-2.5.6-0ubuntu1.15.04.1
  # Problematic frame:
  # C  [i965_dri.so+0x1914e3]
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
  #
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #

  Stack: [0x7f17e831a000,0x7f17e841b000],  sp=0x7f17e84197e0,  free 
space=1021k
  Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
code)
  C  [i965_dri.so+0x1914e3]

  Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
  J 1853  org.lwjgl.opengl.GL11.nglDrawArrays(IIIJ)V (0 bytes) @ 
0x7f18614fc92a [0x7f18614fc8e0+0x4a]
  J 2863 C2 net.minecraft.client.renderer.Tessellator.func_78381_a()I (346 
bytes) @ 0x7f186177e020 [0x7f186177d7e0+0x840]
  J 5013 C2 
WorldRendererThreaded.postRenderBlocksThreaded(ILnet/minecraft/entity/EntityLivingBase;)V
 (114 bytes) @ 0x7f1861ced92c [0x7f1861ced8c0+0x6c]
  J 2709 C2 WorldRendererThreaded.updateRenderer(LIWrUpdateListener;)V (823 
bytes) @ 0x7f18617a3504 [0x7f18617a2b20+0x9e4]
  J 4593% C2 WrUpdateThread.run()V (140 bytes) @ 0x7f1861abb340 
[0x7f1861abb020+0x320]
  v  ~StubRoutines::call_stub

  Dynamic libraries:
  0040-00401000 r-xp  fc:00 13763814   
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
  0060-00601000 r--p  fc:00 13763814   
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
  00601000-00602000 rw-p 1000 fc:00 13763814   
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
  0066f000-0069 rw-p  00:00 0  
[heap]
  b5a0-bda0 rw-p  00:00 0
  bda0-c000 rw-p  00:00 0
  c000-eaa8 rw-p  00:00 0
  eaa8-1 rw-p  00:00 0
  7f1743442000-7f174344a000 rw-s  00:05 3198953/drm 
mm object (deleted)
  7f174344a000-7f1743452000 rw-s  00:05 3198952/drm 
mm object (deleted)
  7f1743452000-7f174345a000 rw-s  00:05 3198951/drm 
mm object (deleted)
  7f174345a000-7f1743462000 rw-s  00:05 3198950/drm 
mm object (deleted)
  7f1743462000-7f174346a000 rw-s 142cc8000 00:06 11074 
/dev/dri/card0
  7f174346a000-7f1743472000 rw-s  00:05 3198949/drm 
mm object (deleted)
  7f1743472000-7f174347a000 rw-s 142cc 00:06 11074 
/dev/dri/card0
  7f174347a000-7f1743482000 rw-s  00:05 3198948/drm 
mm object (deleted)
  7f1743482000-7f174348a000 rw-s 142cb8000 00:06 11074 
/dev/dri/card0
  7f174348a000-7f1743492000 rw-s 142cb 00:06 11074 
/dev/dri/card0

   snip 

  7f1745c72000-7f1745c7a000 rw-s 14168 00:06 11074 
/dev/dri/card0
  7f1745c7a000-7f1745c82000 rw-s 141678000 00:06 11074 
/dev/dri/card0
  7f1745c82000-7f1745c8a000 rw-s 14167 00:06 11074 
/dev/dri/card0
  7f1745c8a000-7f1745c92000 rw-s 141668000 00:06 11074 
/dev/dri/card0
  7f1745c92000-7f1745c9a000 rw-s  00:05 3200480/drm 
mm object (deleted)
  7f1745c9a000-7f1745ca2000 rw-s 14166 00:06 11074 
/dev/dri/card0

[Touch-packages] [Bug 1579182] Re: [drm:intel_pipe_update_end [i915]] ERROR Atomic update failure on pipe A

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

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

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

Title:
  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.04 upgraded from Ubuntu 14.04 on a Dell Inspiron 14z, w
  /Intel-ATI hybrid graphics (but DIS card is OFF through
  vgaswitcheroo).

  Just like bug no. #1525390 [1], Chrome shows some artifacts randomly
  and I have the same kernel trace but from 10 days ago (I use this
  system everyday and it didn't happened since then).

  [1] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525390

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri May  6 15:17:08 2016
  DistUpgraded: 2016-04-25 18:04:08,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 5.0.20, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057f]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2013-08-12 (997 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmDisplayLog:
   [dix] EventToCore: Not implemented yet 
   [dix] EventToCore: Not implemented yet
  MachineType: Dell Inc. Inspiron 5423
  ProcEnviron:
   LANGUAGE=es_AR:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (10 days ago)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 05WDP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/18/2013:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn05WDP7:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May  6 09:34:55 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9020 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1602950] Re: Unity8 crashes when switching back to lockscreen while using WiDi

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

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

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

Title:
  Unity8 crashes when switching back to lockscreen while using WiDi

Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Testing new aethercast changes (https://requests.ci-
  train.ubuntu.com/#/ticket/1620) and found unity8 is crashing when it
  switches after a timeout automatically to the lock screen.

  This is on

  current build number: 142
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-07-13 05:57:58
  version version: 142
  version ubuntu: 20160713
  version device: 20160622.0
  version custom: 20160712--42-19-vivid

  SEGV backtrace:

   #0  0xe656f40e in MirBufferSGTexture::bind() () from 
/usr/lib/arm-linux-gnueabihf/qt5/qml/Unity/Application/libunityapplicationplugin.so
   No symbol table info available.
   #1  0xf6f605e2 in 
QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState 
const&, QSGMaterial*, QSGMaterial*) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
   No symbol table info available.
   #2  0xf6f5194a in 
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) 
() from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
   No symbol table info available.
   #3  0xf6f527c8 in QSGBatchRenderer::Renderer::renderBatches() () from 
/usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
   No symbol table info available.
   #4  0xf70d2f48 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5

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

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

[Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

CONFIRMED. Downgrading Mesa to 12.0.1 fixes the problem:
https://launchpad.net/ubuntu/+source/mesa/12.0.1-3ubuntu2/+build/10506751

So the regression was triggered by:
https://launchpad.net/ubuntu/+source/mesa/12.0.2-1ubuntu1

However that doesn't mean Mesa is buggy necessarily. Our Qt EGL setup
code might be requesting something invalid and it only just became a
fatal error. In that case our Qt code would need fixing rather than
Mesa. Indeed non-Qt clients don't have the bug at all.

** Changed in: mesa (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: mesa (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

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

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

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Another prime candidate that possibly triggered this bug:
   https://launchpad.net/ubuntu/+source/mesa/12.0.2-1ubuntu1
Released on 7 September (which would have been 8 Sept here).

It could easily be that our Qt apps are (and always have been)
requesting some EGL attributes that Mesa can not or should not provide.
That could be a Mesa bug or a Qt bug that's been around for much longer
and Mesa only just became pedantic enough to say no. Remember EGL
clients from the 'mir-demos' package still render OK so this is
something specific to Q* clients.

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

And the app never rendered because its call to eglMakeCurrent failed
with error 3001 (EGL_NOT_INITIALIZED).

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1508905] Re: Graphics disorder, a large "claw" ('>') appearing

** Summary changed:

- Graphics disorder, a "claw" appearing
+ Graphics disorder, a large "claw" ('>') appearing

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

Title:
  Graphics disorder, a large "claw" ('>') appearing

Status in Today Scope:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Currently I have this bug. It was already present in the OTA-6.
  Usually a reboot fix the problem, but after a while it come back
  again.

  It only appears ate the bottom of the scope! If I swipe back to the
  top the "claw" fade out.

  I've attached a screenshot.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1508905/+subscriptions

-- 
Mailing list: https://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 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2016-09-12 Thread Luke Yelavich

Ok, everybody experiencing the constant volume notificatinos, please get
a log from PulseAudio as outlined here:
https://wiki.ubuntu.com/PulseAudio/Log.

Thanks.

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

Title:
Volume notification keeps popping up constantly(the notifyosd bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-09-12 Thread Jarno Suni

This bug is 'Fix Released' because I marked it as such. Maybe too soon
as it is irreversible.

Ok, if someone writes new bug report about kernels not autoremoving,
please link it here.

Ian Weisser, you may e.g contact me privately, if you want to tell me
about the kernel header packages thing.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

[Touch-packages] [Bug 1576692] Re: fully support package installation in systemd

2016-09-12 Thread Patricia Gaughen

We use what's in the archive for what we include in cloud images. So
once cloud-init lands, it will makes it way to an image. I would expect
that Scott working his way through the SRU process.

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  In Progress
Status in init-system-helpers source package in Xenial:
  In Progress

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to have a way to fully support this in cloud-init.

  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out

  SRU INFORMATION
  ===
  FIX for init-system-helpers: 
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02

  REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
  and service, two very central pieces of packaging infrastructure.
  Errors in it will break installation/upgrades of packages or
  /etc/network/if-up.d/ hooks and the like. This changes the condition
  when systemd units get started without their dependencies, and the
  condition gets weakened. This means that behaviour in a booted system
  is unchanged, but during boot this could change the behaviour of if-
  up.d/ hooks (although they have never been defined well during boot
  anyway). However, I tested this change extensively in cloud images and
  desktop installations (particularly I recreated
  https://bugs.debian.org/777113 and confirmed that this approach also
  fixes it) and could not find any regression.

  TEST CASE (for both packages):
  Run
 lxc launch ubuntu-daily:x --config=user.user-data="$(printf 
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1

  This will install all three packages, but "systemctl status
  postgresql@9.5-main" will not be running.

  Now prepare a new image with the proposed cloud-init and init-system-
  helpers:

 lxc launch ubuntu-daily:x xprep
 lxc exec xprep bash
 # enable -proposed and dist-upgrade, then poweroff
 lxc publish xprep x-proposed

  Now run the initial lxc launch again, but against that new x-proposed
  image instead of the standard daily:

lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
  config\npackages: [postgresql, samba, postfix]")" x1

  You should now have "systemctl status postgresql@9.5-main" running.
  Directly after rebooting the instance, check that there are no hanging
  jobs (systemctl list-jobs), particularly networking.service, to ensure
  that https://bugs.debian.org/777113 did not come back.

  Also test interactively installing a package that ships a service,
  like "apache2", and verify that it starts properly after installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+subscriptions

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

[Touch-packages] [Bug 1224007] Re: mtu not always set properly on bond/vlan interface

sorry, the first patch had an issue where it didn't raise the device mtu
if the vlan already existed.  the v2 checks and increases if needed the
dev mtu, even if the vlan already exists.

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

Title:
  mtu not always set properly on bond/vlan interface

Status in ifupdown package in Ubuntu:
  Confirmed
Status in vlan package in Ubuntu:
  New
Status in ifupdown package in Debian:
  New

Bug description:
  * Description

  When configuring a network with bonding+vlan and setting the MTU,
  occasionally the MTU doesn't get set properly on the vlan interface.

  In addition if one checks /var/log/upstart/networking.log whenever there is a 
failure the following message is printed:
  SIOCSIFMTU: Numerical result out of range

  I've tested the latest ifupdown package (0.7.44) and the problem still exists.
  Multi/single CPU settings both exhibit the issue.

  * Versions
  This affects latest ifupdown and ubuntu p/q/r/s.

  * Test Case

  # Create a p/q/r/s server vm with two network interfaces
  # This is reproducible on real hardware as well

  # Install the following
  sudo apt-get install vlan ifenslave-2.6 bridge-utils
  sudo modprobe bonding 8021q

  # Edit the interfaces file
  /etc/networking/interfaces:

  auto bond0
  iface bond0 inet manual
bond-mode 802.3ad
bond-miimon 100
bond-lacp-rate 1
bond-slaves eth0 eth1
post-up ifconfig bond0 mtu 9000

  auto eth0
  iface eth0 inet manual
bond-master bond0
post-up ifconfig eth0 mtu 9000

  auto eth1
  iface eth1 inet manual
bond-master bond0
post-up ifconfig eth1 mtu 9000

  auto bond0.123
  iface bond0.123 inet static
address 192.168.122.68
netmask 255.255.255.0
gateway 192.168.122.1
post-up ifconfig bond0.123 mtu 9000

  # edit rc.local (or another startup script) so we reboot until we hit the 
error
  /etc/rc.local:

  DEVS="eth0 eth1 bond0 bond0.123"
  for d in $DEVS; do
  mtu=$(cat /sys/class/net/$d/mtu)
  if [ $mtu != 9000 ]; then
  echo "FAIL"
  exit 1
  fi
  done

  reboot
  exit 0

  # Now reboot the machine, within 10m or so you should be at the login prompt
  # if you ifconfig | grep MTU you will see some of our interfaces did not get 
  # the MTU properly set and the test failed.
  # Essentially we want to ensure that all MTU's (except lo) were set to 9000

  * Workaround

  Change the bond0.123 post-up command to:
post-up sleep 2 && ifconfig bond0.123 mtu 9000

  Now when rebooting the interfaces will all be brought up with the
  proper MTU.

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

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

[Touch-packages] [Bug 1224007] Re: mtu not always set properly on bond/vlan interface

** Patch added: "patchv2 to yakkety debian/network/if-pre-up.d/vlan script"
   
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1224007/+attachment/4739533/+files/lp1224007-yakkety-v2.patch

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

Title:
  mtu not always set properly on bond/vlan interface

Status in ifupdown package in Ubuntu:
  Confirmed
Status in vlan package in Ubuntu:
  New
Status in ifupdown package in Debian:
  New

Bug description:
  * Description

  When configuring a network with bonding+vlan and setting the MTU,
  occasionally the MTU doesn't get set properly on the vlan interface.

  In addition if one checks /var/log/upstart/networking.log whenever there is a 
failure the following message is printed:
  SIOCSIFMTU: Numerical result out of range

  I've tested the latest ifupdown package (0.7.44) and the problem still exists.
  Multi/single CPU settings both exhibit the issue.

  * Versions
  This affects latest ifupdown and ubuntu p/q/r/s.

  * Test Case

  # Create a p/q/r/s server vm with two network interfaces
  # This is reproducible on real hardware as well

  # Install the following
  sudo apt-get install vlan ifenslave-2.6 bridge-utils
  sudo modprobe bonding 8021q

  # Edit the interfaces file
  /etc/networking/interfaces:

  auto bond0
  iface bond0 inet manual
bond-mode 802.3ad
bond-miimon 100
bond-lacp-rate 1
bond-slaves eth0 eth1
post-up ifconfig bond0 mtu 9000

  auto eth0
  iface eth0 inet manual
bond-master bond0
post-up ifconfig eth0 mtu 9000

  auto eth1
  iface eth1 inet manual
bond-master bond0
post-up ifconfig eth1 mtu 9000

  auto bond0.123
  iface bond0.123 inet static
address 192.168.122.68
netmask 255.255.255.0
gateway 192.168.122.1
post-up ifconfig bond0.123 mtu 9000

  # edit rc.local (or another startup script) so we reboot until we hit the 
error
  /etc/rc.local:

  DEVS="eth0 eth1 bond0 bond0.123"
  for d in $DEVS; do
  mtu=$(cat /sys/class/net/$d/mtu)
  if [ $mtu != 9000 ]; then
  echo "FAIL"
  exit 1
  fi
  done

  reboot
  exit 0

  # Now reboot the machine, within 10m or so you should be at the login prompt
  # if you ifconfig | grep MTU you will see some of our interfaces did not get 
  # the MTU properly set and the test failed.
  # Essentially we want to ensure that all MTU's (except lo) were set to 9000

  * Workaround

  Change the bond0.123 post-up command to:
post-up sleep 2 && ifconfig bond0.123 mtu 9000

  Now when rebooting the interfaces will all be brought up with the
  proper MTU.

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

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

[Touch-packages] [Bug 1224007] Re: mtu not always set properly on bond/vlan interface

** Patch added: "debdiffv2 for yakkety vlan"
   
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1224007/+attachment/4739534/+files/lp1224007-yakkety-v2.debdiff

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

Title:
  mtu not always set properly on bond/vlan interface

Status in ifupdown package in Ubuntu:
  Confirmed
Status in vlan package in Ubuntu:
  New
Status in ifupdown package in Debian:
  New

Bug description:
  * Description

  When configuring a network with bonding+vlan and setting the MTU,
  occasionally the MTU doesn't get set properly on the vlan interface.

  In addition if one checks /var/log/upstart/networking.log whenever there is a 
failure the following message is printed:
  SIOCSIFMTU: Numerical result out of range

  I've tested the latest ifupdown package (0.7.44) and the problem still exists.
  Multi/single CPU settings both exhibit the issue.

  * Versions
  This affects latest ifupdown and ubuntu p/q/r/s.

  * Test Case

  # Create a p/q/r/s server vm with two network interfaces
  # This is reproducible on real hardware as well

  # Install the following
  sudo apt-get install vlan ifenslave-2.6 bridge-utils
  sudo modprobe bonding 8021q

  # Edit the interfaces file
  /etc/networking/interfaces:

  auto bond0
  iface bond0 inet manual
bond-mode 802.3ad
bond-miimon 100
bond-lacp-rate 1
bond-slaves eth0 eth1
post-up ifconfig bond0 mtu 9000

  auto eth0
  iface eth0 inet manual
bond-master bond0
post-up ifconfig eth0 mtu 9000

  auto eth1
  iface eth1 inet manual
bond-master bond0
post-up ifconfig eth1 mtu 9000

  auto bond0.123
  iface bond0.123 inet static
address 192.168.122.68
netmask 255.255.255.0
gateway 192.168.122.1
post-up ifconfig bond0.123 mtu 9000

  # edit rc.local (or another startup script) so we reboot until we hit the 
error
  /etc/rc.local:

  DEVS="eth0 eth1 bond0 bond0.123"
  for d in $DEVS; do
  mtu=$(cat /sys/class/net/$d/mtu)
  if [ $mtu != 9000 ]; then
  echo "FAIL"
  exit 1
  fi
  done

  reboot
  exit 0

  # Now reboot the machine, within 10m or so you should be at the login prompt
  # if you ifconfig | grep MTU you will see some of our interfaces did not get 
  # the MTU properly set and the test failed.
  # Essentially we want to ensure that all MTU's (except lo) were set to 9000

  * Workaround

  Change the bond0.123 post-up command to:
post-up sleep 2 && ifconfig bond0.123 mtu 9000

  Now when rebooting the interfaces will all be brought up with the
  proper MTU.

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

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

[Touch-packages] [Bug 1576692] Re: fully support package installation in systemd

2016-09-12 Thread Dave Chiluk

@smoser

Did you commit your changes to the xenial cloud-init as well?  I'm not
sure where xenial images grab cloud init for themselves, but I assume
out of the xenial archives.  Am I missing something here?

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  In Progress
Status in init-system-helpers source package in Xenial:
  In Progress

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to have a way to fully support this in cloud-init.

  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out

  SRU INFORMATION
  ===
  FIX for init-system-helpers: 
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02

  REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
  and service, two very central pieces of packaging infrastructure.
  Errors in it will break installation/upgrades of packages or
  /etc/network/if-up.d/ hooks and the like. This changes the condition
  when systemd units get started without their dependencies, and the
  condition gets weakened. This means that behaviour in a booted system
  is unchanged, but during boot this could change the behaviour of if-
  up.d/ hooks (although they have never been defined well during boot
  anyway). However, I tested this change extensively in cloud images and
  desktop installations (particularly I recreated
  https://bugs.debian.org/777113 and confirmed that this approach also
  fixes it) and could not find any regression.

  TEST CASE (for both packages):
  Run
 lxc launch ubuntu-daily:x --config=user.user-data="$(printf 
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1

  This will install all three packages, but "systemctl status
  postgresql@9.5-main" will not be running.

  Now prepare a new image with the proposed cloud-init and init-system-
  helpers:

 lxc launch ubuntu-daily:x xprep
 lxc exec xprep bash
 # enable -proposed and dist-upgrade, then poweroff
 lxc publish xprep x-proposed

  Now run the initial lxc launch again, but against that new x-proposed
  image instead of the standard daily:

lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
  config\npackages: [postgresql, samba, postfix]")" x1

  You should now have "systemctl status postgresql@9.5-main" running.
  Directly after rebooting the instance, check that there are no hanging
  jobs (systemctl list-jobs), particularly networking.service, to ensure
  that https://bugs.debian.org/777113 did not come back.

  Also test interactively installing a package that ships a service,
  like "apache2", and verify that it starts properly after installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+subscriptions

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

[Touch-packages] [Bug 1622764] [NEW] package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в паке

2016-09-12 Thread Anton

Public bug reported:

Problem whith Kali Linux

ProblemType: Package
DistroRelease: Kali 2016.2
Package: console-setup-linux 1.108ubuntu15.2
Uname: Linux 4.6.7-rt11 x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Sep 13 00:57:58 2016
ErrorMessage: попытка перезаписать «/lib/systemd/system/console-setup.service», 
который уже имеется в пакете keyboard-configuration 1.108ubuntu15.2
InstallationDate: Installed on 2016-09-12 (0 days ago)
InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10kali1
 apt  1.2.14
SourcePackage: console-setup
Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
попытка перезаписать «/lib/systemd/system/console-setup.service», который уже 
имеется в пакете keyboard-configuration 1.108ubuntu15.2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package kali-rolling third-party-packages

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

Title:
  package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade:
  попытка перезаписать «/lib/systemd/system/console-setup.service»,
  который уже имеется в пакете keyboard-configuration 1.108ubuntu15.2

Status in console-setup package in Ubuntu:
  New

Bug description:
  Problem whith Kali Linux

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: console-setup-linux 1.108ubuntu15.2
  Uname: Linux 4.6.7-rt11 x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Sep 13 00:57:58 2016
  ErrorMessage: попытка перезаписать 
«/lib/systemd/system/console-setup.service», который уже имеется в пакете 
keyboard-configuration 1.108ubuntu15.2
  InstallationDate: Installed on 2016-09-12 (0 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10kali1
   apt  1.2.14
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
попытка перезаписать «/lib/systemd/system/console-setup.service», который уже 
имеется в пакете keyboard-configuration 1.108ubuntu15.2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1605657] Re: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

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

** Changed in: python3-defaults (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python3 3.5.1-3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  I delet python3.5 by wrong using sudo apt-get remove python3.5 and to
  fix that I logged in from terminal because I lost my desktop terminal
  and I reinstalled the ubuntu dektop

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul 22 14:48:23 2016
  DuplicateSignature:
   package:python3:3.5.1-3
   Removing python3 (3.5.1-3) ...
   /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: 
py3clean: not found
   dpkg: error processing package python3 (--remove):
subprocess installed pre-removal script returned error exit status 127
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2016-04-18 (94 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: Upgraded to xenial on 2016-06-01 (50 days ago)

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

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

[Touch-packages] [Bug 1621216] [NEW] [MIR] geoclue-2.0

Brian Murray (brian-murray) has assigned this bug to you for iio-sensor-proxy 
in Ubuntu:

libqt5positioning5 now recommends geoclue-2.0

+qtlocation-opensource-src (5.6.0-1) experimental; urgency=medium
+
+  [ Lisandro DamiÃ¡n Nicanor PÃ©rez Meyer ]
+  * New upstream release.
+- Bump Qt build dependencies.
+  * Make qtlocation5-examples depend on qml-module-qtpositioning.
+  * Make libqt5positioning5 recommend geoclue-2.0. It will connect to it by
+using dbus.

geoclue-2.0 was previously in main see the MIR for it in bug #1388294.

** Affects: geoclue-2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: iio-sensor-proxy (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Touch seeded packages (touch-packages)
 Status: Incomplete


** Tags: yakkety
-- 
[MIR] geoclue-2.0
https://bugs.launchpad.net/bugs/1621216
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is a bug assignee.

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

[Touch-packages] [Bug 1616548] Re: Cups causes LibreOffice unittests to loop in a sbuild

2016-09-12 Thread Björn Michaelsen

This also broke winff:

(21:06:31) elbrus: Sweet5hark: winff FTBFS and seems to time out on libreoffice 
generating pdf's
(21:06:34) elbrus: any idea?
(21:06:43) elbrus: 
https://launchpadlibrarian.net/283037524/buildlog_ubuntu-yakkety-amd64.winff_1.5.3-7_BUILDING.txt.gz
(21:07:10) ***elbrus was pointed to you at #ubuntu-motu by jbicha
(21:17:08) Sweet5hark: elbrus: thats likely 
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1616548 see 
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-yakkety-5.2=28031ef15ac104122180669727c9420bcd51c147
 show a likely workaround broken CUPS
(21:19:35) Sweet5hark: elbrus: thus you need to set SAL_DISABLE_CUPS=true in 
the env for cups not stalling LO in an sbuild
(21:20:57) elbrus: Sweet5hark: ok, but am I correct to say this is Ubuntu 
specific?
(21:21:13) elbrus: In Debian, the build was OK (in pbuilder)
(21:22:47) Sweet5hark: elbrus: yes, this is likely ubuntu specific. testbuilds 
up to libreoffice 5.2.0~rc4 were fine, then it broke, likely by a cups update.
(21:29:19) Sweet5hark: elbrus: you might help triaging if you downgrade cups 
and retry. Using LibreOffices own build as testcase is annoying due to the 
buildtime. but with winff you might have found a good smaller testcase for our 
CUPS guys ...
(21:30:16) Sweet5hark: elbrus: FWIW, "in Debian" is somewhat ambiguous, given 
the number of releases etc. it has. ;)
(21:32:17) elbrus: "in Debian" I mean in unstable... I just uploaded the 
package several days ago
(21:35:14) Sweet5hark: elbrus: FWIW, I couldnt repro that in a pbuilder, only 
in sbuild. I dont know exactly was the difference/root cause.
(21:37:59) elbrus: Sweet5hark: I don't have an sbuild setup...
(21:38:14) elbrus: I'll ask ginggs...
(21:38:20) elbrus: or try in my ppa
(21:38:26) elbrus: maybe that is smarter then
(21:39:36) jbicha: winff built for me in a yakkety sbuild last week
(21:40:00) elbrus: it fails in launchpad multiple times
(21:40:11) jbicha: yes I know
(21:40:27) jbicha: I test built locally and it worked, but not in the launchpad 
builders
(21:40:50) elbrus: jbicha: were you the one that also requested a retry?
(21:41:54) jbicha: last week I did yes
(21:42:22) ***elbrus noticed that the retry was fresher than his own retry
(21:43:07) elbrus: jbicha: you didn't try building it in a ppa did you?
(21:43:23) jbicha: no
(21:43:40) elbrus: well, I will try that tonight probably
(21:56:09) elbrus: jbicha: seems to reproduce in MY pbuilder env
(21:56:17) elbrus: it's hanging currently
(21:56:27) jbicha: good! ;)
(21:57:02) elbrus: trying again with the CUPS env var
(22:15:03) elbrus: Sweet5hark: with your fix, winff builds in my pbuilder 
env so seems like winff is a smaller testcase for the issue
(22:20:13) ricotz: elbrus, jbicha, it likely works if the host system has a 
running cups instance
(22:29:42) elbrus: Sweet5hark: thanks a lot, I now have a successful build in 
my PPA. Will upload to Ubuntu Yakkety shortly
(22:46:18) elbrus: winff is fixed: 
https://launchpad.net/ubuntu/+source/winff/1.5.3-7ubuntu1/+build/10742736

As per above, this is confirmed in cups (Confirmed) and worked around in
winff (Fix Commited).

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

** Changed in: winff (Ubuntu)
   Status: New => Fix Committed

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

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

Title:
  Cups causes LibreOffice unittests to loop in a sbuild

Status in cups package in Ubuntu:
  Confirmed
Status in sbuild package in Ubuntu:
  Incomplete
Status in winff package in Ubuntu:
  Fix Committed

Bug description:
  When building LibreOffice 1:5.2.0-0ubuntu1 on a xenial host with a
  yakkety sbuild, e.g. by:

  sbuild -A -d yakkety-amd64 (...).dsc

  this loops/busy hangs with unittests. This was working ok up to
  5.2.0~rc4 (=final), it is a regression by a LibreOffice dependency,
  most likely CUPS, which was updated.

  I tried to inject debug symbols by running with a: --chroot-setup-
  command and then run something along the lines of:

   apt install cups
   wget http://launchpadlibrarian.net/278966811/cups-dbgsym_2.2~rc1-4_amd64.ddeb
   wget 
http://launchpadlibrarian.net/278966816/libcups2-dbgsym_2.2~rc1-4_amd64.ddeb
   dpkg -i cups-dbgsym_2.2~rc1-4_amd64.ddeb
   dpkg -i libcups2-dbgsym_2.2~rc1-4_amd64.ddeb

  before starting the build proper, but I got only marginally better
  debug info. The hanging LibreOffice test processes usually have 2-4
  child processes. The parent and one of the childs are busy, while the
  rest idle.

  Here is a stacktrace of the busy child:

  Program received signal SIGPIPE, Broken pipe.
  0x2b0a80dd615f in fgetspent (stream=0x11) at fgetspent.c:43
  43in fgetspent.c
  (gdb) bt
  #0  0x2b0a80dd615f in fgetspent (stream=0x11) at

[Touch-packages] [Bug 1619285] Re: cc_growpart fails on yakkety

** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  cc_growpart fails on yakkety

Status in cloud-utils:
  Fix Committed
Status in cloud-utils package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  cc_growpart fails on ppc64el, with the following messages :

  Sep  1 12:06:58 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command 
['growpart', '--dry-run', '/dev/vda', '1'] with allowed return codes [0] 
(shell=False, capture=True)
  Sep  1 12:06:58 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command 
['growpart', '/dev/vda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  Sep  1 12:06:58 ubuntu [CLOUDINIT] util.py[WARNING]: Failed: growpart 
/dev/vda 1
  Sep  1 12:06:58 ubuntu [CLOUDINIT] util.py[DEBUG]: Failed: growpart /dev/vda 
1#012Traceback (most recent call last):#012  File 
"/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 109, in 
resize#012util.subp(["growpart", diskdev, partnum])#012  File 
"/usr/lib/python3/dist-packages/cloudinit/util.py", line 1832, in subp#012
cmd=args)#012cloudinit.util.ProcessExecutionError: Unexpected error while 
running command.#012Command: ['growpart', '/dev/vda', '1']#012Exit code: 
2#012Reason: -#012Stdout: 'FAILED: failed to resize\n'#012Stderr: "attempt to 
resize /dev/vda failed. sfdisk output below:\n| GPT PMBR size mismatch (4612095 
!= 41943039) will be corrected by w(rite).\n| Backup files:\n| PMBR 
(offset 0, size   512): 
/tmp/growpart.wr7bvu/orig.save-vda-0x.bak\n|   GPT Header (offset   
512, size   512): /tmp/growpart.wr7bvu/orig.save-vda-0x0200.bak\n|  GPT 
Entries (offset  1024, size 16384): 
/tmp/growpart.wr7bvu/orig.save-vda-0x0400.bak
 \n| \n| Disk /dev/vda: 20 GiB, 21474836480 bytes, 41943040 sectors\n| Units: 
sectors of 1 * 512 = 512 bytes\n| Sector size (logical/physical): 512 bytes / 
512 bytes\n| I/O size (minimum/optimal): 512 bytes / 512 bytes\n| Disklabel 
type: gpt\n| Disk identifier: 5AF0CCE2-DDF5-4419-B991-213EE1F1B873\n| \n| Old 
situation:\n| \n| Device Start End Sectors  Size Type\n| /dev/vda1  
18432 4612062 4593631  2.2G Linux filesystem\n| /dev/vda2   2048   18431   
163848M PowerPC PReP boot\n| \n| Partition table entries are not in disk 
order.\n| \n| >>> Script header accepted.\n| >>> Script header accepted.\n| >>> 
Script header accepted.\n| >>> Script header accepted.\n| >>> Script header 
accepted.\n| >>> Created a new GPT disklabel (GUID: 
5AF0CCE2-DDF5-4419-B991-213EE1F1B873).\n| Created a new partition 1 of type 
'Linux filesystem' and of size 20 GiB.\n| /dev/vda2: Created a new partition 2 
of type 'PowerPC PReP boot' and of size 8 MiB.\n| /dev/vda3: \n| New 
situation:\n| \n| Device
  Start  End  Sectors Size Type\n| /dev/vda1  18432 41943006 41924575  20G 
Linux filesystem\n| /dev/vda2   20481843116384   8M PowerPC PReP 
boot\n| \n| Partition table entries are not in disk order.\n| \n| The partition 
table has been altered.\n| Calling ioctl() to re-read partition table.\n| 
Re-reading the partition table failed.: Device or resource busy\n| The kernel 
still uses the old table. The new table will be used at the next reboot or 
after you run partprobe(8) or kpartx(8).\n* WARNING: Resize failed, 
attempting to revert **\n512+0 records in\n512+0 records out\n512 bytes 
copied, 0.000671621 s, 762 kB/s\n512+0 records in\n512+0 records out\n512 bytes 
copied, 0.00148717 s, 344 kB/s\n16384+0 records in\n16384+0 records out\n16384 
bytes (16 kB, 16 KiB) copied, 0.0370011 s, 443 kB/s\n* Appears to have gone 
OK \n"
  Sep  1 12:06:58 ubuntu [CLOUDINIT] util.py[DEBUG]: resize_devices took 0.729 
seconds

  Running this command once the system is booted up appears to give the
  same output :

  ubuntu@axino-test:~$ sudo growpart /dev/vda 1
  attempt to resize /dev/vda failed. sfdisk output below:
  | GPT PMBR size mismatch (4612095 != 41943039) will be corrected by w(rite).
  | Backup files:
  | PMBR (offset 0, size   512): 
/tmp/growpart.Je0SXE/orig.save-vda-0x.bak
  |   GPT Header (offset   512, size   512): 
/tmp/growpart.Je0SXE/orig.save-vda-0x0200.bak
  |  GPT Entries (offset  1024, size 16384): 
/tmp/growpart.Je0SXE/orig.save-vda-0x0400.bak
  |
  | Disk /dev/vda: 20 GiB, 21474836480 bytes, 41943040 sectors
  | Units: sectors of 1 * 512 = 512 bytes
  | Sector size (logical/physical): 512 bytes / 512 bytes
  | I/O size (minimum/optimal): 512 bytes / 512 bytes
  | Disklabel type: gpt
  | Disk identifier: 5AF0CCE2-DDF5-4419-B991-213EE1F1B873
  |
  | Old situation:
  |
  | Device Start End Sectors  Size Type
  | /dev/vda1  18432 4612062 4593631  2.2G Linux filesystem
  | /dev/vda2   2048   18431   163848M

Re: [Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Breno Leitão [2016-09-12 20:53 -]:
> Per previous comment, I understand that this bug is still not fixed,
> correct?

Yes, as it isn't even understood yet.

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in busybox source package in Yakkety:
  Fix Released
Status in debian-installer source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  Then it keeps hanged in this stage. We re-tested it by changing the
  file 73-usb-net-by-mac.rules in initrd, replacing "
  /etc/udev/rules.d/80-net-setup-link.rules" to  "/lib/udev/rules.d/80
  -net-setup-link.rules", since the former does not exist whereas the
  latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask Canonical's help in investigating this issue.
  Thanks,

  Guilherme

  
  SRU INFORMATION for systemd
  ===

  Test case:
   * Check what happens for uevents on devices which are not USB network 
interfaces:
 udevadm test /sys/devices/virtual/mem/null
 udevadm test /sys/class/net/lo

   With the current version these will run

PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  /lib/udev/rules.d/73-usb-net-by-mac.rules:6

   which is pointless. With the proposed version these should be gone.

   * Ensure that the rule still works as intended by connecting an USB
  network device that has a permanent MAC address (e. g. Android
  tethering uses a temporary MAC): You should get a MAC-based name like
  "enx12345678" for it. Now disconnect it again, disable ifnames with

  sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

  and reconnect the device. You should now get a kernel name like "usb0"
  for it.

  * Regression potential: Errors in the rule could break persistent
  naming - or its disabling - of USB network interfaces. Running the
  above test carefully is important to ensure this keeps

[Touch-packages] [Bug 1606078] Re: No sound with Ubuntu 16.04

2016-09-12 Thread Arne

Hi, please not that I managed to fix this error following next steps.
Please also note that this is something specific for the Intel HDA chip..

You need to edit this file /etc/modprobe.d/alsa-base.conf and then add a
line in its end. Use the following commands:

sudo gedit /etc/modprobe.d/alsa-base.conf

Now add the following line at its end:

options snd-hda-intel model=generic

Now reboot your computer. It should solve your problem.

Original link where I found this: http://askubuntu.com/questions/117842
/no-sound-from-speakers-but-headphones-work

I hope this can help some other people too!

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

Title:
  No sound with Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual
  laptop there was no sound from the speakers unless external speakers
  where hooked to the headphones socket. This applies to the Ubuntu
  Mate, Xubuntu and Lubuntu variants. This laptop was working fine for
  all previous releases up to 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 01:51:19 2016
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  Symptom_Jack: Line Out, Internal
  Symptom_Type: No sound at all
  Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: RKYWSF0B
  dmi.board.name: ROCKY
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: S1-M401E1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics

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

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

[Touch-packages] [Bug 1576692] Re: fully support package installation in systemd

2016-09-12 Thread Scott Moser

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Confirmed => In Progress

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  In Progress
Status in init-system-helpers source package in Xenial:
  In Progress

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to have a way to fully support this in cloud-init.

  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out

  SRU INFORMATION
  ===
  FIX for init-system-helpers: 
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02

  REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
  and service, two very central pieces of packaging infrastructure.
  Errors in it will break installation/upgrades of packages or
  /etc/network/if-up.d/ hooks and the like. This changes the condition
  when systemd units get started without their dependencies, and the
  condition gets weakened. This means that behaviour in a booted system
  is unchanged, but during boot this could change the behaviour of if-
  up.d/ hooks (although they have never been defined well during boot
  anyway). However, I tested this change extensively in cloud images and
  desktop installations (particularly I recreated
  https://bugs.debian.org/777113 and confirmed that this approach also
  fixes it) and could not find any regression.

  TEST CASE (for both packages):
  Run
 lxc launch ubuntu-daily:x --config=user.user-data="$(printf 
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1

  This will install all three packages, but "systemctl status
  postgresql@9.5-main" will not be running.

  Now prepare a new image with the proposed cloud-init and init-system-
  helpers:

 lxc launch ubuntu-daily:x xprep
 lxc exec xprep bash
 # enable -proposed and dist-upgrade, then poweroff
 lxc publish xprep x-proposed

  Now run the initial lxc launch again, but against that new x-proposed
  image instead of the standard daily:

lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
  config\npackages: [postgresql, samba, postfix]")" x1

  You should now have "systemctl status postgresql@9.5-main" running.
  Directly after rebooting the instance, check that there are no hanging
  jobs (systemctl list-jobs), particularly networking.service, to ensure
  that https://bugs.debian.org/777113 did not come back.

  Also test interactively installing a package that ships a service,
  like "apache2", and verify that it starts properly after installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+subscriptions

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

[Touch-packages] [Bug 1608465] Re: Unity8 does not respect app size limits

2016-09-12 Thread Lukáš Tinkl

** Branch unlinked: lp:~lukas-kde/unity8/edgeMaximize

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

Title:
  Unity8 does not respect app size limits

Status in Canonical System Image:
  In Progress
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Choose a non maximizable app, for example System Settings. There are
  two ways to bypass the restriction:

  - First way: Press Ctrl + Super + Left/Right/Up
  - Second way: Before the app finishes to load, press right mouse click or 
middle mouse click on the maximize button in the title bar

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

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

[Touch-packages] [Bug 1576692] Re: fully support package installation in systemd

2016-09-12 Thread Scott Moser

fixed in 0.7.8.

** Changed in: cloud-init
   Status: Confirmed => Fix Released

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  In Progress

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to have a way to fully support this in cloud-init.

  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out

  SRU INFORMATION
  ===
  FIX for init-system-helpers: 
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02

  REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
  and service, two very central pieces of packaging infrastructure.
  Errors in it will break installation/upgrades of packages or
  /etc/network/if-up.d/ hooks and the like. This changes the condition
  when systemd units get started without their dependencies, and the
  condition gets weakened. This means that behaviour in a booted system
  is unchanged, but during boot this could change the behaviour of if-
  up.d/ hooks (although they have never been defined well during boot
  anyway). However, I tested this change extensively in cloud images and
  desktop installations (particularly I recreated
  https://bugs.debian.org/777113 and confirmed that this approach also
  fixes it) and could not find any regression.

  TEST CASE (for both packages):
  Run
 lxc launch ubuntu-daily:x --config=user.user-data="$(printf 
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1

  This will install all three packages, but "systemctl status
  postgresql@9.5-main" will not be running.

  Now prepare a new image with the proposed cloud-init and init-system-
  helpers:

 lxc launch ubuntu-daily:x xprep
 lxc exec xprep bash
 # enable -proposed and dist-upgrade, then poweroff
 lxc publish xprep x-proposed

  Now run the initial lxc launch again, but against that new x-proposed
  image instead of the standard daily:

lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
  config\npackages: [postgresql, samba, postfix]")" x1

  You should now have "systemctl status postgresql@9.5-main" running.
  Directly after rebooting the instance, check that there are no hanging
  jobs (systemctl list-jobs), particularly networking.service, to ensure
  that https://bugs.debian.org/777113 did not come back.

  Also test interactively installing a package that ships a service,
  like "apache2", and verify that it starts properly after installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+subscriptions

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

[Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

2016-09-12 Thread Breno Leitão

Martin,

Per previous comment, I understand that this bug is still not fixed,
correct?

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in busybox source package in Yakkety:
  Fix Released
Status in debian-installer source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  Then it keeps hanged in this stage. We re-tested it by changing the
  file 73-usb-net-by-mac.rules in initrd, replacing "
  /etc/udev/rules.d/80-net-setup-link.rules" to  "/lib/udev/rules.d/80
  -net-setup-link.rules", since the former does not exist whereas the
  latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask Canonical's help in investigating this issue.
  Thanks,

  Guilherme

  
  SRU INFORMATION for systemd
  ===

  Test case:
   * Check what happens for uevents on devices which are not USB network 
interfaces:
 udevadm test /sys/devices/virtual/mem/null
 udevadm test /sys/class/net/lo

   With the current version these will run

PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  /lib/udev/rules.d/73-usb-net-by-mac.rules:6

   which is pointless. With the proposed version these should be gone.

   * Ensure that the rule still works as intended by connecting an USB
  network device that has a permanent MAC address (e. g. Android
  tethering uses a temporary MAC): You should get a MAC-based name like
  "enx12345678" for it. Now disconnect it again, disable ifnames with

  sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

  and reconnect the device. You should now get a kernel name like "usb0"
  for it.

  * Regression potential: Errors in the rule could break persistent
  naming - or its disabling - of USB network interfaces. Running the
  above test carefully is important to ensure this keeps working. This
  has little to no actual effect on anything else on the

[Touch-packages] [Bug 1621243] Re: [MIR] mesa-demos

2016-09-12 Thread Timo Aaltonen

mesa-utils is the binary package (glxdemo, glxinfo, glxheads, glxgears),
mesa-demos is source. -utils takes 115kB on disk

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is a bug assignee.
https://bugs.launchpad.net/bugs/1621243

Title:
  [MIR] mesa-demos

Status in mesa-demos package in Ubuntu:
  Incomplete

Bug description:
  libqt5gui5 now (as of version 5.6.1+dfsg-3) recommends mesa-utils
  which is provided by mesa-demos.

  
  apt-cache show libqt5gui5
  Package: libqt5gui5
  Priority: optional
  Section: libs
  Installed-Size: 9369
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Qt/KDE Maintainers 

  Architecture: amd64
  Source: qtbase-opensource-src
  Version: 5.6.1+dfsg-3ubuntu3~3
  Replaces: libqt5egldeviceintegration5 (<< 5.6.0~beta+dfsg-5~), libqt5xcbqpa5 
(<< 5.6.0~beta+dfsg-5~)
  Depends: fontconfig, libc6 (>= 2.14), libdrm2 (>= 2.4.25), libegl1-mesa (>= 
7.8.1) | libegl1-x11, libfontconfig1 (>= 2.11.94), libfreetype6 (>= 2.3.5), 
libgbm1 (>= 8.1~0), libgcc1 (>= 1:3.4), libgl1-mesa-glx | libgl1, libglib2.0-0 
(>= 2.12.0), libharfbuzz0b (>= 0.9.11), libice6 (>= 1:1.0.0), libinput10 (>= 
0.15.0), libjpeg8 (>= 8c), libmtdev1 (>= 1.0.8), libpng16-16 (>= 1.6.2-1), 
libqt5core5a (>= 5.6.1), libqt5dbus5 (>= 5.0.2), libqt5network5 (>= 5.0.2), 
libsm6, libstdc++6 (>= 5), libudev1 (>= 183), libx11-6, libx11-xcb1, 
libxcb-glx0, libxcb-icccm4 (>= 0.4.1), libxcb-image0 (>= 0.2.1), 
libxcb-keysyms1 (>= 0.4.0), libxcb-randr0 (>= 1.3), libxcb-render-util0, 
libxcb-render0, libxcb-shape0, libxcb-shm0, libxcb-sync1, libxcb-xfixes0, 
libxcb-xinerama0, libxcb-xkb1, libxcb1 (>= 1.8), libxi6 (>= 2:1.5.99.2), 
libxkbcommon-x11-0 (>= 0.5.0), libxkbcommon0 (>= 0.5.0), libxrender1, 
qtbase-abi-5-6-1, zlib1g (>= 1:1.1.4)
  Recommends: libqt5svg5, mesa-utils

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

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

[Touch-packages] [Bug 1611859] Re: Keyboard layout isn't applied within wizard or in dash after wizard

2016-09-12 Thread Michał Sawicz

** Changed in: canonical-devices-system-image
   Status: Triaged => In Progress

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

Title:
  Keyboard layout isn't applied within wizard or in dash after wizard

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  In https://requests.ci-train.ubuntu.com/#/ticket/1771

  Steps:
  * connect a BT or a physical keyboard
  * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot
  * go through the wizard

  Expected:
  * I can use the selected layout within the wizard
  * and in the dash after completing the wizard

  Current:
  * layout is only applied on first app focus change

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160810.2-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-001]
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 10 19:04:24 2016
  InstallationDate: Installed on 2016-05-06 (95 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620356] Re: 12.0.2 released with lot of fixes

2016-09-12 Thread Timo Aaltonen

it will come in 16.04.2 with lts-yakkety stack

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

Title:
  12.0.2 released with lot of fixes

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 12.0.2 brings many stability improvements to the Mesa 12.0
  release

  Mesa 12.0.2 takes care of addressing crashes in GLX, EGL, and Wayland
  EGL. There are also numerous memory leak fixes for video decoding
  drivers.

  https://lists.freedesktop.org/archives/mesa-
  dev/2016-September/127937.html

  This is hardly requested to get it pushed to the archives asap.

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

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

[Touch-packages] [Bug 1622742] [NEW] ActivityIndicator broken, likely due to Qt 5.6 update

2016-09-12 Thread Michał Sawicz

Public bug reported:

QML ActivityIndicator: file:///usr/lib/x86_64-linux-
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
Invalid property assignment: "implicitHeight" is a read-only property

The indicator isn't displayed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: qml-module-ubuntu-components 
1.3.2073+16.04.20160824build1~~xenialoverlay1~1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 12 22:31:21 2016
InstallationDate: Installed on 2016-05-06 (128 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: ubuntu-ui-toolkit
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  ActivityIndicator broken, likely due to Qt 5.6 update

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

Bug description:
  QML ActivityIndicator: file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

  The indicator isn't displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 
1.3.2073+16.04.20160824build1~~xenialoverlay1~1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 12 22:31:21 2016
  InstallationDate: Installed on 2016-05-06 (128 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1622394] Re: vlc playback flicker and has delays

2016-09-12 Thread Timo Aaltonen

get rid of your /etc/X11/xorg.conf and it should be fine, there's no
fglrx anymore

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

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

Title:
  vlc playback flicker and has delays

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  ubuntu 16.04 LTS 
  Intel® Core™2 CPU 6420 @ 2.13GHz × 2 
  Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep 11 22:19:56 2016
  DistUpgraded: 2016-09-11 12:24:34,299 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cedar [Radeon HD 
5000/6000/7350/8350 Series] [174b:e164]
  InstallationDate: Installed on 2012-12-11 (1370 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=150153c9-a663-4cf4-b335-3e170c2f4845 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-09-11 (0 days ago)
  dmi.bios.date: 07/03/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd07/03/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Sep 11 21:01:07 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft Wireless Optical Desktop® 2.10 KEYBOARD, id 
8
   inputMicrosoft Microsoft Wireless Optical Desktop® 2.10 KEYBOARD, id 
9
   input2.4G wireless Mouse  MOUSE, id 10
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1598300] Re: cups hang after a while

This seems to be a some kind of desktop/laptop power/resource saving
feature that does not take Web UI to the account. CUPS will immediately
start up again if I open the printing dialog or something.

When I read Stephan's error log as well as my own, it reads:

"I [30/Aug/2016:08:42:33 +0200] Printer sharing is off and there are no jobs 
pending, will restart on demand.
I [30/Aug/2016:08:42:33 +0200] Scheduler shutting down normally."

Maybe some kind of xinetd setup would make it possible to shut CUPS down
but start it up when one tries to access the web UI.

Please do not expire this bug, that is not a solution. and Stephan has
provided the requested error log. WONTFIX would be a better solution if
this is the way it is intended to work.

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

Title:
  cups hang after a while

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

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

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

[Touch-packages] [Bug 1622739] [NEW] /bin/bash:11:internal_free:_rl_free_match_list:rl_complete_internal:_rl_dispatch_subseq:_rl_dispatch

2016-09-12 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding bash.  This problem was most recently seen with version
4.3-14ubuntu1.1, the problem page at
https://errors.ubuntu.com/problem/2529a4ca1a68be7bfe59db334f3064a391a2f5f2
contains more details.

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


** Tags: wily xenial

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

Title:
  
/bin/bash:11:internal_free:_rl_free_match_list:rl_complete_internal:_rl_dispatch_subseq:_rl_dispatch

Status in bash package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding bash.  This problem was most recently seen with version
  4.3-14ubuntu1.1, the problem page at
  https://errors.ubuntu.com/problem/2529a4ca1a68be7bfe59db334f3064a391a2f5f2
  contains more details.

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

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

[Touch-packages] [Bug 1622707] Re: CUPS Web UI stops responding after a while

Sorry for this comment flood.

Now I think I have finally solved it out:

If I run cupsd -l in console, it just quits with exit status 0 after a
while. If I run it as a service, it exits but goes back on-line
immediately after I do something that needs printing service.

It almost looks like there is some kind of resource-saving feature here
that does not take the Web UI into account.

This seems to be a duplicate of #1598300
(https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300).

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

Title:
  CUPS Web UI stops responding after a while

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS Web administration UI available at localhost:631 stops responding
  after a while. Initially it works fine, but after it has been running
  for a moment it just shows the "Connection refused" message of the
  browser. The printing system keeps running otherwise. This is a clean
  install of Ubuntu. I have installed Seafile from PPA but I don't think
  it has anything to do with this.

  I am unable to find anything relevant from journalctl nor CUPS logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Mon Sep 12 21:10:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6320
  Papersize: a4
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=0b75be02-897e-4a0b-9ff6-441512bb7493 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 05VMY6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn05VMY6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1622730] [NEW] No sound on headphones after suspend

2016-09-12 Thread Karl Kastner

Public bug reported:

This seems to be a common problem on XMG Clevo W230SS there is no output
on the headphone jack after suspend. The headphones are detected and the
speakers are muted, but there is no output to the headphones. Init-
headphones does not help:

sudo init-headphone 
WARNING:root:Kernel parameter is missing: acpi_enforce_resources=lax
WARNING:root:Module is not loaded: i2c_dev
ERROR:root:Can't find i2c bus
ERROR:root:Operation failed

Any workaround beside reboot?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1:  pia   23276 F pulseaudio
 /dev/snd/controlC0:  pia   23276 F pulseaudio
CurrentDesktop: GNOME-Classic:GNOME
Date: Mon Sep 12 21:56:08 2016
InstallationDate: Installed on 2015-11-05 (312 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-02-15T00:43:38.504815

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  No sound on headphones after suspend

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This seems to be a common problem on XMG Clevo W230SS there is no
  output on the headphone jack after suspend. The headphones are
  detected and the speakers are muted, but there is no output to the
  headphones. Init-headphones does not help:

  sudo init-headphone 
  WARNING:root:Kernel parameter is missing: acpi_enforce_resources=lax
  WARNING:root:Module is not loaded: i2c_dev
  ERROR:root:Can't find i2c bus
  ERROR:root:Operation failed

  Any workaround beside reboot?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  pia   23276 F pulseaudio
   /dev/snd/controlC0:  pia   23276 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Mon Sep 12 21:56:08 2016
  InstallationDate: Installed on 2015-11-05 (312 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-02-15T00:43:38.504815

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

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

[Touch-packages] [Bug 1622707] Re: CUPS Web UI stops responding after a while

It does not seem to affect lighttpd.

Journalctl did output following when it happened last time:

syys 12 22:03:41 sipuli dhclient[3111]: PRC: Renewing lease on wlp2s0b1.
syys 12 22:03:41 sipuli dhclient[3111]: XMT: Renew on wlp2s0b1, interval 9430ms.
syys 12 22:03:41 sipuli dhclient[3111]: RCV: Reply message on wlp2s0b1 from 
fe80::924e:2bff:fe5b:9c6e.
syys 12 22:03:41 sipuli NetworkManager[2495]:   [1473707021.3234]   
valid_lft 7200
syys 12 22:03:41 sipuli NetworkManager[2495]:   [1473707021.3235]   
preferred_lft 3600
syys 12 22:03:41 sipuli NetworkManager[2495]:   [1473707021.3236]   
address 2001:14bb:170:83bf::6
syys 12 22:03:41 sipuli NetworkManager[2495]:   [1473707021.3236]   
nameserver 'fe80::924e:2bff:fe5b:9c6e'
syys 12 22:03:41 sipuli NetworkManager[2495]:   [1473707021.3237] dhcp6 
(wlp2s0b1): state changed bound -> boun
syys 12 22:03:41 sipuli dbus[2491]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' uni
syys 12 22:03:41 sipuli systemd[1]: Starting Network Manager Script Dispatcher 
Service...
syys 12 22:03:41 sipuli dbus[2491]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
syys 12 22:03:41 sipuli systemd[1]: Started Network Manager Script Dispatcher 
Service.
syys 12 22:03:41 sipuli nm-dispatcher[23149]: req:1 'dhcp6-change' [wlp2s0b1]: 
new request (1 scripts)
syys 12 22:03:41 sipuli nm-dispatcher[23149]: req:1 'dhcp6-change' [wlp2s0b1]: 
start running ordered scripts...
syys 12 22:17:01 sipuli CRON[23324]: pam_unix(cron:session): session opened for 
user root by (uid=0)
syys 12 22:17:01 sipuli CRON[23325]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
syys 12 22:17:01 sipuli CRON[23324]: pam_unix(cron:session): session closed for 
user root
syys 12 22:17:33 sipuli unix_chkpwd[2]: password check failed for user (il)
syys 12 22:17:33 sipuli compiz[3410]: pam_unix(unity:auth): authentication 
failure; logname= uid=1000 euid=1000 tty= 
syys 12 22:17:39 sipuli compiz[3410]: pam_ecryptfs: seteuid error
syys 12 22:17:39 sipuli compiz[3410]: gkr-pam: unlocked login keyring
syys 12 22:18:59 sipuli systemd[1]: Started CUPS Scheduler.
syys 12 22:19:12 sipuli dbus[2491]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='d
syys 12 22:19:12 sipuli systemd[1]: Starting Hostname Service...
syys 12 22:19:13 sipuli dbus[2491]: [system] Successfully activated service 
'org.freedesktop.hostname1'
syys 12 22:19:13 sipuli systemd[1]: Started Hostname Service.

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

Title:
  CUPS Web UI stops responding after a while

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS Web administration UI available at localhost:631 stops responding
  after a while. Initially it works fine, but after it has been running
  for a moment it just shows the "Connection refused" message of the
  browser. The printing system keeps running otherwise. This is a clean
  install of Ubuntu. I have installed Seafile from PPA but I don't think
  it has anything to do with this.

  I am unable to find anything relevant from journalctl nor CUPS logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Mon Sep 12 21:10:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6320
  Papersize: a4
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=0b75be02-897e-4a0b-9ff6-441512bb7493 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 05VMY6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn05VMY6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1622717] Re: "Quit" from quicklist doesn’t close all open windows, doesn’t actually quit the application

2016-09-12 Thread Olivier Tilloy

Here is the actual QML code contained in the example click package:

import QtQuick 2.4
import QtQuick.Window 2.2
QtObject {
  readonly property var allWindows: []
  property var windowFactory: Component {
Window {
  onClosing: destroy()
  Component.onCompleted: allWindows.push(this)
  Component.onDestruction: {
for (var w in allWindows) {
  if (this === allWindows[w]) {
allWindows.splice(w, 1)
return
  }
}
  }
  Rectangle {
anchors {
  fill: parent
  margins: 20
}
color: Qt.rgba(Math.random(), Math.random(), Math.random(), 1)
  }
  MouseArea {
anchors.fill: parent
onClicked: windowFactory.createObject(null).show()
  }
}
  }
  property var applicationMonitor: Connections {
target: Qt.application
onAboutToQuit: console.log("quitting application, %1 windows 
open".arg(allWindows.length))
  }
  Component.onCompleted: windowFactory.createObject(null).show()
}

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

Title:
  "Quit" from quicklist doesn’t close all open windows, doesn’t actually
  quit the application

Status in unity8 package in Ubuntu:
  New

Bug description:
  I’m attaching a sample click application that contains a simple qml
  scene that opens several windows. This can be installed on a device
  with:

pkcon install-local --allow-untrusted fubar.osomon_0.4_all.click

  Initially, only one window is open, and tapping on any window opens
  one more window.

  If I reveal the launcher and long press on the app’s icon to select
  the "Quit" option, not all windows are closed:

   - if there is only one window open, it’s closed and the application 
successfully exits
   - if there are two windows open, only the second window is closed, the first 
one remains open (and consequently the application is still running)
   - if there are three windows open, only the first and third one are closed, 
the second one remains…

  Expected behaviour: when "Quit" is tapped, all open windows are
  closed, and the application exits.

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

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

[Touch-packages] [Bug 1622717] [NEW] "Quit" from quicklist doesn’t close all open windows, doesn’t actually quit the application

2016-09-12 Thread Olivier Tilloy

Public bug reported:

I’m attaching a sample click application that contains a simple qml
scene that opens several windows. This can be installed on a device
with:

  pkcon install-local --allow-untrusted fubar.osomon_0.4_all.click

Initially, only one window is open, and tapping on any window opens one
more window.

If I reveal the launcher and long press on the app’s icon to select the
"Quit" option, not all windows are closed:

 - if there is only one window open, it’s closed and the application 
successfully exits
 - if there are two windows open, only the second window is closed, the first 
one remains open (and consequently the application is still running)
 - if there are three windows open, only the first and third one are closed, 
the second one remains…

Expected behaviour: when "Quit" is tapped, all open windows are closed,
and the application exits.

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

** Attachment added: "fubar.osomon_0.4_all.click"
   
https://bugs.launchpad.net/bugs/1622717/+attachment/4739456/+files/fubar.osomon_0.4_all.click

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

Title:
  "Quit" from quicklist doesn’t close all open windows, doesn’t actually
  quit the application

Status in unity8 package in Ubuntu:
  New

Bug description:
  I’m attaching a sample click application that contains a simple qml
  scene that opens several windows. This can be installed on a device
  with:

pkcon install-local --allow-untrusted fubar.osomon_0.4_all.click

  Initially, only one window is open, and tapping on any window opens
  one more window.

  If I reveal the launcher and long press on the app’s icon to select
  the "Quit" option, not all windows are closed:

   - if there is only one window open, it’s closed and the application 
successfully exits
   - if there are two windows open, only the second window is closed, the first 
one remains open (and consequently the application is still running)
   - if there are three windows open, only the first and third one are closed, 
the second one remains…

  Expected behaviour: when "Quit" is tapped, all open windows are
  closed, and the application exits.

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

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

[Touch-packages] [Bug 1619033] Re: System is freezing

2016-09-12 Thread Rodrigo

I report that before I even start the kernel changes as recommended, I
removed my wireless PCI card, to test the system and analyze it could be
the reason for the problem.

It resulted that:
After the removal of Wireless PCI D-Link DWA-520, the system worked perfectly 
with no crashes, then being proven cause of the problem.

What puzzles me is that the system itself has identified the hardware
and installed the correct driver. It should work without crashing!

I tried to install a USB Adapter TP-Link Archer T2U, the system did not
recognize, and also I could not install and put into operation, to
replace the D-link.

Thank you

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

Title:
  System is freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The system freezing constantly!!!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 31 17:11:49 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
   nvidia-367, 367.44, 4.4.0-36-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GM107 [GeForce GTX 750 Ti] 
[19da:288a]
  InstallationDate: Installed on 2016-08-30 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=fdc6e4e3-4350-40d0-8787-fb0bc15f9f4b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2601:bd03/24/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 31 16:51:24 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about

[Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

2016-09-12 Thread Michał Sawicz

@larryprice the black Scopes and blank Settings are splash screens,
basically means the app never rendered.

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

2016-09-12 Thread Larry Price

The System Settings log could actually contain some interesting
information. It seems to imply that the launcher is out of memory.

** Attachment added: "System Settings log"
   
https://bugs.launchpad.net/qtmir/+bug/1620934/+attachment/4739455/+files/application-legacy-ubuntu-system-settings-.log

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

2016-09-12 Thread Larry Price

In my case, the Dash shows up as just a black screen with the Dash icon
and "Scopes" and never finishes loading. When opening up System
Settings, it sits on a white screen with just the titlebar. When opening
up the web browser, I got a crash and a weird update notifier log
(attached) in addition to this message in the regular application-
legacy-webbrowser-app-log:

Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
could not open containers config file  
"/home/lrp/.local/share/libertine/ContainersConfig.json"
[0912/145919:ERROR:gl_surface_egl.cc(253)] No suitable EGL configs found.

** Attachment added: "Weird update error when launching webbrowser from yakkety 
unity8"
   
https://bugs.launchpad.net/qtmir/+bug/1620934/+attachment/4739454/+files/update-notifier-crash-_var_crash__usr_bin_webbrowser-app.1000.crash.log

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

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

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

[Touch-packages] [Bug 1120319] Re: Ubuntu Online Accounts should support Exchange and Kerberos accounts

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

** Changed in: gnome-control-center-signon (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu Online Accounts should support Exchange and Kerberos accounts

Status in gnome-control-center-signon package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu in GNOME Online Account absent Exchange and Kerberos accounts
  But they are present in Fedora 18

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

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

[Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

I ran the test case for systemd on a 16.04.1 desktop live system with an
USB ethernet device. I confirm that naming still works as intended, MAC
naming can be disabled with the /dev/null symlink, and the readlink
calls are gone.

(Again, note that this was merely the side issue, not the main boot
problem here.)

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

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in busybox source package in Yakkety:
  Fix Released
Status in debian-installer source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  Then it keeps hanged in this stage. We re-tested it by changing the
  file 73-usb-net-by-mac.rules in initrd, replacing "
  /etc/udev/rules.d/80-net-setup-link.rules" to  "/lib/udev/rules.d/80
  -net-setup-link.rules", since the former does not exist whereas the
  latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask Canonical's help in investigating this issue.
  Thanks,

  Guilherme

  
  SRU INFORMATION for systemd
  ===

  Test case:
   * Check what happens for uevents on devices which are not USB network 
interfaces:
 udevadm test /sys/devices/virtual/mem/null
 udevadm test /sys/class/net/lo

   With the current version these will run

PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  /lib/udev/rules.d/73-usb-net-by-mac.rules:6

   which is pointless. With the proposed version these should be gone.

   * Ensure that the rule still works as intended by connecting an USB
  network device that has a permanent MAC address (e. g. Android
  tethering uses a temporary MAC): You should get a MAC-based name like
  "enx12345678" for it. Now disconnect it again, disable ifnames with

  sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

  and reconnect the device. You should now get a kernel

[Touch-packages] [Bug 1622707] Re: CUPS Web UI stops responding after a while

It seems to start responding again if I restart the CUPS service but it
seems to clear out after a while anyway. Now I proceed to test if it is
CUPS or the networking of the operating system by installing lighttpd
and trying if it has the same problem.

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

Title:
  CUPS Web UI stops responding after a while

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS Web administration UI available at localhost:631 stops responding
  after a while. Initially it works fine, but after it has been running
  for a moment it just shows the "Connection refused" message of the
  browser. The printing system keeps running otherwise. This is a clean
  install of Ubuntu. I have installed Seafile from PPA but I don't think
  it has anything to do with this.

  I am unable to find anything relevant from journalctl nor CUPS logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Mon Sep 12 21:10:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6320
  Papersize: a4
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=0b75be02-897e-4a0b-9ff6-441512bb7493 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 05VMY6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn05VMY6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1622575] Re: System hangs randomly (log shows 'EQ overflowing').

2016-09-12 Thread Alexander

On Freedesktop website I've found that it's a symptom of another bug (but in 
was about different graphics driver):
https://nouveau.freedesktop.org/wiki/TroubleShooting/#index5h3
In addition: this problem I have had only in Unity, in Gnome it works without 
freezing.

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

Title:
  System hangs randomly (log shows 'EQ overflowing').

Status in xorg package in Ubuntu:
  New

Bug description:
  X Server and then system freezes, ALT+CTRL+Fx doesn't work, sometimes even 
REISUB doesn't work.
  Memtest result is ok, no errors. HDD also is ok. Windows works perfectly on 
the machine.
  It's possible to login via SSH and reboot (but during reboot process it also 
often hangs completely).
  The problem occures randomly during every-day work (usually once or twice a 
day making me loose my work!), like with totally no adequate reasons.
  I'm using AMD Athlon 5350 (SocketAM1 APU) with radeon R3 integrated video.
  My operating system is Ubuntu 16.04.1 LTS with all the last available 
updates. Bug lasts throughout all the time. Tried to reinstall many times 
(MD5sum of the installation image was correct) - nothing changes.

  x-0.log in the attachment

  part of the log:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x562fc426a5ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x562fc424c083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x562fc4124662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f7320d91000+0x61f3) 
[0x7f7320d971f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f7320d91000+0x6a5d) 
[0x7f7320d97a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x562fc40b8000+0x94228) [0x562fc414c228]
  (EE) 6: /usr/lib/xorg/Xorg (0x562fc40b8000+0xb96f2) [0x562fc41716f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f732524e000+0x354a0) 
[0x7f73252834a0]
  (EE) 8: /lib/x86_64-linux-gnu/libpthread.so.0 (pthread_cond_wait+0xbe) 
[0x7f732503e39e]
  (EE) 9: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x6b77fb) [0x7f731f3027fb]
  (EE) 10: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x6b87c1) [0x7f731f3037c1]
  (EE) 11: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x61bf52) [0x7f731f266f52]
  (EE) 12: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x6d521e) [0x7f731f32021e]
  (EE) 13: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x201de4) [0x7f731ee4cde4]
  (EE) 14: /usr/lib/xorg/modules/libglamoregl.so (glamor_block_handler+0x4b) 
[0x7f73204bcffb]
  (EE) 15: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f732133c000+0x471b2) 
[0x7f73213831b2]
  (EE) 16: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) [0x562fc4111034]
  (EE) 17: /usr/lib/xorg/Xorg (WriteToClient+0x244) [0x562fc426e234]
  (EE) 18: /usr/lib/xorg/Xorg (WriteEventsToClient+0x1e2) [0x562fc4117022]
  (EE) 19: /usr/lib/xorg/Xorg (0x562fc40b8000+0x133b5f) [0x562fc41ebb5f]
  (EE) 20: /usr/lib/xorg/Xorg (DamageReportDamage+0x89) [0x562fc41f1359]
  (EE) 21: /usr/lib/xorg/Xorg (0x562fc40b8000+0x139c1a) [0x562fc41f1c1a]
  (EE) 22: /usr/lib/xorg/Xorg (0x562fc40b8000+0x13d140) [0x562fc41f5140]
  (EE) 23: /usr/lib/xorg/Xorg (0x562fc40b8000+0x4fb87) [0x562fc4107b87]
  (EE) 24: /usr/lib/xorg/Xorg (0x562fc40b8000+0x53bbf) [0x562fc410bbbf]
  (EE) 25: /usr/lib/xorg/Xorg (0x562fc40b8000+0x57c33) [0x562fc410fc33]
  (EE) 26: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f732526e830]
  (EE) 27: /usr/lib/xorg/Xorg (_start+0x29) [0x562fc40f9f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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
  Date: Mon Sep 12 14:31:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series] 
[1002:9830] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Kabini [Radeon HD 8400 
/ R3 Series]

[Touch-packages] [Bug 1613729] Re: NetworkManager autoconnects to wired profiles in reverse order

2016-09-12 Thread Brian Murray

>From what I can tell it looks like this patch is only needed for Trusty,
Ubuntu 14.04.  It'd be helpful if you could write a Test Case following
the procedure documented at http://wiki.ubuntu.com/StableReleaseUpdates
so that we know how to test the issue and fix.  Thanks!

** Also affects: network-manager (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Trusty)
   Importance: Undecided => High

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

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

Title:
  NetworkManager autoconnects to wired profiles in reverse order

Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager source package in Trusty:
  New

Bug description:
  When I select a wired profile manually and reboot, NetworkManager
  instead connects to the profile that has the oldest timestamp. So it's
  not connecting to the last used profile, which is troublesome.

  On all of our machines (about 500), we define three wired network
  profiles, one DHCP and two static. We're migrating from Debian to
  Ubuntu, so this bug has only surfaced now for us.

  This can be reproduced by creating a couple of network profiles on the
  same wired interface and then rebooting or restarting network-manager.
  It will loop through the network profiles in the same order always. So
  it's doing the exact reverse of what's supposed to happen.

  I did some digging and I applied a simple patch to the source code.
  This seems to have fixed the issue. I posted my patch for verification
  on the networkmanager mailing list and it was verified as being
  correct by Beniamino Galvani, one of the developers.

  Here is the link to the network-manager topic:
  https://mail.gnome.org/archives/networkmanager-
  list/2016-August/msg00053.html

  This is the patch (also included as attachment):

  --- nm-device.c 2016-08-16 15:37:50.0 +0200
  +++ nm-device_patched.c 2016-08-16 15:44:08.308729955 +0200
  @@ -1267,7 +1267,7 @@
  s_con = nm_connection_get_setting_connection (connection);
  g_assert (s_con);
  if (nm_setting_connection_get_autoconnect (s_con))
  -   available_conns = g_slist_prepend (available_conns, 
connection);
  +   available_conns = g_slist_append (available_conns, 
connection);
  }

  if (!available_conns)

  I hope to get this patch included in the trusty package, so somebody
  else can benefit from this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.3
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CRDA: Error: [Errno 2] Bestand of map bestaat niet: 'iw'
  CurrentDesktop: Unity
  Date: Tue Aug 16 15:23:17 2016
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.30.6.1 dev em1  proto static 
   10.30.6.0/24 dev em1  proto kernel  scope link  src 10.30.6.204  metric 1 
   10.40.8.0/21 dev tun0  proto kernel  scope link  src 10.40.8.31
  IwConfig:
   tun0  no wireless extensions.
   
   em1   no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=nl_BE:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   DHCP  702624f9-f052-473a-b131-acd2045e6ec2   
802-3-ethernet1471353746   di 16 aug 2016 15:22:26 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/1
   Proximus  7a9a5bc2-d51a-46b4-b721-050a607951bc   
802-3-ethernet1471353744   di 16 aug 2016 15:22:24 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   em1802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:

[Touch-packages] [Bug 1608953] Re: PostgreSQL does not start in lx-brand container

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

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

Title:
  PostgreSQL does not start in lx-brand container

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

Bug description:
  We have a 16.04 Ubuntu lx-brand container image available in our
  public cloud and recently discovered a systemd bug that's related to
  running in a container environment.

  I'm forwarded below what one of our engineers discovered:

  

  After installing postgres (apt-get install -y -q postgresql), systemd
  does not actually start any of the postgres services. We tracked this
  down to a failure from sed from within the /lib/systemd/system-
  generators/postgresql-generator script. The sed command tries to close
  stderr (fd 2) which fails, so sed returns an error code, which causes
  the entire postgres generator to fail.

  The root cause of the problem lies in the systemd code. Because we are
  running inside of a container (see detect_container) we don't execute
  the following block of code in the systemd main().

  if (getpid() == 1 && detect_container() <= 0) {

  /* Running outside of a container as PID 1 */
  arg_running_as = MANAGER_SYSTEM;
  make_null_stdio();

  The make_null_stdio function is what sets up fd 0-2 as /dev/null in
  systemd on bare metal. Having those fd's setup is what allows the
  postgres system-generator to work properly since sed expects to be
  able to close stderr.

  Because we never call make_null_stdio when inside any container, the
  low fd's wind up getting setup later using /dev/console with
  O_CLOEXEC, so when we actually run the system generator script, we
  don't have the low fd's setup at all like sed expects.

  Interestingly, looking at the master branch of systemd, at
  src/core/main.c this bug appears to no longer exist. The relevant code
  block has been moved so it is no longer conditional on being in a
  container, but the commit was not intended to fix this problem. It was
  apparently due to color handling on the console/

  commit 3a18b60489504056f9b0b1a139439cbfa60a87e1

  It would be great if this fix could be pulled in to an update for
  Ubuntu 16.04.

  SRU INFORMATION
  ===
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=6df46531727baa

  Regression potential: very low; this does not affect lxc and lxd (our
  officially supported container engines) nor nspawn, as they already
  set up pid1's stdout/stderr. And it's hard to imagine anything
  depending on pid1's stdout/err *not* being existant file descriptors,
  as in pretty much all cases they already are.

  Test case: Specific to lx-brand, must be verified by reporter.
  However, we need to verify that LXC, LXD, and nspawn containers still
  boot with this version.

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

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

[Touch-packages] [Bug 1617063] Re: from alternate lubuntu installs network manager does not manage devices or give network info

2016-09-12 Thread sudodus

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

> Actually it went away with the fix of the master bug of the networking
for beta 1.

That's great :-)

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

Title:
  from alternate lubuntu installs network manager does not manage
  devices or give network info

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  To reproduce on an alternate install complete the install with
  ethernet plugged in  and boot into the new install and log into to the
  lubuntu desktop and move over to the nm-applet and notice it says that
  your ethernet device is not managed and showing connectoin information
  fails

   Description: Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  network-manager:
Installed: 1.2.2-0ubuntu8
Candidate: 1.2.2-0ubuntu8
Version table:
   *** 1.2.2-0ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status
  I expected to be able to show connection info in network manager and connect 
disconnet to ethernet with this network manager with software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
  Uname: Linux 4.4.0-9134-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Aug 25 14:11:11 2016
  InstallationDate: Installed on 2016-08-25 (0 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160825.1)
  IpRoute:
   default via 192.168.122.1 dev ens3 
   192.168.122.0/24 dev ens3  proto kernel  scope link  src 192.168.122.84
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  ACTIVE-PATH 
   Wired connection 1  f8fb3e0c-4ddc-4d20-9585-954d34538369  802-3-ethernet  0  
never   yes  0 no
/org/freedesktop/NetworkManager/Settings/0  no  --  -- --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   ens3ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  none  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1590005] Re: activeFocusOnTab is ignored when Button is embedded inside ListItem in a horizontal ListView

2016-09-12 Thread Tim Peeters

The code in the bug description still does not work as it should. You
can focus one-beyond-the-last with keyboard navigation and the focus
goes inside the list item.

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

Title:
  activeFocusOnTab is ignored when Button is embedded inside ListItem in
  a horizontal ListView

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Run this code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(50)
  height: units.gu(50)

  ListView {
  anchors.fill: parent
  model: 10
  orientation: ListView.Horizontal
  delegate: ListItem {
  width: units.gu(5)
  height: units.gu(5)
  Button {
  activeFocusOnTab: false
  anchors {
  fill: parent
  margins: units.gu(1)
  }
  text: "Button #" + index
  }
  }
  }
  }

  Use TAB to select the first ListItem in the list. Pressing the LEFT
  arrow after that will put the focus on the Button in the first
  ListItem (you can see the focus outline changing).

  The same happens when using keyboard navigation to go to the last
  ListItem and then pressing the RIGHT cursor key.

  I could not reproduce the issue with a vertical ListView.

  This gives problems for the new Toolbar with scrolling icons inside
  it, because there I am wrapping an AbstractButton inside a ListItem in
  order to be able to get cursor key navigation until this bug is fixed:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
  toolkit/+bug/1573616

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

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

[Touch-packages] [Bug 1622709] [NEW] wrong app name "docker"

2016-09-12 Thread Stefan Helmert

Public bug reported:

This is a minor name bug. If I want to start the command "docker" in
bash and docker.io is not installed, It recommends to  install docker:
"sudo apt-get install docker" - This is not the right package name. The
docker command is associated with the "docker.io" package. So It has to
recommend "sudo apt-get install docker.io".

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.14
ProcVersionSignature: Ubuntu 3.16.0-76.98~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-76-generic x86_64
NonfreeKernelModules: openafs nvidia
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 12 20:22:18 2016
InstallationDate: Installed on 2016-01-21 (235 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  wrong app name "docker"

Status in apt package in Ubuntu:
  New

Bug description:
  This is a minor name bug. If I want to start the command "docker" in
  bash and docker.io is not installed, It recommends to  install docker:
  "sudo apt-get install docker" - This is not the right package name.
  The docker command is associated with the "docker.io" package. So It
  has to recommend "sudo apt-get install docker.io".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.14
  ProcVersionSignature: Ubuntu 3.16.0-76.98~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-76-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 12 20:22:18 2016
  InstallationDate: Installed on 2016-01-21 (235 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1610479] Re: interface-order needs definitions for systemd predictable names

2016-09-12 Thread Brian Murray

** Changed in: resolvconf (Ubuntu)
   Importance: Wishlist => High

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

Title:
  interface-order needs definitions for systemd predictable names

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  Another release, another round of interface name changes.

  This time systemd has gotten into the fray to make things even more
  interesting.

  
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

  As such, IPv4 resolvers are now being preferred over IPv6 again on
  these new interface names.

  kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.*
  /run/resolvconf/interface/ens3.dhclient:search nivex.lan.
  /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30
  /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net.
  /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10
  /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug  5 19:53:25 2016
  InstallationDate: Installed on 2016-08-04 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1617063] Re: from alternate lubuntu installs network manager does not manage devices or give network info

2016-09-12 Thread Brendan Perrine

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

On Mon, 12 Sep 2016 06:08:47 -
sudodus <1617...@bugs.launchpad.net> wrote:

> *** This bug is a duplicate of bug 1616400 ***
> https://bugs.launchpad.net/bugs/1616400
> 
> Hi Brendan,
> 
> Is this really a a duplicate of bug #1616400? I guess you can check, if
> the bug has been squashed. If it is still alive, it is a separate bug.
> 
> I suspect it is still alive, but you wrote the bug report, so please
> check if the bug you reported is still there.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1617063
> 
> Title:
>   from alternate lubuntu installs network manager does not manage
>   devices or give network info
> 
> Status in network-manager package in Ubuntu:
>   Confirmed
> 
> Bug description:
>   To reproduce on an alternate install complete the install with
>   ethernet plugged in  and boot into the new install and log into to the
>   lubuntu desktop and move over to the nm-applet and notice it says that
>   your ethernet device is not managed and showing connectoin information
>   fails
> 
>Description:   Ubuntu Yakkety Yak (development branch)
>   Release:16.10
>   network-manager:
> Installed: 1.2.2-0ubuntu8
> Candidate: 1.2.2-0ubuntu8
> Version table:
>*** 1.2.2-0ubuntu8 500
>   500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
>   100 /var/lib/dpkg/status
>   I expected to be able to show connection info in network manager and 
> connect disconnet to ethernet with this network manager with software.
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: network-manager 1.2.2-0ubuntu8
>   ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
>   Uname: Linux 4.4.0-9134-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: LXDE
>   Date: Thu Aug 25 14:11:11 2016
>   InstallationDate: Installed on 2016-08-25 (0 days ago)
>   InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160825.1)
>   IpRoute:
>default via 192.168.122.1 dev ens3 
>192.168.122.0/24 dev ens3  proto kernel  scope link  src 192.168.122.84
>   IwConfig:
>lono wireless extensions.
>I arrive at a red screen with the text: "No network interfaces were found 
> ..."


>ens3  no wireless extensions.
>   NetworkManager.conf:
>[main]
>plugins=ifupdown,keyfile,ofono
>
>[ifupdown]
>managed=false
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   RfKill:
>
>   SourcePackage: network-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   nmcli-con:
>NAMEUUID  TYPE
> TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
> DBUS-PATH   ACTIVE  DEVICE  STATE  
> ACTIVE-PATH 
>Wired connection 1  f8fb3e0c-4ddc-4d20-9585-954d34538369  802-3-ethernet  
> 0  never   yes  0 no
> /org/freedesktop/NetworkManager/Settings/0  no  --  -- --
>   nmcli-dev:
>DEVICE  TYPE  STATE  DBUS-PATH  
> CONNECTION  CON-UUID  CON-PATH 
>ens3ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  -- 
>  ----   
>lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
>  ----
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
> WIFI WWAN-HW  WWAN
>running  1.2.2connected  started  none  enabled enabled  
> enabled  enabled  enabled
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1617063/+subscriptions

Actually it went away with the fix of the master bug of the networking for beta 
1. 
-- 
Brendan Perrine 

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

Title:
  from alternate lubuntu installs network manager does not manage
  devices or give network info

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  To reproduce on an alternate install complete the install with
  ethernet plugged in  and boot into the new install and log into to the
  lubuntu desktop and move over to the nm-applet and notice it says that
  your ethernet device is not managed and showing connectoin information
  fails

   Description: Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  network-manager:
Installed: 1.2.2-0ubuntu8
Candidate: 1.2.2-0ubuntu8
Version table:
   *** 1.2.2-0ubuntu8 500

[Touch-packages] [Bug 1622707] [NEW] CUPS Web UI stops responding after a while

Public bug reported:

CUPS Web administration UI available at localhost:631 stops responding
after a while. Initially it works fine, but after it has been running
for a moment it just shows the "Connection refused" message of the
browser. The printing system keeps running otherwise. This is a clean
install of Ubuntu. I have installed Seafile from PPA but I don't think
it has anything to do with this.

I am unable to find anything relevant from journalctl nor CUPS logs.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 
CurrentDesktop: Unity
Date: Mon Sep 12 21:10:33 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-09-12 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Latitude E6320
Papersize: a4
ProcEnviron:
 LANGUAGE=fi
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=0b75be02-897e-4a0b-9ff6-441512bb7493 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 05VMY6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn05VMY6:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6320
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  CUPS Web UI stops responding after a while

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS Web administration UI available at localhost:631 stops responding
  after a while. Initially it works fine, but after it has been running
  for a moment it just shows the "Connection refused" message of the
  browser. The printing system keeps running otherwise. This is a clean
  install of Ubuntu. I have installed Seafile from PPA but I don't think
  it has anything to do with this.

  I am unable to find anything relevant from journalctl nor CUPS logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Mon Sep 12 21:10:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6320
  Papersize: a4
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=0b75be02-897e-4a0b-9ff6-441512bb7493 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 05VMY6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn05VMY6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-12 Thread Brian Murray

** Tags added: rls-y-incoming

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

Title:
  mtu not always set properly on bond/vlan interface

Status in ifupdown package in Ubuntu:
  Confirmed
Status in vlan package in Ubuntu:
  New
Status in ifupdown package in Debian:
  New

Bug description:
  * Description

  When configuring a network with bonding+vlan and setting the MTU,
  occasionally the MTU doesn't get set properly on the vlan interface.

  In addition if one checks /var/log/upstart/networking.log whenever there is a 
failure the following message is printed:
  SIOCSIFMTU: Numerical result out of range

  I've tested the latest ifupdown package (0.7.44) and the problem still exists.
  Multi/single CPU settings both exhibit the issue.

  * Versions
  This affects latest ifupdown and ubuntu p/q/r/s.

  * Test Case

  # Create a p/q/r/s server vm with two network interfaces
  # This is reproducible on real hardware as well

  # Install the following
  sudo apt-get install vlan ifenslave-2.6 bridge-utils
  sudo modprobe bonding 8021q

  # Edit the interfaces file
  /etc/networking/interfaces:

  auto bond0
  iface bond0 inet manual
bond-mode 802.3ad
bond-miimon 100
bond-lacp-rate 1
bond-slaves eth0 eth1
post-up ifconfig bond0 mtu 9000

  auto eth0
  iface eth0 inet manual
bond-master bond0
post-up ifconfig eth0 mtu 9000

  auto eth1
  iface eth1 inet manual
bond-master bond0
post-up ifconfig eth1 mtu 9000

  auto bond0.123
  iface bond0.123 inet static
address 192.168.122.68
netmask 255.255.255.0
gateway 192.168.122.1
post-up ifconfig bond0.123 mtu 9000

  # edit rc.local (or another startup script) so we reboot until we hit the 
error
  /etc/rc.local:

  DEVS="eth0 eth1 bond0 bond0.123"
  for d in $DEVS; do
  mtu=$(cat /sys/class/net/$d/mtu)
  if [ $mtu != 9000 ]; then
  echo "FAIL"
  exit 1
  fi
  done

  reboot
  exit 0

  # Now reboot the machine, within 10m or so you should be at the login prompt
  # if you ifconfig | grep MTU you will see some of our interfaces did not get 
  # the MTU properly set and the test failed.
  # Essentially we want to ensure that all MTU's (except lo) were set to 9000

  * Workaround

  Change the bond0.123 post-up command to:
post-up sleep 2 && ifconfig bond0.123 mtu 9000

  Now when rebooting the interfaces will all be brought up with the
  proper MTU.

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

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

[Touch-packages] [Bug 1622689] Re: Motorola HT820, playback No sound at all

2016-09-12 Thread aanno

dmesg:

Sep 12 17:43:00 unke bluetoothd[869]: Endpoint registered: sender=:1.48 
path=/MediaEndpoint/A2DPSource
Sep 12 17:43:00 unke bluetoothd[869]: Endpoint registered: sender=:1.48 
path=/MediaEndpoint/A2DPSink
Sep 12 17:43:00 unke bluetoothd[869]: Endpoint registered: sender=:1.48 
path=/MediaEndpoint/A2DPSource
Sep 12 17:43:00 unke bluetoothd[869]: Endpoint registered: sender=:1.48 
path=/MediaEndpoint/A2DPSink
Sep 12 17:43:00 unke pulseaudio[5094]: [pulseaudio] backend-ofono.c: Failed to 
register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
Sep 12 17:43:00 unke kernel: [  143.258228] Bluetooth: RFCOMM TTY layer 
initialized
Sep 12 17:43:00 unke kernel: [  143.258254] Bluetooth: RFCOMM socket layer 
initialized
Sep 12 17:43:00 unke kernel: [  143.258276] Bluetooth: RFCOMM ver 1.11

[...]

Sep 12 18:59:50 unke pulseaudio[5094]: [pulseaudio] module-bluez5-device.c: 
Default profile not connected, selecting off
 profile
Sep 12 18:59:52 unke bluetoothd[869]: 
/org/bluez/hci1/dev_00_07_A4_B5_F1_5E/fd0: fd(54) ready
Sep 12 18:59:52 unke rtkit-daemon[5095]: Supervising 4 threads of 1 processes 
of 1 users.
Sep 12 18:59:52 unke rtkit-daemon[5095]: Successfully made thread 9823 of 
process 5094 (n/a) owned by '1000' RT at prior
ity 5.
Sep 12 18:59:52 unke rtkit-daemon[5095]: Supervising 5 threads of 1 processes 
of 1 users.
Sep 12 18:59:52 unke pulseaudio[5094]: [pulseaudio] bluez5-util.c: Transport 
TryAcquire() failed for transport /org/blue
z/hci1/dev_00_07_A4_B5_F1_5E/fd0 (Operation Not Authorized)
Sep 12 18:59:52 unke kernel: [ 4754.448700] input: 00:07:A4:B5:F1:5E as 
/devices/virtual/input/input17
Sep 12 19:01:40 unke acpid: input device has been disconnected, fd 19
Sep 12 19:01:40 unke bluetoothd[869]: Unable to get io data for Headset Voice 
gateway: getpeername: Transport endpoint is not connected (107)
Sep 12 19:01:56 unke bluetoothd[869]: Unable to get Headset Voice gateway SDP 
record: Host is down
Sep 12 19:01:59 unke pulseaudio[5094]: [pulseaudio] module-bluez5-device.c: 
Default profile not connected, selecting off profile
Sep 12 19:02:01 unke bluetoothd[869]: 
/org/bluez/hci1/dev_00_07_A4_B5_F1_5E/fd1: fd(54) ready
Sep 12 19:02:01 unke rtkit-daemon[5095]: Supervising 4 threads of 1 processes 
of 1 users.
Sep 12 19:02:01 unke rtkit-daemon[5095]: Successfully made thread 9914 of 
process 5094 (n/a) owned by '1000' RT at priority 5.
Sep 12 19:02:01 unke rtkit-daemon[5095]: Supervising 5 threads of 1 processes 
of 1 users.
Sep 12 19:02:01 unke rtkit-daemon[5095]: Successfully made thread 9914 of 
process 5094 (n/a) owned by '1000' RT at priority 5.
Sep 12 19:02:01 unke rtkit-daemon[5095]: Supervising 5 threads of 1 processes 
of 1 users.
Sep 12 19:02:01 unke pulseaudio[5094]: [pulseaudio] bluez5-util.c: Transport 
TryAcquire() failed for transport /org/bluez/hci1/dev_00_07_A4_B5_F1_5E/fd1 
(Operation Not Authorized)
Sep 12 19:02:01 unke kernel: [ 4883.476061] input: 00:07:A4:B5:F1:5E as 
/devices/virtual/input/input18
Sep 12 19:02:30 unke bluetoothd[869]: a2dp-sink profile connect failed for 
00:07:A4:B5:F1:5E: Operation already in progress
Sep 12 19:03:27 unke acpid: input device has been disconnected, fd 19
Sep 12 19:05:19 unke whoopsie[821]: [19:05:19] Parsing 
/var/crash/_usr_bin_blueman-assistant.1000.crash.
Sep 12 19:05:19 unke whoopsie[821]: [19:05:19] Uploading 
/var/crash/_usr_bin_blueman-assistant.1000.crash.
Sep 12 19:05:20 unke whoopsie[821]: [19:05:20] Sent; server replied with: No 
error
Sep 12 19:05:20 unke whoopsie[821]: [19:05:20] Response code: 200
Sep 12 19:05:20 unke whoopsie[821]: [19:05:20] Reported OOPS ID 
15bcde7e-790b-11e6-b121-fa163e8d4bab
Sep 12 19:05:57 unke pulseaudio[5094]: [pulseaudio] module-bluez5-device.c: 
Default profile not connected, selecting off profile
Sep 12 19:05:58 unke bluetoothd[869]: 
/org/bluez/hci1/dev_00_07_A4_B5_F1_5E/fd2: fd(55) ready
Sep 12 19:05:58 unke rtkit-daemon[5095]: Supervising 4 threads of 1 processes 
of 1 users.
Sep 12 19:05:58 unke rtkit-daemon[5095]: Successfully made thread 10815 of 
process 5094 (n/a) owned by '1000' RT at priority 5.
Sep 12 19:05:58 unke rtkit-daemon[5095]: Supervising 5 threads of 1 processes 
of 1 users.
Sep 12 19:05:58 unke pulseaudio[5094]: [pulseaudio] bluez5-util.c: Transport 
TryAcquire() failed for transport /org/bluez/hci1/dev_00_07_A4_B5_F1_5E/fd2 
(Operation Not Authorized)
Sep 12 19:05:58 unke bluetoothd[869]: Control: Refusing unexpected connect
Sep 12 19:05:59 unke kernel: [ 5122.179002] input: 00:07:A4:B5:F1:5E as 
/devices/virtual/input/input19
Sep 12 19:06:26 unke acpid: input device has been disconnected, fd 19
Sep 12 19:06:30 unke pulseaudio[5094]: [pulseaudio] module-bluez5-device.c: 
Default profile not connected, selecting off profile
Sep 12 19:06:45 unke pulseaudio[5094]: [pulseaudio] module-bluez5-device.c: 
Default profile not connected, selecting off profile
Sep 12 19:06:49 unke

[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

tested on yakkety:

using isc-dhcp-client 4.3.3-5ubuntu13, bug exists; dhcpv6 prefix is set
to /64.

using isc-dhcp-client 4.3.3-5ubuntu13.1, bug is fixed; dhcpv6 prefix is
set correctly to /128.

** Tags added: verification-done-yakkety

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

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

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

[Touch-packages] [Bug 1622682] Re: incorrect use of 'summary' event property in popup notifications

** Branch linked: lp:~charlesk/indicator-datetime/lp-1622682-use-valarm-
description-property-in-popups

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

Title:
  incorrect use of 'summary' event property in popup notifications

Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  As described in RFC 2445:

  > When the action is "DISPLAY", the alarm MUST also include a
  "DESCRIPTION" property, which contains the text to be displayed when
  the alarm is triggered.

  The ingest code in engine-eds.cpp is correctly reading the
  `description' property to initialize the Alarm struct's 'text' field,
  but then when it comes time to display the alarm, it uses
  Appointment.summary instead.

  This appears to be a code leftover from the time before indicator-
  datetime added multiple valarm support by separating the Alarm and
  Appointment structures.

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

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

[Touch-packages] [Bug 1622689] [NEW] Motorola HT820, playback No sound at all

2016-09-12 Thread aanno

Public bug reported:

several crashes of bluetooth-manager (2.0.4) before connecting to a bt
a2dp sink.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Sep 12 19:10:31 2016
InstallationDate: Installed on 2014-01-06 (980 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: Motorola HT820
Symptom_Type: No sound at all
Title: [Motorola HT820, playback] No sound at all
UpgradeStatus: Upgraded to xenial on 2016-04-23 (142 days ago)
dmi.bios.date: 11/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0504
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: E2KM1I-DELUXE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd11/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnE2KM1I-DELUXE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2016-06-04T22:16:20.544523

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
   Motorola HT820, playback  No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  several crashes of bluetooth-manager (2.0.4) before connecting to a bt
  a2dp sink.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Sep 12 19:10:31 2016
  InstallationDate: Installed on 2014-01-06 (980 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Motorola HT820
  Symptom_Type: No sound at all
  Title: [Motorola HT820, playback] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (142 days ago)
  dmi.bios.date: 11/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: E2KM1I-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd11/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnE2KM1I-DELUXE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2016-06-04T22:16:20.544523

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

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

[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2016-09-12 Thread magic8east

I also have the same problem. Audio from my Blue microphones snowball is
distorted (slowed down) as well. It's *really* annoying.

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

Title:
Volume notification keeps popping up constantly(the notifyosd bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

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

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

[Touch-packages] [Bug 1622682] [NEW] incorrect use of 'summary' event property in popup notifications

2016-09-12 Thread Charles Kerr

Public bug reported:

As described in RFC 2445:

> When the action is "DISPLAY", the alarm MUST also include a
"DESCRIPTION" property, which contains the text to be displayed when the
alarm is triggered.

The ingest code in engine-eds.cpp is correctly reading the `description'
property to initialize the Alarm struct's 'text' field, but then when it
comes time to display the alarm, it uses Appointment.summary instead.

This appears to be a code leftover from the time before indicator-
datetime added multiple valarm support by separating the Alarm and
Appointment structures.

** Affects: indicator-datetime (Ubuntu)
 Importance: Medium
 Assignee: Charles Kerr (charlesk)
 Status: In Progress

** Changed in: indicator-datetime (Ubuntu)
   Status: New => In Progress

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- should use vevent 'description' property in notifications
+ incorrect use of 'summary' event property in popup notifications

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

Title:
  incorrect use of 'summary' event property in popup notifications

Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  As described in RFC 2445:

  > When the action is "DISPLAY", the alarm MUST also include a
  "DESCRIPTION" property, which contains the text to be displayed when
  the alarm is triggered.

  The ingest code in engine-eds.cpp is correctly reading the
  `description' property to initialize the Alarm struct's 'text' field,
  but then when it comes time to display the alarm, it uses
  Appointment.summary instead.

  This appears to be a code leftover from the time before indicator-
  datetime added multiple valarm support by separating the Alarm and
  Appointment structures.

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

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

[Touch-packages] [Bug 1508905] Re: Graphics disorder, a "claw" appearing

2016-09-12 Thread Kyle Nitzsche

** Changed in: unity8 (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Graphics disorder, a "claw" appearing

Status in Today Scope:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Currently I have this bug. It was already present in the OTA-6.
  Usually a reboot fix the problem, but after a while it come back
  again.

  It only appears ate the bottom of the scope! If I swipe back to the
  top the "claw" fade out.

  I've attached a screenshot.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1508905/+subscriptions

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

[Touch-packages] [Bug 1612259] Re: [MIR] libusermetrics

2016-09-12 Thread Michael Terry

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

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

Title:
  [MIR] libusermetrics

Status in libusermetrics package in Ubuntu:
  Fix Committed

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has both unit tests and integration tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * qdjango (bug #1612270)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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

[Touch-packages] [Bug 1508905] Re: Graphics disorder, a "claw" appearing

2016-09-12 Thread Ivo Xavier

Hi @saviq,

Sadly the claw is back again. Today, I've enable the twitter feed in the
Today Scope, schooled up and down a few times and this graphic disorder
return again, see screenshot. One thing I notice, is that this graph is
bigger then previous ones.

Device name: Krillin
OS: OTA12


** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/today-scope/+bug/1508905/+attachment/4739389/+files/photo_2016-09-12_17-35-34.jpg

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

Title:
  Graphics disorder, a "claw" appearing

Status in Today Scope:
  Invalid
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Hi,

  Currently I have this bug. It was already present in the OTA-6.
  Usually a reboot fix the problem, but after a while it come back
  again.

  It only appears ate the bottom of the scope! If I swipe back to the
  top the "claw" fade out.

  I've attached a screenshot.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1508905/+subscriptions

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

[Touch-packages] [Bug 1619784] Re: rsync with -fake-super and --link-dest copies symlinks even when they haven't changed

2016-09-12 Thread Robie Basak

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

You haven't provided any package or release version information with
your report. In any case, this sounds like a bug that should be reported
upstream to the rsync project itself, as in Ubuntu we don't expect to
make rsync behaviour special as that would be confusing to rsync users
across the ecosystem.

Please check to see if in your opinion this affects the latest version
of rsync as available directly from the rsync project, and if this is
the case then please file a bug upstream and report the link to that bug
here.

If there is a change made upstream that Ubuntu should be following in
some specific Ubuntu releases, please provide a link to the upstream
change and provide Ubuntu package version information, state why you
think this should be fixed in a patch in Ubuntu, and then change the bug
status to New.

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

** Tags added: needs-upstream-report

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

Title:
  rsync with -fake-super and --link-dest copies symlinks even when they
  haven't changed

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  The title says it all!

  rsync with -fake-super and --link-dest copies symlinks even when they
  haven't changed.

  This is incorrect behavior: symlinks, like all other files, should be
  copied only if they have changed.

  Without -fake-super, it works fine (nothing is copied unless it is
  changed).

  Without --link-dest, it works fine (nothing is copied unless it is
  changed).

  With both options specified, symlinks are copied regardless of whether
  or not they changed

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

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

[Touch-packages] [Bug 1516443] Re: Wishlist: (RedShift) Night mode for Ubuntu Phones

2016-09-12 Thread MichaeL.

We are waiting for this feature. We already use it in ubuntu desktop and
android and like it very much. Please implement redshift functions in
ubuntu touch also or make it available as app. Thank you

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

Title:
  Wishlist: (RedShift) Night mode for Ubuntu Phones

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Triaged
Status in Ubuntu UX:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I would love to see a feature to make the backlight less agressive for
  the late hours of the day. For desktor there is the possibility to
  turn the screen 'red' and it feels really good compared to normal.

  This is a wish, I don't know where to put it else.

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

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

[Touch-packages] [Bug 1534964] Re: Hotplugging HDMI fails

2016-09-12 Thread Sean

This issue initially happened on both intel and nvidia gpus after 16.04
was released but the bug was fixed for intel gpus at some point but
remains for nvidia on 352 and 340 drivers.

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

Title:
  Hotplugging HDMI fails

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Affected computer: Dell Precision 15 5000 Series (5510) with Quadro
  M1000M/PCIe/SSE2 graphics card (kernel 4.2.0-23-generic).

  Expected behaviour:

  - hotplugging HDMI cable would work

  Current behaviour:

  - Hotpluging doesn't work (no kernel events, used udevadm monitor to
  verify)

  Current observations:

  - HDMI output works if connected from the boot
  - When DPMS kicks in HDMI output disappears (tested with 2 different monitors)
  - Hotpluging doesn't work (no kernel events, used udevadm monitor to verify)
  - VGA (via usb-c adapter) works, hotplugging also
  - HDMI (via usb-c adapter) causes black screen in computer display and 
eventually crashes X. Unplugging adapter before crash restores state (computer 
display restored)
  - display port (via usb-c adapter) not confirmed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 
PST 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 16 19:13:22 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed
   nvidia-352, 352.63, 4.2.0-23-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Device [8086:191d] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06e5]
 Subsystem: Dell Device [1028:06e5]
  InstallationDate: Installed on 2016-01-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 007: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-23-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.15
  dmi.board.name: 08R8KJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.15:bd12/18/2015:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn08R8KJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3

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

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

[Touch-packages] [Bug 1600000] Re: libnss-resolve treats two trailing dots on a domain name incorrectly

This bug was fixed in the package systemd - 231-6

---
systemd (231-6) unstable; urgency=medium

  [ Martin Pitt ]
  * Add alternative iptables-dev build dependencies
libiptc-dev is very new and not yet present in stable Debian/Ubuntu 
releases.
Add it as a fallback build dependency for backports and upstream tests.
  * Detect if seccomp is enabled but seccomp filtering is disabled
(Closes: #832713)
  * resolved: recognize DNS names with more than one trailing dot as invalid
(LP: #160)
  * debian/tests/smoke: Store udev db dump artifact on failure
  * networkd: limit the number of routes to the kernel limit
  * systemctl: consider service running only when it is in active or reloading 
state
  * networkd: remove route if carrier is lost
  * Add Ref()/Unref() bus calls for units

  [ Felipe Sateler ]
  * git-cherry-pick: always recreate the patch-queue branch.

  [ Dimitri John Ledkov ]
  * Use idiomatic variables from dpkg include.

 -- Martin Pitt   Sun, 11 Sep 2016 15:00:55
+0200

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

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

Title:
  libnss-resolve treats two trailing dots on a domain name incorrectly

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged

Bug description:
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' 
/etc/nsswitch.conf 
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM  
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ 

  This is responsible for the new regression in glibc:

  --
  FAIL: posix/tst-getaddrinfo5
  original exit status 1
  resolving "localhost." worked, proceeding to test
  resolving "localhost.." failed, test passed
  resolving "www.gnu.org." worked, proceeding to test
  resolving "www.gnu.org.." worked, test failed
  --

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

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

[Touch-packages] [Bug 1608953] Re: PostgreSQL does not start in lx-brand container

2016-09-12 Thread Christopher Horrell

I installed the systemd 229-4ubuntu8 package from xenial-proposed and it
looks like the package fixes this bug.

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

Title:
  PostgreSQL does not start in lx-brand container

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

Bug description:
  We have a 16.04 Ubuntu lx-brand container image available in our
  public cloud and recently discovered a systemd bug that's related to
  running in a container environment.

  I'm forwarded below what one of our engineers discovered:

  

  After installing postgres (apt-get install -y -q postgresql), systemd
  does not actually start any of the postgres services. We tracked this
  down to a failure from sed from within the /lib/systemd/system-
  generators/postgresql-generator script. The sed command tries to close
  stderr (fd 2) which fails, so sed returns an error code, which causes
  the entire postgres generator to fail.

  The root cause of the problem lies in the systemd code. Because we are
  running inside of a container (see detect_container) we don't execute
  the following block of code in the systemd main().

  if (getpid() == 1 && detect_container() <= 0) {

  /* Running outside of a container as PID 1 */
  arg_running_as = MANAGER_SYSTEM;
  make_null_stdio();

  The make_null_stdio function is what sets up fd 0-2 as /dev/null in
  systemd on bare metal. Having those fd's setup is what allows the
  postgres system-generator to work properly since sed expects to be
  able to close stderr.

  Because we never call make_null_stdio when inside any container, the
  low fd's wind up getting setup later using /dev/console with
  O_CLOEXEC, so when we actually run the system generator script, we
  don't have the low fd's setup at all like sed expects.

  Interestingly, looking at the master branch of systemd, at
  src/core/main.c this bug appears to no longer exist. The relevant code
  block has been moved so it is no longer conditional on being in a
  container, but the commit was not intended to fix this problem. It was
  apparently due to color handling on the console/

  commit 3a18b60489504056f9b0b1a139439cbfa60a87e1

  It would be great if this fix could be pulled in to an update for
  Ubuntu 16.04.

  SRU INFORMATION
  ===
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=6df46531727baa

  Regression potential: very low; this does not affect lxc and lxd (our
  officially supported container engines) nor nspawn, as they already
  set up pid1's stdout/stderr. And it's hard to imagine anything
  depending on pid1's stdout/err *not* being existant file descriptors,
  as in pretty much all cases they already are.

  Test case: Specific to lx-brand, must be verified by reporter.
  However, we need to verify that LXC, LXD, and nspawn containers still
  boot with this version.

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

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

[Touch-packages] [Bug 1608953] Re: PostgreSQL does not start in lx-brand container

2016-09-12 Thread Christopher Horrell

TEST CASE:

- Added xenial-proposed  to /etc/apt/sources.list
- Installed systemd: pt install systemd/xenial-proposed
- Install postgres: apt-get install -y -q postgresql

Verified the postgresql service is running:

- su postgres
- psql

and also:

- systemctl status postgresql
- ystemctl status postgresql@9.5-main.service

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

Title:
  PostgreSQL does not start in lx-brand container

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

Bug description:
  We have a 16.04 Ubuntu lx-brand container image available in our
  public cloud and recently discovered a systemd bug that's related to
  running in a container environment.

  I'm forwarded below what one of our engineers discovered:

  

  After installing postgres (apt-get install -y -q postgresql), systemd
  does not actually start any of the postgres services. We tracked this
  down to a failure from sed from within the /lib/systemd/system-
  generators/postgresql-generator script. The sed command tries to close
  stderr (fd 2) which fails, so sed returns an error code, which causes
  the entire postgres generator to fail.

  The root cause of the problem lies in the systemd code. Because we are
  running inside of a container (see detect_container) we don't execute
  the following block of code in the systemd main().

  if (getpid() == 1 && detect_container() <= 0) {

  /* Running outside of a container as PID 1 */
  arg_running_as = MANAGER_SYSTEM;
  make_null_stdio();

  The make_null_stdio function is what sets up fd 0-2 as /dev/null in
  systemd on bare metal. Having those fd's setup is what allows the
  postgres system-generator to work properly since sed expects to be
  able to close stderr.

  Because we never call make_null_stdio when inside any container, the
  low fd's wind up getting setup later using /dev/console with
  O_CLOEXEC, so when we actually run the system generator script, we
  don't have the low fd's setup at all like sed expects.

  Interestingly, looking at the master branch of systemd, at
  src/core/main.c this bug appears to no longer exist. The relevant code
  block has been moved so it is no longer conditional on being in a
  container, but the commit was not intended to fix this problem. It was
  apparently due to color handling on the console/

  commit 3a18b60489504056f9b0b1a139439cbfa60a87e1

  It would be great if this fix could be pulled in to an update for
  Ubuntu 16.04.

  SRU INFORMATION
  ===
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=6df46531727baa

  Regression potential: very low; this does not affect lxc and lxd (our
  officially supported container engines) nor nspawn, as they already
  set up pid1's stdout/stderr. And it's hard to imagine anything
  depending on pid1's stdout/err *not* being existant file descriptors,
  as in pretty much all cases they already are.

  Test case: Specific to lx-brand, must be verified by reporter.
  However, we need to verify that LXC, LXD, and nspawn containers still
  boot with this version.

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

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

[Touch-packages] [Bug 1212360] Re: Cannot import OpenVPN profiles

2016-09-12 Thread Matthias Seidel

On Ubuntu 16.04 there was no import button by default.

I had manually to install:

 - network-manager-openvpn
 - network-manager-openvpn-gnome

After that there was an "import OpenVPN profile" button on the "new VPN"
dialog

** Attachment added: "Bildschirmfoto vom 2016-09-12 17-41-25.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1212360/+attachment/4739364/+files/Bildschirmfoto%20vom%202016-09-12%2017-41-25.png

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

Title:
  Cannot import OpenVPN profiles

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.10 / Intel / ASUS Zenbook
  Package: network-manager

  1. receive an OpenVPN profile (ovpn and crt files) by email or download.
  2. open Network Manager
  3. look in vain for an "import" button or link.

  What should have happened instead:

  3. there should be an "import OpenVPN profile" button on the "new VPN"
  dialog

  Prior to Unity, the gnome network manager had an "import VPN" button
  which allowed importing configuration files for OpenVPN and Cisco.
  The new Unity network manager has removed that button and not replaced
  it with anything.  The only workaround is to install the old Gnome
  network manager, launch it from the command line, and use it to import
  the VPN profile.

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

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

[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

tested on xenial:

using isc-dhcp-client 4.3.3-5ubuntu12.1, bug exists; dhcpv6 prefix is
set to /64.

using isc-dhcp-client 4.3.3-5ubuntu12.2, bug is fixed; dhcpv6 prefix is
correctly set to /128.

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

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

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

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

[Touch-packages] [Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs

Note, there hasn't been any debian installer fix yet, as we don't even
understand what's actually happening there. There has just been an SRU
to systemd/udev to fix the "No such file or directory" error message in
udev rules, but apparently that was not the actual problem.

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in busybox source package in Yakkety:
  Fix Released
Status in debian-installer source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  Then it keeps hanged in this stage. We re-tested it by changing the
  file 73-usb-net-by-mac.rules in initrd, replacing "
  /etc/udev/rules.d/80-net-setup-link.rules" to  "/lib/udev/rules.d/80
  -net-setup-link.rules", since the former does not exist whereas the
  latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask Canonical's help in investigating this issue.
  Thanks,

  Guilherme

  
  SRU INFORMATION for systemd
  ===

  Test case:
   * Check what happens for uevents on devices which are not USB network 
interfaces:
 udevadm test /sys/devices/virtual/mem/null
 udevadm test /sys/class/net/lo

   With the current version these will run

PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  /lib/udev/rules.d/73-usb-net-by-mac.rules:6

   which is pointless. With the proposed version these should be gone.

   * Ensure that the rule still works as intended by connecting an USB
  network device that has a permanent MAC address (e. g. Android
  tethering uses a temporary MAC): You should get a MAC-based name like
  "enx12345678" for it. Now disconnect it again, disable ifnames with

  sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

  and reconnect the device. You should now get a kernel name like "usb0"
  for it.

  * Regression potential: Errors in the rule could break persistent
  naming - or

[Touch-packages] [Bug 1612259] Re: [MIR] libusermetrics

This bug was fixed in the package libusermetrics -
1.1.1+16.10.20160909-0ubuntu1

---
libusermetrics (1.1.1+16.10.20160909-0ubuntu1) yakkety; urgency=medium

  * Remove debconf from pre and post -inst scripts (LP: #1612259)

 -- Pete Woods   Fri, 09 Sep 2016 12:52:40
+

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

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

Title:
  [MIR] libusermetrics

Status in libusermetrics package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has both unit tests and integration tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * qdjango (bug #1612270)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

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

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

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

2016-09-12 Thread bugproxy

--- Comment From dougm...@us.ibm.com 2016-09-12 11:09 EDT---
Reopening: xenial-proposed installer has not been updated, cannot verify fix. 
Set back to fixed/verify once 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-proposed installer has been 
updated with fixed systemd to be tested.

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in busybox source package in Yakkety:
  Fix Released
Status in debian-installer source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  Then it keeps hanged in this stage. We re-tested it by changing the
  file 73-usb-net-by-mac.rules in initrd, replacing "
  /etc/udev/rules.d/80-net-setup-link.rules" to  "/lib/udev/rules.d/80
  -net-setup-link.rules", since the former does not exist whereas the
  latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask Canonical's help in investigating this issue.
  Thanks,

  Guilherme

  
  SRU INFORMATION for systemd
  ===

  Test case:
   * Check what happens for uevents on devices which are not USB network 
interfaces:
 udevadm test /sys/devices/virtual/mem/null
 udevadm test /sys/class/net/lo

   With the current version these will run

PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  /lib/udev/rules.d/73-usb-net-by-mac.rules:6

   which is pointless. With the proposed version these should be gone.

   * Ensure that the rule still works as intended by connecting an USB
  network device that has a permanent MAC address (e. g. Android
  tethering uses a temporary MAC): You should get a MAC-based name like
  "enx12345678" for it. Now disconnect it again, disable ifnames with

  sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

  and reconnect the device. You should now get a kernel name like "usb0"
  for it.

  * Regression potential: Errors in the rule could break

[Touch-packages] [Bug 1025562] Re: Need green/yellow/red icons for software-properties driver installation spec

2016-09-12 Thread Magdalena Mirowicz

** Changed in: software-properties (Ubuntu)
 Assignee: Magdalena Mirowicz (magdalena-mirowicz) => (unassigned)

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

Title:
  Need green/yellow/red icons for software-properties driver
  installation spec

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  From https://wiki.ubuntu.com/SoftwareAndUpdatesSettings#drivers:
  "Each device in the list should have an indicator light: green if the driver 
tested with that Ubuntu release is being used, yellow if any other driver is 
being used, or red if no driver is being used."

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

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

[Touch-packages] [Bug 1620557] Re: weather.noaa.gov was shut down

2016-09-12 Thread Alberts Muktupāvels

Lanoxx, bug will be updated when new package will be in proposed...

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

Title:
  weather.noaa.gov was shut down

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Trusty:
  Triaged
Status in libgweather source package in Xenial:
  In Progress

Bug description:
  The provider which libgweather was using was shut down in August.

  We need to update libgweather in Xenial to new upstream micro release,
  3.18.2, which switched to a new METAR data provider.

  Impact: this affects all libgweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in gnome-applets is able to
  display weather information.

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

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

[Touch-packages] [Bug 1621925] Re: package openssh-server 1:7.2p2-4ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-09-12 Thread ChristianEhrhardt

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

>From the log:
Sep 09 19:38:56 hostname sshd[11183]: error: Bind to port 22 on 0.0.0.0 failed: 
Address already in use.
Sep 09 19:38:56 hostname sshd[11183]: error: Bind to port 22 on :: failed: 
Address already in use.
Sep 09 19:38:56 hostname sshd[11183]: fatal: Cannot bind any address.
Sep 09 19:38:56 hostname systemd[1]: Failed to start OpenBSD Secure Shell 
server.
Sep 09 19:38:56 hostname systemd[1]: ssh.service: Failed with result 
'exit-code'.
Sep 09 19:39:32 hostname sshd[11683]: error: Bind to port 22 on 0.0.0.0 failed: 
Address already in use.
Sep 09 19:39:32 hostname sshd[11683]: error: Bind to port 22 on :: failed: 
Address already in use.
Sep 09 19:39:32 hostname sshd[11683]: fatal: Cannot bind any address.
Sep 09 19:39:32 hostname systemd[1]: Failed to start OpenBSD Secure Shell 
server.
Sep 09 19:39:32 hostname systemd[1]: ssh.service: Failed with result 
'exit-code'.

It seems you already have some other ssh server (or something else on
that port) running.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I was trying to install openssh server and I got following error

  $ sudo apt-get install openssh-server
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
ncurses-term openssh-sftp-server ssh-import-id
  Suggested packages:
ssh-askpass rssh molly-guard monkeysphere
  The following NEW packages will be installed:
ncurses-term openssh-server openssh-sftp-server ssh-import-id
  0 upgraded, 4 newly installed, 0 to remove and 290 not upgraded.
  Need to get 636 kB of archives.
  After this operation, 5,145 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Get:1 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 ncurses-term all 
6.0+20160213-1ubuntu1 [249 kB]
  Get:2 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
openssh-sftp-server amd64 1:7.2p2-4ubuntu2.1 [38.8 kB]
  Get:3 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
openssh-server amd64 1:7.2p2-4ubuntu2.1 [338 kB]
  Get:4 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 ssh-import-id all 
5.5-0ubuntu1 [10.2 kB]
  Fetched 636 kB in 3s (161 kB/s)   
  Preconfiguring packages ...
  Selecting previously unselected package ncurses-term.
  (Reading database ... 227909 files and directories currently installed.)
  Preparing to unpack .../ncurses-term_6.0+20160213-1ubuntu1_all.deb ...
  Unpacking ncurses-term (6.0+20160213-1ubuntu1) ...
  Selecting previously unselected package openssh-sftp-server.
  Preparing to unpack .../openssh-sftp-server_1%3a7.2p2-4ubuntu2.1_amd64.deb ...
  Unpacking openssh-sftp-server (1:7.2p2-4ubuntu2.1) ...
  Selecting previously unselected package openssh-server.
  Preparing to unpack .../openssh-server_1%3a7.2p2-4ubuntu2.1_amd64.deb ...
  Unpacking openssh-server (1:7.2p2-4ubuntu2.1) ...
  Selecting previously unselected package ssh-import-id.
  Preparing to unpack .../ssh-import-id_5.5-0ubuntu1_all.deb ...
  Unpacking ssh-import-id (5.5-0ubuntu1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (229-4ubuntu4) ...
  Processing triggers for ufw (0.35-0ubuntu2) ...
  Setting up ncurses-term (6.0+20160213-1ubuntu1) ...
  Setting up openssh-sftp-server (1:7.2p2-4ubuntu2.1) ...
  Setting up openssh-server (1:7.2p2-4ubuntu2.1) ...
  Creating SSH2 RSA key; this may take some time ...
  2048 SHA256:98ONRH/YVE1YPZXLZhT5Z9fChL53mOp6YvItMWkQ45o 
root@surendra-Vostro-1540 (RSA)
  Creating SSH2 DSA key; this may take some time ...
  1024 SHA256:oDGGUWnfPR9vSlBpv9iGW0rNt6O4Wi2MyNtr8UuDpE4 
root@surendra-Vostro-1540 (DSA)

[Touch-packages] [Bug 1546733] Re: Update of today screen messes up scopes layout.

2016-09-12 Thread Kyle Nitzsche

** Changed in: today-scope
   Status: New => Invalid

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

Title:
  Update of today screen messes up scopes layout.

Status in Today Scope:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  BQ4.5, OTA9, official channel.

  Observed the following:
  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions

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

[Touch-packages] [Bug 1622447] Re: libnss3-1d: dependcies update

2016-09-12 Thread Bug Watch Updater

** Changed in: ecryptfs-utils (Debian)
   Status: Unknown => Fix Released

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

Title:
  libnss3-1d: dependcies update

Status in ecryptfs-utils package in Ubuntu:
  New
Status in nss package in Ubuntu:
  New
Status in ecryptfs-utils package in Debian:
  Fix Released

Bug description:
  in Yakkety Yak one dependency(or more precisely dependency definition)
  of the package libnss3-1d is outdated

  it has 'Depends: libnss3 (= 2:3.25-1ubuntu1)' but it should has
  'Depends: libnss3 >= 2:3.25-1ubuntu1)' or something like
  that(otherwise libnss3-1d can't install when libnss3 !=
  2:3.25-1ubuntu1)...

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

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

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

[Touch-packages] [Bug 1622406] Re: Libertine (X11 App) page disappeared (OTA12) on BQ M10

2016-09-12 Thread Larry Price

Thanks for the bug report.

* Is the "Desktop Applications" scope still available in the scope list? Pull 
up on the small arrow at the bottom of the Dash to view all available scopes. 
If it is still in that list, then you may have just accidentally un-favorited 
the scope. Click the empty star icon to re-favorite the scope.
* Can you describe the process you used to add these keyboard layouts?

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

Title:
  Libertine (X11 App)  page disappeared (OTA12) on BQ M10

Status in Libertine:
  New
Status in libertine package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Under OTA12 of BQ M10 (Cooler), I opened Libreoffice and tried to add
  an additional language layout for external keyboard (Thai).  I was
  able to add US and Thai Pattachote keyboards (for external keyboard),
  but did not know how to switch the keyboard layout.  I tried ALT-Shift
  and CTR-Shift without a success.

  There was no Internet connection during the keyboard layout adding.

  It turned out that the X11 App or Libertine page disappeared.  I tried
  to restart and even turned of the M10.  However, the X11 App page did
  not come back.  Could it be I did type in unkonw hot keys?

  Is there a way to bring back the missing Libertine (X11 App) page?  Or
  can I bring up the missing programmes under terminal (e.g.
  Libreoffice, Firefox, Gimp)?

  
  PS I used K380 Logitech Bluetooth external keyboard.  And I use this M10 
around once a week.

  Thanks.

  Namsommut

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

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

[Touch-packages] [Bug 1620955] Re: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd w

2016-09-12 Thread ChristianEhrhardt

Hi,
that can depend on many things - transient error happen and are hard to track 
down. Usually reasonable and fixable issues turn out to occur often and also 
are reproducible.
The few transient ones just show up every now and then, but after a certain 
type is seen often enough debugging can begin on the assumptions one can make 
of the sum of reports.

That said thanks for your report, and also I'm happy things are resolved
for you right now.

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

Title:
  package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: pakket libhcrypto4-heimdal:amd64
  1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat
  libhcrypto4-heimdal:i386 van een andere versie is (1.7~git20150920
  +dfsg-4ubuntu1)

Status in heimdal package in Ubuntu:
  Incomplete

Bug description:
  No clue whatsoever

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
  Uname: Linux 4.6.0-040600-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep  6 14:32:43 2016
  ErrorMessage: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan 
niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere 
versie is (1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-04-04 (155 days ago)
  InstallationMedia: It
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: heimdal
  Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan 
niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere 
versie is (1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: Upgraded to yakkety on 2016-05-20 (110 days ago)

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

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

[Touch-packages] [Bug 1618371] Re: package linux-image-4.4.0-36-generic 4.4.0-36.55 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-4.4.0-36-generic 4.4.0-36.55 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  freezing...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  justin 4312 F pulseaudio
   /dev/snd/controlC1:  justin 4312 F pulseaudio
  Date: Tue Aug 30 12:09:44 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=3211ba14-3ea4-408a-a0ed-99761076dfe7
  InstallationDate: Installed on 2015-05-29 (458 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Acer Aspire VN7-791
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=ef933f4c-4227-4bfa-894c-4a0c3363ef17 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-36-generic 4.4.0-36.55 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-05-16 (105 days ago)
  dmi.bios.date: 09/05/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-791
  dmi.board.vendor: Acer
  dmi.board.version: V1.07
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2014:svnAcer:pnAspireVN7-791:pvrV1.07:rvnAcer:rnAspireVN7-791:rvrV1.07:cvnAcer:ct10:cvrV1.07:
  dmi.product.name: Aspire VN7-791
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1622447] Re: libnss3-1d: dependcies update

2016-09-12 Thread Kai Kasurinen

** Bug watch added: Debian Bug tracker #834687
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834687

** Also affects: ecryptfs-utils (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834687
   Importance: Unknown
   Status: Unknown

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

Title:
  libnss3-1d: dependcies update

Status in ecryptfs-utils package in Ubuntu:
  New
Status in nss package in Ubuntu:
  New
Status in ecryptfs-utils package in Debian:
  Unknown

Bug description:
  in Yakkety Yak one dependency(or more precisely dependency definition)
  of the package libnss3-1d is outdated

  it has 'Depends: libnss3 (= 2:3.25-1ubuntu1)' but it should has
  'Depends: libnss3 >= 2:3.25-1ubuntu1)' or something like
  that(otherwise libnss3-1d can't install when libnss3 !=
  2:3.25-1ubuntu1)...

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

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

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

[Touch-packages] [Bug 1622473] Re: Home button works on M10 in a strange way

2016-09-12 Thread Pat McGowan

@michael I would have expected no input as well, but why is the dash
freezing like that? Something must incorrectly handle whatever is being
sent in, so more like two bugs

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

Title:
  Home button works on M10 in a strange way

Status in Canonical System Image:
  Confirmed
Status in frieza:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  bq M10FHD with rc-proposed r186

  Today I've noticed the hardware home button below the screen works. I
  was holding the tablet in one hand in a way that my thumb was covering
  the button. Then I've noticed the interaction (scrolling webpage in
  this case) was weird. Later on I checked with scrolling scopes while
  keeping my thumb on the button. And it also changes the experience.
  I'll attach a video later on.

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

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

[Touch-packages] [Bug 1587271] Re: missing libopenal.so

2016-09-12 Thread Bret Curtis

Looks like x-plane needs to be rebuilt against libopenal.so.1 using pkg-
config to point to the right library location.

Many other applications (steam, wildmidi and etc.) are capable of doing
this without a problem.

** Changed in: openal-soft (Ubuntu)
   Status: New => Invalid

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

Title:
  missing libopenal.so

Status in openal-soft package in Ubuntu:
  Invalid

Bug description:
  First install with synaptic openal.

  Then cd to the directory with libopenal and link like above:

  ln -s libopenal.so.1 libopenal.so

  
  This is needed for x-plane on Ubuntu. So what century are you in, 19th?
  Thanks for fixing

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

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

[Touch-packages] [Bug 1622473] Re: Home button works on M10 in a strange way

2016-09-12 Thread Michael Zanetti

FWIW, this is not unity8, the button should not deliver anything from
the lower level drivers as it has been disabled in there. It seems some
corner cases were forgotten though.

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

Title:
  Home button works on M10 in a strange way

Status in Canonical System Image:
  Confirmed
Status in frieza:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  bq M10FHD with rc-proposed r186

  Today I've noticed the hardware home button below the screen works. I
  was holding the tablet in one hand in a way that my thumb was covering
  the button. Then I've noticed the interaction (scrolling webpage in
  this case) was weird. Later on I checked with scrolling scopes while
  keeping my thumb on the button. And it also changes the experience.
  I'll attach a video later on.

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

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

[Touch-packages] [Bug 1547024] Re: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem

2016-09-12 Thread FIGIEL

I have the exact same problem, is there a fix for this now ?
Does upgrading the kernel really works ?

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

Title:
  [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise
  Problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure what's happening, my sound works great, there's just a
  static noise in the background that can get very annoying.

  Let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.5.0-040500rc4-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zkanda 1519 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Feb 18 21:34:15 2016
  InstallationDate: Installed on 2016-02-16 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160216)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.204:bd11/12/2015:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1576692] Re: fully support package installation in systemd

2016-09-12 Thread Scott Moser

Martin,
I moved all things that do package installation into final.  The user could 
still manage to have some things run at 'config' point in boot that would 
install packages, but anything that does it in cloud-init directly is now part 
of final.

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  In Progress

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to have a way to fully support this in cloud-init.

  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out

  SRU INFORMATION
  ===
  FIX for init-system-helpers: 
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02

  REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
  and service, two very central pieces of packaging infrastructure.
  Errors in it will break installation/upgrades of packages or
  /etc/network/if-up.d/ hooks and the like. This changes the condition
  when systemd units get started without their dependencies, and the
  condition gets weakened. This means that behaviour in a booted system
  is unchanged, but during boot this could change the behaviour of if-
  up.d/ hooks (although they have never been defined well during boot
  anyway). However, I tested this change extensively in cloud images and
  desktop installations (particularly I recreated
  https://bugs.debian.org/777113 and confirmed that this approach also
  fixes it) and could not find any regression.

  TEST CASE (for both packages):
  Run
 lxc launch ubuntu-daily:x --config=user.user-data="$(printf 
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1

  This will install all three packages, but "systemctl status
  postgresql@9.5-main" will not be running.

  Now prepare a new image with the proposed cloud-init and init-system-
  helpers:

 lxc launch ubuntu-daily:x xprep
 lxc exec xprep bash
 # enable -proposed and dist-upgrade, then poweroff
 lxc publish xprep x-proposed

  Now run the initial lxc launch again, but against that new x-proposed
  image instead of the standard daily:

lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
  config\npackages: [postgresql, samba, postfix]")" x1

  You should now have "systemctl status postgresql@9.5-main" running.
  Directly after rebooting the instance, check that there are no hanging
  jobs (systemctl list-jobs), particularly networking.service, to ensure
  that https://bugs.debian.org/777113 did not come back.

  Also test interactively installing a package that ships a service,
  like "apache2", and verify that it starts properly after installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+subscriptions

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

[Touch-packages] [Bug 1622473] Re: Home button works on M10 in a strange way

2016-09-12 Thread Pat McGowan

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Home button works on M10 in a strange way

Status in Canonical System Image:
  Confirmed
Status in frieza:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  bq M10FHD with rc-proposed r186

  Today I've noticed the hardware home button below the screen works. I
  was holding the tablet in one hand in a way that my thumb was covering
  the button. Then I've noticed the interaction (scrolling webpage in
  this case) was weird. Later on I checked with scrolling scopes while
  keeping my thumb on the button. And it also changes the experience.
  I'll attach a video later on.

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

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

[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported

2016-09-12 Thread Rod Smith

Matthew, note that the change I was trying to make did not take effect.
This might be independent of the warning message, but it's the real
problem being reported. As noted, omitting "-fnoninteractive" enables it
to work, but as I'm trying to do this in a script, that omission is not
a reasonable option.

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

Title:
  dpkg-reconfigure unattended-upgrades results in update-rc.d warning
  that start and stop actions are no longer supported

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  I'm trying to script a change to the automatic updating of servers,
  and tried the following:

  echo "debconf unattended-upgrades/enable_auto_updates boolean false" | 
debconf-set-selections -
  dpkg-reconfigure -fnoninteractive unattended-upgrades

  The result, however, is a warning message:

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  At this point, the change I tried to make seems to be lost. To show
  this in an expanded sequence:

  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: true
  root@brennan:/home/ubuntu# echo "debconf 
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections 
-
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: false
  root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive 
unattended-upgrades
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/enable_auto_updates: true
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

  If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
  get the warning message, but the change IS accepted and takes effect.
  Of course, this isn't useful in a script that should be run non-
  interactively. I've tried the equivalent commands to reconfigure other
  packages, and they work without error message, so I believe the
  problem is with unattended-upgrades, not with debconf/dpkg-
  reconfigure.

  This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
  not tested it). It works as expected with Ubuntu 14.04. (That version,
  of course, defeaults to "false" for the unattended-
  upgrades/enable_auto_updates value. I've tested both with the default
  "false" value and after changing it to "true," with successful runs
  both times.)

  Version information, as requested:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
   *** 0.90 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy debconf
  debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
   *** 1.5.58ubuntu1 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1621215] Re: Sidebar: Other Locations fails to open

This bug was fixed in the package gtk+3.0 - 3.20.9-1ubuntu2

---
gtk+3.0 (3.20.9-1ubuntu2) yakkety; urgency=medium

  * Add 0002-Fix-other-locations-with-glib-249.patch and
0003-use-null-for-generic-marshallers.patch:
- Backport patches from 3.22 to fix "Other Locations" link in
  file browser sidebar with glib 2.49.6 (LP: #1621215)

 -- Jeremy Bicha   Fri, 09 Sep 2016 04:24:36 -0400

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

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

Title:
  Sidebar: Other Locations fails to open

Status in GTK+:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Fresh daily image from today, also seen on recent install, updated.

  Open nautilus, click on Other Locations
  Nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity
  Date: Wed Sep  7 19:13:51 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+65+24'"
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1616517] Re: whoopsie does not send fields from some package management application crashes