[Group.of.nepali.translators] [Bug 1594681] Re: Don't override IM variables

2016-08-18 Thread Bug Watch Updater 
** Changed in: gnome-session
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1594681

Title:
  Don't override IM variables

Status in gnome-session:
  Fix Released
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-session source package in Xenial:
  In Progress
Status in gnome-settings-daemon source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Currently these variable settings are hardcoded in gnome-session and
  gnome-settings-daemon:

  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  That way the use of alternative IM frameworks, for instance fcitx, is
  prevented. The variables should only be set if they are empty, so the
  values set by im-config are honored.

  [Test Case]

  * Install Ubuntu GNOME
  * Install both the gnome-session and gnome-settings-daemon proposed updates
  * Install fcitx
  * Set fcitx as the input method:
    im-config -n fcitx
  * Relogin
  * Check the IM-related environment variables:
    env | grep -E '_IM|XMOD'

  After the proposed uploads of gnome-session and gnome-settings-daemon,
  those variables are consistently (unlike before) set to "fcitx".

  [Regression Potential]

  Low. im-config sets "ibus" by default in Ubuntu GNOME anyway. This
  change prevents an inconsistent input method configuration for users
  who have actively chosen some other IM framework.

  The gnome-settings-daemon change was included upstream in 3.19.3 and
  the gnome-session change was included upstream in 3.21.90.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1602579] Re: the system hangs in the dma driver when reboot or shutdown on a baytrail-m laptop

2016-08-18 Thread Hui Wang 
** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1602579

Title:
  the system hangs in the dma driver when reboot or shutdown on a
  baytrail-m laptop

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  1. System got hang on reboot of installation phase 1;
  2. Power off system by long-press power button, then power on system again.
  3. System got hang on power off of installation phase 2.

  The hang issue blocked the installation. Can not finish the
  installation procession.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1602579/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1594681] Re: Don't override IM variables

2016-08-18 Thread Launchpad Bug Tracker 
This bug was fixed in the package gnome-session - 3.20.2-1ubuntu2

---
gnome-session (3.20.2-1ubuntu2) yakkety; urgency=medium

  * debian/patches/dont_override_IM_variables.patch:
