[Group.of.nepali.translators] [Bug 1646784] Re: /usr/lib/snapd-glib/snapd-login-service:11:read_data:read_from_snapd:read_cb:socket_source_dispatch:g_main_dispatch

[Robert Ancell]

** Also affects: snapd-glib (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: snapd-glib (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: snapd-glib (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: snapd-glib (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: snapd-glib (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: snapd-glib (Ubuntu Yakkety)
   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/1646784

Title:
  /usr/lib/snapd-glib/snapd-login-
  
service:11:read_data:read_from_snapd:read_cb:socket_source_dispatch:g_main_dispatch

Status in snapd-glib:
  Fix Released
Status in snapd-glib package in Ubuntu:
  Fix Committed
Status in snapd-glib source package in Xenial:
  Triaged
Status in snapd-glib source package in Yakkety:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
snapd-glib.  This problem was most recently seen with package version 
1.3-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/f6f7a1014bf13b394285650a50d00752e05f427b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd-glib/+bug/1646784/+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 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-December/081252.html

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux (Ubuntu)
   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/1616107

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in bridge-utils source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in bridge-utils source package in Yakkety:
  Invalid

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
 

[Group.of.nepali.translators] [Bug 1646857] Re: Ubuntu16.10 - EEH on BELL3 adapter fails to recover (serial/tty)

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-December/081251.html

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

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

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

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

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: Canonical Kernel Team (canonical-kernel-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/1646857

Title:
  Ubuntu16.10 - EEH on BELL3 adapter fails to recover (serial/tty)

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

Bug description:
  ---Problem Description---
  Error injection on BELL3 serial adapter fails to recover adapter & throws 
kernel warning/traces. I had to reboot system to reclaim adapter. 
   
  ---uname output---
  Linux ltcalpine-lp4 3.13.0-69-generic #112-Ubuntu SMP Tue Nov 10 16:29:16 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8408-E8E 

  ---Steps to Reproduce---
   1. Install librtas & ibm-lop utils
  2. Enable EEH in FSP
  3. Run workload on serial ports & trigger EEH

  i.e
  root@ltcalpine-lp4:/home/ubuntu# lspci -v
  :01:00.0 Serial controller: Digi International Device 00f6 (prog-if 06 
[16950])
Subsystem: IBM Device 0422
Flags: fast devsel, IRQ 504
Memory at 3fc20040 (32-bit, non-prefetchable) [size=16K]
Memory at 3fc20020 (32-bit, non-prefetchable) [size=2M]
Memory at 3fc2 (32-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable- Count=16 Masked-
Capabilities: [100] Device Serial Number 00-30-e0-11-11-00-01-50
Capabilities: [110] Power Budgeting 
Kernel driver in use: serial

  root@ltcalpine-lp4:/home/ubuntu# ls -l
  total 576376
  -rw-rw-r-- 1 ubuntu ubuntu 87264 Nov 13 03:51 
devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  -rw-r--r-- 1 ubuntu ubuntu 18726 Nov 13 03:51 dmesg_after_DLPAR.txt
  -rw-r--r-- 1 root   root   24144 Nov 13 04:20 dmesg-dlpar
  -rw-r--r-- 1 root   root   32697 Nov 17 07:33 dmesg-eeh
  -rw-rw-r-- 1 ubuntu ubuntu 36380 Nov 13 03:51 
dynamicrm_2.0.1-3_ppc64el.deb
  drwxr-xr-x 6 root   root4096 Nov 13 05:42 ibm-lop-utils
  -rw-r--r-- 1 root   root   24692 Aug 13 18:47 
ibm-lop-utils-0.1.4-1.ppc64le.rpm
  -rw-r--r-- 1 root   root   27070 Aug 10 18:30 
librtas1_1.3.13-1~errinjct.0_ppc64el.deb
  -rw-r--r-- 1 root   root   29598 Aug 11 18:48 
librtas-dev_1.3.13-1~errinjct.0_ppc64el.deb
  -rw-rw-r-- 1 ubuntu ubuntu   8040530 Nov 13 03:51 
rsct.core_3.2.0.6-15111_ppc64el.deb
  -rw-rw-r-- 1 ubuntu ubuntu771156 Nov 13 03:51 
rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  -rw-rw-r-- 1 ubuntu ubuntu219058 Nov 13 03:51 
src_3.2.0.6-15111_ppc64el.deb
  -rw-r--r-- 1 root   root   580864000 Nov 13 00:48 trusty-server-ppc64el.iso
  root@ltcalpine-lp4:/home/ubuntu#
  root@ltcalpine-lp4:/home/ubuntu# while true ; do dmesg > /dev/ttyS0 ; done &
  [1] 1211
  root@ltcalpine-lp4:/home/ubuntu# while true ; do dmesg > /dev/ttyS1 ; done &
  [2] 1216
  root@ltcalpine-lp4:/home/ubuntu#

  root@ltcalpine-lp4:/home/ubuntu/ibm-lop-utils/src/errinjct# ./errinjct eeh -v 
-f 0 -p U78C7.001.RCH0040-P1-C12
  Injecting an ioa-bus-error with the following data:

  BUS ADDR: 
  ADDR MASK:
  CONFIG ADDR:  1
  PHB UNIT_ID:  8002019
  FUNCTION: 0
  Load to PCI 

[Group.of.nepali.translators] [Bug 1647462] [NEW] Xenial update to v4.4.36 stable release

[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.36 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.36 stable release shall be
applied:

** 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/1647462

Title:
  Xenial update to v4.4.36 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.36 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.36 stable release shall be
  applied:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647462/+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 1646253] Re: I am getting frequent DRM hangs while playing Cities: Skylines from Steam

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc8

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  I am getting frequent DRM hangs while playing Cities: Skylines from
  Steam

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

Bug description:
  It happens during normal gameplay. Have tried reducing settings. Seems
  like a legitimate driver bug. The program crashes, but X does not.

  [16868.151225] [drm] stuck on render ring
  [16868.155458] [drm] GPU HANG: ecode 8:0:0x84dffefc, in Cities.x64 [21076], 
reason: Ring hung, action: reset
  [16868.155472] [ cut here ]
  [16868.155503] WARNING: CPU: 1 PID: 13959 at 
/build/linux-j9zxaP/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 
intel_mmio_flip_work_func+0x38e/0x3d0 [i915]()
  [16868.155505] WARN_ON(__i915_wait_request(mmio_flip->req, 
mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips))
  [16868.155506] Modules linked in:
  [16868.155508]  tcp_diag inet_diag hid_microsoft hid_generic snd_usb_audio 
usbhid hid snd_usbmidi_lib usb_serial_simple usbserial ctr ccm pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 ipt_REJECT nf_reject_ipv4 
xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rfcomm 
aufs bnep arc4 iwlmvm uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 intel_rapl videobuf2_core x86_pkg_temp_thermal v4l2_common 
intel_powerclamp cdc_mbim snd_hda_codec_hdmi coretemp cdc_wdm 
snd_hda_codec_realtek snd_hda_codec_generic cdc_ncm videodev joydev iwlwifi
  [16868.155545]  input_leds cdc_acm btusb usbnet serio_raw media btrtl 
snd_hda_intel mii btbcm rtsx_pci_ms thinkpad_acpi snd_hda_codec btintel 
memstick snd_hda_core cfg80211 bluetooth snd_hwdep snd_seq_midi 
snd_seq_midi_event intel_pch_thermal nvram snd_rawmidi lpc_ich snd_pcm mei_me 
mei shpchp snd_seq snd_seq_device snd_timer snd soundcore kvm_intel mac_hid kvm 
irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher 
af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect 
sysimgblt rtsx_pci fb_sys_fops ahci psmouse ptp drm libahci pps_core wmi fjes 
video
  [16868.155589] CPU: 1 PID: 13959 Comm: kworker/1:0 Tainted: GW  OE   
4.4.0-51-generic #72-Ubuntu
  [16868.155591] Hardware name: LENOVO 20CLS5N900/20CLS5N900, BIOS N10ET36W 
(1.15 ) 06/19/2015
  [16868.155617] Workqueue: events intel_mmio_flip_work_func [i915]
  [16868.155619]  0286 dd043c13 880382bbbd20 
813f5fc3
  [16868.155622]  880382bbbd68 c03a7ab8 880382bbbd58 
810812b2
  [16868.155624]  8802970af040 88042dc56500 88042dc5ae00 
0040
  [16868.155626] Call Trace:
  [16868.155632]  [] dump_stack+0x63/0x90
  [16868.155637]  [] warn_slowpath_common+0x82/0xc0
  [16868.155639]  [] warn_slowpath_fmt+0x5c/0x80
  [16868.155643]  [] ? __switch_to+0x437/0x5c0
  [16868.155667]  [] intel_mmio_flip_work_func+0x38e/0x3d0 
[i915]
  [16868.155672]  [] process_one_work+0x165/0x480
  [16868.155674]  [] worker_thread+0x4b/0x4c0
  [16868.155677]  [] ? process_one_work+0x480/0x480
  [16868.155679]  [] kthread+0xd8/0xf0
  [16868.155681]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [16868.155685]  [] ret_from_fork+0x3f/0x70
  [16868.155687]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [16868.155689] ---[ end trace 1339c06922e659f4 ]---
  [16868.157772] drm/i915: Resetting chip after gpu hang
  [16874.163802] [drm] stuck on render ring
 

[Group.of.nepali.translators] [Bug 1647075] Re: Unable to enter password to decrypt filesystem on boot after upgrading kernel to 4.4.0-51

[Joseph Salisbury]

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.36


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

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

** Tags added: kernel-da-key needs-bisect

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

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

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

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

Title:
  Unable to enter password to decrypt filesystem on boot after upgrading
  kernel to 4.4.0-51

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

Bug description:
  Disk is encrypted using full disk encryption.  I could enter my
  password to decrypt the disk when booting in 4.4.0-47, but after
  upgrading to 4.4.0-51, I'm prompted for the password, but I can't type
  anything.

  I think the last time this happened there was some change with the USB
  HID modules or something (I'm using a USB keyboard).  Has there been
  any changes to the USB modules or configuration between kernel
  4.4.0-47 and 4.4.0-51?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-51-generic 4.4.0-51.72
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  2447 F pulseaudio
   /dev/snd/controlC1:  chris  2447 F pulseaudio
   /dev/snd/controlC0:  chris  2447 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec  3 11:39:50 2016
  HibernationDevice: RESUME=UUID=8a9bf6f5-bb32-459a-8f5b-fc7f95451c26
  InstallationDate: Installed on 2014-07-04 (883 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet nosplash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH P67
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHP67:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647075/+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 1647093] Re: Elantech Touchpad detected intermittently, not detected when these system logs were taken

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc8

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

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

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

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

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

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

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

Title:
  Elantech Touchpad detected intermittently, not detected when these
  system logs were taken

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

Bug description:
  Hi,

  The Elantech Touchpad appears to be buggy in linux/Ubuntu through
  messages.

  Today, the touchpad was not detected on startup and I am using an external 
mouse to drive the cursor.
  ubuntu-bug linux output attached.

  For comparison, when the touchpad was working, the same system logs
  are recorded in bug #1644919.

  Have tried both the mainline and stable kernel.

  These logs are on the stable kernel, same as those in bug 1644919

  Expected behaviour. Start computer up, cursor responds to touchpad command
  Current behaviour. Start computer up, cursor not visible until external mouse 
plugged in and moved. Cursor responds normally to external mouse, issue with 
touchpad driver.

  xinput shows no touchpad detected

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-51-generic 4.4.0-51.72
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  horace 1893 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Dec  4 07:58:01 2016
  HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e
  InstallationDate: Installed on 2016-11-13 (20 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: GIGABYTE P57
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed 
root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-51-generic N/A
   linux-backports-modules-4.4.0-51-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB0B
  dmi.board.asset.tag: Default string
  dmi.board.name: P57
  dmi.board.vendor: GIGABYTE
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: P57
  dmi.product.version: Default string
  dmi.sys.vendor: GIGABYTE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647093/+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 1247528] Re: Build and distribute intel-virtual-output

[Gunnar Hjalmarsson]

Since I made some noise on the ubuntu-devel list about this, I thought
I'd help out.

I added those build dependencies, and could build it successfully:

https://launchpad.net/~gunnarhj/+archive/ubuntu/intel-virtual-output

New debdiff attached.

Thanks LocutusOfBorg and Dmitry for your assistance!

** Patch added: "bugfix2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1247528/+attachment/4787664/+files/bugfix2.debdiff

** Changed in: xserver-xorg-video-intel (Ubuntu Trusty)
   Importance: Undecided => Wishlist

** Changed in: xserver-xorg-video-intel (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: xserver-xorg-video-intel (Ubuntu Trusty)
 Assignee: (unassigned) => Daniel Gimpelevich (daniel-gimpelevich)

** No longer affects: xserver-xorg-video-intel (Ubuntu Xenial)

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

Title:
  Build and distribute intel-virtual-output

Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Trusty:
  In Progress
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]

  xserver-xorg-video-intel 2.99.904 adds support for virtual displays
  that can be used to clone to discrete outputs. The tool to do this is
  included with the xserver-xorg-video-intel source (with not-so-great
  man page and all), but the binary is currently not shipped by Ubuntu
  trusty, despite being built. It is shipped in utopic and later.

  The tool will allocate a virtual output for the specified outputs on a
  different X server (or for all outputs with the -a parameter). It will
  also copy over resolution information etc from xrandr. You can then
  use your desktop environment's display tool to configure these
  external displays the way you would normally do in a non-hybrid
  situation.

  Since the trusty release is LTS, this bug qualifies for SRU status "to
  enable new hardware," or rather, newly supported at the time of the
  trusty release.

  [Test Case]

  1) Install the package.
  2) Attempt to execute /usr/bin/intel-virtual-output in a shell.

  [Regression Potential]

  Absolutely none.

  [Other Info]

  The intel-gpu-tools package is the only reverse dependency, and that
  package has no reverse dependencies in turn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1247528/+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 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

[Scott Moser]

re-opening this for cloud-init as the change in cloud-init actually
regressed the behavior.


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

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Released => Confirmed

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

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

Title:
  Commissioning fails when competing cloud metadata resides on disk

Status in cloud-init:
  Confirmed
Status in MAAS:
  Triaged
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed

Bug description:
  A customer reused hardware that had previously deployed a RHEL
  Overcloud-controller which places metadata on the disk as a legitimate
  source, that cloud-init looks at by default.  When the newly enlisted
  node appeared it had the name of "overcloud-controller-0" vs. maas-
  enlist, pulled from the disk metadata which had overridden MAAS'
  metadata.  Commissioning continually failed on all of the nodes until
  the disk metadata was manually removed (KVM boot Ubuntu ISO, rm -f
  data or dd zeros to disk).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1582323/+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 1647312] Re: Containers don't restart after clean host shutdown

[Stéphane Graber]

** Changed in: lxd (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/1647312

Title:
  Containers don't restart after clean host shutdown

Status in lxd package in Ubuntu:
  In Progress
Status in lxd source package in Trusty:
  Fix Released
Status in lxd source package in Xenial:
  Fix Released

Bug description:
  LXD is supposed to record the containers state on host shutdown and
  restore them to their previous state on restart.

  A change in LXD 2.6.2 and LXD 2.0.8 regressed this, so now containers
  need to be manually started after reboot.

  Upstream bug report: https://github.com/lxc/lxd/issues/2686
  Upstream fix: https://github.com/lxc/lxd/pull/2687

  This will need to be SRUed very quickly.

  # SRU paperwork
  ## Rationale
  Regresses "lxd shutdown".

  ## Test case
   - lxc launch ubuntu:16.04 abc
   - lxd shutdown
   - ps aux | grep -q abc && echo "FAIL, container still running"
   - lxc finger
   - lxc list | grep abc | grep RUNNING

  ## Regression potential
  Fix is pretty straightforward and specific to this issue. A test was also 
added as part of this, so it's very unlikely that anything else would be 
affected by this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1647312/+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 1647312] Re: Containers don't restart after clean host shutdown

[Launchpad Bug Tracker]

This bug was fixed in the package lxd - 2.0.8-0ubuntu1~ubuntu16.04.2

---
lxd (2.0.8-0ubuntu1~ubuntu16.04.2) xenial; urgency=medium

  * Fix container last-state recording (LP: #1647312)
- 0001-Fix-container-state-recording.patch
- 0002-tests-Test-lxd-shutdown.patch
- 0003-Only-mark-ready-once-containers-are-up.patch

 -- Stéphane Graber   Mon, 05 Dec 2016 13:45:44
+0100

** Changed in: lxd (Ubuntu Xenial)
   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/1647312

Title:
  Containers don't restart after clean host shutdown

Status in lxd package in Ubuntu:
  In Progress
Status in lxd source package in Trusty:
  Fix Released
Status in lxd source package in Xenial:
  Fix Released

Bug description:
  LXD is supposed to record the containers state on host shutdown and
  restore them to their previous state on restart.

  A change in LXD 2.6.2 and LXD 2.0.8 regressed this, so now containers
  need to be manually started after reboot.

  Upstream bug report: https://github.com/lxc/lxd/issues/2686
  Upstream fix: https://github.com/lxc/lxd/pull/2687

  This will need to be SRUed very quickly.

  # SRU paperwork
  ## Rationale
  Regresses "lxd shutdown".

  ## Test case
   - lxc launch ubuntu:16.04 abc
   - lxd shutdown
   - ps aux | grep -q abc && echo "FAIL, container still running"
   - lxc finger
   - lxc list | grep abc | grep RUNNING

  ## Regression potential
  Fix is pretty straightforward and specific to this issue. A test was also 
added as part of this, so it's very unlikely that anything else would be 
affected by this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1647312/+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 1247528] Re: Build and distribute intel-virtual-output

[Dmitry Shachnev]

In the zesty package /usr/bin/intel-virtual-output is installed, so
closing this bug in Ubuntu and adding an Ubuntu (Xenial) task.

The patch is incomplete — according to the Debian package changelog, you
need to add some build-dependencies.

** Also affects: xserver-xorg-video-intel (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-intel (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: xserver-xorg-video-intel (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/1247528

Title:
  Build and distribute intel-virtual-output

Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Trusty:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]

  xserver-xorg-video-intel 2.99.904 adds support for virtual displays
  that can be used to clone to discrete outputs. The tool to do this is
  included with the xserver-xorg-video-intel source (with not-so-great
  man page and all), but the binary is currently not shipped by Ubuntu
  trusty, despite being built. It is shipped in utopic and later.

  The tool will allocate a virtual output for the specified outputs on a
  different X server (or for all outputs with the -a parameter). It will
  also copy over resolution information etc from xrandr. You can then
  use your desktop environment's display tool to configure these
  external displays the way you would normally do in a non-hybrid
  situation.

  Since the trusty release is LTS, this bug qualifies for SRU status "to
  enable new hardware," or rather, newly supported at the time of the
  trusty release.

  [Test Case]

  1) Install the package.
  2) Attempt to execute /usr/bin/intel-virtual-output in a shell.

  [Regression Potential]

  Absolutely none.

  [Other Info]

  The intel-gpu-tools package is the only reverse dependency, and that
  package has no reverse dependencies in turn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1247528/+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 1571989] Re: package snapd (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/snap.1.gz', which is also in package snap 2013-11-29-1

[Launchpad Bug Tracker]

This bug was fixed in the package snap - 2013-11-29-1ubuntu6

---
snap (2013-11-29-1ubuntu6) zesty; urgency=medium

  * debian/patches/werror-indent
- fix another -Werror indent error that actually looks like
  a real coding error

 -- Michael Vogt   Mon, 05 Dec 2016 12:55:03
+0100

** Changed in: snap (Ubuntu)
   Status: Triaged => 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/1571989

Title:
  package snapd (not installed) failed to install/upgrade: trying to
  overwrite '/usr/share/man/man1/snap.1.gz', which is also in package
  snap 2013-11-29-1ubuntu2

Status in snap package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Confirmed
Status in snap source package in Xenial:
  In Progress
Status in snapd source package in Xenial:
  Confirmed
Status in snap source package in Yakkety:
  In Progress
Status in snapd source package in Yakkety:
  Confirmed

Bug description:
  TEST CASE:
  1. install snapd
  2. install snap
  3. verify that there is a file conflict error
  4. install snap from xenial-proposed
  5. verify that there is no longer a file conflict

  Regression potential: 
  - low, only the man-page for snap(-dna) package got renamed which now 
actually matches the binary of the snap(-dna) package.

  
  Ran 'sudo apt install snapd' on a clean installation of Ubuntu 16.04 Beta 2.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: snapd (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Apr 19 08:40:57 2016
  DuplicateSignature:
   Unpacking snapd (2.0.1) ...
   dpkg: error processing archive /var/cache/apt/archives/snapd_2.0.1_amd64.deb 
(--unpack):
    trying to overwrite '/usr/share/man/man1/snap.1.gz', which is also in 
package snap 2013-11-29-1ubuntu2
  ErrorMessage: trying to overwrite '/usr/share/man/man1/snap.1.gz', which is 
also in package snap 2013-11-29-1ubuntu2
  InstallationDate: Installed on 2016-04-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.7
  SourcePackage: snapd
  Title: package snapd (not installed) failed to install/upgrade: trying to 
overwrite '/usr/share/man/man1/snap.1.gz', which is also in package snap 
2013-11-29-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1571989/+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 1593407] Re: Guest session cannot run snaps

[Michael Vogt]

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

** Also affects: snapd (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/1593407

Title:
  Guest session cannot run snaps

Status in Light Display Manager:
  Confirmed
Status in Snappy:
  Confirmed
Status in lightdm package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  New
Status in snapd source package in Xenial:
  New

Bug description:
  I'm using Ubuntu 16.04.

  The guest session cannot execute snaps, because of a permission error.
  The LightDM's guest session AppArmor profile is not allowing access to /snap 
and other needed files and folders.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1647312] [NEW] Containers don't restart after clean host shutdown

[Stéphane Graber]

Public bug reported:

LXD is supposed to record the containers state on host shutdown and
restore them to their previous state on restart.

A change in LXD 2.6.2 and LXD 2.0.8 regressed this, so now containers
need to be manually started after reboot.

Upstream bug report: https://github.com/lxc/lxd/issues/2686
Upstream fix: https://github.com/lxc/lxd/pull/2687

This will need to be SRUed very quickly.

# SRU paperwork
## Rationale
Regresses "lxd shutdown".

## Test case
 - lxc launch ubuntu:16.04 abc
 - lxd shutdown
 - ps aux | grep -q abc && echo "FAIL, container still running"
 - lxc finger
 - lxc list | grep abc | grep RUNNING

## Regression potential
Fix is pretty straightforward and specific to this issue. A test was also added 
as part of this, so it's very unlikely that anything else would be affected by 
this fix.

** Affects: lxd (Ubuntu)
 Importance: High
 Status: In Progress

** Affects: lxd (Ubuntu Trusty)
 Importance: High
 Status: In Progress

** Affects: lxd (Ubuntu Xenial)
 Importance: High
 Status: In Progress

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

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

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

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

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

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

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

Title:
  Containers don't restart after clean host shutdown

Status in lxd package in Ubuntu:
  In Progress
Status in lxd source package in Trusty:
  In Progress
Status in lxd source package in Xenial:
  In Progress

Bug description:
  LXD is supposed to record the containers state on host shutdown and
  restore them to their previous state on restart.

  A change in LXD 2.6.2 and LXD 2.0.8 regressed this, so now containers
  need to be manually started after reboot.

  Upstream bug report: https://github.com/lxc/lxd/issues/2686
  Upstream fix: https://github.com/lxc/lxd/pull/2687

  This will need to be SRUed very quickly.

  # SRU paperwork
  ## Rationale
  Regresses "lxd shutdown".

  ## Test case
   - lxc launch ubuntu:16.04 abc
   - lxd shutdown
   - ps aux | grep -q abc && echo "FAIL, container still running"
   - lxc finger
   - lxc list | grep abc | grep RUNNING

  ## Regression potential
  Fix is pretty straightforward and specific to this issue. A test was also 
added as part of this, so it's very unlikely that anything else would be 
affected by this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1647312/+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 1625932] Re: Backlight does not change when adjust it higher than 50% after S3

[Anthony Wong]

** Also affects: hwe-next/vivid
   Importance: Undecided
   Status: New

** Also affects: hwe-next/xenial
   Importance: Undecided
   Status: Fix Released

** Changed in: hwe-next/vivid
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: hwe-next/vivid
   Importance: Undecided => High

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

Title:
  Backlight does not change when adjust it higher than 50% after S3

Status in HWE Next:
  Fix Released
Status in HWE Next vivid series:
  New
Status in HWE Next xenial series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Backlight does not change when adjust it higher than 50% after S3

  Steps:
  1. Install ubuntu 16.04 and boot into OS
  2. suspend system
  3. resume system from S3
  4. Try to adjust brightness level

  Expected results: Backlight should be changed when adjust it

  Actual results: Backlight does not change when adjust it higher than
  50% after S3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1625932/+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 1571989] Re: package snapd (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/snap.1.gz', which is also in package snap 2013-11-29-1

[Michael Vogt]

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

** Also affects: snapd (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/1571989

Title:
  package snapd (not installed) failed to install/upgrade: trying to
  overwrite '/usr/share/man/man1/snap.1.gz', which is also in package
  snap 2013-11-29-1ubuntu2

Status in snap package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Confirmed
Status in snap source package in Xenial:
  New
Status in snapd source package in Xenial:
  New

Bug description:
  Ran 'sudo apt install snapd' on a clean installation of Ubuntu 16.04
  Beta 2.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: snapd (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Apr 19 08:40:57 2016
  DuplicateSignature:
   Unpacking snapd (2.0.1) ...
   dpkg: error processing archive /var/cache/apt/archives/snapd_2.0.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/share/man/man1/snap.1.gz', which is also in 
package snap 2013-11-29-1ubuntu2
  ErrorMessage: trying to overwrite '/usr/share/man/man1/snap.1.gz', which is 
also in package snap 2013-11-29-1ubuntu2
  InstallationDate: Installed on 2016-04-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.7
  SourcePackage: snapd
  Title: package snapd (not installed) failed to install/upgrade: trying to 
overwrite '/usr/share/man/man1/snap.1.gz', which is also in package snap 
2013-11-29-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1571989/+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 1646240] Re: qemu-image creats broken vmdk file

[ChristianEhrhardt]

That is qemu commit:
commit d62d9dc4b814950dcc8bd261a3e2e9300d9065e6
Author: Fam Zheng 
Date:   Thu Sep 17 13:04:10 2015 +0800

vmdk: Create streamOptimized as version 3

Which is in:
>= qemu v2.6.0

So setting fixed in Yakkety, Zesty and marking it for work on a backport
to Xenial.

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

** Changed in: qemu (Ubuntu Xenial)
   Status: New => Triaged

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

** Changed in: qemu (Ubuntu)
   Status: Triaged => 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/1646240

Title:
  qemu-image creats broken vmdk file

Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Triaged

Bug description:
  qemu-img create function produce VMDK image files with unsupported
  format option for an OVA file for importing a virtual machine into
  VMware vSphere/ESXi.

  
  VMDK file created by qemu-img failes during import with error message "Not a 
supported disk format (sparse VMDK version too old)"

  Ubuntu 16.04 LTS
  qemu version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1646240/+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