|
Title: issue with bitcoin-qt and new ubuntu 17.10 Post by: ccminer.net on January 31, 2018, 07:55:13 PM Just updated my ubuntu OS and I'm not able to open my bitcoin core wallet anymore!!!
I get this error: Code: QXcbConnection: Could not connect to display desktop:0 I have a CLAM coin client that is based on a similar client and it works with no issues I've googled a bit about it but with no solution! thx for the support Title: Re: issue with bitcoin-qt and new ubuntu 17.10 Post by: achow101 on February 01, 2018, 02:22:37 AM Can you post your debug.log file?
This looks more like a problem with your X server rather than Bitcoin Core. Title: Re: issue with bitcoin-qt and new ubuntu 17.10 Post by: kiemnhieutien on February 01, 2018, 03:43:33 AM Can you post your debug.log file? This looks more like a problem with your X server rather than Bitcoin Core. Yes. I met this before. The problem is X-server Just updated my ubuntu OS and I'm not able to open my bitcoin core wallet anymore!!! I get this error: Code: QXcbConnection: Could not connect to display desktop:0 I have a CLAM coin client that is based on a similar client and it works with no issues I've googled a bit about it but with no solution! thx for the support How to solve: You need to use an X-server on Jenkins machine to run the GUI program. Hope it help Title: Re: issue with bitcoin-qt and new ubuntu 17.10 Post by: ccminer.net on February 01, 2018, 11:13:32 AM Can you post your debug.log file? This looks more like a problem with your X server rather than Bitcoin Core. Yes. I met this before. The problem is X-server Just updated my ubuntu OS and I'm not able to open my bitcoin core wallet anymore!!! I get this error: Code: QXcbConnection: Could not connect to display desktop:0 I have a CLAM coin client that is based on a similar client and it works with no issues I've googled a bit about it but with no solution! thx for the support How to solve: You need to use an X-server on Jenkins machine to run the GUI program. Hope it help Thanks both of you guys!! I solved by simply reinstall the whole ubuntu |