- Honor values set by e.g. im-config, and with that give users
  the option to use fcitx or other framework (LP: #1594681).

 -- Gunnar Hjalmarsson   Sun, 14 Aug 2016 02:04:00
+0200

** Changed in: gnome-session (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1594681

Title:
  Don't override IM variables

Status in gnome-session:
  Confirmed
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-session source package in Xenial:
  In Progress
Status in gnome-settings-daemon source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Currently these variable settings are hardcoded in gnome-session and
  gnome-settings-daemon:

  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  That way the use of alternative IM frameworks, for instance fcitx, is
  prevented. The variables should only be set if they are empty, so the
  values set by im-config are honored.

  [Test Case]

  * Install Ubuntu GNOME
  * Install both the gnome-session and gnome-settings-daemon proposed updates
  * Install fcitx
  * Set fcitx as the input method:
    im-config -n fcitx
  * Relogin
  * Check the IM-related environment variables:
    env | grep -E '_IM|XMOD'

  After the proposed uploads of gnome-session and gnome-settings-daemon,
  those variables are consistently (unlike before) set to "fcitx".

  [Regression Potential]

  Low. im-config sets "ibus" by default in Ubuntu GNOME anyway. This
  change prevents an inconsistent input method configuration for users
  who have actively chosen some other IM framework.

  The gnome-settings-daemon change was included upstream in 3.19.3 and
  the gnome-session change was included upstream in 3.21.90.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1614618] Re: hv-fcopy-daemon.service system failed start

2016-08-18 Thread Joseph Salisbury 
Is it possible for you to test other kernels with that instance?  It
would be good to confirm this is in fact a regression and bisect it
down.

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Tags added: kernel-da-key kernel-hyper-v

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614618

Title:
  hv-fcopy-daemon.service system failed start

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I booted a  yakkety system on azure, and saw

  $ systemctl status hv-fcopy-daemon.service --no-pager --full 
  ● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon
 Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Thu 2016-08-18 16:01:51 UTC; 
32min ago
   Main PID: 2291 (code=exited, status=1/FAILURE)

  Aug 18 16:01:51 ubuntu systemd[1]: Started Hyper-V File Copy Protocol Daemon.
  Aug 18 16:01:51 ubuntu systemd[1]: hv-fcopy-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Aug 18 16:01:51 ubuntu systemd[1]: hv-fcopy-daemon.service: Unit entered 
failed state.
  Aug 18 16:01:51 ubuntu systemd[1]: hv-fcopy-daemon.service: Failed with 
result 'exit-code'.

  Also, random information but surprising none the less:
  $ systemd-analyze 
  Startup finished in 5min 14.289s (kernel) + 1min 43.164s (userspace) = 6min 
57.454s

  $ systemd-analyze critical-chain 
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  graphical.target @1min 43.124s
  └─multi-user.target @1min 43.124s
└─ephemeral-disk-warning.service @1min 42.888s +235ms
  └─cloud-final.service @1min 39.480s +3.407s
└─cloud-config.service @1min 2.517s +36.961s
  └─network-online.target @1min 2.464s
└─cloud-init.service @35.453s +26.967s
  └─networking.service @32.799s +2.622s
└─network-pre.target @32.766s
  └─cloud-init-local.service @12.044s +20.690s
└─local-fs.target @12.030s
  └─mnt.mount @1min 29.655s
└─dev-sdb1.device @1min 8.310s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-cloud-tools-common 4.4.0-34.53
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 18 16:01 seq
   crw-rw 1 root audio 116, 33 Aug 18 16:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Aug 18 16:31:54 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PackageArchitecture: all
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=314ea127-227e-4b64-b5b4-d70ab0fb7eb7 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.160
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

[Group.of.nepali.translators] [Bug 1614113] Re: New upstream microreleases 9.1.23, 9.3.14, 9.5.4

2016-08-18 Thread Launchpad Bug Tracker 
This bug was fixed in the package postgresql-9.3 - 9.3.14-0ubuntu0.14.04

---
postgresql-9.3 (9.3.14-0ubuntu0.14.04) trusty-security; urgency=medium

  * New upstream security/bug fix release (LP: #1614113):
- Fix possible mis-evaluation of nested CASE-WHEN expressions
  A CASE expression appearing within the test value subexpression of
  another CASE could become confused about whether its own test value was
  null or not.  Also, inlining of a SQL function implementing the equality
  operator used by a CASE expression could result in passing the wrong
  test value to functions called within a CASE expression in the SQL
  function's body.  If the test values were of different data types, a
  crash might result; moreover such situations could be abused to allow
  disclosure of portions of server memory.  (CVE-2016-5423)

- Fix client programs' handling of special characters in database and role
  names
  Numerous places in vacuumdb and other client programs could become
  confused by database and role names containing double quotes or
  backslashes.  Tighten up quoting rules to make that safe. Also, ensure
  that when a conninfo string is used as a database name parameter to
  these programs, it is correctly treated as such throughout.

  Fix handling of paired double quotes in psql's \connect and \password
  commands to match the documentation.

  Introduce a new -reuse-previous option in psql's \connect command to
  allow explicit control of whether to re-use connection parameters from a
  previous connection.  (Without this, the choice is based on whether the
  database name looks like a conninfo string, as before.)  This allows
  secure handling of database names containing special characters in
  pg_dumpall scripts.

  pg_dumpall now refuses to deal with database and role names containing
  carriage returns or newlines, as it seems impractical to quote those
  characters safely on Windows.  In future we may reject such names on the
  server side, but that step has not been taken yet.

  These are considered security fixes because crafted object names
  containing special characters could have been used to execute commands
  with superuser privileges the next time a superuser executes pg_dumpall
  or other routine maintenance operations.  (CVE-2016-5424)

- Details:
http://www.postgresql.org/docs/9.3/static/release-9-3-14.html

 -- Martin Pitt   Wed, 17 Aug 2016 16:37:41
+0200

** Changed in: postgresql-9.3 (Ubuntu Trusty)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614113

Title:
  New upstream microreleases 9.1.23, 9.3.14, 9.5.4

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.1 source package in Precise:
  Fix Released
Status in postgresql-9.1 source package in Trusty:
  Fix Released
Status in postgresql-9.3 source package in Trusty:
  Fix Released
Status in postgresql-9.5 source package in Xenial:
  Fix Released
Status in postgresql-9.5 source package in Yakkety:
  Fix Released

Bug description:
  Last week PostgreSQL published new microreleases:
  https://www.postgresql.org/about/news/1688/

  These contain two CVEs, thus should go via -security.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1614113] Re: New upstream microreleases 9.1.23, 9.3.14, 9.5.4

2016-08-18 Thread Launchpad Bug Tracker 
This bug was fixed in the package postgresql-9.1 - 9.1.23-0ubuntu0.12.04

---
postgresql-9.1 (9.1.23-0ubuntu0.12.04) precise-security; urgency=medium

  * New upstream security/bug fix release (LP: #1614113)
- Fix possible mis-evaluation of nested CASE-WHEN expressions
  A CASE expression appearing within the test value subexpression of
  another CASE could become confused about whether its own test value was
  null or not.  Also, inlining of a SQL function implementing the equality
  operator used by a CASE expression could result in passing the wrong
  test value to functions called within a CASE expression in the SQL
  function's body.  If the test values were of different data types, a
  crash might result; moreover such situations could be abused to allow
  disclosure of portions of server memory.  (CVE-2016-5423)

- Fix client programs' handling of special characters in database and role
  names
  Numerous places in vacuumdb and other client programs could become
  confused by database and role names containing double quotes or
  backslashes.  Tighten up quoting rules to make that safe. Also, ensure
  that when a conninfo string is used as a database name parameter to
  these programs, it is correctly treated as such throughout.

  Fix handling of paired double quotes in psql's \connect and \password
  commands to match the documentation.

  Introduce a new -reuse-previous option in psql's \connect command to
  allow explicit control of whether to re-use connection parameters from a
  previous connection.  (Without this, the choice is based on whether the
  database name looks like a conninfo string, as before.)  This allows
  secure handling of database names containing special characters in
  pg_dumpall scripts.

  pg_dumpall now refuses to deal with database and role names containing
  carriage returns or newlines, as it seems impractical to quote those
  characters safely on Windows.  In future we may reject such names on the
  server side, but that step has not been taken yet.

  These are considered security fixes because crafted object names
  containing special characters could have been used to execute commands
  with superuser privileges the next time a superuser executes pg_dumpall
  or other routine maintenance operations.  (CVE-2016-5424)

   - Details:
https://www.postgresql.org/docs/9.1/static/release-9-1-23.html

 -- Martin Pitt   Wed, 17 Aug 2016 16:18:31
+0200

** Changed in: postgresql-9.5 (Ubuntu Xenial)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614113

Title:
  New upstream microreleases 9.1.23, 9.3.14, 9.5.4

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.1 source package in Precise:
  Fix Released
Status in postgresql-9.1 source package in Trusty:
  Fix Released
Status in postgresql-9.3 source package in Trusty:
  In Progress
Status in postgresql-9.5 source package in Xenial:
  Fix Released
Status in postgresql-9.5 source package in Yakkety:
  Fix Released

Bug description:
  Last week PostgreSQL published new microreleases:
  https://www.postgresql.org/about/news/1688/

  These contain two CVEs, thus should go via -security.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1614113] Re: New upstream microreleases 9.1.23, 9.3.14, 9.5.4

2016-08-18 Thread Launchpad Bug Tracker 
This bug was fixed in the package postgresql-9.1 - 9.1.23-0ubuntu0.14.04

---
postgresql-9.1 (9.1.23-0ubuntu0.14.04) trusty-security; urgency=medium

  * New upstream bug fix release (LP: #1614113). No effective changes for
PL/Perl, the version must just be higher than the one in precise, to not
break upgrades.

 -- Martin Pitt   Wed, 17 Aug 2016 16:30:41
+0200

** Changed in: postgresql-9.1 (Ubuntu Trusty)
   Status: In Progress => Fix Released

** Changed in: postgresql-9.1 (Ubuntu Precise)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614113

Title:
  New upstream microreleases 9.1.23, 9.3.14, 9.5.4

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.1 source package in Precise:
  Fix Released
Status in postgresql-9.1 source package in Trusty:
  Fix Released
Status in postgresql-9.3 source package in Trusty:
  In Progress
Status in postgresql-9.5 source package in Xenial:
  Fix Released
Status in postgresql-9.5 source package in Yakkety:
  Fix Released

Bug description:
  Last week PostgreSQL published new microreleases:
  https://www.postgresql.org/about/news/1688/

  These contain two CVEs, thus should go via -security.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1612669] Re: wrong PPA series used if system name not Ubuntu

2016-08-18 Thread Jonathan Riddell 
** Changed in: software-properties (Ubuntu Xenial)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1612669

Title:
  wrong PPA series used if system name not Ubuntu

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Released
Status in software-properties source package in Yakkety:
  Fix Released

Bug description:
  If the DISTRIB_ID in /etc/lsb-release is not 'ubuntu' add-apt-
  repositories will use the latest series of the PPA even if the
  DISTRIB_CODENAME would match with what is available in the PPA.

  # Test Case

  - change lsb-release to say DISTRIB_ID=yolo
  - copy /usr/share/python-apt/templates/Ubuntu.info to 
/usr/share/python-apt/templates/yolo.info
  - sudo add-apt-repository ppa:graphics-drivers/ppa 
  - should add xenial to sources.list.d

  # Regression potential

  The current behavior of using the latest series is last ditch effort
  at come up with anything valid. The proposed change simply extends the
  acceptable deviation from 100 match.

  # Other info

  Change has been used in production in KDE neon for months now. No side
  effects observed.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1614565] Re: ISST-LTE:pKVM311:lotg5:Ubutu16041:lotg5 crashed @ writeback_sb_inodes+0x30c/0x590

