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
Random segmentation faults when enabling this plugin #82
Comments
Thanks for raising the issue. Suggest run rhythmbox in debug mode rhythmbox -d Once we've narrowed down the issue, I'll ask you to install the rhythmbox debug symbols package for your distro and then run gdb to get a backtrace. This will pinpoint where the crash actually occurs. The last dozen or so lines often gives a hint as to what the issue is. What is your linux variant? Anything special about your setup e.g. new version of python? Upgraded GTK stack from what the distro gave you? |
BTW - when testing please make sure no other plugins are enabled at the same time. Some plugins such as llyrics do interfere because of some threading issues. |
I started rhythmbox in debug mode and was unable to cause a crash. Without debug mode I can still cause crashes. |
ok - suggest use gdb |
I am unable to cause a crash with gdb. After using gdb I cannot even cause a crash in rhythmbox without gdb. rhythmbox-3.2.1 use-flags
gtk+-3.16.7 I will debug it when it crashes the next time. Compiling rhythmbox with debug symbols now. |
an alternative way to get some-sort of tracing without recompiling is to run rhythmbox -D alt i.e. this will spit out in the terminal all the python print statements for all python modules starting with "alt" - most of the alternative-toolbar python modules are alt[something] |
no feedback. closing. |
When enabling this plug-in rhythmbox (3.2.1) crashes randomly when changing the song or browsing through the library. The command line does not give any further information, it just says
segmentation fault
. Without the plug-in enabled I didn't run into any issues. Any suggestions on how to address this problem?The text was updated successfully, but these errors were encountered: