[Group.of.nepali.translators] [Bug 1629600] Re: Installed application from .deb does not appear unless Ubuntu is restarted

[dino99]

** Tags removed: yakkety

** Changed in: gnome-software (Ubuntu Zesty)
   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/1629600

Title:
  Installed application from .deb does not appear unless Ubuntu is
  restarted

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  New
Status in gnome-software source package in Zesty:
  Invalid
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  I'm using Ubuntu 16.04 x64 and the installed version of gnome-software
  is 3.20.1

* I install a desktop application from a .deb package. I tried several 
methods (apt install, dpkg -i, xdg-open then click on install button).
* After the installation, I control that the application is visible from 
the system:
  * The application appears correctly in the application list in Unity Dash
  * The application appears in the "Open With" menu list in Nautilus 
(because of registered mime types)
  * The package name of the application can be used as an argument of apt 
commands (apt show, apt remove...) and dpkg (dpkg -l, dpkg -L...)
* I start gnome-software.
* I click on the "installed" tab to get the list of installed applications.

  expected result: the freshly installed application is in the list
  actual result: the freshly installed application is not in the list.

  If I reboot my computer and start gnome-software, the installed
  application appears in the list.

  It looks like there is some kind of cache that is not refreshed at the
  right moment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1629600/+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 1557115] Re: [regression] RadioTray won't launch without python-xdg & gir1.2-appindicator3-0.1

[dino99]

** Changed in: hundredpapercuts
   Status: Confirmed => 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/1557115

Title:
  [regression] RadioTray won't launch without python-xdg &
  gir1.2-appindicator3-0.1

Status in GTK+:
  Invalid
Status in One Hundred Papercuts:
  Invalid
Status in radiotray package in Ubuntu:
  Fix Released
Status in radiotray source package in Xenial:
  Triaged
Status in radiotray package in Debian:
  Invalid

Bug description:
  Although I've been previously running RadioTray in Ubuntu 16.04, it
  has recently become unlaunchable.

  Typically when you launch RadioTray, an indicator appears on the top-
  right-panel (left of the clock), and you are able to select a radio-
  station to stream.

  Now, when you launch it, nothing apparently happens.

  
  
  This is a lack of dependencies by default:

  Need adding depends to « python-xdg and gir1.2-appindicator3-0.1 »

  note: as the latest ubuntu release now mainly use python3-xdg,
  radiotray should use it too, instead of the deprecated python-xdg
  package.

  
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: radiotray 0.7.3-5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 14 13:35:53 2016
  InstallationDate: Installed on 2016-03-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: radiotray
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1557115/+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 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu

[dino99]

Zesty EOL reached

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

Title:
  need to ensure microcode updates are available to all bare-metal
  installs of Ubuntu

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta source package in Trusty:
  Fix Released
Status in linux-meta source package in Xenial:
  Fix Released
Status in linux-meta-hwe source package in Xenial:
  Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
  Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
  New
Status in linux-meta source package in Zesty:
  Invalid
Status in linux-meta source package in Artful:
  Fix Released
Status in linux-meta source package in Bionic:
  Fix Released

Bug description:
  From time to time, CPU vendors release updates to microcode that can
  be loaded into the CPU from the OS.  For x86, we have these updates
  available in the archive as amd64-microcode and intel-microcode.

  Sometimes, these microcode updates have addressed security issues with
  the CPU.  They almost certainly will again in the future.

  We should ensure that all users of Ubuntu on baremetal x86 receive
  these security updates, and have them applied to the CPU in early boot
  where at all feasible.

  Because these are hardware-dependent packages which we don't want to
  install except on baremetal (so: not in VMs or containers), the
  logical place to pull them into the system is via the kernel, so that
  only the kernel baremetal flavors pull them in.  This is analogous to
  linux-firmware, which is already a dependency of the linux-
  image-{lowlatency,generic} metapackages, and whose contents are
  applied to the hardware by the kernel similar to microcode.

  So, please update the linux-image-{lowlatency,generic} metapackages to
  add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
  and the corresponding hwe metapackages also.

  Please time this change to coincide with the next updates of the
  microcode packages in the archive.

  I believe we will also need to promote the *-microcode packages to
  main from restricted as part of this (again, by analogy with linux-
  firmware).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1738259/+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 1590799] Re: nfs-kernel-server does not start because of dependency failure

