After some fiddling, I get a different failure.  I populated the thin LV, took a number of multisnap snapshots, then deleted the snapshots.

Here is the output of lvs --all and the crash from system-config-lvm

$ lvs --all
  LV            VG   Attr     LSize   Pool  Origin Data%  Move Log Copy%  Convert
  home          g1   -wi-ao--  15.62g
  root          g1   -wi-ao--  15.62g
  spare         g1   -wi-ao--  36.00g
  spare         g2   -wi-ao-- 515.00g
  swap          g2   -wi-a--- 100.50g
  vhome         g2   -wi-ao-- 100.00g
  vimages       g2   Vwi-aotz 399.00g vpool         15.16
  vpool         g2   twi-a-tz 399.00g               15.16
  [vpool_tdata] g2   Twi-aot- 399.00g
  [vpool_tmeta] g2   ewi-aot- 100.00m

[root@vh3] ~
$ system-config-lvm
Traceback (most recent call last):
  File "/usr/sbin/system-config-lvm", line 172, in <module>
    runFullGUI()
  File "/usr/sbin/system-config-lvm", line 157, in runFullGUI
    blvm = baselvm(glade_xml, app)
  File "/usr/sbin/system-config-lvm", line 105, in __init__
    self.volume_tab_view = Volume_Tab_View(glade_xml, self.lvmm, self.main_win)
  File "/usr/share/system-config-lvm/Volume_Tab_View.py", line 133, in __init__
    self.prepare_tree()
  File "/usr/share/system-config-lvm/Volume_Tab_View.py", line 214, in prepare_tree
    self.model_factory.reload()
  File "/usr/share/system-config-lvm/lvm_model.py", line 168, in reload
    self.__query_LVs()
  File "/usr/share/system-config-lvm/lvm_model.py", line 520, in __query_LVs
    ph_ext_beg = int(devs[0][idx+1:len(devs[0])-1])
ValueError: invalid literal for int() with base 10: ''

I took a look at the code last night and realized that there is zero support for the new multisnap LVs (pools and thinp volumes).  The change in error messages was solely due to a rename of the pool which changed the parsing order of the various LVs.

I tried to extend some of the attribute checking logic to just ignore the new LV types ("t" and "V"), but without a real understanding of the overall design, that became a game of whack-a-mole.

My immediate use case is to make the GUI tool usable for legacy VMs, while I create a few multisnap volumes (mainly for hourly snapshots of an origin LV holding all my VM images).  Does anybody with an understanding of the GUI architecture have suggestions on whether there is some simply way to "NO-OP" the new LVs, and if so, provide some suggestions?

Thanks!

OOPS in the above comment about my use case I meant "legacy LVs", NOT "legacy VMs" :-(

Yes, system-config-lvm is rather in maintenance mode, and new features are not added, thus system-config-lvm gets confused when new LV types are available.

@Charles:

I will try to fix it, so system-config-lvm won't crash and will be usable for supported volumes. Zdenek is right that we are in maintanance mode and this tool will be soon replaced by alternative which can keep track of dynamicity of development.

Created attachment 650755 [details]
Patch to avoid immediate crash with thin LV and snapshots

I tweaked the existing code a bit to the point where it will show the new thin LVs and both classic and new snapshots without crashing.  I took the approach of only rendering LVs on the GUI cylinder when they were the SOLE owner of some storage blocks.  Thus I inhibited rendering of thin LVs (regular or snapshots) as well as the thin pool LV (since it is just a holder for its two underlying LVs), but do render the two underlying <pool>_tdata and <pool>_tmeta LV's.

I did NOT suppress the listing of all of the LVs, just the space rendering on the GUI cylinder.

Note sure it that is in line with what you are planning, but it works for my needs.

I have attached a patch file (with some commented out debug print) in case it is useful.  This is my first foray into Python.  Please excuse any newbie goofiness.

I tried the above patches on my Fedora-17 system with system-config-lvm-1.1.18, but it was not successful, even though the 5 patched files are almost identical between 1.1.12 and 1.1.18.  The GUI comes up after emitting some error messages, then seems to hang.

So sad :-(

@Charles:

sorry for late response. 

Thin pools/volumes are not supported because this project is in maintaince mode only but it surely should not crash. Patch that fixes this was sent to upstream and will be part of next version. 

http://git.fedorahosted.org/cgit/system-config-lvm.git/commit/?id=97b353cc0469f6067f53117a9557d6750bd00dc2

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1403.html