Bug 1038199 - gramps - after update to 3.4.6 stopped working few views
Summary: gramps - after update to 3.4.6 stopped working few views
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: gramps
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-04 15:36 UTC by Jiri Kastner
Modified: 2019-01-09 12:33 UTC (History)
4 users (show)

Fixed In Version: gramps-3.4.6-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-23 21:30:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jiri Kastner 2013-12-04 15:36:32 UTC
Description of problem:
after upgrade i'm not able to use several views, like ancestry, relationship...

Version-Release number of selected component (if applicable):
3.4.6

How reproducible:
alwaya

Steps to Reproduce:
1. create database with 3.4.5
2. import some gedcom
3. update to 3.4.6
4. restart gramps and go to database created in step 1
5. click on 'Ancestry' view
6. check results

Actual results:

[user@localhost ~]$ gramps
/usr/share/gramps/Utils.py:286: DeprecationWarning: Module 'PyICU' is deprecated, import 'icu' instead'
  import PyICU
2013-12-04 16:16:35.785: ERROR: gramps.py: line 107: Unhandled exception
Traceback (most recent call last):
  File "/usr/share/gramps/gui/viewmanager.py", line 1032, in view_changed
    self.__change_page(page_num)
  File "/usr/share/gramps/gui/viewmanager.py", line 1045, in __change_page
    self.active_page.set_active()
  File "/usr/share/gramps/gui/views/navigationview.py", line 154, in set_active
    PageView.set_active(self)
  File "/usr/share/gramps/gui/views/pageview.py", line 305, in set_active
    self.build_tree()
  File "/usr/share/gramps/plugins/view/pedigreeview.py", line 856, in build_tree
    self.rebuild_trees(active)
  File "/usr/share/gramps/plugins/view/pedigreeview.py", line 1023, in rebuild_trees
    self.find_tree(person, 0, 1, lst)
  File "/usr/share/gramps/plugins/view/pedigreeview.py", line 1677, in find_tree
    alive = probably_alive(person, self.dbstate.db)
  File "/usr/share/gramps/Utils.py", line 991, in probably_alive
    birth, death, explain))
ValueError: zero length field name in format



Expected results:
will work as expected

Additional info:

Comment 1 Douglas Blank 2013-12-04 16:31:51 UTC
This was fixed in Gramps 3.4.7:

http://www.gramps-project.org/bugs/view.php?id=7167

Please use our bug tracker in the future; thanks!

Comment 2 Jiri Kastner 2013-12-04 20:22:13 UTC
(In reply to Douglas Blank from comment #1)
> This was fixed in Gramps 3.4.7:
> 
> http://www.gramps-project.org/bugs/view.php?id=7167
> 
> Please use our bug tracker in the future; thanks!

i know i run in-the-place 3.4.7, but it was not yet released :)

Comment 3 Fedora Update System 2013-12-07 20:27:01 UTC
gramps-3.4.6-2.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/gramps-3.4.6-2.el6

Comment 4 Fedora Update System 2013-12-08 18:27:48 UTC
Package gramps-3.4.6-2.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing gramps-3.4.6-2.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12320/gramps-3.4.6-2.el6
then log in and leave karma (feedback).

Comment 5 Jiri Kastner 2013-12-10 10:18:06 UTC
small note, 'about' dialog shows 3.4.6-1 while this is 3.4.6-2 release

Comment 6 Robert Scheck 2013-12-10 10:36:12 UTC
Good pointer. I just backported the fix and didn't notice this. I just was
very interested in getting my local gramps working again. I expect that the
3.4.7 release anyway fixes that.

Comment 7 Fedora Update System 2013-12-23 21:30:19 UTC
gramps-3.4.6-2.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.


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