Qt Meego Bluetooth Segmentation Fault - qt

I have created a game that runs fine on Symbian but won't run on the Meego/Harmattan emulator. It gives me a lot of No AEGIS_HASH_FDS environment errors and a Segmentation fault. I think it may have something to do with QBluetooth because I have a version of the same app that doesn't use it which runs fine. What could be causing this and how do I use QBluetooth with Meego/Harmattan? If it helps I have also tried running the Bluetooth Chat example that comes with Qt on wich my app is based and it gives the exact same errors on the emulator.

Related

QMediaPlayer and Segmentation Fault

Hello Guys i used just this simple example to play music with this code:
QMediaPlayer *mediaPlayer { new QMediaPlayer };
mediaPlayer->setMedia(QUrl(currentMediaFileName));
mediaPlayer->setVolume(50);
mediaPlayer->play();
he show me in debug mode the message "Segmentation fault" and my application crash.
I used Qt 5.15.0
This seems to be a bug in Qt. I found this bug report. Hopefully this issue will be resolved soon.
Based on my experience, the problem seems to occur only on certain hardware: I have two laptop computers, both with XUbuntu 21.04 and both using proprietary drivers, and when running the same code i get SIGSEGV on one system but on the other (older) system there is no problem.

Can't make Siri Shortcuts work in macCatalyst app

I'm trying to port my iOS app to Mac using macCatalyst, and I'm having problem with Siri Shortcuts. The code complies and runs, but when I try to add shortcut using INUIAddVoiceShortcutViewController I'm seeing 'Shortcuts unavailable.'
Using
INVoiceShortcutCenter.shared.getAllVoiceShortcuts returns error [Intents] -[INVoiceShortcutCenter getAllVoiceShortcutsWithCompletion:]_block_invoke Error from -getVoiceShortcutsWithCompletion: Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application."
Any ideas what's I'm doing wrong? Same code works perfectly fine on iOS.
The Intents framework is unavailable at runtime on macOS except for WidgetKit support. The APIs are available at compile time in the Mac Catalyst environment to reduce the amount of changes required to compile for Mac Catalyst. Calling into the APIs as part of the shared code path between iOS and Mac Catalyst is fine, they will just return an error for Mac Catalyst, as you're seeing.
Posted 11 hours ago by edford 

Microsoft.EntityFrameworkCore.Infrastructure.EnsureDeleted will cause Crash when not attached to debugger

Have a Xamarin.Forms project using EntityFrameworkCore for the onboard db. On startup of the app we will call:
Database.EnsureDeleted();
Which will reset the onboard db when needed. When running for iOS and Android this will run fine when connected to the debugger. As soon as I disconnect the cord from the device and just run the app it will crash on load and I've singled it out to the EnsureDeleted being the issue, if I comment out that line it will work fine. Also I just put an empty try catch around it and it will still crash the entire app.
Any ideas?
It appears to be related to this issue:
github.com/xamarin/xamarin-android/issues/3112
Which was introduced in the 16.1 release of VS 2019.
Following the steps in this post: github.com/xamarin/xamarin-android/issues/3112#issuecomment-495780758
With version 9.2.3.0 of the Xamarin Android SDK, fixed the crash.

QML crashed if static build

I build static Qt 5.10.1 with mingw32.
Ref: https://github.com/arkceajin/QtDemos/blob/master/windows-build-qt-static/windows-build-qt-static.ps1
For testing purpose, build an empty QML project, it could run perfectly in QtCreator.
But if I copy the release build to another Win10&7 PC which doesn't contain the Qt environment, it will crash after the windows appeared. I'm guessing something missed inside QML.
Update:
I found No qmlscene installed appears in the Qt Versions tab, not sure it relates to the issue or not.
These two files did generate in the build folder.
projectname_plugin_import.cpp
projectname_qml_plugin_import.cpp
Found the similar issue: https://forum.qt.io/topic/42145/i-can-t-run-static-qt-qml-app-on-another-computer
Update 2:
Problem solved but I want to know why.
Here is I tried:
Connect a Win PC using remote desktop from another Win PC, run a static build QML program, then it crashed immediately after the Window appeared.
Directly login into the same local machine, run the same static build QML program, successful run.
Using the remote desktop run dynamic link QML program with Qt libs, successful run.
So the problem is Windows remote desktop, but I can't find the doc or bug report about it, if you have any idea or guessing, please help me.

Tricky Qt / OpenGL bug - everything crashes

I have an annoying and unfortunately urgent problem. I started out by trying to subclass the QGLWidget for my Windows application in Visual Studio 2008 x86. It crashed immediately upon running, as far as I could tell, when the QGLWidget was instantiated. Finally I ended up trying all the included Qt examples for Open GL, and they all behave the same - crashing as follows:
Error message pops up:
"Windows has triggered a breakpoint in
2dpainting.exe..."
The execution halts in qgl_win.cpp (breakpoint indicated):
QGLTemporaryContext::~QGLTemporaryContext()
{
wglMakeCurrent(d->dmy_pdc, 0);
wglDeleteContext(d->dmy_rc);
ReleaseDC(d->dmy_id, d->dmy_pdc);
DestroyWindow(d->dmy_id);
--> if (d->old_dc && d->old_context)
wglMakeCurrent(d->old_dc, d->old_context);
}
Output:
... HEAP[2dpainting.exe]: HEAP: Free
Heap block a40c108 modified at a40c288
after it was freed Windows has
triggered a breakpoint in
2dpainting.exe.
This may be due to a corruption of the
heap, which indicates a bug in
2dpainting.exe or any of the DLLs it
has loaded ...
Also happens when I switch from debug to release. However, I can run most of these Open GL example compiled executables just fine.
I can't find anything through internet searches. Gurus, please help!
Thanks,
Matt
I resolved the problem by updating my graphics drivers to their latest version. Strange, because I'm using the Intel GMA 965 Express chipset, which is already very old.
Now all the Qt examples compile just fine. No heap corruption.
I'm also able to run the main Qt Examples and Demos app from the start menu, which I was never able to do before - it would just crash.

Resources