2016-08-18 Thread Tim Gardner 
git describe --contains dc5ff2b1d66f21c27a4c37236636dff6946437e4
v4.8-rc1~22^2~13

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: New

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

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Taco Screen team (taco-screen-team) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614565

Title:
  ISST-LTE:pKVM311:lotg5:Ubutu16041:lotg5 crashed @
  writeback_sb_inodes+0x30c/0x590

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - PRIYA M. A  - 2016-06-17 10:01:28 ==
  Problem Description:
  
  - lotg5 crashed at writeback_sb_inodes+0x30c/0x590

  Steps to re-create:
  ==
  - Install lotg5 with Ubuntu16041(4.4.0-24-generic)
  - Start the regression tests in lotg5
  Logs:
  
  root@lotg5:~# show.report.py
  HOSTNAMEKERNEL VERSION  DISTRO INFO
  ---
  lotg5   4.4.0-24-genericUbuntu 16.04 LTS \n \l

   Current Time: Fri Jun 17 01:10:46 2016 
  Job-ID  FOCUS   Start-Time  DurationFunction
  --  -   --  
  1   BASE20160614-05:50:19   67.0 hr(s) 20.0 min(s)  Test
  2   IO  20160614-05:50:26   67.0 hr(s) 20.0 min(s)  IO_Focus
  3   NFS 20160614-06:24:35   66.0 hr(s) 46.0 min(s)  
