Qubes manager segfaults
111 views
Skip to first unread message
Pascal Nexus
Sep 13, 2015, 12:12:06 PM9/13/15
to qubes...@googlegroups.com
Hi.
I run Qubes 3.0 with all the updates and sometimes qubes-manager segfaults.
I run Qubes 3.0 with all the updates and sometimes qubes-manager segfaults.
I can reproduce this issue when starting qubes-manager from the console and when I start or stop the sys-net or sys-firewall (it depends...).
Please look at the attachment.
Best regards
Marek Marczykowski-Górecki
Sep 13, 2015, 2:15:12 PM9/13/15
to Pascal Nexus, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
We've been hunting this issue for some time, but not able to reproduce
it... If you're able to reproduce it, call "ulimit -c unlimited" before
starting qubes-manager - this would create core dump the next time
qubes-manager will crash. Then extract backtrace with "gdb -ex bt
/usr/bin/python core.*". You may need to install gdb first (using
qubes-dom0-update).
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCAAGBQJV9b0pAAoJENuP0xzK19csUccH/3vArE45MBXQFxVeNGMuuH2w
WaDa+5Kdv7gMomO42EfKYiJYV8Su5F4Mtvdyk/ID52ehbFC9nhlLguchi6jkWmDz
87RLUJh9zl1QOwWxP6BDymLpfb8Ul6ZUElPoGg4qCybseKNijQseGJ+xaGMusYMA
5a0ceDWRioeNGD+qNoRH2+jZaRSIRlr+MXX2G/wxWoz2bmOHsdR4Ms0NSkd6uelU
rYeG1+WSN+Gf/yudFndKdUmd/ur94gF7PLJbit5FWEJTvoQH7fnSFaeV5MqnIB7I
3egKv+tBfdIhkr2yOReSEIt9Zr5jLSEmGZUadxvVoamKyNmt2zoAtQTbqfWyYEE=
=p3Se
-----END PGP SIGNATURE-----
Hash: SHA256
it... If you're able to reproduce it, call "ulimit -c unlimited" before
starting qubes-manager - this would create core dump the next time
qubes-manager will crash. Then extract backtrace with "gdb -ex bt
/usr/bin/python core.*". You may need to install gdb first (using
qubes-dom0-update).
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCAAGBQJV9b0pAAoJENuP0xzK19csUccH/3vArE45MBXQFxVeNGMuuH2w
WaDa+5Kdv7gMomO42EfKYiJYV8Su5F4Mtvdyk/ID52ehbFC9nhlLguchi6jkWmDz
87RLUJh9zl1QOwWxP6BDymLpfb8Ul6ZUElPoGg4qCybseKNijQseGJ+xaGMusYMA
5a0ceDWRioeNGD+qNoRH2+jZaRSIRlr+MXX2G/wxWoz2bmOHsdR4Ms0NSkd6uelU
rYeG1+WSN+Gf/yudFndKdUmd/ur94gF7PLJbit5FWEJTvoQH7fnSFaeV5MqnIB7I
3egKv+tBfdIhkr2yOReSEIt9Zr5jLSEmGZUadxvVoamKyNmt2zoAtQTbqfWyYEE=
=p3Se
-----END PGP SIGNATURE-----
Connor Page
Sep 13, 2015, 4:32:23 PM9/13/15
to qubes-users
I have one vm that almost always crashes qubes-manager. I hope this log will help.
=====
[me@dom0 ~]$ ulimit -c unlimited
[me@dom0 ~]$ qubes-manager
libpng warning: iCCP: known incorrect sRGB profile
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Oxygen::WidgetStateEngine(0x2588010), parent's thread is QThread(0x2056df0), current thread is QThread(0x7f1e740029b0)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Oxygen::ScrollBarEngine(0x2589210), parent's thread is QThread(0x2056df0), current thread is QThread(0x7f1e740029b0)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Oxygen::WidgetStateEngine(0x2588010), parent's thread is QThread(0x2056df0), current thread is QThread(0x7f1e740029b0)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Oxygen::ScrollBarEngine(0x2589210), parent's thread is QThread(0x2056df0), current thread is QThread(0x7f1e740029b0)
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPainter::begin: Paint device returned engine == 0, type: 2
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
Segmentation fault (core dumped)
[me@dom0 ~]$ gdb -ex bt /usr/bin/python core.*
GNU gdb (GDB) Fedora 7.7.1-21.fc20
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/python...Reading symbols from /usr/bin/python...(no debugging symbols found)...done.
(no debugging symbols found)...done.
=====
[me@dom0 ~]$ ulimit -c unlimited
[me@dom0 ~]$ qubes-manager
libpng warning: iCCP: known incorrect sRGB profile
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Oxygen::WidgetStateEngine(0x2588010), parent's thread is QThread(0x2056df0), current thread is QThread(0x7f1e740029b0)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Oxygen::ScrollBarEngine(0x2589210), parent's thread is QThread(0x2056df0), current thread is QThread(0x7f1e740029b0)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Oxygen::WidgetStateEngine(0x2588010), parent's thread is QThread(0x2056df0), current thread is QThread(0x7f1e740029b0)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Oxygen::ScrollBarEngine(0x2589210), parent's thread is QThread(0x2056df0), current thread is QThread(0x7f1e740029b0)
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPainter::begin: Paint device returned engine == 0, type: 2
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
Segmentation fault (core dumped)
[me@dom0 ~]$ gdb -ex bt /usr/bin/python core.*
GNU gdb (GDB) Fedora 7.7.1-21.fc20
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/python...Reading symbols from /usr/bin/python...(no debugging symbols found)...done.
(no debugging symbols found)...done.
warning: core file may not match specified executable file.
[New LWP 29090]
[New LWP 29093]
[New LWP 29213]
[New LWP 29085]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/python2 /usr/bin/qubes-manager'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00000039bd2b0ec2 in qt_toX11Pixmap(QPixmap const&) () from /lib64/libQtGui.so.4
#0 0x00000039bd2b0ec2 in qt_toX11Pixmap(QPixmap const&) () from /lib64/libQtGui.so.4
#1 0x00000039bd261099 in QWidgetPrivate::setWindowIcon_sys(bool) () from /lib64/libQtGui.so.4
#2 0x00000039bd21437a in QWidget::create(unsigned long, bool, bool) () from /lib64/libQtGui.so.4
#3 0x00000039bd21ce6a in QWidget::setVisible(bool) () from /lib64/libQtGui.so.4
#4 0x00000039bd693f9e in QDialog::setVisible(bool) () from /lib64/libQtGui.so.4
#5 0x00007f1e8c221cfc in sipQMessageBox::setVisible(bool) ()
Missing separate debuginfos, use: debuginfo-install python-2.7.5-16.fc20.x86_64
---Type <return> to continue, or q <return> to quit---
from /usr/lib64/python2.7/site-packages/PyQt4/QtGui.so
#6 0x00000039bd693a06 in QDialog::exec() () from /lib64/libQtGui.so.4
#7 0x00007f1e8c41c2f5 in meth_QDialog_exec_ () from /usr/lib64/python2.7/site-packages/PyQt4/QtGui.so
#8 0x00000039b04e0bc4 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#9 0x00000039b04e21dd in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
#10 0x00000039b046f0d8 in ?? () from /lib64/libpython2.7.so.1.0
#11 0x00000039b044a0d3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
#12 0x00000039b04dc027 in PyEval_CallObjectWithKeywords () from /lib64/libpython2.7.so.1.0
#13 0x00000039b04fcf7c in PyErr_PrintEx () from /lib64/libpython2.7.so.1.0
#14 0x00007f1e8839634d in libvirt_virConnectDomainEventLifecycleCallback ()
from /usr/lib64/python2.7/site-packages/libvirtmod.so
#15 0x00007f1e87f75bca in virDomainEventDispatchDefaultFunc () from /lib64/libvirt.so.0
#16 0x00007f1e87f74101 in virObjectEventTimer () from /lib64/libvirt.so.0
#17 0x00007f1e87eeef09 in virEventPollRunOnce () from /lib64/libvirt.so.0
#18 0x00007f1e87eed862 in virEventRunDefaultImpl () from /lib64/libvirt.so.0
#19 0x00007f1e883a0466 in libvirt_virEventRunDefaultImpl ()
from /usr/lib64/python2.7/site-packages/libvirtmod.so
#20 0x00000039b04e0bc4 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#21 0x00000039b04e0980 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#22 0x00000039b04e21dd in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
#23 0x00000039b046f1cd in ?? () from /lib64/libpython2.7.so.1.0
#24 0x00000039b044a0d3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
#25 0x00000039b04dd417 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#26 0x00000039b04e0980 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#27 0x00000039b04e0980 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#28 0x00000039b04e21dd in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
#29 0x00000039b046f0d8 in ?? () from /lib64/libpython2.7.so.1.0
#30 0x00000039b044a0d3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
#31 0x00000039b04590c5 in ?? () from /lib64/libpython2.7.so.1.0
#32 0x00000039b044a0d3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
#33 0x00000039b04dc027 in PyEval_CallObjectWithKeywords () from /lib64/libpython2.7.so.1.0
#34 0x00000039b0510822 in ?? () from /lib64/libpython2.7.so.1.0
#35 0x00000039ad407ee5 in start_thread () from /lib64/libpthread.so.0
#36 0x00000039ad0f4d1d in clone () from /lib64/libc.so.6
Marek Marczykowski-Górecki
Sep 13, 2015, 5:04:24 PM9/13/15
to Connor Page, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Sun, Sep 13, 2015 at 01:32:22PM -0700, Connor Page wrote:
> I have one vm that almost always crashes qubes-manager. I hope this log will help.
Yes, its somehow helpful :)
> I have one vm that almost always crashes qubes-manager. I hope this log will help.
In short: it crashes when trying to show (graphical) error message. Could
you disable that handler and retry (to see the actual message)? Edit
/usr/lib64/python2.7/site-packages/qubesmanager/main.py and comment out
line 2025 (sys.excepthook = handle_exception).
question is where QPixmap is used and why it is outsize of the GUI
thread. This is where the backtrace helps a little.
> #7 0x00007f1e8c41c2f5 in meth_QDialog_exec_ () from /usr/lib64/python2.7/site-packages/PyQt4/QtGui.so
> #8 0x00000039b04e0bc4 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
> #9 0x00000039b04e21dd in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
> #10 0x00000039b046f0d8 in ?? () from /lib64/libpython2.7.so.1.0
> #11 0x00000039b044a0d3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #12 0x00000039b04dc027 in PyEval_CallObjectWithKeywords () from /lib64/libpython2.7.so.1.0
> #13 0x00000039b04fcf7c in PyErr_PrintEx () from /lib64/libpython2.7.so.1.0
> #14 0x00007f1e8839634d in libvirt_virConnectDomainEventLifecycleCallback ()
> from /usr/lib64/python2.7/site-packages/libvirtmod.so
explicit dialog message call there
(qubes.qubesutils.QubesWatch._domain_list_changed), so I guess it tries
to some some error message (python exception).
> #15 0x00007f1e87f75bca in virDomainEventDispatchDefaultFunc () from /lib64/libvirt.so.0
> #16 0x00007f1e87f74101 in virObjectEventTimer () from /lib64/libvirt.so.0
> #17 0x00007f1e87eeef09 in virEventPollRunOnce () from /lib64/libvirt.so.0
> #18 0x00007f1e87eed862 in virEventRunDefaultImpl () from /lib64/libvirt.so.0
> #19 0x00007f1e883a0466 in libvirt_virEventRunDefaultImpl ()
> from /usr/lib64/python2.7/site-packages/libvirtmod.so
> #20 0x00000039b04e0bc4 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
> #21 0x00000039b04e0980 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
> #22 0x00000039b04e21dd in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
> #23 0x00000039b046f1cd in ?? () from /lib64/libpython2.7.so.1.0
> #24 0x00000039b044a0d3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #25 0x00000039b04dd417 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
> ---Type <return> to continue, or q <return> to quit---
> #26 0x00000039b04e0980 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
> #27 0x00000039b04e0980 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
> #28 0x00000039b04e21dd in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
> #29 0x00000039b046f0d8 in ?? () from /lib64/libpython2.7.so.1.0
> #30 0x00000039b044a0d3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #31 0x00000039b04590c5 in ?? () from /lib64/libpython2.7.so.1.0
> #32 0x00000039b044a0d3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #33 0x00000039b04dc027 in PyEval_CallObjectWithKeywords () from /lib64/libpython2.7.so.1.0
> #34 0x00000039b0510822 in ?? () from /lib64/libpython2.7.so.1.0
> #35 0x00000039ad407ee5 in start_thread () from /lib64/libpthread.so.0
> #36 0x00000039ad0f4d1d in clone () from /lib64/libc.so.6
>
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCAAGBQJV9eTRAAoJENuP0xzK19cs6ywH/id3Qj0nubmnCKL0SSoJ9rcH
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
/lxUvM1SNZm80d42kneXQUPAWbm5XloTXhqFk8g/66L7mri/4mWcEVmpLqWHwK8S
wZV4NkCKuDaREBsMW5NavlfDa3wsYgBecZBUumKr7+FyrJcw6LRIz+FLo8rnNh4+
c8Ql+c2y3X88gS28v9648QAHY8HqjexO+4Mbc6Hv57ORqLny+kNFBkgpjFw6QcfM
qMyQlW02IDZREvnIYIKeqMnP/PUkmV3BhLYOQWl4tEltuQ07fuvuCvRP7eyzT5Zc
se8geSd7VjhFPC4m7WyokdtmQmjgPtyvprxo5DLmh4FqL2VXQQE1/sZcKp6caIU=
=dL7N
-----END PGP SIGNATURE-----
pasca...@gmail.com
Sep 14, 2015, 1:09:07 PM9/14/15
to qubes-users, pasca...@gmail.com
I don't know how to copy/paste from the dom0 but I can make a photo if you're interested.
Connor Page
Sep 14, 2015, 7:13:43 PM9/14/15
to qubes-users
LOL. After commenting that line out qubes-manager doesn't crash anymore, the vm starts properly and there are no warning windows.
Still, there is a problem somewhere else. This appears in the console:
[me@dom0 ~]$ qubes-manager
libpng warning: iCCP: known incorrect sRGB profile
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4607, in _dispatchDomainEventLifecycleCallback
cb(self, virDomain(self, _obj=dom), event, detail, opaque)
File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 827, in _domain_list_changed
self._register_watches(domain)
File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 810, in _register_watches
self._qdb[name].watch('/qubes-block-devices')
qubes.qdb.Error: (104, 'Connection reset by peer')
Still, there is a problem somewhere else. This appears in the console:
[me@dom0 ~]$ qubes-manager
libpng warning: iCCP: known incorrect sRGB profile
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4607, in _dispatchDomainEventLifecycleCallback
cb(self, virDomain(self, _obj=dom), event, detail, opaque)
File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 827, in _domain_list_changed
self._register_watches(domain)
File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 810, in _register_watches
self._qdb[name].watch('/qubes-block-devices')
qubes.qdb.Error: (104, 'Connection reset by peer')
But again, when it gets past this the vm continues to boot, not stuck in some transitional state. I guess it's something else, not qubes-manager that tries to notify me about qubes db error and crash qubes-manager.
Marek Marczykowski-Górecki
Sep 14, 2015, 7:26:33 PM9/14/15
to Connor Page, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Mon, Sep 14, 2015 at 04:13:43PM -0700, Connor Page wrote:
> LOL. After commenting that line out qubes-manager doesn't crash anymore, the vm starts properly and there are no warning windows.
> Still, there is a problem somewhere else. This appears in the console:
> [me@dom0 ~]$ qubes-manager
> libpng warning: iCCP: known incorrect sRGB profile
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4607, in _dispatchDomainEventLifecycleCallback
> cb(self, virDomain(self, _obj=dom), event, detail, opaque)
> File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 827, in _domain_list_changed
> self._register_watches(domain)
> File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 810, in _register_watches
> self._qdb[name].watch('/qubes-block-devices')
> qubes.qdb.Error: (104, 'Connection reset by peer')
Thanks, now I know where to look :)
> LOL. After commenting that line out qubes-manager doesn't crash anymore, the vm starts properly and there are no warning windows.
> Still, there is a problem somewhere else. This appears in the console:
> [me@dom0 ~]$ qubes-manager
> libpng warning: iCCP: known incorrect sRGB profile
> Traceback (most recent call last):
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4607, in _dispatchDomainEventLifecycleCallback
> cb(self, virDomain(self, _obj=dom), event, detail, opaque)
> File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 827, in _domain_list_changed
> self._register_watches(domain)
> File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 810, in _register_watches
> self._qdb[name].watch('/qubes-block-devices')
> qubes.qdb.Error: (104, 'Connection reset by peer')
> But again, when it gets past this the vm continues to boot, not stuck in some transitional state. I guess it's something else, not qubes-manager that tries to notify me about qubes db error and crash qubes-manager.
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
+RBYgqXWdTxvoi2ezQMAGGdo68N0tPy1MzSwt7MWJRihKpYzo4ZhtD7uTRvgmEnv
ih/r4Hclph9P7Jp+OxHhT5ZVig/d8ET0IZ+lUmPdrN3GhiOj6XcpNy3t78JlyiZV
6+lBIFkRO7p+2rLOhCM+LKtbleYV5ecFdsiNu3ficgYSti3BK1R5AP9oTMTNz+gh
h3amuzax/kNbTqlNehQ0iAeMwHY9PWNOtjv/2H1w/NmIMaPL9hG1ytwB9zkfhzMF
I8RTXG6pMBJnVyi8RTypLuFtNfGv2EHnLAAq2BAx+3+FM+WzCwQbN2e9n7gGJQ0=
=XTN1
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Sep 14, 2015, 7:38:56 PM9/14/15
to Connor Page, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Tue, Sep 15, 2015 at 01:26:25AM +0200, Marek Marczykowski-Górecki wrote:
> On Mon, Sep 14, 2015 at 04:13:43PM -0700, Connor Page wrote:
> > LOL. After commenting that line out qubes-manager doesn't crash anymore, the vm starts properly and there are no warning windows.
> > Still, there is a problem somewhere else. This appears in the console:
> > [me@dom0 ~]$ qubes-manager
> > libpng warning: iCCP: known incorrect sRGB profile
> > Traceback (most recent call last):
> > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4607, in _dispatchDomainEventLifecycleCallback
> > cb(self, virDomain(self, _obj=dom), event, detail, opaque)
> > File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 827, in _domain_list_changed
> > self._register_watches(domain)
> > File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 810, in _register_watches
> > self._qdb[name].watch('/qubes-block-devices')
> > qubes.qdb.Error: (104, 'Connection reset by peer')
>
> Thanks, now I know where to look :)
>
> > But again, when it gets past this the vm continues to boot, not stuck in some transitional state. I guess it's something else, not qubes-manager that tries to notify me about qubes db error and crash qubes-manager.
>
> Is that by any chance some HVM domain? Windows? With tools or without?
Ok, finally I've managed to reproduce the issue:
> On Mon, Sep 14, 2015 at 04:13:43PM -0700, Connor Page wrote:
> > LOL. After commenting that line out qubes-manager doesn't crash anymore, the vm starts properly and there are no warning windows.
> > Still, there is a problem somewhere else. This appears in the console:
> > [me@dom0 ~]$ qubes-manager
> > libpng warning: iCCP: known incorrect sRGB profile
> > Traceback (most recent call last):
> > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4607, in _dispatchDomainEventLifecycleCallback
> > cb(self, virDomain(self, _obj=dom), event, detail, opaque)
> > File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 827, in _domain_list_changed
> > self._register_watches(domain)
> > File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 810, in _register_watches
> > self._qdb[name].watch('/qubes-block-devices')
> > qubes.qdb.Error: (104, 'Connection reset by peer')
>
> Thanks, now I know where to look :)
>
> > But again, when it gets past this the vm continues to boot, not stuck in some transitional state. I guess it's something else, not qubes-manager that tries to notify me about qubes db error and crash qubes-manager.
>
> Is that by any chance some HVM domain? Windows? With tools or without?
1. create HVM domain (no need to install any OS there)
2. start it from qubes-manager (not console, not menu)
It crashes in about 50% cases.
Thanks for the info provided!
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
OBDDJbx26fVTf9D7S4XfYDwUPIKxLvsbzMFDCRjercHzdFsRBtSHMQ6ao+f2hCvK
fGhILsHFEVeFCUNmCiCd3SJmqZmv0/+mobLqKXztGww1b3KDel+hz6vvgvDyI80U
WPam9MxIObdovlbVngtlOwiAWvIZ1puE/nGiVHJKag/Fh8kvjuZ+dpnh2jEWhg5K
D8k8JdA45D7ASSHE/29b2xb4JajnJt2gqrp9Zzfci+ObAlBIjss/0xfddg/NB4UY
AG2av7RMehwuDXQkTT21pecUmWHnFA98YGZZFOcKIwIAFgI1CXKY/W9/oaV/k04=
=twaQ
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Sep 14, 2015, 9:19:49 PM9/14/15
to Connor Page, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Tue, Sep 15, 2015 at 01:38:48AM +0200, Marek Marczykowski-Górecki wrote:
> On Tue, Sep 15, 2015 at 01:26:25AM +0200, Marek Marczykowski-Górecki wrote:
> > On Mon, Sep 14, 2015 at 04:13:43PM -0700, Connor Page wrote:
> > > LOL. After commenting that line out qubes-manager doesn't crash anymore, the vm starts properly and there are no warning windows.
> > > Still, there is a problem somewhere else. This appears in the console:
> > > [me@dom0 ~]$ qubes-manager
> > > libpng warning: iCCP: known incorrect sRGB profile
> > > Traceback (most recent call last):
> > > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4607, in _dispatchDomainEventLifecycleCallback
> > > cb(self, virDomain(self, _obj=dom), event, detail, opaque)
> > > File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 827, in _domain_list_changed
> > > self._register_watches(domain)
> > > File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 810, in _register_watches
> > > self._qdb[name].watch('/qubes-block-devices')
> > > qubes.qdb.Error: (104, 'Connection reset by peer')
> >
> > Thanks, now I know where to look :)
> >
> > > But again, when it gets past this the vm continues to boot, not stuck in some transitional state. I guess it's something else, not qubes-manager that tries to notify me about qubes db error and crash qubes-manager.
> >
> > Is that by any chance some HVM domain? Windows? With tools or without?
>
> Ok, finally I've managed to reproduce the issue:
> 1. create HVM domain (no need to install any OS there)
> 2. start it from qubes-manager (not console, not menu)
>
> It crashes in about 50% cases.
>
> Thanks for the info provided!
I think I've found a fix, just want to confirm that fixes the problem in
> On Tue, Sep 15, 2015 at 01:26:25AM +0200, Marek Marczykowski-Górecki wrote:
> > On Mon, Sep 14, 2015 at 04:13:43PM -0700, Connor Page wrote:
> > > LOL. After commenting that line out qubes-manager doesn't crash anymore, the vm starts properly and there are no warning windows.
> > > Still, there is a problem somewhere else. This appears in the console:
> > > [me@dom0 ~]$ qubes-manager
> > > libpng warning: iCCP: known incorrect sRGB profile
> > > Traceback (most recent call last):
> > > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4607, in _dispatchDomainEventLifecycleCallback
> > > cb(self, virDomain(self, _obj=dom), event, detail, opaque)
> > > File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 827, in _domain_list_changed
> > > self._register_watches(domain)
> > > File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 810, in _register_watches
> > > self._qdb[name].watch('/qubes-block-devices')
> > > qubes.qdb.Error: (104, 'Connection reset by peer')
> >
> > Thanks, now I know where to look :)
> >
> > > But again, when it gets past this the vm continues to boot, not stuck in some transitional state. I guess it's something else, not qubes-manager that tries to notify me about qubes db error and crash qubes-manager.
> >
> > Is that by any chance some HVM domain? Windows? With tools or without?
>
> Ok, finally I've managed to reproduce the issue:
> 1. create HVM domain (no need to install any OS there)
> 2. start it from qubes-manager (not console, not menu)
>
> It crashes in about 50% cases.
>
> Thanks for the info provided!
your case. Open /usr/lib64/python2.7/site-packages/qubes/qubesutils.py,
go to line 826 and change VIR_DOMAIN_EVENT_STARTED to
VIR_DOMAIN_EVENT_RESUMED. Then restart qubes-manager.
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
CsmYLfUf2mo9jyWPtmzpTazWQnKTVZTzp9CUrLWtPdsyfver5155U4sPgHGHdMTH
dddpbEZqZ/jsSxBNDC+p7wbwMTJ2L/6ipffuLqE8E0ZlCZaDmWgkdPQKbyo+eAKK
/SOtyXYj8h41BSDLQgx04nIFSgTA/rM43XpHNnzVIp3/ohJks7ORE49zNfvd80fB
ZQFI2BBIDLhjW8nTdpq6tPj/bWYJnaHTqNY8H/vhgCFo8mczbonLaYGxVhQGz1MF
W6OP6HYo8IlbgeLftRM8lvmIQh6wNzVUXtg4mtsrulOOuRSszUSMBiGzzt+GWjY=
=ZW0w
-----END PGP SIGNATURE-----
Connor Page
Sep 15, 2015, 3:50:27 AM9/15/15
to qubes-users
it's fedora pvm. will test tonight when I'm back.
Connor Page
Sep 15, 2015, 5:27:49 PM9/15/15
to qubes-users
Marek, it doesn't crash anymore and there are no error messages (except that wrong icc profile message from libpng). I tried 10 times, all successful.
pasca...@gmail.com
Sep 16, 2015, 10:43:36 AM9/16/15
to qubes-users, conp...@gmail.com
> I think I've found a fix, just want to confirm that fixes the problem in
> your case. Open /usr/lib64/python2.7/site-packages/qubes/qubesutils.py,
> go to line 826 and change VIR_DOMAIN_EVENT_STARTED to
> VIR_DOMAIN_EVENT_RESUMED. Then restart qubes-manager.
Marek, your fix works for me too.
When the package qubes-manager gets an update one day, will it update correctly if I keep the modified version of /usr/lib64/python2.7/site-packages/qubes/qubesutils.py ?
Thank you
Marek Marczykowski-Górecki
Sep 16, 2015, 10:48:42 AM9/16/15
to pasca...@gmail.com, qubes-users, conp...@gmail.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
then, you'll need to apply this modification after qubes-manager package
update...
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
NHzAqfYqXTsepN9U95Jy9AECRAxR5t5grtzMSfL4endT8tTVRKUP5BKQWPw0zYPX
i+r7RWgik2wN1gnflcDMmRC3bd2phObs7mA3SfZMDbjxtdWwBtQRhP1jV4IaQhPN
I/x5hV1clbowisblOz4WW7CTBKxUjcm5SzsAvIj+pbZOR8Um05AlLhCqGthH4MA1
688UFPqWqQLW9A+6AQimLnBBS76yutzh8SufeG087drVqkx83IrJpwKFdTrfL+wF
wBwZJ99JT4efxy58r+/yEv67154fzTFWyE+9Hh93KGq5+XDCNQEYmAf9h999hQM=
=kaLt
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages