facing error when trying to contact support in Qt GUI Bitmessage #1633

New Issue

2020-05-30T13:08:56+02:00

surbhicis commented

2020-05-30 13:08:56 +02:00

(Migrated from github.com)

2020-05-30 16:28:50,656 - CRITICAL - Major error occurred when trying to execute a SQL statement within the sqlThread. Please tell Atheros about this error message or post it in the forum! Error occurred while trying to execute statement: "INSERT INTO addressbook VALUES (?,?)" Here are the parameters; you might want to censor this data with asterisks (***) as it can contain private information: (PyQt4.QtCore.QString(u'PyBitmessage support'), 'BM-2cUdgkDDAahwPAU6oD2A7DnjqZz3hgY832'). Here is the actual error message thrown by the sqlThread: Error binding parameter 0 - probably unsupported type.
2020-05-30 16:28:50,656 - CRITICAL - This program shall now abruptly exit!

2020-05-30 16:28:50,656 - CRITICAL - Major error occurred when trying to execute a SQL statement within the sqlThread. Please tell Atheros about this error message or post it in the forum! Error occurred while trying to execute statement: "INSERT INTO addressbook VALUES (?,?)" Here are the parameters; you might want to censor this data with asterisks (***) as it can contain private information: (PyQt4.QtCore.QString(u'PyBitmessage support'), 'BM-2cUdgkDDAahwPAU6oD2A7DnjqZz3hgY832'). Here is the actual error message thrown by the sqlThread: Error binding parameter 0 - probably unsupported type. 2020-05-30 16:28:50,656 - CRITICAL - This program shall now abruptly exit!

👍 1

PeterSurda commented

2020-05-30 13:42:18 +02:00

(Migrated from github.com)

We should aim to merge the QT tests to prevent things like this.

PeterSurda commented

2020-06-06 07:29:31 +02:00

(Migrated from github.com)

There is a related issue, if you click on "contact support" and there is no account yet, you'll also get a crash. I encountered this when testing OSX build. If you create the address before clicking on "contact support", it's ok.

This:
b750b02963/src/bitmessageqt/support.py (L91)
is causing the problem, down the line it gets into trouble with BMConfigParser and throws a TypeError: option values must be strings

There is a related issue, if you click on "contact support" and there is no account yet, you'll also get a crash. I encountered this when testing OSX build. If you create the address before clicking on "contact support", it's ok. This: https://github.com/Bitmessage/PyBitmessage/blob/b750b02963dae629618a4bf0d0637d45ce516378/src/bitmessageqt/support.py#L91 is causing the problem, down the line it gets into trouble with `BMConfigParser` and throws a `TypeError: option values must be strings`

😕 1

navjotcis commented

2020-09-07 15:56:04 +02:00

(Migrated from github.com)

There is a related issue, if you click on "contact support" and there is no account yet, you'll also get a crash. I encountered this when testing OSX build. If you create the address before clicking on "contact support", it's ok.

This:
b750b02963/src/bitmessageqt/support.py (L91)

is causing the problem, down the line it gets into trouble with BMConfigParser and throws a TypeError: option values must be strings

As I have tested this issue is not appearing any more now whenever the user tries to send a message on contact support without creating an address then it is not throwing error because it is automatically creating a new address when no address presents.

> There is a related issue, if you click on "contact support" and there is no account yet, you'll also get a crash. I encountered this when testing OSX build. If you create the address before clicking on "contact support", it's ok. > > This: > https://github.com/Bitmessage/PyBitmessage/blob/b750b02963dae629618a4bf0d0637d45ce516378/src/bitmessageqt/support.py#L91 > > > is causing the problem, down the line it gets into trouble with `BMConfigParser` and throws a `TypeError: option values must be strings` As I have tested this issue is not appearing any more now whenever the user tries to send a message on contact support without creating an address then it is not throwing error because it is automatically creating a new address when no address presents.

This repo is archived. You cannot comment on issues.