DistributeFS_Testing
  4   TCP 20160614-06:32:03   66.0 hr(s) 38.0 min(s)  
networkTest2lotg3

  FOCUS   BASEIO  NFS TCP SUM
  TOTAL   48647   1825517 82690   133679
  FAIL50280   0   24  5052
  PASS43619   1825517 82666   128627
  (%) (89%)   (100%)  (100%)  (99%)   (96%)

  DLPAR is not tested!
  root@lotg5:~#

  - After 65+ hr of execution lotg5 crashed with follwoing call traces
  Logs:
  
  [root@lotkvm ~]# virsh console lotg5
  Connected to domain lotg5
  Escape character is ^]

  0:mon> c
  cpus stopped: 0x0 0x4 0x8 0xc
  0:mon> d
      ||
  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000c4f4b620]
  pc: c0323720: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c0326dbc: writeback_sb_inodes+0x30c/0x590
  sp: c000c4f4b8a0
 msr: 80019033
 dar: 0
   dsisr: 4000
current = 0xc0017191cf60
paca= 0xc7b4   softe: 0irq_happened: 0x01
  pid   = 5792, comm = kworker/u32:5
  0:mon> t
  [c000c4f4b900] c0326dbc writeback_sb_inodes+0x30c/0x590
  [c000c4f4ba10] c0327124 __writeback_inodes_wb+0xe4/0x150
  [c000c4f4ba70] c032758c wb_writeback+0x30c/0x450
  [c000c4f4bb40] c032803c wb_workfn+0x14c/0x570
  [c000c4f4bc50] c00dd1d0 process_one_work+0x1e0/0x5a0
  [c000c4f4bce0] c00dd724 worker_thread+0x194/0x680
  [c000c4f4bd80] c00e61e0 kthread+0x110/0x130
  [c000c4f4be30] c0009538 ret_from_kernel_thread+0x5c/0xa4
  --- Exception: 0  at 
  0:mon>

  
  == Comment: #4 - Chandan Kumar  - 2016-06-20 06:23:33 ==
  dmesg log:
  -
  [251403.003999] EXT4-fs (loop0): mounted filesystem without journal. Opts: 