[dino99]

Yakkety is now unsupported, and the other supported releases are fixed.

** Changed in: nfs-utils (Ubuntu Yakkety)
   Status: Fix Committed => 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/1590799

Title:
  nfs-kernel-server does not start because of dependency failure

Status in nfs-utils package in Ubuntu:
  Fix Released
Status in nfs-utils source package in Trusty:
  Invalid
Status in nfs-utils source package in Xenial:
  Fix Released
Status in nfs-utils source package in Yakkety:
  Invalid
Status in nfs-utils source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * nfs-mountd doesn't get started because of a race condition happening when 
rpcbind.socket is not specified as a needed service for it to start.
   * nfs-server using rpcbind.target instead of using rpcbind.socket. Target 
should not be used (Comment #24)

  [Test Case]

   * Install nfs-kernel-server inside a xenial lxc guest and restart it until 
nfs-mountd doesn't start complaining on rpc error.
   * Comment #25

  [Regression Potential]

   * Cons: Systemd dependencies could brake for nfs-server and nfs-mountd.
   * Pros: Patches have been accepted upstream (and tested).

  [Other Info]
   
  # Original Bug Description

  Immediately after boot:

  root@feynmann:~# systemctl status nfs-kernel-server
  ● nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor 
preset: enabled)
     Active: inactive (dead)

  Jun 09 14:35:47 feynmann systemd[1]: Dependency failed for NFS server and 
services.
  Jun 09 14:35:47 feynmann systemd[1]: nfs-server.service: Job 
nfs-server.service/start failed

  root@feynmann:~# systemctl status nfs-mountd.service
  ● nfs-mountd.service - NFS Mount Daemon
     Loaded: loaded (/lib/systemd/system/nfs-mountd.service; static; vendor 
preset: enabled)
     Active: failed (Result: exit-code) since Thu 2016-06-09 14:35:47 BST; 7min 
ago
    Process: 1321 ExecStart=/usr/sbin/rpc.mountd $RPCMOUNTDARGS (code=exited, 
status=1/FAILURE)

  Jun 09 14:35:47 feynmann systemd[1]: Starting NFS Mount Daemon...
  Jun 09 14:35:47 feynmann rpc.mountd[1321]: mountd: could not create listeners
  Jun 09 14:35:47 feynmann systemd[1]: nfs-mountd.service: Control process 
exited, code=exited
  Jun 09 14:35:47 feynmann systemd[1]: Failed to start NFS Mount Daemon.
  Jun 09 14:35:47 feynmann systemd[1]: nfs-mountd.service: Unit entered failed 
state.
  Jun 09 14:35:47 feynmann systemd[1]: nfs-mountd.service: Failed with result 
'exit-code'.

  root@feynmann:~# systemctl list-dependencies nfs-kernel-server
  nfs-kernel-server.service
  ● ├─auth-rpcgss-module.service
  ● ├─nfs-config.service
  ● ├─nfs-idmapd.service
  ● ├─nfs-mountd.service
  ● ├─proc-fs-nfsd.mount
  ● ├─rpc-svcgssd.service
  ● ├─system.slice
  ● ├─network.target
  ● └─rpcbind.target
  ●   └─rpcbind.service

  root@feynmann:~# systemctl list-dependencies nfs-mountd.service
  nfs-mountd.service
  ● ├─nfs-config.service
  ● ├─nfs-server.service
  ● ├─proc-fs-nfsd.mount
  ● └─system.slice
  root@feynmann:~#

  root@feynmann:~# lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  root@feynmann:~# apt-cache policy nfs-kernel-server
  nfs-kernel-server:
    Installed: 1:1.2.8-9ubuntu12
    Candidate: 1:1.2.8-9ubuntu12
    Version table:
   *** 1:1.2.8-9ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Additional comments:

  1. There seems to be a circular dependency between nfs-mountd and 
