Re: [Touch-packages] [Bug 1676482] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Lamulani]

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

After the bug report that i filled, I re-installed ubuntu  and genymotion
(which works with a Vbox), then  I ran a systems update but the problem
still persisted. I checked the genymotion website but I couldn't find
anything helpful. I have tried to look for help @ask ubuntu but it seems my
problem is somewhat unique.

On Tue, Apr 11, 2017 at 9:47 PM, Hans Joachim Desserud <
1676...@bugs.launchpad.net> wrote:

> *** This bug is a duplicate of bug 1676380 ***
> https://bugs.launchpad.net/bugs/1676380
>
> > i m using Genymotion android emulator.
>
> Hm... I must admit I'm not familiar with this, but it doesn't seem
> immediately related. Could be that some update (or something blocked by
> the cups failure) causes it, but I didn't see any additional error
> messages in the attached DpkgTerminalLog.txt.
>
> If you still experience this problem, I would consider filing a separate
> bug against the genymotion package, though feel free to include a link
> back here in case it is releated.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1676482
>
> Title:
>   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
>   pre-removal script returned error exit status 1
>
> Status in cups package in Ubuntu:
>   New
>
> Bug description:
>   error brokencount>0
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: cups-daemon 2.1.3-4
>   ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
>   Uname: Linux 4.4.0-57-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.5
>   Architecture: amd64
>   CupsErrorLog:
>
>   Date: Mon Mar 27 17:12:26 2017
>   ErrorMessage: subprocess new pre-removal script returned error exit
> status 1
>   InstallationDate: Installed on 2016-08-17 (221 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat:
> No destinations added.
>   MachineType: Hewlett-Packard HP 255 G3 Notebook PC
>   Papersize: letter
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic
> root=UUID=5a01c360-8aab-4b9d-87f5-f55f468d86a9 ro quiet splash
> vt.handoff=7
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic
> root=UUID=5a01c360-8aab-4b9d-87f5-f55f468d86a9 ro quiet splash
> vt.handoff=7
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.1
>apt  1.2.19
>   SourcePackage: cups
>   Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
> new pre-removal script returned error exit status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/30/2014
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.16
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: 22CD
>   dmi.board.vendor: Hewlett-Packard
>   dmi.board.version: 93.15
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.chassis.version: Chassis Version
>   dmi.modalias: dmi:bvnInsyde:bvrF.16:bd05/30/2014:svnHewlett-Packard:
> pnHP255G3NotebookPC:pvr0990101600087:
> rvnHewlett-Packard:rn22CD:rvr93.15:cvnHewlett-Packard:
> ct10:cvrChassisVersion:
>   dmi.product.name: HP 255 G3 Notebook PC
>   dmi.product.version: 0990101600087
>   dmi.sys.vendor: Hewlett-Packard
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676482/+subscriptions
>

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  error brokencount>0

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Mar 27 17:12:26 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-17 (221 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard HP 255 G3 Notebook PC
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=5a01c360-8aab-4b9d-87f5-f55f468d86a9 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=5a01c360-8aab-4b9d-87f5-f55f468d86a9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  

[Touch-packages] [Bug 1627743] Re: Arale dash scrolling performance regression between 416 and 420

[Launchpad Bug Tracker]

[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/1627743

Title:
  Arale dash scrolling performance regression between 416 and 420

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  dip between 416 ~60fps and 420 ~50fps

  https://platform-qa-dashboard.canonical.com/dashboard/db/arale-dash

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

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

[Touch-packages] [Bug 1663679] Re: tracker-miner-fs assert failure: *** Error in `/usr/lib/tracker/tracker-miner-fs': double free or corruption (out): 0x000055c09c7eab30 ***

[Launchpad Bug Tracker]

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

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

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

Title:
  tracker-miner-fs assert failure: *** Error in `/usr/lib/tracker
  /tracker-miner-fs': double free or corruption (out):
  0x55c09c7eab30 ***

Status in tracker package in Ubuntu:
  Expired

Bug description:
  When I boot the computer

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: tracker-miner-fs 1.10.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/tracker/tracker-miner-fs': double 
free or corruption (out): 0x55c09c7eab30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Feb 10 18:36:26 2017
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  InstallationDate: Installed on 2014-12-30 (772 days ago)
  InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: tracker
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f561dd8c3a8 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7f561dd8c4b8 "double free or corruption (out)", action=3) at malloc.c:5046
   _int_free (av=, p=, have_lock=) 
at malloc.c:3902
   __GI___libc_free (mem=) at malloc.c:2982
   g_pattern_match () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: tracker-miner-fs assert failure: *** Error in 
`/usr/lib/tracker/tracker-miner-fs': double free or corruption (out): 
0x55c09c7eab30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip epoptes fuse lpadmin mysql mythtv 
plugdev sambashare sudo vboxsf vboxusers video

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

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

[Touch-packages] [Bug 1675892] StacktraceSource.txt

[Brian Murray]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1675892/+attachment/4860492/+files/StacktraceSource.txt

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

Title:
  pulseaudio crashed with SIGABRT

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  A random pulseaudio crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  Uname: Linux 4.10.4-041004-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   1902 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Mar 23 07:51:00 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  Stacktrace:
   #0  
   No locals.
   #1  0x in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x0
  StacktraceTop: ?? ()
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago)
  UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  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.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr: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/1675892/+subscriptions

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

[Touch-packages] [Bug 1675892] ThreadStacktrace.txt

[Brian Murray]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1675892/+attachment/4860493/+files/ThreadStacktrace.txt

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

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

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

Title:
  pulseaudio crashed with SIGABRT

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  A random pulseaudio crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  Uname: Linux 4.10.4-041004-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   1902 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Mar 23 07:51:00 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  Stacktrace:
   #0  
   No locals.
   #1  0x in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x0
  StacktraceTop: ?? ()
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago)
  UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  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.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr: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/1675892/+subscriptions

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

[Touch-packages] [Bug 1675892] Stacktrace.txt

[Brian Murray]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1675892/+attachment/4860491/+files/Stacktrace.txt

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

Title:
  pulseaudio crashed with SIGABRT

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  A random pulseaudio crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  Uname: Linux 4.10.4-041004-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   1902 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Mar 23 07:51:00 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  Stacktrace:
   #0  
   No locals.
   #1  0x in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x0
  StacktraceTop: ?? ()
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago)
  UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  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.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr: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/1675892/+subscriptions

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

[Touch-packages] [Bug 1675892]

[Brian Murray]

StacktraceTop:
 pa_sink_input_assert_ref (o=) at ./pulsecore/sink-input.h:257
 pa_sink_input_finish_move (i=i@entry=0x55eb29defc70, 
dest=dest@entry=0x55eb29d9c350, save=save@entry=false) at 
pulsecore/sink-input.c:1836
 pa_sink_move_all_finish (s=0x55eb29d9c350, q=q@entry=0x55eb29da5cc0, 
save=save@entry=false) at pulsecore/sink.c:917
 card_set_profile (c=0x55eb29eabd90, new_profile=0x55eb29d10880) at 
modules/alsa/module-alsa-card.c:255
 pa_card_set_profile (c=0x55eb29eabd90, profile=profile@entry=0x55eb29d10880, 
save=save@entry=false) at pulsecore/card.c:320

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

Title:
  pulseaudio crashed with SIGABRT

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  A random pulseaudio crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  Uname: Linux 4.10.4-041004-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   1902 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Mar 23 07:51:00 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  Stacktrace:
   #0  
   No locals.
   #1  0x in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x0
  StacktraceTop: ?? ()
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago)
  UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  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.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr: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/1675892/+subscriptions

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

[Touch-packages] [Bug 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate

[Albert Astals Cid]

** Changed in: qtubuntu (Ubuntu)
 Assignee: Albert Astals Cid (aacid) => (unassigned)

** Changed in: unity8 (Ubuntu)
 Assignee: Albert Astals Cid (aacid) => (unassigned)

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

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

Title:
  unity8 freezes for a second while opening a client-side submenu in
  kate

Status in qtmir package in Ubuntu:
  Invalid
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Steps:

  - Launch kate
  - Right-click on its main, text editor, area. A pop-up menu should show up.
  - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with 
"Set Bookmark" and "Clear All Bookmarks" options will show up.

  Expected outcome:
  The sub menu opens immediately and the mouse pointer is responsive throughout

  Actual outcome:
  unity8 freezes for a bit, with mouse pointer becoming unresponsive, before 
finally resuming and showing up the submenu.

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

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

[Touch-packages] [Bug 1604025] Re: CroppedImageMinimumSourceSize loads the image twice in the bad scenario

[Albert Astals Cid]

** Changed in: unity8 (Ubuntu)
 Assignee: Albert Astals Cid (aacid) => (unassigned)

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

Title:
  CroppedImageMinimumSourceSize loads the image twice in the bad
  scenario

Status in qtdeclarative-opensource-src package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  To get the best looking possible Image sometimes we end up loading the
  Image twice, see http://lists.qt-
  project.org/pipermail/development/2016-July/026562.html for an in
  depth explanation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1604025/+subscriptions

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

[Touch-packages] [Bug 1672719] Re: Launcher quicklist should close if tabbing to a different item

[Albert Astals Cid]

** Changed in: unity8 (Ubuntu)
 Assignee: Albert Astals Cid (aacid) => (unassigned)

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

Title:
  Launcher quicklist should close if tabbing to a different item

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:
   * Alt+F1
  - Launcher appears
   * Press down
  - First item of launcher is selected
   * Press right
  - Quicklist of first item of launcher is opened
   * Press tab
  - Second item of launcher is selected BUT quicklist of first item of 
launcher is still open

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

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

[Touch-packages] [Bug 1681908] Re: aa-notify difficult to use with gnome-shell

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.11.0-2ubuntu4

---
apparmor (2.11.0-2ubuntu4) zesty; urgency=medium

  * debian/patches/aa-notify-urgency-normal.patch: adjust the notify-send
urgency to 'normal' to accommodate gnome-shell (LP: #1681908)

 -- Jamie Strandboge   Tue, 11 Apr 2017 18:34:18 +

** Changed in: apparmor (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  aa-notify difficult to use with gnome-shell

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  aa-notify currently calls notify-send with urgency of 'critical'. In
  gnome-shell critical urgency notifications result in a notification
  that must be explicitly clicked to dismiss (ie, they don't time out)
  and gnome-shell does not honor --expire-time with (at least) critical
  urgency. In other popular DEs critical urgency notifications time out.
  We should adjust the urgency to 'normal' to obtain intended behavior
  across DEs.

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

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

[Touch-packages] [Bug 1176127] Re: GLib Application Registers a DBus name under application confinement

[Ted Gould]

** Changed in: glib2.0 (Ubuntu)
 Assignee: Ted Gould (ted) => (unassigned)

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

Title:
  GLib Application Registers a DBus name under application confinement

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Under application confinement applications won't be allowed to
  register names on DBus.  GApplication returns an error if it can't do
  that which makes programs unhappy.  Instead they should just believe
  they are the primary app instance if they're running under isolation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1176127/+subscriptions

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

[Touch-packages] [Bug 1324848] Re: [Gmail] can't switch to another account

[Ted Gould]

** Changed in: url-dispatcher
 Assignee: Ted Gould (ted) => (unassigned)

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

Title:
  [Gmail] can't switch to another account

Status in URL Dispatcher:
  Incomplete
Status in The Webapps-core project:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  When using the Gmail webapp it is currently impossible to switch to
  another account.

  To reproduce:
  - login in Gmail with your user account
  - go to the left hand side menu button
  - select the user account button at the top; you should see an Accounts 
dialog to switch users
  - select 'Sign into another account...,"

  Expected result: you go to the account signon page
  Actual result: nothing happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/url-dispatcher/+bug/1324848/+subscriptions

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

[Touch-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher

[Ted Gould]

** Changed in: mediaplayer-app (Ubuntu)
 Assignee: Ted Gould (ted) => (unassigned)

** Changed in: mediaplayer-app (Ubuntu RTM)
 Assignee: Ted Gould (ted) => (unassigned)

** Changed in: url-dispatcher (Ubuntu)
 Assignee: Ted Gould (ted) => (unassigned)

** Changed in: url-dispatcher (Ubuntu RTM)
 Assignee: Ted Gould (ted) => (unassigned)

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

Title:
  Media Player should not be visible in the app scope and launcher

Status in Canonical System Image:
  Fix Released
Status in Ubuntu UX:
  Fix Committed
Status in mediaplayer-app package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  Triaged
Status in mediaplayer-app package in Ubuntu RTM:
  Fix Released
Status in url-dispatcher package in Ubuntu RTM:
  Invalid

Bug description:
  The mediaplayer is an 'auxiliary app' in the current design approach.
  That means that its purpouse it playback media launched by other apps
  (e.g Messaging) or scopes (e.g. Videos). It should not be launched
  from the App scopes.

  However, the 'Update' section System Settings should still display it
  when an update to mediaplayer is available.

  Current behaviour
  - Mediaplayer app displayed in App Scope, Launcher and Settings

  Desired behaviour
  - Mediaplayer app not displayed in App Scope or Launcher
  - Mediaplayer displayed in Settings > Update

  --- --- --- --- ---

  UX Comment:

  Fix appears partially released.

  Implemented:
  - Mediaplayer app not displayed in App Scope/ Ubuntu Store

  Not implemented:
  - Mediaplayer app not displayed in Launcher (still visible in launcher, can 
be 'pinned' to launcher, etc).
  - Mediaplayer displayed in Settings > Update

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

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

[Touch-packages] [Bug 1656252] Re: Applications fail to start on the second use

[Ted Gould]

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

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

Title:
  Applications fail to start on the second use

Status in Canonical System Image:
  Fix Released
Status in address-book-app package in Ubuntu:
  In Progress
Status in camera-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  zesty desktop
  unity8 session snap 349

  Test Case:
  1. Launch the webbrowser from the app scope
  2. close it (or the app crashes)
  3. Launch the webbrowser from the app scope

  Expected result:
  It starts twice

  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

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

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

[Touch-packages] [Bug 1628589] Re: Need better session management for apps

[Ted Gould]

** Changed in: ubuntu-app-launch (Ubuntu)
 Assignee: Ted Gould (ted) => (unassigned)

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

Title:
  Need better session management for apps

Status in Canonical System Image:
  Triaged
Status in Libertine:
  Triaged
Status in Libertine devel series:
  Triaged
Status in Libertine trunk series:
  Triaged
Status in libertine package in Ubuntu:
  Triaged
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  This is the master bug for better session management for apps.  All
  other bugs affected by this will be dup'ed to this bug.

  Currently, if a user closes an app using the 'X' button on the window,
  many bad things can happen including data loss.

  If a user is editing a document and accidentally hits the X while the
  data is not saved, the user will not be prompted to save and the data
  will be lost.

  Another example is Libertine helper apps can crash when Xmir is
  killed.

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

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

[Touch-packages] [Bug 1670704] Re: No way to discern multiple versions of the same app (from different sources)

[Ted Gould]

** Changed in: ubuntu-app-launch (Ubuntu)
 Assignee: Ted Gould (ted) => (unassigned)

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

Title:
  No way to discern multiple versions of the same app (from different
  sources)

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  In the new world there's basically an infinite number of the same
  application you can have installed at the same time:

  - snap
- multiple different snaps can ship the same application
  - libertine
- you can have multiple containers with the same application
  - deb
- you could have a PPA added that has the same application under a 
different package name

  Today the result is that the app drawer shows all of them, in
  undefined order. This makes it impossible to know which of them you
  launch.

  === Proposal 1 ===

  In the app drawer, have "badges" for apps that have multiple versions
  installed, and a drop-down to select between the different versions.

  Since we'd be grouping in the app drawer, I'd propose to group
  elsewhere in the shell (launcher, switcher), with icon badges
  indicating for each top-level window.

  === Proposal 2 ===

  Have all the different versions listed as usual, but have unique
  badges for those that have multiple versions.

  In this case we'd treat all of them as completely separate in the rest
  of the shell as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170303.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 15:15:58 2017
  InstallationDate: Installed on 2016-05-06 (304 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (105 days ago)

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

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

[Touch-packages] [Bug 1571099] Re: [bq E5] [OTA10.1] Catalan layout differs from shift to normal

[Michael Sheldon]

** Changed in: ubuntu-keyboard (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => In Progress

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

Title:
  [bq E5] [OTA10.1] Catalan layout differs from shift to normal

Status in ubuntu-keyboard package in Ubuntu:
  In Progress

Bug description:
  Holding dot key shows different options depending if shift key is on
  or off (write layout should be the one that appears with caps off)

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

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

[Touch-packages] [Bug 1642767] Re: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.

[Pierre-Louis Bonicoli]

I was able to reproduce this bug on Debian unstable (lxc=2.0.7-2,
libpam-cgfs=2.0.6-1, systemd=232-22, linux-image-4.9.0-2-amd64=4.9.18-1
or even using 4.11.0-rc6-1, libpam-cgm not installed, cgmanager not
installed) with Debian Jessie unprivileged container (created using
download template [1]). Systemd version in the container: 215-17+deb8u6.

In addition to the three symptoms listed in the bug description, here is
another: in the container "/sys/fs/cgroup/systemd" isn't mounted
(systemctl command fails and any attempt to manually mount it will hangs
forever).

It appears there are two problems:

1. When using umask, create lxc cgroups before running lxc-start:

$ mkdir 
/sys/fs/cgroup/systemd/user.slice/user-$UID.slice/session-$XDG_SESSION_ID.scope/lxc
$ mkdir /sys/fs/cgroup/{freezer,memory}/user/$USER/0/lxc

# replace 
$ sudo chgrp  
/sys/fs/cgroup/systemd/user.slice/user-$UID.slice/session-$XDG_SESSION_ID.scope/lxc
$ sudo chgrp  /sys/fs/cgroup/{freezer,memory}/user/$USER/0/lxc

$ chmod g+x 
/sys/fs/cgroup/systemd/user.slice/user-$UID.slice/session-$XDG_SESSION_ID.scope/lxc
$ chmod g+x /sys/fs/cgroup/{memory,freezer}/user/$USER/0/lxc

Start the container, systemd will be able to mount
/sys/fs/cgroup/systemd/:

$ lxc-start -n 

And lxc-stop works, host is able to reboot without hard reset.

2. About the kernel related problem: systemd try to mount
"/sys/fs/cgroup/systemd/" twice ([2]: mount_table and mount_setup): once
using "none,name=systemd,xattr" options then if the first try fails
there is another using "none,name=systemd". The first try returns
"permission denied" and then systemd become stuck at the second try.

Without manually creating the lxc cgroups, I was able to reproduce this
problem using unprivileged container Alpine edge (Alpine doesn't use
systemd):

$ lxc-attach -n alpine_container --clear-env
# mount -t tmpfs tmpfs /sys/fs/cgroup
# mkdir /sys/fs/cgroup/systemd
# mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd
-> mount command hangs, lxc-stop hangs, host needs a hard reset

[1] http://images.linuxcontainers.org/
[2] 
https://github.com/systemd/systemd/blob/1b59cf04aee20525179f81928f1e1794ce970551/src/core/mount-setup.c#L104

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

Title:
  starting any container with umask 007 breaks host system shutdown.
  lxc-stop just hangs.

Status in lxc package in Ubuntu:
  New

Bug description:
  If I have umask 007 (or any other value that masks the world-execute
  bit) when I run lxc-start for the first time after logging in, my host
  system enters a state with the following problems:

  * lxc-stop hangs forever instead of stopping any container, even one that 
wasn't started with umask 007.
  * lxc-stop --kill --nolock hangs in the same way.
  * Attempts to reboot or shut down the host system fail, requiring a hard 
reset to recover.

  When lxc-stop hangs, messages like these appear in syslog every couple
  of minutes:

  Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 
blocked for more than 120 seconds.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091629]   Tainted: P   OE  
 4.4.0-47-generic #68-Ubuntu
  Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 
8800c6febb58 0 12179  12168 0x0104
  Nov 17 01:22:11 hostbox kernel: [ 3360.091638]  8800c6febb58 
8800d318d280 88040c649b80 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091641]  8800c6fec000 
8800345bc088 8800345bc070 
  Nov 17 01:22:11 hostbox kernel: [ 3360.091644]  fffe0001 
8800c6febb70 81830f15 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace:
  Nov 17 01:22:11 hostbox kernel: [ 3360.091653]  [] 
schedule+0x35/0x80
  Nov 17 01:22:11 hostbox kernel: [ 3360.091657]  [] 
rwsem_down_write_failed+0x202/0x350
  Nov 17 01:22:11 hostbox kernel: [ 3360.091662]  [] ? 
kernfs_sop_show_options+0x40/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091666]  [] 
call_rwsem_down_write_failed+0x13/0x20
  Nov 17 01:22:11 hostbox kernel: [ 3360.091669]  [] ? 
down_write+0x2d/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091672]  [] 
grab_super+0x30/0xa0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091674]  [] 
sget_userns+0x152/0x450
  Nov 17 01:22:11 hostbox kernel: [ 3360.091677]  [] ? 
kernfs_sop_show_path+0x50/0x50
  Nov 17 01:22:11 hostbox kernel: [ 3360.091680]  [] 
kernfs_mount_ns+0x7e/0x230
  Nov 17 01:22:11 hostbox kernel: [ 3360.091685]  [] 
cgroup_mount+0x2eb/0x7f0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091687]  [] 
mount_fs+0x38/0x160
  Nov 17 01:22:11 hostbox kernel: [ 3360.091691]  [] 
vfs_kern_mount+0x67/0x110
  Nov 17 01:22:11 hostbox kernel: [ 3360.091694]  [] 

[Touch-packages] [Bug 1675571] Re: Cloud-init update renders secondary addresses to be incompatible with standard tools

[Bug Watch Updater]

** Changed in: resolvconf (Debian)
   Status: Unknown => Won't Fix

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

Title:
  Cloud-init update renders secondary addresses to be incompatible with
  standard tools

Status in cloud-init:
  Confirmed
Status in curtin:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  New
Status in resolvconf package in Debian:
  Won't Fix

Bug description:
  The change of how cloud-init renders 
/etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as 
expected:
  * resolvconf will nullify nameservers
  * if* commands ignore secondary addresses

  [ORIGINAL REPORT]

  Regresion from Bug #1657940.

  When provisioning with multiple eth0 addresses, /etc/resolv.conf is
  empty:

  Consider:
  root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
  address 138.197.98.102
  dns-nameservers 8.8.8.8 8.8.4.4
  gateway 138.197.96.1
  netmask 255.255.240.0

  # control-alias eth0
  iface eth0 inet static
  address 10.17.0.11
  netmask 255.255.0.0

  Which then yields an empty /etc/resolv.conf:
  root@tester:/run/resolvconf# cat interface/eth0.inet

  root@tester:/run/resolvconf# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  The problem is that resolvconfg does pattern matching for eth*.inet.
  The second definition of eth0 has no nameserver and therefore
  overrides the definition.

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

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

[Touch-packages] [Bug 1653323] Re: Severe screen flicker on Unity when terminal maximized

[Damon Lynch]

Appears to be fixed as of 4.10.0-19-generic. I'm relieved!

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

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

Title:
  Severe screen flicker on Unity  when terminal maximized

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  The screen experiences severe flicker when using Nvidia 375.26 on a
  GTX 1070 in 16.10, Unity Desktop -- but only when the terminal is in
  the top left of the screen or maximized, and is full of text.

  I made a video illustrating the problem: http://damonlynch.net/share
  /Ubuntu1610screen-flicker.mp4

  Driver is from the "graphics-drivers" PPA.

  At this point I don't know if it's a hardware problem or software
  problem -- I've never seen anything like it before. I've ruled out the
  DisplayPort cable as a problem, because it exhibits the same problem
  with two different cables.

  The LCD is a Dell UP3017.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 
PST 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .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.3-0ubuntu8.2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 340580/915712 files, 2047147/3661865 blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec 30 23:05:25 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-30-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2016-10-09 (82 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=b2cca22d-b1af-498e-84e2-4f06fd41880d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF6:bd03/01/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 

[Touch-packages] [Bug 1681912] Re: [Zesty] missing dnsmasq package breaks NetworkManager connection sharing feature

[Martin Wimpress]

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

** Changed in: ubuntu-mate-meta (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/1681912

Title:
  [Zesty] missing dnsmasq package breaks NetworkManager connection
  sharing feature

Status in ubuntu-mate:
  New
Status in network-manager package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Invalid

Bug description:
  Network settings in Zesty allow users to define a connection as
  "Shared to other computers", this does not currently work in Ubuntu
  MATE 17.04 Beta 2 at least for wired connections.

  The reason, from the logs is that dnsmasq binary, from dnsmasq package
  is not present:

  [...]
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1052] 
Executing: /sbin/iptables --table nat --insert POSTROUTING --source 
10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255.255.0 --jump 
MASQUERADE
  Apr 11 20:37:22 Edge NetworkManager[946]:  [1491935842.1117] device 
(enp1s0f2): share: (enp1s0f2) failed to start dnsmasq: Could not find "dnsmasq" 
binary
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1119] 
Executing: /sbin/iptables --table nat --delete POSTROUTING --source 
10.42.0.0/255.
  [...]

  ouroumov@Edge:~$ apt-cache policy dnsmasq
  dnsmasq:
    Installed: (none)
    Candidate: 2.76-5
    Version table:
   2.76-5 500
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe i386 Packages

  After installing package dnsmasq, connection sharing works again as
  expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-mate-core 1.190
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 11 20:39:44 2017
  InstallationDate: Installed on 2017-04-05 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package url-dispatcher -
0.1+17.04.20170328-0ubuntu2

---
url-dispatcher (0.1+17.04.20170328-0ubuntu2) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:34:10 +0100

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package libertine-scope -
1.3.2+17.04.20170228-0ubuntu2

---
libertine-scope (1.3.2+17.04.20170228-0ubuntu2) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:33:06 +0100

** Changed in: libertine-scope (Ubuntu)
   Status: New => Fix Released

** Changed in: url-dispatcher (Ubuntu)
   Status: New => Fix Released

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-transfer -
0.2+17.04.20170215-0ubuntu2

---
indicator-transfer (0.2+17.04.20170215-0ubuntu2) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:32:56 +0100

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: New => Fix Released

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-system-settings-online-accounts
- 0.7+17.04.20170308.2-0ubuntu3

---
ubuntu-system-settings-online-accounts (0.7+17.04.20170308.2-0ubuntu3) zesty; 
urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:33:39 +0100

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package pay-service -
15.10+17.04.20170211-0ubuntu2

---
pay-service (15.10+17.04.20170211-0ubuntu2) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:33:12 +0100

** Changed in: indicator-transfer (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package qtmir - 0.5.1+17.04.20170404-0ubuntu2

---
qtmir (0.5.1+17.04.20170404-0ubuntu2) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:33:18 +0100

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

** Changed in: pay-service (Ubuntu)
   Status: New => Fix Released

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Jeffrey Blanchard]

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

I just got a new Dell loaded with 16.04. Using wireless I updated to
16.10 then tried to get on our wired network. I ran into this problem
and comment #6 worked.  Thank you!

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170404.7-0ubuntu3

---
unity8 (8.15+17.04.20170404.7-0ubuntu3) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:33:55 +0100

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-datetime -
15.10+17.04.20170322-0ubuntu2

---
indicator-datetime (15.10+17.04.20170322-0ubuntu2) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:32:50 +0100

** Changed in: indicator-datetime (Ubuntu)
   Status: Triaged => Fix Released

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

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-app-launch -
0.12+17.04.20170404.2-0ubuntu2

---
ubuntu-app-launch (0.12+17.04.20170404.2-0ubuntu2) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:33:25 +0100

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1675571] Re: Cloud-init update renders secondary addresses to be incompatible with standard tools

[Scott Moser]

** Bug watch added: Debian Bug tracker #783596
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783596

** Also affects: resolvconf (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783596
   Importance: Unknown
   Status: Unknown

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

Title:
  Cloud-init update renders secondary addresses to be incompatible with
  standard tools

Status in cloud-init:
  Confirmed
Status in curtin:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  New
Status in resolvconf package in Debian:
  Unknown

Bug description:
  The change of how cloud-init renders 
/etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as 
expected:
  * resolvconf will nullify nameservers
  * if* commands ignore secondary addresses

  [ORIGINAL REPORT]

  Regresion from Bug #1657940.

  When provisioning with multiple eth0 addresses, /etc/resolv.conf is
  empty:

  Consider:
  root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
  address 138.197.98.102
  dns-nameservers 8.8.8.8 8.8.4.4
  gateway 138.197.96.1
  netmask 255.255.240.0

  # control-alias eth0
  iface eth0 inet static
  address 10.17.0.11
  netmask 255.255.0.0

  Which then yields an empty /etc/resolv.conf:
  root@tester:/run/resolvconf# cat interface/eth0.inet

  root@tester:/run/resolvconf# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  The problem is that resolvconfg does pattern matching for eth*.inet.
  The second definition of eth0 has no nameserver and therefore
  overrides the definition.

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

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

[Touch-packages] [Bug 1676482] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Hans Joachim Desserud]

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

> i m using Genymotion android emulator.

Hm... I must admit I'm not familiar with this, but it doesn't seem
immediately related. Could be that some update (or something blocked by
the cups failure) causes it, but I didn't see any additional error
messages in the attached DpkgTerminalLog.txt.

If you still experience this problem, I would consider filing a separate
bug against the genymotion package, though feel free to include a link
back here in case it is releated.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  error brokencount>0

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Mar 27 17:12:26 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-17 (221 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard HP 255 G3 Notebook PC
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=5a01c360-8aab-4b9d-87f5-f55f468d86a9 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=5a01c360-8aab-4b9d-87f5-f55f468d86a9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22CD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 93.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd05/30/2014:svnHewlett-Packard:pnHP255G3NotebookPC:pvr0990101600087:rvnHewlett-Packard:rn22CD:rvr93.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 255 G3 Notebook PC
  dmi.product.version: 0990101600087
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-push -
0.68+17.04.20170211-0ubuntu2

---
ubuntu-push (0.68+17.04.20170211-0ubuntu2) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:33:31 +0100

** Changed in: ubuntu-push (Ubuntu)
   Status: New => Fix Released

** Changed in: content-hub (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package content-hub -
0.3+17.04.20170403-0ubuntu2

---
content-hub (0.3+17.04.20170403-0ubuntu2) zesty; urgency=medium

  * No-change rebuild (LP: #1681870).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com>  Tue, 11 Apr
2017 17:32:34 +0100

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

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1173915] Re: initctl continuously takes 100% of CPU

[Andrew]

This happens daily on my 14.04/64 bit

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

Title:
  initctl continuously takes 100% of CPU

Status in upstart :
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Many programs are fairly slow to start on my computer, despite it
  being relatively new (core i5). Suspecting a heavy CPU usage, I
  started gnome-system-monitor: all processes were displayed at 0% CPU,
  but the overall load was 1.33; 1.33; 1.34.

  Using the "top" command, however, revealed the real CPU use, with the
  "initctl" process taking 100%CPU, even 1 hour after startup.

  I upgraded to roaring ringtail before checking this but the symptoms
  were the same with quantal quetzal, so there is a fair chance the
  causes were identical.

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upstart 1.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  Date: Sun Apr 28 13:04:05 2013
  ExecutablePath: /sbin/initctl
  InstallationDate: Installed on 2012-12-15 (133 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7
  SourcePackage: upstart
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UpstartBugCategory: System

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

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

[Touch-packages] [Bug 1589005] Re: After update DNS work unstable

[Rowan Wookey]

I had an issue that sounds like this, after disconnecting from an
OpenVPN session my DNS would fail, killing dnsmasq and restarting
network manager would resolve the problem.

To fix it I removed all network interfaces (lan/wifi/vpn etc) from
network manager, rebooted, then re-added the interfaces, the problem
appears to have gone away. Hopefully others find this helpful.

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

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  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.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Luca Ciavatta]

Same issue on Acer Aspire ES1-111M-C1LE with Ubuntu 16.10 (before) and
17.04 (now).

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  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
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  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 Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  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: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1681908] [NEW] aa-notify difficult to use with gnome-shell

[Jamie Strandboge]

Public bug reported:

aa-notify currently calls notify-send with urgency of 'critical'. In
gnome-shell critical urgency notifications result in a notification that
must be explicitly clicked to dismiss (ie, they don't time out) and
gnome-shell does not honor --expire-time with (at least) critical
urgency. In other popular DEs critical urgency notifications time out.
We should adjust the urgency to 'normal' to obtain intended behavior
across DEs.

** Affects: apparmor (Ubuntu)
 Importance: Medium
 Assignee: Jamie Strandboge (jdstrand)
 Status: In Progress

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

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

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  aa-notify difficult to use with gnome-shell

Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  aa-notify currently calls notify-send with urgency of 'critical'. In
  gnome-shell critical urgency notifications result in a notification
  that must be explicitly clicked to dismiss (ie, they don't time out)
  and gnome-shell does not honor --expire-time with (at least) critical
  urgency. In other popular DEs critical urgency notifications time out.
  We should adjust the urgency to 'normal' to obtain intended behavior
  across DEs.

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

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

[Touch-packages] [Bug 1557739] Re: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device')

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  apport-bug crashed with termios.error in raw_input_char(): (25,
  'Inappropriate ioctl for device')

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  While running through the install, ubiquity crashed, then apport
  crashed so couldn't file a bug on ubiquity.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CrashReports: 640:999:999:18776:2016-03-15 16:19:14.974973678 
-0400:2016-03-15 16:19:15.974973678 
-0400:/var/crash/_usr_bin_apport-bug.999.crash
  Date: Tue Mar 15 16:19:15 2016
  ExecutablePath: /usr/bin/apport-bug
  InterpreterPath: /usr/bin/python3.5
  LiveMediaBuild: Xubuntu Core 16.04 - amd64 - 20160314
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/apport-bug', 'ubiquity']
  SourcePackage: apport
  Title: apport-bug crashed with termios.error in raw_input_char(): (25, 
'Inappropriate ioctl for device')
  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/apport/+bug/1557739/+subscriptions

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

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

[bugproxy]

--- Comment From maur...@br.ibm.com 2017-04-11 13:43 EDT---
For the record, Guilherme brought to my attention that  commit:

91864f5852f99 net: use net->count to check whether a netns is alive or
not

was the one fixing the issue. The culprit is mentioned in the commit
message:

002d8a1a6c11 ("net: skip genenerating uevents for network namespaces
that are exiting")

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

Title:
  [Regression] Interface configuration not restored after driver
  unbind/bind (generic)

Status in ifupdown package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  Interface configuration not restored after driver unbind/bind
   

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4163  mtu 1500
  inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
  inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 13  bytes 1046 (1.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto ibmveth2
  iface ibmveth2 inet static
address 9.47.68.120
netmask 255.255.240.0
network 9.47.64.0
broadcast 9.47.79.255
gateway 9.47.79.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 9.12.18.2
dns-search pok.stglabs.ibm.com

  auto enP28p96s0f0
  iface enP28p96s0f0 inet static
 address 10.10.10.11
 netmask 255.255.255.0

  root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0
  driver: be2net
  version: 11.1.0.0
  firmware-version: 10.2.252.1913
  expansion-rom-version: 
  bus-info: 001c:60:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: no
  supports-priv-flags: yes

  root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
  /sys/bus/pci/drivers/be2net/unbind

  root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 
  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  remove_id  
uevent  unbind

  root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
  /sys/bus/pci/drivers/be2net/bind

  root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net
  001c:60:00.0  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  
remove_id  uevent  unbind

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4098  mtu 1500
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0
  ifup: interface enP28p96s0f0 already configured

  root@ltciofvtr-s824-lp8:~# ifdown enP28p96s0f0
  RTNETLINK answers: Cannot assign requested address

  root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0

  root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
  enP28p96s0f0: flags=4163  mtu 1500
  inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
  inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
  ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 16  bytes 1344 (1.3 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

   
  ---uname output---
  Linux ltciofvtr-s824-lp8 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 12:52:39 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8286-42A LPAR 

  ---Steps to Reproduce---
   # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind

  # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind
   
  == Comment - Vaishnavi Bhat
  Hi,

  To bind a device to a driver, the device must first not be controlled by any 
other driver. Can you check for 'driver' in the below before you bind ?
   $ tree /sys//bus/pci/devices/001c:60:00.0 

  Thank you.

  == Comment - Murilo Fossa Vicentini
  Just adding some information, this is not a driver specific issue, this was 
also seen with tg3 and i40e adapters . This behavior is a regression when 
compared to Ubuntu 16.04 where the interfaces where properly reconfigured upon 
bind 

[Touch-packages] [Bug 1681901] [NEW] missing packages for kdenlive

[Cgiraud]

Public bug reported:

Kdenlive error at startup: "Missing package Breeze icons" & "Missing app
vlc or xine"

UbuntuStudio Live CD: dccf4a94304ce6eab37eda15b775ca71  zesty-dvd-
amd64.iso

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

** Package changed: indicator-datetime (Ubuntu) => kdenlive (Ubuntu)

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

Title:
  missing packages for kdenlive

Status in kdenlive package in Ubuntu:
  New

Bug description:
  Kdenlive error at startup: "Missing package Breeze icons" & "Missing
  app vlc or xine"

  UbuntuStudio Live CD: dccf4a94304ce6eab37eda15b775ca71  zesty-dvd-
  amd64.iso

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

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

[Touch-packages] [Bug 1665359] Re: apport-gtk crashed with SIGABRT in raise()

[Brian Murray]

** Tags removed: apport-failed-retrace

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

Title:
  apport-gtk crashed with SIGABRT in raise()

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  No further information available.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-lowlatency 4.9.5
  Uname: Linux 4.9.0-15-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Feb 16 14:46:52 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2011-10-14 (1952 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Signal: 6
  SourcePackage: apport
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install

[Matthias Klumpp]

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

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

Title:
  Kubuntu 16.04.1 discover empty after fresh install

Status in appstream package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid
Status in plasma-discover package in Ubuntu:
  Invalid
Status in appstream source package in Xenial:
  Fix Committed
Status in packagekit source package in Xenial:
  Invalid
Status in plasma-discover source package in Xenial:
  Invalid

Bug description:
  [Impact]

   * A previous update made AppStream use modern-style component-ids, thereby 
breaking the Qt library if it is reading data from the cache and if that data 
happens to be a desktop-application.
   * This leads to KDE's Discover not displaying applications.
   * The issue was introduced by a patch to the Xenial version of AppStream, 
and is not present in any other version of the package in Ubuntu, affecting 
Xenial only.

  [Test Case 1]

   * Update the libappstream-qt package, run Discover: All apps should
  be loaded correctly.

  [Regression Potential]

   * Low, this change affects only the Qt bindings and nothing else. The
  change is also a simple string value change.

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

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

[Touch-packages] [Bug 1665359] ThreadStacktrace.txt

[Brian Murray]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1665359/+attachment/4860302/+files/ThreadStacktrace.txt

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

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

** Summary changed:

- apport-gtk crashed with SIGABRT in g_assertion_message()
+ apport-gtk crashed with SIGABRT in raise()

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

Title:
  apport-gtk crashed with SIGABRT in raise()

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  No further information available.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-lowlatency 4.9.5
  Uname: Linux 4.9.0-15-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Feb 16 14:46:52 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2011-10-14 (1952 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Signal: 6
  SourcePackage: apport
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1665359] StacktraceSource.txt

[Brian Murray]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1665359/+attachment/4860301/+files/StacktraceSource.txt

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

Title:
  apport-gtk crashed with SIGABRT in raise()

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  No further information available.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-lowlatency 4.9.5
  Uname: Linux 4.9.0-15-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Feb 16 14:46:52 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2011-10-14 (1952 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Signal: 6
  SourcePackage: apport
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1665359] Stacktrace.txt

[Brian Murray]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1665359/+attachment/4860300/+files/Stacktrace.txt

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

Title:
  apport-gtk crashed with SIGABRT in raise()

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  No further information available.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-lowlatency 4.9.5
  Uname: Linux 4.9.0-15-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Feb 16 14:46:52 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2011-10-14 (1952 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Signal: 6
  SourcePackage: apport
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1665359]

[Brian Murray]

StacktraceTop:
 raise () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 
17.04/i386/report-sandbox/lib/i386-linux-gnu/libc.so.6
 abort () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 
17.04/i386/report-sandbox/lib/i386-linux-gnu/libc.so.6
 g_test_trap_subprocess (test_path=0x83 , usec_timeout=17794492649015600712, 
test_flags=(G_TEST_SUBPROCESS_INHERIT_STDERR | unknown: 4288713752)) at 
../../../../glib/gtestutils.c:2965
 syscall () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 
17.04/i386/report-sandbox/lib/i386-linux-gnu/libc.so.6
 ?? () at ../../../../glib/gthread-posix.c:1380 from 
/mnt/sec-machines/apport-sandbox-dir/Ubuntu 
17.04/i386/report-sandbox/lib/i386-linux-gnu/libglib-2.0.so.0

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

Title:
  apport-gtk crashed with SIGABRT in raise()

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  No further information available.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-lowlatency 4.9.5
  Uname: Linux 4.9.0-15-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Thu Feb 16 14:46:52 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2011-10-14 (1952 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Signal: 6
  SourcePackage: apport
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to zesty on 2017-01-05 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1681884] Re: [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

[spike speigel]

Could this be the same issue as bug #1676547 ??

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

Title:
  [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04
  Zesty

Status in network-manager package in Ubuntu:
  New

Bug description:
  Upon a "clean" upgrade (No software installed except base system from
  ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
  Network Manager fails to detect wiFi device in 17.04 Zesty after a few
  boots/updates.  Wifi works initially.  I apply Zesty updates.  I
  autoremoved some packages.  I reboot.  Wifi is killed.  I cannot
  report the bug using "ubuntu-bug" because I have no network
  connectivity.

  The wifi device was not detected despite re-enabling Dell's Xenial
  repos after upgrades.

  I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
  Plugging ethernet cable into that does not work either.  It seemed the
  adapter was "half" recognized.  Something did show up in Network
  Manager after fiddling with settings, but no network connectivity ever
  occurred.  I can create a separate bug for that if needed.

  I subsequently had to revert back to 16.04 LTS with a clean install to
  report the bug.  I'm not so familiar with what the Dell repos provide
  for Xenial.  Do they provide the drivers needed for the wifi?  Or is
  that supplied through the kernel?  Could the autoremove have caused
  the wifi drivers to be removed?

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

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

[Touch-packages] [Bug 1557739] Re: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device')

[David Pires]

Still occurring with Xubuntu Core 17.04 - amd64 - 20170409

** Tags added: zenial

** Tags removed: zenial
** Tags added: zesty

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

Title:
  apport-bug crashed with termios.error in raw_input_char(): (25,
  'Inappropriate ioctl for device')

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  While running through the install, ubiquity crashed, then apport
  crashed so couldn't file a bug on ubiquity.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CrashReports: 640:999:999:18776:2016-03-15 16:19:14.974973678 
-0400:2016-03-15 16:19:15.974973678 
-0400:/var/crash/_usr_bin_apport-bug.999.crash
  Date: Tue Mar 15 16:19:15 2016
  ExecutablePath: /usr/bin/apport-bug
  InterpreterPath: /usr/bin/python3.5
  LiveMediaBuild: Xubuntu Core 16.04 - amd64 - 20160314
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/apport-bug', 'ubiquity']
  SourcePackage: apport
  Title: apport-bug crashed with termios.error in raw_input_char(): (25, 
'Inappropriate ioctl for device')
  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/apport/+bug/1557739/+subscriptions

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

[Touch-packages] [Bug 1675571] Re: Cloud-init update renders secondary addresses to be incompatible with standard tools

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~utlemming/cloud-init/+git/cloud-init-1/+merge/322382

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

Title:
  Cloud-init update renders secondary addresses to be incompatible with
  standard tools

Status in cloud-init:
  Confirmed
Status in curtin:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  New

Bug description:
  The change of how cloud-init renders 
/etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as 
expected:
  * resolvconf will nullify nameservers
  * if* commands ignore secondary addresses

  [ORIGINAL REPORT]

  Regresion from Bug #1657940.

  When provisioning with multiple eth0 addresses, /etc/resolv.conf is
  empty:

  Consider:
  root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
  address 138.197.98.102
  dns-nameservers 8.8.8.8 8.8.4.4
  gateway 138.197.96.1
  netmask 255.255.240.0

  # control-alias eth0
  iface eth0 inet static
  address 10.17.0.11
  netmask 255.255.0.0

  Which then yields an empty /etc/resolv.conf:
  root@tester:/run/resolvconf# cat interface/eth0.inet

  root@tester:/run/resolvconf# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  The problem is that resolvconfg does pattern matching for eth*.inet.
  The second definition of eth0 has no nameserver and therefore
  overrides the definition.

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

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

[Touch-packages] [Bug 1557739] Re: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device')

[Launchpad Bug Tracker]

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

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

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

Title:
  apport-bug crashed with termios.error in raw_input_char(): (25,
  'Inappropriate ioctl for device')

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  While running through the install, ubiquity crashed, then apport
  crashed so couldn't file a bug on ubiquity.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CrashReports: 640:999:999:18776:2016-03-15 16:19:14.974973678 
-0400:2016-03-15 16:19:15.974973678 
-0400:/var/crash/_usr_bin_apport-bug.999.crash
  Date: Tue Mar 15 16:19:15 2016
  ExecutablePath: /usr/bin/apport-bug
  InterpreterPath: /usr/bin/python3.5
  LiveMediaBuild: Xubuntu Core 16.04 - amd64 - 20160314
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/apport-bug', 'ubiquity']
  SourcePackage: apport
  Title: apport-bug crashed with termios.error in raw_input_char(): (25, 
'Inappropriate ioctl for device')
  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/apport/+bug/1557739/+subscriptions

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

[Touch-packages] [Bug 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install

[Carlo Vanini]

It works for me updating libappstreamqt1 to 0.9.4-1ubuntu3 on Xenial
16.04.2.

Can someone else confirm, please?

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

Title:
  Kubuntu 16.04.1 discover empty after fresh install

Status in appstream package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid
Status in plasma-discover package in Ubuntu:
  Invalid
Status in appstream source package in Xenial:
  Fix Committed
Status in packagekit source package in Xenial:
  Invalid
Status in plasma-discover source package in Xenial:
  Invalid

Bug description:
  [Impact]

   * A previous update made AppStream use modern-style component-ids, thereby 
breaking the Qt library if it is reading data from the cache and if that data 
happens to be a desktop-application.
   * This leads to KDE's Discover not displaying applications.
   * The issue was introduced by a patch to the Xenial version of AppStream, 
and is not present in any other version of the package in Ubuntu, affecting 
Xenial only.

  [Test Case 1]

   * Update the libappstream-qt package, run Discover: All apps should
  be loaded correctly.

  [Regression Potential]

   * Low, this change affects only the Qt bindings and nothing else. The
  change is also a simple string value change.

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

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Łukasz Zemczak]

** Also affects: libertine-scope (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: pay-service (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Also affects: ubuntu-push (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: ubuntu-system-settings-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-click (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: url-dispatcher (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Łukasz Zemczak]

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

** Also affects: indicator-transfer (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681255] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Antonio Contreras]

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

Wrong! The duplicate is https://bugs.launchpad.net/ubuntu/+source
/indicator-datetime/+bug/1681870

This is the original. Please see the date

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  It appears every time I start the OS. Installed using daily build of the 8th 
April 2017.
  OS: Ubuntu 17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr  9 20:11:45 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2017-04-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   LANG=es_ES.UTF-8
   LANGUAGE=es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681255/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

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

** Changed in: content-hub (Ubuntu)
   Status: New => Confirmed

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

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

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

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

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

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

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Antonio Contreras]

Original post: https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1681255

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/content-hub/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681884] Re: [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

[spike speigel]

Both the onboard wifi and ethernet through the Dell DA200 USB-C adapter
work properly in 16.04 LTS running the following kernel:

$ uname -a
Linux blackhole 4.10.0-19-generic #21~16.04.1-Ubuntu SMP Fri Apr 7 08:20:02 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04
  Zesty

Status in network-manager package in Ubuntu:
  New

Bug description:
  Upon a "clean" upgrade (No software installed except base system from
  ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
  Network Manager fails to detect wiFi device in 17.04 Zesty after a few
  boots/updates.  Wifi works initially.  I apply Zesty updates.  I
  autoremoved some packages.  I reboot.  Wifi is killed.  I cannot
  report the bug using "ubuntu-bug" because I have no network
  connectivity.

  The wifi device was not detected despite re-enabling Dell's Xenial
  repos after upgrades.

  I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
  Plugging ethernet cable into that does not work either.  It seemed the
  adapter was "half" recognized.  Something did show up in Network
  Manager after fiddling with settings, but no network connectivity ever
  occurred.  I can create a separate bug for that if needed.

  I subsequently had to revert back to 16.04 LTS with a clean install to
  report the bug.  I'm not so familiar with what the Dell repos provide
  for Xenial.  Do they provide the drivers needed for the wifi?  Or is
  that supplied through the kernel?  Could the autoremove have caused
  the wifi drivers to be removed?

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

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

[Touch-packages] [Bug 1681884] [NEW] [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

[spike speigel]

Public bug reported:

Upon a "clean" upgrade (No software installed except base system from
ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
Network Manager fails to detect wiFi device in 17.04 Zesty after a few
boots/updates.  Wifi works initially.  I apply Zesty updates.  I
autoremoved some packages.  I reboot.  Wifi is killed.  I cannot report
the bug using "ubuntu-bug" because I have no network connectivity.

The wifi device was not detected despite re-enabling Dell's Xenial repos
after upgrades.

I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
Plugging ethernet cable into that does not work either.  It seemed the
adapter was "half" recognized.  Something did show up in Network Manager
after fiddling with settings, but no network connectivity ever occurred.
I can create a separate bug for that if needed.

I subsequently had to revert back to 16.04 LTS with a clean install to
report the bug.  I'm not so familiar with what the Dell repos provide
for Xenial.  Do they provide the drivers needed for the wifi?  Or is
that supplied through the kernel?  Could the autoremove have caused the
wifi drivers to be removed?

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


** Tags: 17.04 9360 autoremove dell latest-bios-1.3.2 manager network repo 
upgrade wifi xenial zesty

** Tags added: latest-bios-1.3.2

** Summary changed:

- [Dell 9360] NetworkManager fails to detect wifi device in 17.04 Zesty
+ [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

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

Title:
  [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04
  Zesty

Status in network-manager package in Ubuntu:
  New

Bug description:
  Upon a "clean" upgrade (No software installed except base system from
  ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
  Network Manager fails to detect wiFi device in 17.04 Zesty after a few
  boots/updates.  Wifi works initially.  I apply Zesty updates.  I
  autoremoved some packages.  I reboot.  Wifi is killed.  I cannot
  report the bug using "ubuntu-bug" because I have no network
  connectivity.

  The wifi device was not detected despite re-enabling Dell's Xenial
  repos after upgrades.

  I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
  Plugging ethernet cable into that does not work either.  It seemed the
  adapter was "half" recognized.  Something did show up in Network
  Manager after fiddling with settings, but no network connectivity ever
  occurred.  I can create a separate bug for that if needed.

  I subsequently had to revert back to 16.04 LTS with a clean install to
  report the bug.  I'm not so familiar with what the Dell repos provide
  for Xenial.  Do they provide the drivers needed for the wifi?  Or is
  that supplied through the kernel?  Could the autoremove have caused
  the wifi drivers to be removed?

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

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

[Touch-packages] [Bug 1675571] Re: Cloud-init update renders secondary addresses to be incompatible with standard tools

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~utlemming/cloud-init/+git/cloud-init-1/+merge/322380

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

Title:
  Cloud-init update renders secondary addresses to be incompatible with
  standard tools

Status in cloud-init:
  Confirmed
Status in curtin:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  New

Bug description:
  The change of how cloud-init renders 
/etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as 
expected:
  * resolvconf will nullify nameservers
  * if* commands ignore secondary addresses

  [ORIGINAL REPORT]

  Regresion from Bug #1657940.

  When provisioning with multiple eth0 addresses, /etc/resolv.conf is
  empty:

  Consider:
  root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
  address 138.197.98.102
  dns-nameservers 8.8.8.8 8.8.4.4
  gateway 138.197.96.1
  netmask 255.255.240.0

  # control-alias eth0
  iface eth0 inet static
  address 10.17.0.11
  netmask 255.255.0.0

  Which then yields an empty /etc/resolv.conf:
  root@tester:/run/resolvconf# cat interface/eth0.inet

  root@tester:/run/resolvconf# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  The problem is that resolvconfg does pattern matching for eth*.inet.
  The second definition of eth0 has no nameserver and therefore
  overrides the definition.

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

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

[Touch-packages] [Bug 1681840] Re: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: gconf (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 135

Status in gconf package in Ubuntu:
  Invalid

Bug description:
  I am unable to use libre office

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gconf2 3.2.6-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Apr 11 18:30:22 2017
  DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:subprocess installed 
post-installation script returned error exit status 135
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 135
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: gconf
  Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 135
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1681255]

[Brian Murray]

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

StacktraceTop:
 __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top 
(av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse 
(old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at 
malloc.c:2400
 _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at 
malloc.c:3862
 __GI___libc_malloc (bytes=260) at malloc.c:2925
 operator new (sz=260) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:50

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  It appears every time I start the OS. Installed using daily build of the 8th 
April 2017.
  OS: Ubuntu 17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr  9 20:11:45 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2017-04-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   LANG=es_ES.UTF-8
   LANGUAGE=es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681255/+subscriptions

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

[Touch-packages] [Bug 1675571] Re: Cloud-init update renders secondary addresses to be incompatible with standard tools

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~utlemming/cloud-init/+git/cloud-init-1/+merge/322379

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

Title:
  Cloud-init update renders secondary addresses to be incompatible with
  standard tools

Status in cloud-init:
  Confirmed
Status in curtin:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  New

Bug description:
  The change of how cloud-init renders 
/etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as 
expected:
  * resolvconf will nullify nameservers
  * if* commands ignore secondary addresses

  [ORIGINAL REPORT]

  Regresion from Bug #1657940.

  When provisioning with multiple eth0 addresses, /etc/resolv.conf is
  empty:

  Consider:
  root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
  address 138.197.98.102
  dns-nameservers 8.8.8.8 8.8.4.4
  gateway 138.197.96.1
  netmask 255.255.240.0

  # control-alias eth0
  iface eth0 inet static
  address 10.17.0.11
  netmask 255.255.0.0

  Which then yields an empty /etc/resolv.conf:
  root@tester:/run/resolvconf# cat interface/eth0.inet

  root@tester:/run/resolvconf# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  The problem is that resolvconfg does pattern matching for eth*.inet.
  The second definition of eth0 has no nameserver and therefore
  overrides the definition.

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

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

[Touch-packages] [Bug 1681255] ThreadStacktrace.txt

[Brian Murray]

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


** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1681255/+attachment/4860275/+files/ThreadStacktrace.txt

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

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

** This bug has been marked a duplicate of bug 1681870
   indicator-datetime-service crashed with SIGABRT in __malloc_assert()

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  It appears every time I start the OS. Installed using daily build of the 8th 
April 2017.
  OS: Ubuntu 17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr  9 20:11:45 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2017-04-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   LANG=es_ES.UTF-8
   LANGUAGE=es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681255/+subscriptions

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

[Touch-packages] [Bug 1681255] Stacktrace.txt

[Brian Murray]

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


** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1681255/+attachment/4860273/+files/Stacktrace.txt

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  It appears every time I start the OS. Installed using daily build of the 8th 
April 2017.
  OS: Ubuntu 17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr  9 20:11:45 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2017-04-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   LANG=es_ES.UTF-8
   LANGUAGE=es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681255/+subscriptions

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

[Touch-packages] [Bug 1681255] StacktraceSource.txt

[Brian Murray]

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


** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1681255/+attachment/4860274/+files/StacktraceSource.txt

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  It appears every time I start the OS. Installed using daily build of the 8th 
April 2017.
  OS: Ubuntu 17.04

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr  9 20:11:45 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2017-04-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   LANG=es_ES.UTF-8
   LANGUAGE=es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681255/+subscriptions

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Iain Lane]

We think this is an undisclosed ABI break and we'll rebuild for it (in a
silo) to see if that works.

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Triaged

** Changed in: indicator-datetime (Ubuntu)
   Importance: Medium => High

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] ThreadStacktrace.txt

[Brian Murray]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1681870/+attachment/4860240/+files/ThreadStacktrace.txt

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

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

** Tags added: iso-testing

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] StacktraceSource.txt

[Brian Murray]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1681870/+attachment/4860239/+files/StacktraceSource.txt

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] Stacktrace.txt

[Brian Murray]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1681870/+attachment/4860238/+files/Stacktrace.txt

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870]

[Brian Murray]

StacktraceTop:
 __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == initial_top 
(av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse 
(old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
 _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
 __GI___libc_malloc (bytes=260) at malloc.c:2925
 operator new (sz=260) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:50

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1681870/+attachment/4860234/+files/ThreadStacktrace.txt

** Tags added: apport-failed-retrace

** Tags removed: need-i386-retrace

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870]

[Apport retracing service]

Stacktrace:
 #0  0xb775dcf9 in ?? ()
 No symbol table info available.
 #1  0x in ?? ()
 No symbol table info available.
StacktraceSource:
 #0  0xb775dcf9 in ?? ()
 #1  0x in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681870] [NEW] indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Dave Morley]

Public bug reported:

Install I386 version of desktop or run live desktop and the indicator is
crashed.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
CurrentDesktop: Unity:Unity7
Date: Tue Apr 11 15:41:03 2017
ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
ExecutableTimestamp: 1490207290
InstallationDate: Installed on 2017-04-11 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
ProcCwd: /home/davmor2
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
Signal: 6
SourcePackage: indicator-datetime
StacktraceTop:
 __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == initial_top 
(av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse 
(old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
 _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
 __GI___libc_malloc (bytes=260) at malloc.c:2925
 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: apport-crash i386 need-i386-retrace zesty

** Information type changed from Private to Public

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  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/indicator-datetime/+bug/1681870/+subscriptions

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

[Touch-packages] [Bug 1681597] Re: DNS broken after >50m of uptime

[Launchpad Bug Tracker]

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

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

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

Title:
  DNS broken after >50m of uptime

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After about 50m of uptime news.ycombinator.com stops working in Chromium: 
news.ycombinator.com’s server's DNS address could not be found. 
DNS_PROBE_FINISHED_NXDOMAIN
  $ host news.ycombinator.com
  Host news.ycombinator.com not found: 2(SERVFAIL)

  This is a *regression* from Ubuntu 16.10, where DNS worked flawlessly.

  Workarounds:
   * 'systemctl restart systemd-resolved' solves the problem for another 50m
   * disable systemd-resolved and use the DNS server directly. This involves 
removing 'resolve [!UNAVAIL=return]' from nsswitch.conf, and disabling the 
systemd-resolved unit

  Logs show DNSSEC related errors, and DNSSEC getting disabled and reenabled:
  -- Logs begin at Mon 2017-04-10 23:10:59 BST, end at Tue 2017-04-11 00:11:14 
BST. --
  Apr 10 23:11:01 bolt systemd[1]: Starting Network Name Resolution...
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Positive Trust Anchors:
  Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 
19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 
23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 
27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 
31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal 
intranet lan local private test
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Using system hostname 'bolt'.
  Apr 10 23:11:01 bolt systemd[1]: Started Network Name Resolution.
  Apr 10 23:11:05 bolt systemd-resolved[1351]: Switching to DNS server 
194.168.4.100 for interface wlp3s0.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Using degraded feature set 
(UDP+EDNS0) for DNS server 194.168.4.100.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question ubuntu.com IN DS: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN DS: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN A: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Server 194.168.4.100 does not 
support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Switching to DNS server 
194.168.8.100 for interface wlp3s0.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: Using degraded feature set 
(UDP+EDNS0) for DNS server 194.168.8.100.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question cvd.clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question cvd.clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question current.cvd.clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question current.cvd.clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question current.cvd.clamav.net IN TXT: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: Server 194.168.8.100 does not 
support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN A: failed-auxiliary
  Apr 10 23:11:52 bolt systemd[1]: Stopping Network Name 

[Touch-packages] [Bug 1681867] [NEW] package initramfs-tools 0.125ubuntu9 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück

[KB5.at]

Public bug reported:

I only reboot the Workstation and then I update with apt dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: initramfs-tools 0.125ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Tue Apr 11 16:11:44 2017
Df:
 
Dmesg:
 
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
InstallationDate: Installed on 2017-03-22 (20 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170313)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package initramfs-tools 0.125ubuntu9 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  2 zurück

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I only reboot the Workstation and then I update with apt dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 11 16:11:44 2017
  Df:
   
  Dmesg:
   
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
  InstallationDate: Installed on 2017-03-22 (20 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170313)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable

[Dimitri John Ledkov]

This change got uploaded into ubuntu on 2017-03-28, before this bug
report was filed, but due to various regressions was not published until
2017-04-08.

With most current Ubuntu 17.04, and 232-21ubuntu2 stable interface names
are used for virtio_net defices based on the bus IDs just like on LPAR
and z/VM. Specifically interfaces names are renamed into: enc2 and enc3
for my xml of the guest, which corresponds to the devno in the xml
definition:

   
  
  
  
  
  
  


  
  
  
  
  
  


I am marking this bug as fix released.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1679674

Title:
  s390x: Interface order in kvm guest image not predictable

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

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

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

[Touch-packages] [Bug 1674201] Re: cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to libudev.so being in a different directory to where libudev.pc searches for it

[mir-ci-bot]

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.28.0

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

Title:
  cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev]
  due to libudev.so being in a different directory to where libudev.pc
  searches for it

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

Bug description:
  Mir fails to build on arm64 cross-compiled:

  [ 11%] Linking CXX shared library ../../lib/libmirplatform.so
  /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
  /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: 
cannot find -ludev
  collect2: error: ld returned 1 exit status

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

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

[Touch-packages] [Bug 1316873] Re: Left mouse button stops working

[Mike Meyer]

It looks like there may be more than one bug here. But let me narrow at
least one of them down some. When it happens to me, my screen locker
quits working. Both slock and xtrlock just blank the screen and exit.
When run from a shell, I get an error message that they can't grab the
cursor. Restarting the window manager clears up both problems, even if I
don't end the session. Since that window manager is spectrum, the only
part of the unity desktop that's running is lightdm.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  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: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1540373] Re: TLD key (.com/.co.uk/etc) inserts period even when there already is one

[Michael Sheldon]

** Changed in: ubuntu-keyboard (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  TLD key (.com/.co.uk/etc) inserts period even when there already is
  one

Status in ubuntu-keyboard package in Ubuntu:
  In Progress

Bug description:
  1. In the Browser app, tap in the address field.
  2. Type “example.” with a period (full stop) at the end.
  3. Realize that the rest of the address could be typed more quickly with the 
“.com” key.
  4. Tap “.com”.

  What you get: “example..com”
  What you should get: “example.com”

  It may save time to fix bug 1473590 at the same time as this bug.

  Problem occurs with: Ubuntu 15.04 (r248)
  Does not occur with: iOS (any version)

  [Originally reported by Dominik Wnęk on ubuntu-phone@ mailing list.
  ]

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

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

[Touch-packages] [Bug 1576235] Re: FTBFS - ubuntu-keyboard - xenial arm64

[Michael Sheldon]

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  FTBFS - ubuntu-keyboard - xenial arm64

Status in Canonical System Image:
  Fix Released
Status in platform-api package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Invalid

Bug description:
  ubuntu-keyboard fails to build on xenial arm64

  https://launchpad.net/ubuntu/+source/ubuntu-
  keyboard/0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1/+build/9278079

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

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

[Touch-packages] [Bug 1565238] Re: Persian(Farsi) layout for Ubuntu Touch

[Michael Sheldon]

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Persian(Farsi) layout for Ubuntu Touch

Status in ubuntu-keyboard:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released

Bug description:
  Hi
  Ubuntu Touch lacks Persian keyboard layout.
  there is pre require for most ubuntu touch users to found desired keyboard 
layout to start using that device in real world.
  i also can help on develop for add this small but important feature
  best regards

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

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

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

[umoser]

In Ubuntu 16.04 LTS the error still persists. Should be fixed asap since
it affects any notebook I am running on 16.04 LTS.

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

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

[Michael Sheldon]

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: In Progress => Fix Released

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

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

Status in Canonical System Image:
  In Progress
Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Released
Status in address-book-service package in Ubuntu:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released
Status in history-service package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Released
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  Fix Released
Status in indicator-location package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-network package in Ubuntu:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-session package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in maliit-framework package in Ubuntu:
  In Progress
Status in mediaplayer-app package in Ubuntu:
  Fix Released
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity-scope-scopes package in Ubuntu:
  Won't Fix
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1681840] Re: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 135

Status in gconf package in Ubuntu:
  New

Bug description:
  I am unable to use libre office

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gconf2 3.2.6-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Apr 11 18:30:22 2017
  DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:subprocess installed 
post-installation script returned error exit status 135
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 135
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: gconf
  Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 135
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1681840] [NEW] package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135

[sandeep kumar]

Public bug reported:

I am unable to use libre office

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gconf2 3.2.6-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Tue Apr 11 18:30:22 2017
DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:subprocess installed 
post-installation script returned error exit status 135
ErrorMessage: subprocess installed post-installation script returned error exit 
status 135
InstallationDate: Installed on 2017-04-11 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: gconf
Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 135
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 135

Status in gconf package in Ubuntu:
  New

Bug description:
  I am unable to use libre office

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gconf2 3.2.6-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Apr 11 18:30:22 2017
  DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:subprocess installed 
post-installation script returned error exit status 135
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 135
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: gconf
  Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 135
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1669440] Re: Does not fall back to English layout

[Launchpad Bug Tracker]

** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-1669440

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

Title:
  Does not fall back to English layout

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Steps:
  * install ubuntu-keyboard-* (other than English)
  * select the newly installed layout in the OSK
  * remove the package again

  Expected:
  * keyboard falls back to an available layout

  Current:
  * blank! http://imgur.com/a/26Vkb

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-keyboard 0.100+17.04.20170301-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar  2 15:02:02 2017
  InstallationDate: Installed on 2016-05-06 (299 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (100 days ago)

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

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

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Robie Basak]

14:45  slashd: I'm sure I asked you this before, and you
answered, but I can't find your answer anywhere, sorry. Are you
proposing your debdiff in commit 40 as ready for upload to Trusty? Or is
it still in progress? And do you have a debdiff for the transitional
package in Xenial please? That needs to go in first.

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

Title:
  isc-dhcp dhclient listens on extra random ports

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

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to take 
the sysctl values into account (net.ipv4.ip_local_port_range & 
net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion 
isc-dhcp upstream doesn't want to rely on kernel for randomization.
   
  There is no realtime configuration to disable the feature or workaround this. 
The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  
  [Regression Potential] 

  * none expected

  I did the split such that users will automatically get isc-dhcp-client-ddns 
installed but users bothered by this bug then will have the option to switch to 
the one without it by uninstalling (isc-dhcp-client-ddns), 
  so existing Trusty users can continue to use this DDNS functionality after 
the SRU without any necessary intervention.

  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Note that this is how Xenial does it.

  [Other Info]
   
   * See : 
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to 
look at my discussion with rbasak on if that approach would be acceptable for 
SRU.

  [Original Description]

  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient
  udp6   0  0 :::45664:::*  
  2659/dhclient

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

-- 
Mailing 

[Touch-packages] [Bug 1375782] Re: Unable to perform search error when syncing Evolution with Google Contacts

[Robert McKee]

This bug appears in Ubuntu Gnome 17.04 (beta), noted by the text that is
raised in Evolution above the address books.

The backend for this address book was unable to parse this query. Invalid 
request URI or header, or unsupported nonstandard parameter: 
http://schemas.google.com/g/2005;>
 
  GData
  invalid
  Bad updated-min timestamp format: 2017-04-08T16:43:09.01 
00:00
 


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

Title:
  Unable to perform search error when syncing Evolution with Google
  Contacts

Status in libgdata package in Ubuntu:
  Fix Released
Status in libgdata source package in Utopic:
  Fix Released
Status in evolution package in Arch Linux:
  New

Bug description:
  [ Description ]

  Google changed their expected date format to fix a bug which libgdata
  was working around. We don't need the workaround any more.

  [ Fix ]

  This is fixed in 0.16.1. I think we should take this update, as it
  includes other bugfixes too. I think it falls under the GNOME MRE. If
  not, we can cherry-pick this one fix.

  This is in vivid already.

  [ QA ]

  If you get the below error, check that upgrading to the new libgdata
  fixes it for you.

  [ Original Report ]

  Hello,

  When trying to synchronise Google Contacts with Evolution, I am
  getting the error message:

  The backend for this address book was unable to parse this query. 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code16:
 Invalid request URI or header, or unsupported nonstandard parameter: 
  http://schemas.google.com/g/2005;>
   
    GData
    invalid
    Bad updated-min timestamp format: 
2014-09-30T12:48:18.01 00:00
   
  

  My system is Ubunru 14.10, Evolution 3.12.6.

  Before updating to Ubuntu 14.10 (in 14.04) it worked without an error.

  Ruben

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

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

[Touch-packages] [Bug 1679691] Re: libseccomp fix - s390: handle multiplexed syscalls correctly

[bugproxy]

** Tags removed: targetmilestone-inin1604
** Tags added: targetmilestone-inin16041

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

Title:
  libseccomp fix - s390: handle multiplexed syscalls correctly

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed
Status in libseccomp source package in Xenial:
  New
Status in libseccomp source package in Yakkety:
  New
Status in libseccomp source package in Zesty:
  Confirmed
Status in libseccomp source package in aa-series:
  New

Bug description:
  Within Xenial version 2.2.3 of seccomp is included.
  With Yaketty version 2.3.1 is available and fixed this problem.

  Even Docker is working on a SNAP solution, please provide the fix to
  16.04.

  
  With following patches this can be applied to 2.2.3 in support of the 16.04 
LTS Release
  16.04

  Here the upstream git commits for the patches:

  0001-arch-fix-a-problem-with-the-rule-rewrites-in-_seccom.patch
  1d63fad4a064b80e0b921b16ed419f3342337ed4
   
  0001-all-block-negative-syscall-numbers-from-the-filter.patch
  51c46f80c1edee863bbc4eb21b03decc44e69a45 

  0001-api-limit-errno-values-to-MAX_ERRNO.patch
  0d287caf43792239b107ee3215b32b8bc901f9c3 

  0001-db-fix-a-minor-style-problem.patch
  61c28579a984a6c4bd87ec585dc6d5cd4cc0e702 

  0001-db-make-the-individual-db-filter-ops-private.patch
  a4478ddcd4e3b34fcd9c526dcf54f0d79b33ac16

  0001-db-store-the-rules-used-to-build-the-filter.patch
  f16f405f61ecdbad202257b61004b85fce64d75c 

  0001-arch-make-use-of-function-tables-instead-of-switch-s.patch
  57df79c166b26d5044e7e27099e6e69671e727dd 

  0001-db-introduce-transaction-support.patch
  9be1538a4ac0e45047a3f1b79691505c3d11ca31 

  0001-arch-move-the-low-level-filter-rule-addition-code-in.patch
  996e445a74823c735757413fda809e1ed0afc7d4 

  0001-arch-enable-more-involved-arch-ABI-specific-rule-cre.patch
  5b42b8cfa25506fa260c8f46b4a063b5cfd09d1c 

  0001-arch-basic-support-for-multiplexed-and-direct-socket.patch
  d32c3bfa4b07add90dcd04292eb4ba278dd103ba 

  0001-arch-generate-both-multiplexed-and-direct-socket-sys.patch
  983835f3e0fd000a42c8beaea9d7fbe72665 

  0001-tests-add-a-test-for-the-different-types-of-socket-s.patch
  099f4214ce4fe5f53cf0f59e96b71bf4d54a8cd6 

  0001-api-add-a-seccomp_version-API-call.patch
  58a7c20d4c2defc1c984c5c7391ecc60093f85fa 

  0001-tests-create-a-simple-live-test-to-verify-we-can-set.patch
  8ed78c3859f476d302995b43d6739f3341f5b37d 

  0001-s390-handle-multiplexed-syscalls-correctly.patch
  47516603828396f85107ea3e2a254958c2bc3ff5 

  0001-arch-fix-the-multiplexed-ipc-syscalls.patch
  3a89bd144885f54aff86f2e275859a1483992edd

  With the following additional commit all tests pass with "make check"

  0001-tests-remove-fuzzing-from-28-sim-arch_x86.tests.patch
  0d8504bc192e0989494df06efc4b186a9f02e20a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679691/+subscriptions

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

[Touch-packages] [Bug 1681832] [NEW] Wrong /dev/hwrng for non-existing generator

[Hadmut Danisch]

Public bug reported:

Hi,

just ran into a problem:

I have some software dealing with openssl and some crypto stuff. I
recently extended it to read bytes from /dev/hwrng if it exists, because
the software should run on a Raspberry Pi as well. The Raspi does not
have a clock and usually no user input, thus lack of randomness, but a
hardware random number generator, so it is necessary to use /dev/hwrng
if it exists.

But now the software aborts on regular (intel) PCs, since my regular
Ubuntu PCs get a /dev/hwrng entry as well, which just throws a „no such
device“ error when trying to read.

For some strange reason there is this device entry even if the device is
not present, causing trouble.


/dev/hwrng should exist only if there is really some hardware generator.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: udev 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
CustomUdevRuleFiles: 50-usb-hbox.rules 50-net-hbox.rules 70-snap.core.rules
Date: Tue Apr 11 14:17:28 2017
InstallationDate: Installed on 2016-04-22 (353 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
 Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-45-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (176 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
dmi.board.vendor: ASRock
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.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr: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.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Wrong /dev/hwrng for non-existing generator

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  just ran into a problem:

  I have some software dealing with openssl and some crypto stuff. I
  recently extended it to read bytes from /dev/hwrng if it exists,
  because the software should run on a Raspberry Pi as well. The Raspi
  does not have a clock and usually no user input, thus lack of
  randomness, but a hardware random number generator, so it is necessary
  to use /dev/hwrng if it exists.

  But now the software aborts on regular (intel) PCs, since my regular
  Ubuntu PCs get a /dev/hwrng entry as well, which just throws a „no
  such device“ error when trying to read.

  For some strange reason there is this device entry even if the device
  is not present, causing trouble.

  
  /dev/hwrng should exist only if there is really some hardware generator.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 50-usb-hbox.rules 50-net-hbox.rules 70-snap.core.rules
  Date: Tue Apr 11 14:17:28 2017
  InstallationDate: Installed on 2016-04-22 (353 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-45-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: systemd
  

[Touch-packages] [Bug 1604025] Re: CroppedImageMinimumSourceSize loads the image twice in the bad scenario

[Timo Jyrinki]

** Changed in: qtdeclarative-opensource-src (Ubuntu)
 Assignee: Timo Jyrinki (timo-jyrinki) => (unassigned)

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

Title:
  CroppedImageMinimumSourceSize loads the image twice in the bad
  scenario

Status in qtdeclarative-opensource-src package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  To get the best looking possible Image sometimes we end up loading the
  Image twice, see http://lists.qt-
  project.org/pipermail/development/2016-July/026562.html for an in
  depth explanation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1604025/+subscriptions

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

[Touch-packages] [Bug 1620173] Re: Qt5 5.6 regression: conversion from QVariant to QString is broken

[Timo Jyrinki]

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: Timo Jyrinki (timo-jyrinki) => (unassigned)

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

Title:
  Qt5 5.6 regression: conversion from QVariant to QString is broken

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  A regression was introduced in Qt5 5.5 - fixed in 5.7 - whereas
  conversion from QVariant to QString is broken for double and float
  values (you can see more details on this here:
  https://bugreports.qt.io/browse/QTBUG-47192).

  The patch fixing this issue is the following:
  
http://code.qt.io/cgit/qt/qtbase.git/patch/src/corelib/tools/qlocale.h?id=726fed0d67013cbfac7921d3d4613ca83406fb0f

  Would it be possible to apply this patch against the package (based on
  Qt5 5.6.1) Ubuntu 16.10 will ship in October? It's a pretty ugly bug,
  which needs addressing. Hopefully the Qt devs can eventually merge
  this patch onto their 5.6 LTS branch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620173/+subscriptions

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

[Touch-packages] [Bug 1661743] Re: XmlListModel with xml string triggers AppArmor denials

[Timo Jyrinki]

** Changed in: qtdeclarative-opensource-src (Ubuntu)
 Assignee: Timo Jyrinki (timo-jyrinki) => (unassigned)

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

Title:
  XmlListModel with xml string triggers AppArmor denials

Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  XmlListModel with xml string triggers AppArmor denials, when the xml
  prop is set no network call should be made since the source is a just
  a string not a url and no source prop is set

  import QtQuick 2.4
  import Ubuntu.Components 1.3
  import Ubuntu.Components.ListItems 1.3 as ListItem

  import QtQuick.XmlListModel 2.0

  import "servers_list.js" as Servers

  MainView {
  objectName: "mainView"
  applicationName: "demo.daker"

  width: units.gu(50)
  height: units.gu(75)

  automaticOrientation: true
  implicitWidth: units.gu(90)
  implicitHeight: units.gu(71)

  ListItem.ItemSelector {
  id: srvSelector
  model: XmlListModel {
  id: srvModel
  xml: Servers.list
  query: "/servers/server"
  XmlRole { name: "hostname"; query: "host/string()" }
  XmlRole { name: "port"; query: "port/string()" }
  }
  containerHeight: srvSelector.itemHeight * 4

  delegate: OptionSelectorDelegate {
  text: hostname + ":" + port;
  }
  }
  }

  # servers_list.js
  .pragma library

  
  var list = '' +
  '80google.com' +
  '80facebook.com' +
  '80twitter.com';

  AppArmor denials :

  QNetworkManagerInterface::QNetworkManagerInterface(QObject*) propsReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.3076" (uid=32011 pid=4922 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene demo") 
interface="org.freedesktop.DBus.Properties" member="GetAll" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1705 comm="NetworkManager ")"
  QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply "An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.3076" (uid=32011 pid=4922 
comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene demo") 
interface="org.freedesktop.NetworkManager" member="GetDevices" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" 
(uid=0 pid=1705 comm="NetworkManager ")"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1661743/+subscriptions

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

[Touch-packages] [Bug 1668982] Re: Backport memory leak fix

[Timo Jyrinki]

This was not done as there two other very big landings before this, and
now the work has ended.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
 Assignee: Timo Jyrinki (timo-jyrinki) => (unassigned)

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

Title:
  Backport memory leak fix

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  https://codereview.qt-project.org/#/c/187028/2

  fixes a small memory leak that happens in some corner case.

  It's not very important but nice to have.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1668982/+subscriptions

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

[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property

[Timo Jyrinki]

** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

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

Title:
  dbus-cpp crash on arm64 in core::dbus::Object::get_property

Status in Canonical System Image:
  Fix Released
Status in dbus-cpp package in Ubuntu:
  Invalid
Status in location-service package in Ubuntu:
  Fix Released
Status in mtp package in Ubuntu:
  Fix Released

Bug description:
  Requests to location service cause crashes on arm64:

  $ system-image-cli -i
  current build number: 23
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-08-30 09:13:12
  version version: 23
  version ubuntu: 20160830
  version device: 20160824.0
  version custom: 20160830

  Steps:
  * flash the above channel (remember --device frieza_arm64)
  * go to a scope using location
  * refresh

  == Stacktrace =
  #0  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, 
__mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49
  __val = -1
  __mem = 0x29
  #1  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, 
__mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82
  __val = -1
  __mem = 0x29
  #2  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at 
/usr/include/c++/5/bits/shared_ptr_base.h:147
  #3  0x007f97922a28 in 
std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2>
 const&) (this=this@entry=0x8b34558, __r=...) at 
/usr/include/c++/5/bits/shared_ptr_base.h:678
  __tmp = 0x8b34ba0
  #4  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867
  property = 
  #5  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93
  property = 
  #6  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162
  property = 
  #7  0x007f97931c08 in 
com::ubuntu::location::service::Stub::Stub(std::shared_ptr 
const&) (object=warning: can't find linker symbol for virtual table for 
`std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value
  warning: can't find linker symbol for virtual table for 
`std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  Date: Tue Aug 30 09:39:24 2016
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  DistroRelease: Ubuntu 16.04
  Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  PackageArchitecture: arm64
  Tags: third-party-packages xenial
  Uname: Linux 3.10.93+ aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video
  _MarkForUpload: True

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

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