Bug 1299426 - AttributeError: 'NoneType' object has no attribute 'add'
AttributeError: 'NoneType' object has no attribute 'add'
Product: Virtualization Tools
Classification: Community
Component: virt-manager (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Cole Robinson
Depends On:
  Show dependency treegraph
Reported: 2016-01-18 05:55 EST by Oliver Leitner
Modified: 2016-01-19 10:28 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-01-19 10:28:18 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Compile and Install and Error Log (27.84 KB, text/plain)
2016-01-18 05:55 EST, Oliver Leitner
no flags Details

  None (edit)
Description Oliver Leitner 2016-01-18 05:55:07 EST
Created attachment 1115799 [details]
Compile and Install and Error Log

Type of error:
Reproducible, show-stopper

Follow up errors:
No icons/text shown in "storage"

Program Version:
Github version from 18.01.2016 / 11:30

Distributor ID: Ubuntu
Description:    Ubuntu 14.04.3 LTS
Release:        14.04
Codename:       trusty

Linux MyOwn 4.3.0-040300rc6-lowlatency #201510182030 SMP PREEMPT Mon Oct 19 00:36:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Starting freshly build and installed virt-manager from /usr/local/bin/virt-manager and trying to create a new machine does not work, causes the above error message in a box.

virt-manager.build.log (build and install tasks logged)
virt-manager.log (output from ~/.cache/virt-manager/virt-manager.log)

Running the old version via /usr/bin/virt-manager

Bugtracker specific:
Needed to combine both logs, as your bugzilla doesnt support more than one attachment.
Comment 1 Oliver Leitner 2016-01-19 09:30:02 EST
ok, i think i found the problem myself.

for some reason, the git version of virt-manager doesnt install under /usr/local anymore, but instead overwrites stuff in /usr.

so the version under /usr/bin indeed is the more current one, thats also why it might work.

the version i had under /usr/local was 1.2.1, somewhere around that version, the behaviour of the make install changed.

i dont know if thats a bug or a feature?
Comment 2 Cole Robinson 2016-01-19 10:28:18 EST
The build system was changed a bit in the last release, the default install directory is different. The reason is that things like gsettings schema don't work by default under /usr/local, so the user had to do some extra steps to make it work. Use python setup.py configure --prefix=/usr/local to maintain the old behavior

Note You need to log in before you can comment on or make changes to this bug.