nfs-kernel-server
  2. I can get it working by changing the AFter,Requires in 
/lib/ssystemd/system/nfs-{mountd|server}.service files. I have managed to get 
nfs-kernel-server to start but not nfs-mountd.
  3. /usr/lib/systemd/scripts/nfs-utils_env.sh references 
/etc/sysconfig/nfs which is Centos/RedHat location of this file. Also 
/etc/default/nfs does not exist. (possibly unrelated to this bug)
  4. A file "/lib/systemd/system/-.slice" exists. this file prevents 
execution of 'ls *' or 'grep xxx *' commands in that directory. I am unsure 
whether this is intended by the systemd developers but it is unfriendly when 
investigating this bug.

  Attempted solution:

  1. Edit /lib/systemd/system/nfs-server.service (original lines are
  commented out:

  [Unit]
  Description=NFS server and services
  DefaultDependencies=no
  Requires=network.target proc-fs-nfsd.mount rpcbind.target
  # Requires=nfs-mountd.service
  Wants=nfs-idmapd.service

  After=local-fs.target
  #After=network.target proc-fs-nfsd.mount rpcbind.target nfs-mountd.service
  After=network.target proc-fs-nfsd.mount rpcbind.target
  After=nfs-idmapd.service rpc-statd.service
  #Before=rpc-statd-notify.service
  Before=nfs-mountd.service rpc-statd-notify.service
  

[Group.of.nepali.translators] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler

[dino99]

Looks like everything is ok now in 2018; closing that report.

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

** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: gcc-defaults (Ubuntu)
   Status: Confirmed => 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/1574982

Title:
  Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
  not supported by compiler

Status in dkms package in Ubuntu:
  Invalid
Status in gcc-defaults package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Invalid
Status in dkms source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Installing the latest 4.4.0-22 kernel ends with that error logged into 
dkmsbuildlog
  (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)

  https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt

  make "CC=cc"  KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 
NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build 
NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia 
nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules
  make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  arch/x86/Makefile:133: stack-protector enabled but compiler support broken
  Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler

  the latest error logged is:

  /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error:
  code model kernel does not support PIC mode

  Looks like it is related to the latest changes updates: gcc-6/gcc-5 
5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the 
packages built with gcc-6)
  Maybe some alternatives has not been updated to take care of these changes, 
as asked some time ago:
  http://askubuntu.com/questions/26498/choose-gcc-and-g-version

  This has been firstly reported against a nvidia crash:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gcc 4:5.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 08:41:32 2016
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2014 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2014 F...m pulseaudio
   /dev/snd/controlC0:  oem2014 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: ubuntu
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  yakkety
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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: 

[Group.of.nepali.translators] [Bug 1673247] Re: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine

[dino99]

** Changed in: dpkg (Ubuntu Trusty)
 Assignee: Néstor O. Gozza (mangosta11) => (unassigned)

** Changed in: dpkg (Ubuntu Xenial)
 Assignee: Reinhardt Pflanz (sajaha-e) => (unassigned)

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

** Changed in: snapd (Ubuntu Yakkety)
   Status: Confirmed => 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/1673247

Title:
  package snapd 2.23.1 failed to install/upgrade: trying to overwrite
  '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package
  snap-confine 2.23.1

Status in dpkg package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in dpkg source package in Trusty:
  Confirmed
Status in snapd source package in Trusty:
  In Progress
Status in dpkg source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in dpkg source package in Yakkety:
  Invalid
Status in snapd source package in Yakkety:
  Invalid
Status in dpkg source package in Zesty:
  Confirmed
