Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
in .7.2pre1 I get seg faults when using the Manual,
MusE web site or Report a bug link. There are no lines
output when starting with -D so I am not really sure
how to troubleshoot this.
Logged In: YES
Ok, these alternatives all have to do with web browsers.
I recall vaguely some similar report a long time ago. Do you know
what webbrowsers are installed on your system?
Also check what browser MusE detected, available in Settings->Global
What user is MusE started as?
Logged In: YES
OK the "help browser" field was blank. Is global settings
per user? If so, then it's possible it was blank because of
the earlier install(s) which go back to .63.
Putting in /usr/bin/firefox makes everybody happy, so the
menu should probably be grayed out with hover text stating
that a browser needs to be selected? That's simple enough,
perhaps I can make a patch.
Muse is running suid root.
This attached patch should do it. I wonder what the overall
strategy is for sanity checking the configuration file. It
seems like the current version could fail in many places,
but this patch only addresses the helpbrowser segfault.
Thanks, I'll take a look at it.
Though I still don't understand why it crashes. There is a test that
checks if the string is empty. Perhaps different qt versions behave
As for config validation, feel free to take the discussion to the devel
> Though I still don't understand why it crashes. There is a test that
> checks if the string is empty. Perhaps different qt versions
Ok, got it, if the tag exists but is empty it fails.