(null)
  [251403.471118] Unable to handle kernel paging request for data at address 
0x
  [251403.473391] Faulting instruction address: 0xc0323720  <<  PC
  -

  0:mon> di c0323720
  c0323720  e93fld  r9,0(r31)  
  // [R31 = , trying to de-reference null address]
  c0323724  39290050addir9,r9,80
  c0323728  7fbf4840cmpld   cr7,r31,r9

  

  Dominic,

  Can you please take a look and assign this to suitable developer.

  Thanks,
  Chandan

  == Comment: #6 - Laurent Dufour  - 2016-06-20 
13:03:15 ==
  It sounds that inode->i_wb has been cleared while waiting for IO to be 
dropped in writeback_sb_inodes().

  That's need to be double checked...

  == Comment: #10 - Laurent Dufour  - 2016-06-21 
05:11:35 ==
  That seems to be an already known issue raised by commit 43d1c0eb7e11 "block: 
detach bdev inode from its wb in __blkdev_put()".

  There is a patch pushed on the lkml but there is still on going discussion 
about it :
  https://patchwork.kernel.org/patch/9184495/

[Group.of.nepali.translators] [Bug 1614560] [NEW] Xenial update to v4.4.18 stable release

2016-08-18 Thread Tim Gardner 
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.4.18 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.4.18 stable release shall be
applied:

tcp: enable per-socket rate limiting of all 'challenge acks'
ipv4: reject RTNH_F_DEAD and RTNH_F_LINKDOWN from user space
bonding: set carrier off for devices created through netlink
net: bgmac: Fix infinite loop in bgmac_dma_tx_add()
net/irda: fix NULL pointer dereference on memory allocation failure
qed: Fix setting/clearing bit in completion bitmap
tcp: consider recv buf for the initial window scale
ipath: Restrict use of the write() interface
scsi: ignore errors from scsi_dh_add_device()
HID: sony: do not bail out when the sixaxis refuses the output report
i2c: i801: Allow ACPI SystemIO OpRegion to conflict with PCI BAR
arm: oabi compat: add missing access checks
KEYS: 64-bit MIPS needs to use compat_sys_keyctl for 32-bit userspace
Revert "s390/kdump: Clear subchannel ID to signal non-CCW/SCSI IPL"
random: strengthen input validation for RNDADDTOENTCNT
devpts: clean up interface to pty drivers
x86/mm/pat: Add support of non-default PAT MSR setting
x86/mm/pat: Add pat_disable() interface
x86/mm/pat: Replace cpu_has_pat with boot_cpu_has()
x86/mtrr: Fix Xorg crashes in Qemu sessions
x86/mtrr: Fix PAT init handling when MTRR is disabled
x86/xen, pat: Remove PAT table init code from Xen
x86/pat: Document the PAT initialization sequence
x86/mm/pat: Fix BUG_ON() in mmap_mem() on QEMU/i386
drm/i915: Pretend cursor is always on for ILK-style WM calculations (v2)
x86/syscalls/64: Add compat_sys_keyctl for 32-bit userspace
block: fix use-after-free in seq file
sysv, ipc: fix security-layer leaking
fuse: fsync() did not return IO errors
fuse: fuse_flush must check mapping->flags for errors
fuse: fix wrong assignment of ->flags in fuse_send_init()
fs/dcache.c: avoid soft-lockup in dput()
crypto: gcm - Filter out async ghash if necessary
crypto: scatterwalk - Fix test in scatterwalk_done
ext4: check for extents that wrap around
ext4: fix deadlock during page writeback
ext4: don't call ext4_should_journal_data() on the journal inode
ext4: validate s_reserved_gdt_blocks on mount
ext4: short-cut orphan cleanup on error
ext4: fix reference counting bug on block allocation error
mm: memcontrol: fix cgroup creation failure after many small jobs
mm: memcontrol: fix swap counter leak on swapout from offline cgroup
mm: memcontrol: fix memcg id ref counter on swap charge move
Linux 4.4.18

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

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614560

