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
Nightingale crashes on ubuntu after some time #83
Comments
NG Version? There is a ubuntu bug fixed in a testing build (for x64):Nightingale_1.11.1-2269-ubuntu-x64.tar.gz Not sure if it is only x64, through. |
@jigarshah |
Not yet..will do it today On 30 May 2012 16:50, "Antoine Turmel" < @jigarshah Reply to this email directly or view it on GitHub: |
@GeekShadow it looks like its only for 64 bit. can you check if there is 32 bit version available too ? |
I remember some random crashes here on Sabayon AMD64 bit as well, but I can't reproduce them. I also haven't had them for some time now. |
its easily reproducible on my sytem...can someone add pointer so i can add more details. its kind of blocker for me. |
I have removed the label "Not yet reproduced". Can you provide a back trace and could you also provide steps to reproduce? |
How do I get trace? It says core dump. Reproducing straight. Just run On 20 Jun 2012 15:39, "Janek Bevendorff" < I have removed the label "Not yet reproduced". Can you provide a back trace and could you also provide steps to reproduce? Reply to this email directly or view it on GitHub: |
When it says core dump, there should be a coredump file somewhere in your home directory. You can examine it with gdb. |
I had this issue too, maybe it's issue #77 ? I have to do more tests. |
I have this problem too, when scrolling or trying to play video in mashtape. |
@jigarshah @muzena |
@jigarshah @muzena - still happening? If so, reopen. |
I am on Ubuntu : 12.04 LTS
Linux jigar-nvs 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:52 UTC 2012 i686 i686 i386 GNU/Linux
nightingale crashes and says segmentation fault (core dump) let me know how to provide more info.
The text was updated successfully, but these errors were encountered: