{"id":7637,"date":"2023-02-12T17:05:01","date_gmt":"2023-02-12T15:05:01","guid":{"rendered":"https:\/\/hex.ro\/wp\/?p=7637"},"modified":"2023-02-13T09:01:47","modified_gmt":"2023-02-13T07:01:47","slug":"error-launching-details-nothing-connected-to-bound-method-vmmvmwindow-control_vm_pause-of-vmwindow-vmmvmwindow","status":"publish","type":"post","link":"https:\/\/hex.ro\/wp\/blog\/error-launching-details-nothing-connected-to-bound-method-vmmvmwindow-control_vm_pause-of-vmwindow-vmmvmwindow\/","title":{"rendered":"Nothing connected to bound method vmmVMWindow.control_vm_pause"},"content":{"rendered":"\n<p>This error appeared after upgrading to Fedora 36 and leaving Virt-Manager (Virtual Machine Manager) running for few days.<\/p>\n\n\n\n<p>Reconnecting to my session, I couldn&#8217;t open (or start) any VM, since most clicks were followed by this popup:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"402\" height=\"513\" src=\"https:\/\/hex.ro\/wp\/wp-content\/uploads\/2023\/02\/Screenshot_2023-02-12_15-12-42.png\" alt=\"\" class=\"wp-image-7638\" srcset=\"https:\/\/hex.ro\/wp\/wp-content\/uploads\/2023\/02\/Screenshot_2023-02-12_15-12-42.png 402w, https:\/\/hex.ro\/wp\/wp-content\/uploads\/2023\/02\/Screenshot_2023-02-12_15-12-42-235x300.png 235w\" sizes=\"auto, (max-width: 402px) 100vw, 402px\" \/><figcaption class=\"wp-element-caption\">Virtual Machine Manager Error<\/figcaption><\/figure>\n\n\n\n<p>I&#8217;ve tried to restart Virt-Manager, but I was encountering the same behavior.<\/p>\n\n\n\n<p>Finally, the problem was that <code>virt-manager<\/code> was still running in the background, even if the GUI part was closed:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code><code>$ ps -ef | grep python\nroot      1056      1 0 Jan31 ? 00:00:00 \/usr\/bin\/python3 -s \/usr\/sbin\/firewalld --nofork --nopid\nroot      1159      1 0 Jan31 ? 00:02:12 \/usr\/bin\/python3 \/usr\/bin\/supervisord -c \/etc\/supervisord.conf\nviulian 411081 410754 0 Feb07 ? 00:00:01 \/usr\/bin\/python3 \/usr\/bin\/blueman-applet\nviulian 412909      1 0 Feb07 ? 00:58:56 \/usr\/bin\/python3 \/usr\/bin\/virt-manager\nviulian 714827 714779 0 15:30 pts\/4 00:00:00 grep --color=auto python<\/code><\/code><\/pre>\n\n\n\n<p>A <code>kill -9 412909<\/code> fixed the problem.<\/p>\n\n\n\n<p>The full message was:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>Error launching details: nothing connected to &lt;bound method vmmVMWindow.control_vm_pause of &lt;vmwindow.vmmVMWindow object at 0x7f4cf897c880 (virtManager+vmwindow+vmmVMWindow at 0x55d716a88aa0)&gt;&gt;<\/p>\n\n\n\n<p>Traceback (most recent call last):<\/p>\n\n\n\n<p>File &#8220;\/usr\/share\/virt-manager\/virtManager\/vmwindow.py&#8221;, line 475, in set_pause_state<\/p>\n\n\n\n<p>src.handler_block_by_func(self.control_vm_pause)<\/p>\n\n\n\n<p>TypeError: nothing connected to &lt;bound method vmmVMWindow.control_vm_pause of &lt;vmwindow.vmmVMWindow object at 0x7f4cf897c880 (virtManager+vmwindow+vmmVMWindow at 0x55d716a88aa0)&gt;&gt;<\/p>\n\n\n\n<p>During handling of the above exception, another exception occurred:<\/p>\n\n\n\n<p>Traceback (most recent call last):<\/p>\n\n\n\n<p>File &#8220;\/usr\/share\/virt-manager\/virtManager\/vmwindow.py&#8221;, line 40, in get_instance<\/p>\n\n\n\n<p>cls._instances[key] = vmmVMWindow(vm)<\/p>\n\n\n\n<p>File &#8220;\/usr\/share\/virt-manager\/virtManager\/vmwindow.py&#8221;, line 157, in __init__<\/p>\n\n\n\n<p>self._refresh_vm_state()<\/p>\n\n\n\n<p>File &#8220;\/usr\/share\/virt-manager\/virtManager\/vmwindow.py&#8221;, line 425, in _refresh_vm_state<\/p>\n\n\n\n<p>self.set_pause_state(paused)<\/p>\n\n\n\n<p>File &#8220;\/usr\/share\/virt-manager\/virtManager\/vmwindow.py&#8221;, line 478, in set_pause_state<\/p>\n\n\n\n<p>src.handler_unblock_by_func(self.control_vm_pause)<\/p>\n\n\n\n<p>TypeError: nothing connected to &lt;bound method vmmVMWindow.control_vm_pause of &lt;vmwindow.vmmVMWindow object at 0x7f4cf897c880 (virtManager+vmwindow+vmmVMWindow at 0x55d716a88aa0)&gt;&gt;<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>This error appeared after upgrading to Fedora 36 and leaving Virt-Manager (Virtual Machine Manager) running for few days. Reconnecting to my session, I couldn&#8217;t open (or start) any VM, since most clicks were followed by this popup: I&#8217;ve tried to restart Virt-Manager, but I was encountering the same behavior. Finally, the problem was that virt-manager [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[24],"tags":[],"class_list":["post-7637","post","type-post","status-publish","format-standard","hentry","category-it"],"_links":{"self":[{"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/posts\/7637","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/comments?post=7637"}],"version-history":[{"count":4,"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/posts\/7637\/revisions"}],"predecessor-version":[{"id":7679,"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/posts\/7637\/revisions\/7679"}],"wp:attachment":[{"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/media?parent=7637"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/categories?post=7637"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hex.ro\/wp\/wp-json\/wp\/v2\/tags?post=7637"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}