| 39 | | In a [http://lists.kde.org/?t=139557219200002&r=1&w=2&n=6 post to KDE-DEVEL] it is described what happens when the user tries to call the bug report wizard in KDE applications. This usually simply opens a browser accessing bugs.kde.org, but it fails on MacPorts even if a web browser is configured properly in the system configuration of KDE software. In the latter case this leads to an endless respawning of browser windows, but this can also happen on Linux, see [https://sourceforge.net/p/be-shell/tickets/21/ be-shell's ticket 21 on SourceForge]. |
| | 39 | In a [http://lists.kde.org/?t=139557219200002&r=1&w=2&n=6 post to KDE-DEVEL] it is described what happens when the user tries to call the bug report wizard in KDE applications. This usually simply opens a browser accessing bugs.kde.org, but it fails on MacPorts if there is no web browser configured in the system configuration of KDE software. This usually isn't preconfigured correctly after installation. In case the user now enters the path to a (Safari or Konqueror) browser executable (in the app's package below Contents/MacOS/) preceded by an exclamation mark, it leads to an endless respawning of browser windows, but this can also happen on Linux, see [https://sourceforge.net/p/be-shell/tickets/21/ be-shell's ticket 21 on SourceForge]. Instead one must configure a KDE internal browser (like e.g. Konqueror) but using the “KDE control module” |
| | 40 | {{{ |
| | 41 | $ /Applications/MacPorts/KDE4/kcmshell4.app/Contents/MacOS/kcmshell4 componentchooser |
| | 42 | }}} |
| | 43 | using the “Select preferred Web browser application” dialog under "Known Applications/Internet/Konqueror" or on the console via |
| | 44 | {{{ |
| | 45 | $ kwriteconfig --group General --key BrowserApplication 'konqbrowser' |
| | 46 | }}} |