Status in snapd source package in Zesty:
  Confirmed

Bug description:
  When the ubuntu installer runs it has an option to download updates during 
the install. When this happens snapd/snap-confine 2.22.6 are installed on 
/target. The upgrade brings in snapd/snap-confine 2.23.1 which has a conffile 
in /etc/apparmor.d/usr.lib.snapd.snap-confine. The snapd packages declares a 
breaks/replaces: snapd-confine (<< 2.23) which works correctly on regular 
upgrades. However it does fail on upgrades with the "--root=/target" that is 
used by ubiquity. After a bit of debugging it turns out the reason is that
  src/archives.c:tarobject() has a check for obsolete conffiles in the block
  around "Is the file an obsolete conffile ...". There is a stat() here that
  checks that the conff->name and the fnamevb are the same file. This check
  fails to take the instdir into account and therefore the loop does not 
  continue but falls through to the "does_replace()" checks.

  
  
  Snap 2.23.1 fails to upgrade from 2.21.

  Known facts:
  - reporters (and apport) indicate it fails during the install via the live-cd
  - not reproducible so far on an already installed system
  - breaks/replaces of snapd are correct
  - When adding "xenial-proposed" to apt-setup in ubiquity and installing

  Cause:
  - when ubiquity runs it uses "dpkg --root=/target --unpack ..." - however 
when doing the conffile checking dpkg does not handle the "--root" parameter 
correctly and checks something against "/" instead of "/target".

  -
  I really don't know what else to add...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: snapd 2.23.1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CasperVersion: 1.376.2
  Date: Wed Mar 15 16:03:33 2017
  DuplicateSignature:
   package:snapd:2.23.1
   Unpacking snapd (2.23.1) over (2.21) ...
   dpkg: error processing archive 
/target/var/cache/apt/archives/snapd_2.23.1_amd64.deb (--unpack):
    trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is 
also in package snap-confine 2.23.1
  ErrorMessage: trying to overwrite 
'/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package 
snap-confine 2.23.1
  LiveMediaBuild: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: snapd
  Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite 
'/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package 
snap-confine 2.23.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1673247/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[dino99]

** Changed in: cracklib2 (Ubuntu Trusty)
   Status: Incomplete => Invalid

** Changed in: apt (Ubuntu)
   Status: Confirmed => 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/1681231

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Invalid
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Invalid
Status in cracklib2 source package in Xenial:
  Fix Released
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Fix Released
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+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 1523767] Re: hexer: FTBFS with glibc-2.21 and gcc-5

[dino99]

** Changed in: hexer (Ubuntu Wily)
   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/1523767

Title:
  hexer: FTBFS with glibc-2.21 and gcc-5

Status in hexer package in Ubuntu:
  Fix Released
Status in hexer source package in Wily:
  Invalid
Status in hexer source package in Xenial:
  Fix Released
Status in hexer package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/788740:

  Source: hexer
  Version: 0.1.8-1
  Severity: normal

  From my pbuilder build log, using a setup preferring glibc and gcc-
  defaults packages from experimental:

  ...
 dh_auto_build
  make -j1
  make[1]: Entering directory '/tmp/buildd/hexer-0.1.8'
  cc -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security  
-D_FORTIFY_SOURCE=2 -DHE_DEFAULT_PAGER=\"pager\" -DHEXER_VERSION=\"0.1.8\"  -c 
-o buffer.o buffer.c
  cc -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security  