Title:
  Xenial update to v4.4.18 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.18 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.18 stable release shall be
  applied:

  tcp: enable per-socket rate limiting of all 'challenge acks'
  ipv4: reject RTNH_F_DEAD and RTNH_F_LINKDOWN from user space
  bonding: set carrier off for devices created through netlink
  net: bgmac: Fix infinite loop in bgmac_dma_tx_add()
  net/irda: fix NULL pointer dereference on memory allocation failure
  qed: Fix setting/clearing bit in completion bitmap
  tcp: consider recv buf for the initial window scale
  ipath: Restrict use of the write() interface
  scsi: ignore errors from scsi_dh_add_device()
  HID: sony: do not bail out when the sixaxis refuses the output report
  i2c: i801: Allow ACPI SystemIO OpRegion to conflict with PCI BAR
  arm: oabi compat: add missing access checks
  KEYS: 64-bit MIPS

[Group.of.nepali.translators] [Bug 1608953] Re: PostgreSQL does not start in lx-brand container

2016-08-18 Thread Martin Pitt 
OK, thanks. Marking this as "hw-specific" then, which is not entirely
accurate, but it essentially means "only the reporter can test a stable
release update". I'll pull in the patch into the xenial branch and will
ask you for testing once it gets into xenial-proposed (which might still
take a while as this is low-priority). Thanks!

** Summary changed:

- PostgreSQL does not start in container
+ PostgreSQL does not start in lx-brand container

** Tags added: hw-specific

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1608953

Title:
  PostgreSQL does not start in lx-brand container

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

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

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

  

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

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

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

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

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

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

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

  commit 3a18b60489504056f9b0b1a139439cbfa60a87e1

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

  

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1614131] Re: [SRU] OpenStack Mitaka point releases

2016-08-18 Thread Corey Bryant 
** No longer affects: sahara (Ubuntu)

** No longer affects: sahara (Ubuntu Xenial)

** Description changed:

  This SRU will include the following point releases:
  aodh 2.0.4
  cinder 8.1.0
  keystone 9.1.0
  nova 13.1.1
- sahara 4.0.1

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614131

Title:
  [SRU] OpenStack Mitaka point releases

Status in aodh package in Ubuntu:
  Invalid
Status in cinder package in Ubuntu:
  Invalid
Status in keystone package in Ubuntu:
  Invalid
Status in nova package in Ubuntu:
  Invalid
Status in aodh source package in Xenial:
  New
Status in cinder source package in Xenial:
  New
Status in keystone source package in Xenial:
  New
Status in nova source package in Xenial:
  New

Bug description:
  This SRU will include the following point releases:
  aodh 2.0.4
  cinder 8.1.0
  keystone 9.1.0
  nova 13.1.1

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1614322] Re: [SRU] New stable micro release 2.15

2016-08-18 Thread Launchpad Bug Tracker 
This bug was fixed in the package snapcraft - 2.15+16.10.1

