Ref. #278 - Application Crashes When Removing Contact

[GONQ]

I am experiencing this issue, version 1.1.4. If I try to delete any contact, pending or accepted, the application crashes. I replaced the chip ID with zeroes since I'm not going to publish my chipset serial.

libGL error: MESA-LOADER: failed to retrieve device information
libGL error: image driver extension not found
libGL error: failed to load driver: radeon
libGL error: MESA-LOADER: failed to retrieve device information
unknown chip id 0x0000, can't guess. <replaced chip id>
libGL error: failed to create dri screen
libGL error: failed to load driver: radeon
QBackingStore::endPaint() called with active painter on backingstore paint device
QBackingStore::endPaint() called with active painter on backingstore paint device
src/core/ContactUser.cpp:330:38: runtime error: member call on null pointer of type 'struct QObject'

Originally posted by @GONQ in https://github.com/ricochet-im/ricochet/issue_comments#issuecomment-441468328

[GONQ]

I downloaded the tar.gz from the richochet site and that version does not reproduce the error. Perhaps the ubuntu / mint .deb package does not include the fix yet.

[yurivict]

It seems like this project is abandoned.

[GONQ]

Perhaps the Ricochet-im developer is on hiatus. In the meantime some of the privacy wonks are working on PyBitmessage. You can find more info on Bitmessage [chan] DevTalk. Spammers hit the other public chans hard with DDoS flooding, so I advise not to bother with public chans until they come up with a better flood mitigation mechanism.

[yurivict]

Thanks for this info.

[ghost]

I replaced the chip ID with zeroes since I'm not going to publish my chipset serial.

That number is not a serial number in case you were wondering. Everyone in the world with the same chipset as you (so multiple mainboards) would have the same id.

In any case it is unrelated to this issue. The issue seems to be:

src/core/ContactUser.cpp:330:38: runtime error: member call on null pointer of type 'struct QObject'

Without a core dump there isn't much that can be done without trying to reproduce the error which doesn't happen all the time? You will likely need to build from source for that ie CONFIG+=debug.

One would need this information in order to track down the cause of that null pointer.