-D_FORTIFY_SOURCE=2 -DHE_DEFAULT_PAGER=\"pager\" -DHEXER_VERSION=\"0.1.8\"  -c 
-o tio.o tio.c
  tio.c: In function 'tio_init':
  tio.c:819:17: error: incompatible types when assigning to type '__sigset_t 
{aka struct }' from type 'int'
   act.sa_mask = 0;
   ^
  tio.c: In function 'tio_set_colors':
  tio.c:1779:1: warning: type of 'fg' defaults to 'int' [-Wimplicit-int]
   tio_set_colors(fg, bg)
   ^
  tio.c:1779:1: warning: type of 'bg' defaults to 'int' [-Wimplicit-int]
  tio.c: In function 'tio_raw_readwait':
  tio.c:2177:1: warning: type of 'tmout' defaults to 'int' [-Wimplicit-int]
   tio_raw_readwait(tmout)
   ^
  : recipe for target 'tio.o' failed
  make[1]: *** [tio.o] Error 1
  make[1]: Leaving directory '/tmp/buildd/hexer-0.1.8'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:31: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2
  -- 
  Daniel Schepler

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hexer/+bug/1523767/+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 1507418] Re: python-nmap: FTBFS: IOError: [Errno 2] No such file or directory: 'scanme_output.xml'

[dino99]

** Changed in: python-nmap (Ubuntu Wily)
   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/1507418

Title:
  python-nmap: FTBFS: IOError: [Errno 2] No such file or directory:
  'scanme_output.xml'

Status in python-nmap package in Ubuntu:
  Fix Released
Status in python-nmap source package in Wily:
  Invalid
Status in python-nmap source package in Xenial:
  Fix Released
Status in python-nmap package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/799761:

  Source: python-nmap
  Version: 0.4.0-2
  Severity: serious
  Justification: fails to build from source
  User: reproducible-bui...@lists.alioth.debian.org
  Usertags: ftbfs
  X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

  Dear Maintainer,

  python-nmap fails to build from source in unstable/amd64:

[..]

pybuild --test --test-nose -i python{version} -p 2.7 --dir .
I: pybuild base:170: cd
/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build; python2.7
-m nose 
..EE.E
==
ERROR: nmap.test_nmap.test_command_line
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
  setUp
