-
Notifications
You must be signed in to change notification settings - Fork 86
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 when opening file dialoge #1
Comments
I have a hunch what the problem is. I will hopefully be able to do a bugfix release soon. |
Yeah, the problem is related to KDE. I don't get that crash on gnome-shell. The problem probably is this: I created a wrapper for QDom* (because it's not officially supported by Qt anymore => deprecated), but KDE apparently still uses the old QtXML libraries. Now the QDom* wrapper and QtXML are getting in conflict with each other, because the KDE libraries are dynamically linked at runtime for the filemanager (to make it look more integrated). I will try to put my wrapper into a different namespace to avoid conflicts. I just installed KDE and tried to reproduce this bug, but so far could not do so. I also don't seem to get that fancy KDE filedialog. Do you have any extra libraries installed for that purpose (getting KDE filedialog in Qt apps)? I just commited the likely fix to the repository. Unfortunately I can't test, so your help would be greatly appreciated. |
just create a branch with the possible fix and i can test it locally in my kde environment. |
I already commited it to master. Even if it's not the fix, it's definitely best practice to put something like that in a namespace. |
Forgot to push it. :-( Now you can test it. |
I was able to reproduce it myself now. And it looks like the last commit fixed the issue. Waiting for you to confirm. |
it works for me as well. i guess closing this is appropriate? |
aqemu0.9 is crashing consistently on an up-to-date archlinux system.
Steps to reproduce:
-> instant crash.
full gdb backtrace at http://pastebin.com/eRt5k9XW
The text was updated successfully, but these errors were encountered: