On Wed, 08 Jan 2014, Michael Hamilton wrote:
I recently upgraded to 13.1 from 12.3. On both yast2 disk is failing to start. After answering yes to the standard warning popup dialog, yast2 disk terminates. If I run yast2 disk from the command line I see the following messages:
Unknown config. Invalid snapshot ''.
The first message is general and occurs whenever I start any yast2 module, but doesn't seem to be causing any issues. The second message occurs when yast2 disk terminates.
This machine is anything but a fresh install, and has been upgraded through several releases and has also had a change in hostname.
Looking in /var/log/messages/YaST2/y2log I can see:
2014-01-08 09:39:24 <1> kosmos1(9914) [libstorage] Storage.cc(equalBackupStates):7514 lhs:expert-partitioner rhs: verbose:true 2014-01-08 09:39:24 <1> kosmos1(9914) [libstorage] Storage.cc(equalBackupStates):7564 ret:true 2014-01-08 09:39:24 <1> kosmos1(9914) [libstorage] Storage.cc(createBackupState):7448 comp:true 2014-01-08 09:39:24 <3> kosmos1(9914) [Ruby] yast/wfm.rb:86 Client call failed with key not found: :CT_UNKNOWN and backtrace ["/usr/share/YaST2/modules/StorageFields.rb:70:in `fetch'", "/usr/share/YaST2/modules/StorageFields.rb:70:in `block in IterateTargetMap'", "/usr/share/YaST2/modules/StorageFields.rb:69:in `sort!'", "/usr/share/YaST2/modules/StorageFields.rb:69:in `IterateTargetMap'", "/usr/share/YaST2/include/partitioning/ep-main.rb:363:in `MakeNavigationTree'", "/usr/share/YaST2/include/partitioning/ep-main.rb:664:in `ExpertPartitioner'", "/usr/share/YaST2/clients/inst_custom_part.rb:37:in `main'", "/usr/share/YaST2/clients/inst_custom_part.rb:42:in `
'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:71:in `CallFunction'", "/usr/share/YaST2/clients/inst_disk.rb:84:in `main'", "/usr/share/YaST2/clients/inst_disk.rb:105:in ` '", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:71:in `CallFunction'", "/usr/share/YaST2/clients/disk_worker.rb:88:in `DiskSequence'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/fun_ref.rb:33:in `call'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/fun_ref.rb:33:in `call'", "/usr/share/YaST2/modules/CommandLine.rb:1590:in `Run'", "/usr/share/YaST2/clients/disk_worker.rb:80:in `main'", "/usr/share/YaST2/clients/disk_worker.rb:158:in ` '", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:67:in `call'", "/usr/share/YaST2/clients/disk.rb:85:in `main'", "/usr/share/YaST2/clients/disk.rb:103:in ` '", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'"] 2014-01-08 09:39:24 <1> kosmos1(9914) [Interpreter] clients/inst_disk.rb:84 Called YaST client returned. 2014-01-08 09:39:24 <2> kosmos1(9914) [Ruby] yast/convert.rb:54 Cannot convert FalseClass from 'any' to 'symbol' 2014-01-08 09:39:24 <1> kosmos1(9914) [Ruby] clients/inst_disk.rb:99 end inst_disk ret:nil 2014-01-08 09:39:24 <1> kosmos1(9914) [Interpreter] clients/disk_worker.rb:88 Called YaST client returned. 2
See https://bugzilla.novell.com/show_bug.cgi?id=861301 The suggested patch fixes the issue. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org