try_run(self.test, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
  try_run
return func()
  File
  
"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
  line 67, in xmlfile_read_setup
nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
IOError: [Errno 2] No such file or directory: 'scanme_output.xml'

==
ERROR: nmap.test_nmap.test_scan_info
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
  setUp
try_run(self.test, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
  try_run
return func()
  File
  
"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
  line 67, in xmlfile_read_setup
nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
IOError: [Errno 2] No such file or directory: 'scanme_output.xml'

==
ERROR: nmap.test_nmap.test_all_hosts
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
  setUp
try_run(self.test, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
  try_run
return func()
  File
  
"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
  line 67, in xmlfile_read_setup
nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
IOError: [Errno 2] No such file or directory: 'scanme_output.xml'

==
ERROR: nmap.test_nmap.test_host
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
  setUp
try_run(self.test, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
  try_run
return func()
  File
  
"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
  line 67, in xmlfile_read_setup
nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
IOError: [Errno 2] No such file or directory: 'scanme_output.xml'

==
ERROR: nmap.test_nmap.test_port
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 267, in
  setUp
try_run(self.test, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in
  try_run
return func()
  File
  
"/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build/nmap/test_nmap.py",
  line 67, in xmlfile_read_setup
nm.analyse_nmap_xml_scan(open('scanme_output.xml').read())
IOError: [Errno 2] No such file or directory: 'scanme_output.xml'

==
ERROR: 

[Group.of.nepali.translators] [Bug 1639180] Re: no login possible after update to nvidia 304.132

[dino99]

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Yakkety)
   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/1639180

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Fix Released
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1557115] Re: [regression] RadioTray won't launch without python-xdg & gir1.2-appindicator3-0.1

[dino99]

From: Elías Alejandro 
To: 801232-d...@bugs.debian.org
Subject: Closed bug: radiotray wont start
Date: Wed, 6 Jul 2016 10:50:17 -0500
Hi,
I'm closing this bug, since it seems was already fixed. 
If you have new reasons to point out this
problem, please feel free to re-open it or ask me to do it.

Regards,

--
Elías Alejandro

** Changed in: radiotray (Debian)
   Importance: Unknown => Undecided

** Changed in: radiotray (Debian)
 Remote watch: Debian Bug tracker #801232 => None

** Changed in: radiotray (Debian)
   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/1557115

Title:
  [regression] RadioTray won't launch without python-xdg &
  gir1.2-appindicator3-0.1

Status in GTK+:
  Invalid
Status in One Hundred Papercuts:
  Confirmed
Status in radiotray package in Ubuntu:
  Triaged
Status in radiotray source package in Xenial:
  Triaged
Status in radiotray package in Debian:
  Invalid

Bug description:
  Although I've been previously running RadioTray in Ubuntu 16.04, it
  has recently become unlaunchable.

  Typically when you launch RadioTray, an indicator appears on the top-
  right-panel (left of the clock), and you are able to select a radio-
  station to stream.

  Now, when you launch it, nothing apparently happens.

  
  
  This is a lack of dependencies by default:

  Need add depends to « python-xdg and gir1.2-appindicator3-0.1 »

  
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: radiotray 0.7.3-5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 14 13:35:53 2016
  InstallationDate: Installed on 2016-03-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: radiotray
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1557115/+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 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler

[dino99]

Feedback: installing kernel 4.4.0−23 (without other kbuild∕makefile tweak)
- no crasher at installation
- reboot with no black screen

 * Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not
supported by compiler (LP: #1574982)
- SAUCE: (no-up) disable -pie when gcc has it enabled by default

Good job done 
So the other 'affected' packages can be closed now, as the kernel build config 
takes care of that issue

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

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

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

Title:
  Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
  not supported by compiler

Status in dkms package in Ubuntu:
  Invalid
Status in gcc-defaults package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in dkms source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Installing the latest 4.4.0-22 kernel ends with that error logged into 
dkmsbuildlog
  (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)

  https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt

  make "CC=cc"  KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 
NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build 
NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia 
nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules
  make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  arch/x86/Makefile:133: stack-protector enabled but compiler support broken
  Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler

  the latest error logged is:

  /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error:
  code model kernel does not support PIC mode

  Looks like it is related to the latest changes updates: gcc-6/gcc-5 
5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the 
packages built with gcc-6)
  Maybe some alternatives has not been updated to take care of these changes, 
as asked some time ago:
  http://askubuntu.com/questions/26498/choose-gcc-and-g-version

  This has been firstly reported against a nvidia crash:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gcc 4:5.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 08:41:32 2016
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2014 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2014 F...m pulseaudio
   /dev/snd/controlC0:  oem2014 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: ubuntu
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  yakkety
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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: 

[Group.of.nepali.translators] [Bug 1557115] Re: [regression] RadioTray won't launch without python-xdg

[dino99]

** Changed in: gtk
   Status: New => Invalid

** Summary changed:

- [regression] RadioTray won't launch without python-xdg
+ [regression] RadioTray won't launch without python-xdg & 
gir1.2-appindicator3.01

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

Title:
  [regression] RadioTray won't launch without python-xdg &
  gir1.2-appindicator3.01

Status in GTK+:
  Invalid
Status in One Hundred Papercuts:
  Confirmed
Status in radiotray package in Ubuntu:
  Triaged
Status in radiotray source package in Xenial:
  Triaged
Status in radiotray package in Debian:
  New

Bug description:
  Although I've been previously running RadioTray in Ubuntu 16.04, it
  has recently become unlaunchable.

  Typically when you launch RadioTray, an indicator appears on the top-
  right-panel (left of the clock), and you are able to select a radio-
  station to stream.

  Now, when you launch it, nothing apparently happens.

  
  
  This is a lack of dependencies by default:

  Need add depends to « python-xdg and gir1.2-appindicator3.01 »

  
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: radiotray 0.7.3-5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 14 13:35:53 2016
  InstallationDate: Installed on 2016-03-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: radiotray
  UpgradeStatus: No upgrade log present (probably fresh install)

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