---
snapcraft (2.15+16.10.1) yakkety; urgency=medium

  [ Harald Sitter ]
  * add multiple generator script options to autotools (#679)

  [ Sam Yaple ]
  * python2 plugin: Add support for constraints (#657)

  [ Blake Rouse ]
  * Add option disable-parallel for all plugins. (#698)
  * python3 plugin: allow setup.py to work on some projects. (#718)

  [ Christian Ehrhardt ]
  * fix checker errors to let runtests.sh pass again (#717)

  [ Dan Watkins ]
  * python plugins: add process-dependency-links option (#734)

  [ Leo Arias ]
  * Start the fake parts server only in the tests that need it. (#720)
(LP: #1611828)
  * In travis, install the static checkers with pip. (#724)
  * go plugin: add a go-buildtags property to the plugin (#733)

  [ Joe Talbott ]
  * Set owner/group for directories in stage and prime (#723)
  * parser - Return non-zero code for wiki errors. (#658)
  * Factor parts config into snapcraft/internal/parts.py (#731)

  [ Kyle Fazzari ]
  * Use link_or_copy instead of just hard-links for deb cache. (#728)
  * Support having the snapcraft.yaml in a subdir. (#725)
  * Dump plugin: Don't remove install directory. (#729)

  [ Jason Hobbs ]
  * Add artifacts option to make plugin. (#715)

  [ Michael McCracken ]
  * Clarification of make plugin help text (#730)

  [ Sergio Schvezov ]
  * Globally cache stage-packages (#677)
  * Remove store dispute logic (#732)
  * New upstream release 2.15 (LP: #1614322)

 -- Sergio Schvezov   Wed, 17 Aug 2016
17:47:44 -0300

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614322

Title:
  [SRU] New stable micro release 2.15

Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  This is an SRU bug to release 2.15 of snapcraft which follows the
  guidelines defined in the wiki over at
  https://wiki.ubuntu.com/SnapcraftUpdates

  The list of bugs and features in this release are defined at
  https://launchpad.net/snapcraft/+milestone/2.15

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1579905] Re: cups-browsed causes shutdown hang/delay in Ubuntu 16.04

2016-08-18 Thread Martin Pitt 
Adding xenial task. Till, can you please prepare an SRU for this?

** Also affects: cups-filters (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cups-filters (Ubuntu Xenial)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1579905

Title:
  cups-browsed causes shutdown hang/delay in Ubuntu 16.04

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Triaged

Bug description:
  Using the debug process found here
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917 I have
  determined that the cause of my 16.04 install's shutdown hang is cups-
  browsed.  It was the only process running when I did a systemctl list-
  jobs in the VT9 shell.  If I do sudo service cups-browsed stop and
  then shutdown, I do not get a hang.

  I have confirmed this on a virtual machine and a real system.  If I
  disable cups-browsed from ever starting, my problem is fixed.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

2016-08-18 Thread Martin Pitt 
sorry, correct link: https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu-xenial=5c4291769c

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  In Progress
Status in systemd package in Fedora:
  Unknown

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

2016-08-18 Thread Martin Pitt 
Thanks! Moving this to the systemd package then. This commit is included
in v231, so fixed in yakkety. I'll backport it to xenial.

** Changed in: libvirt (Ubuntu)
   Status: Triaged => Invalid

** Changed in: systemd (Ubuntu)
   Status: Invalid => Fix Released

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

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

** Also affects: systemd (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1350909
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  In Progress
Status in systemd package in Fedora:
  Unknown

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1583388] Re: Information about Ubuntu system automatically written to iPod

2016-08-18 Thread Martin Pitt 
I cannot find iPod_Control or iTunesControl in libimobiledevice or gvfs,
so I'm not sure what component actually creates those. But it's
certainly not util-linux, so removing package name for now.

** Package changed: util-linux (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: Triaged => New

** Also affects: Ubuntu Xenial
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1583388

Title:
  Information about Ubuntu system automatically written to iPod

Status in Ubuntu:
  New
Status in The Xenial Xerus:
  New

Bug description:
  On Xubuntu 16.04, I connected an iPod Nano 5th Generation (8 GB) to my
  computer. After working on the files on the iPod from within the
  terminal for a while, I found that the almost 21 MB file
  /media/username/DEVICENAME/iPod_Control/iTunes/iTunesControl contained
  sensitive information about my Ubuntu system, such as my username,
  commands that I had run recently, commands that I had run a long time
  ago, the full paths of some of those commands, environment variables,
  my UID, and text that appeared in my terminal window (such as the
  prompt, which included a path that I was on; it even included ANSI
  escape sequences for the prompt).

  I've attached the output of `strings iTunesControl`, with my username,
  hostname, and the iPod device name changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mount 2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed May 18 20:12:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-04 (1140 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (54 days ago)

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp