← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1571702] Re: unable to take VM screenshot

 

This bug was fixed in the package virt-manager -
1:1.3.2-3ubuntu1.16.04.1

---------------
virt-manager (1:1.3.2-3ubuntu1.16.04.1) xenial; urgency=medium

  * debian/patches/0001-details-Fix-screenshot-on-F24-rawhide-bz-1297988.patch:
    Cherry-pick from upstream. Fix screenshot capture with newer
    gdk-pixbuf/pygobject. (LP: #1571702)

 -- Iain Lane <iain@xxxxxxxxxxxxxxxxxxx>  Wed, 18 May 2016 11:08:46
+0100

** Changed in: virt-manager (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/1571702

Title:
  unable to take VM screenshot

Status in virt-manager package in Ubuntu:
  Fix Released
Status in virt-manager source package in Xenial:
  Fix Released

Bug description:
  Description:    Ubuntu 16.04 LTS
  Release:        16.04

  [ Description, reproducer ]

  Start a KVM VM in via virt-manager. In the VM window, click "Virtual
  Machine", then "Take Screenshot" and "Save". It should save a
  screenshot.

  Instead of creating a screenshot, it creates an empty png file and
  virt-manager throws this error:

  Error taking screenshot: argument 1 must be convertible to a buffer,
  not _ResultTuple

  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/details.py", line 1455, in control_vm_screenshot
      return self._take_screenshot()
    File "/usr/share/virt-manager/virtManager/details.py", line 1507, in _take_screenshot
      file(filename, "wb").write(ret)
  TypeError: argument 1 must be convertible to a buffer, not _ResultTuple

  [ Fix ]

  Looks like "ret" is now a named tuple. Upstream have a fix to check
  for this and take 'buffer' if so. We cherry-pick this commit.

  [ Development fix ]

  The same.

  [ Regression potential ]

  I'm not sure which part of the stack changed, I can imagine that if
  you run on an older version there might have been problems if you got
  the non-named tuple. But upstream cared for this by making the new
  codepath conditional, so I can't think of any other possibilities.

  virt-manager:
    Installed: 1:1.3.2-3ubuntu1
    Candidate: 1:1.3.2-3ubuntu1
    Version table:
   *** 1:1.3.2-3ubuntu1 500
          500 http://be.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
          500 http://be.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
          100 /var/lib/dpkg/status

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virt-manager 1:1.3.2-3ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 18 17:16:49 2016
  InstallationDate: Installed on 2016-04-05 (13 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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