Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash after update to .70 #2046

Closed
djwlindenaar opened this issue Nov 7, 2019 · 18 comments
Closed

Crash after update to .70 #2046

djwlindenaar opened this issue Nov 7, 2019 · 18 comments
Labels

Comments

@djwlindenaar
Copy link
Contributor

I'm getting a Crash after upgrading to the .70 beta. I'm on a raspbian with the raspbee hardware. I get:

deCONZ: /usr/lib/arm-linux-gnueabihf/libQt5SerialPort.so.5: no version information available (required by deCONZ)
deCONZ: /usr/lib/arm-linux-gnueabihf/libQt5Network.so.5: no version information available (required by deCONZ)
deCONZ: /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5: no version information available (required by deCONZ)
deCONZ: /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5: no version information available (required by deCONZ)
deCONZ: /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5: no version information available (required by deCONZ)
deCONZ: /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5: no version information available (required by /usr/lib/libdeCONZ.so.1)
deCONZ: /usr/lib/arm-linux-gnueabihf/libQt5SerialPort.so.5: no version information available (required by /usr/lib/libdeCONZ.so.1)
deCONZ: /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5: no version information available (required by /usr/lib/libdeCONZ.so.1)
libEGL warning: DRI2: failed to authenticate
deCONZ: relocation error: deCONZ: symbol _ZN9QMetaType22registerNormalizedTypeERK10QByteArrayPFvPvEPFS3_S3_PKvEi6QFlagsINS_8TypeFlagEEPK11QMetaObject, version Qt_5 not defined in file libQt5Core.so.5 with link time reference
@mysteryan
Copy link
Contributor

mysteryan commented Nov 7, 2019

GUI seems to crash for me as well on .70, but runs fine without GUI on Pi 3 / Stretch / Conbee.

`(deCONZ:13258): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed

(deCONZ:13258): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed

(deCONZ:13258): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed

(deCONZ:13258): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed

(deCONZ:13258): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed

(deCONZ:13258): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed

(deCONZ:13258): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed

(deCONZ:13258): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed

(deCONZ:13258): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed
`

@manup
Copy link
Member

manup commented Nov 7, 2019

Are you using the shipped plugin or is that compiled manually?

@mysteryan
Copy link
Contributor

Both for me. Shipped .69 seems to be okay. I noticed that it started crashing with a manually compiled one sometime after that. Thinking it's an issue with my own compilation, I've just kept quiet about it. With shipped .70, the crashing still seems to persist.

@djwlindenaar
Copy link
Contributor Author

As shipped. I noticed the name of the package changed to ....Buster.... from ...Jessie...
Could that be the issue? I'm still on Jessie...

@manup
Copy link
Member

manup commented Nov 8, 2019

When installing via APT repository the Jessie package (also compiled on Jessie) should be selected. The steps in the installation instructions should setup the matching distribution:

https://phoscon.de/conbee2/install#raspbian

@djwlindenaar
Copy link
Contributor Author

I installed from here:
https://www.dresden-elektronik.de/deconz/raspbian/beta/

I guess that is now outdated... Maybe it's time to start using the apt route...

@mysteryan
Copy link
Contributor

I installed from here:
https://www.dresden-elektronik.de/deconz/raspbian/beta/

I guess that is now outdated... Maybe it's time to start using the apt route...

I also used that download link instead of using apt route.

@salopette
Copy link

I also have the problem that Deconz has always restarted after a few seconds and was always asked for firmware update.

I have now reinstalled .67 and it works. Do not trust me to make an update again.

manup added a commit that referenced this issue Nov 9, 2019
Issues: #2046 #2033

The deCONZ core was further fixed to preserve the original argc and argv on each restart. QApplication would otherwise strip parameters like "-platform minimal" and
start the GUI albeit headless mode was specified.
@mysteryan
Copy link
Contributor

Not sure about OP, but this issue seems resolved after using a manually compiled version of today’s commits. GUI seems to runs as it should for me (via headless VNC).

@salopette
Copy link

What is the best way to update Pi3 to the last beta?

@Smanar
Copy link
Collaborator

Smanar commented Nov 9, 2019

Last deconz beta ? using package I think.
But if the V70 is not yet in stable branch after 15 days, I think there is a reason, don't be hurry.

@salopette
Copy link

Thx

@salopette
Copy link

How can you downgrade from .70 to .69?

@manup
Copy link
Member

manup commented Nov 10, 2019

Depends on the platform, assuming Linux you need to manually install the .deb package:

dpkg -i <deconz deb file>

The files can be downloaded from:
https://github.com/dresden-elektronik/deconz-rest-plugin#precompiled-deconz-packages-for-manual-installation

@salopette
Copy link

I have Pi3, is that right?

wget https://www.dresden-elektronik.de/rpi/deconz/beta/deconz-2.05.70-qt5.deb

sudo dpkg -i deconz-2.05.70-qt5.deb

@manup
Copy link
Member

manup commented Nov 10, 2019

Yes but to downgrade you need the .69 version.

@salopette
Copy link

salopette commented Nov 10, 2019

Ok, THX!

Do you already know when the .71 comes out without bugs?

@stale
Copy link

stale bot commented Mar 9, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 9, 2020
@stale stale bot closed this as completed Mar 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants