Summary: | kfmclient started in a endless loop | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Andreas Scherf <ascherfy> |
Component: | kcm_componentchooser | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | b.brachaczek, eric, pfmiller, reavertm, wrar, xenomorph |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.10 | |
Sentry Crash Report: |
Description
Andreas Scherf
2009-07-08 20:37:49 UTC
Confirmed same bug with my system as well. Edit field was blank causing an endless loop. Changed to 'firefox' and problem resolved. Tried to re-create behavior by blanking edit field but kfmclient now displays error message "Could not find the program '%u'". Same problem if edit field has one space as well. Kubuntu 9.04 KDE 4.2.2 from kubuntu sources. Confirming that the bug is still valid for KDE SC 4.4.1. Steps to Reproduce: 1. Set your default browser to something different from Konqueror, e.g. Firefox. 2. Remove/Rename Firefox's .desktop file (/usr/share/applications/mozilla-firefox-3.6.desktop in my case). 3. Relogin. 4. Try to run `kfmclient openURL http://kde.org`. Current Behavior: You can observe an endless loop. Expected Behavior: Don't know, maybe display an error message, or fallback to Konqueror. And it's definitely not a bug in systemsettings, as kfmclient is konqueror/general, AFAIK. Not sure, but I guess it might be a bug in KRun, i.e. kio/http. *** Bug 217835 has been marked as a duplicate of this bug. *** gcc (Gentoo 4.3.5 p1.0, pie-10.1.5) 4.3.5 KDE Development Platform: 4.5.00 (KDE 4.5.0) Bug was catched and the browser string was empty too. Changing to autodetect resolve this problem, but I still want to know that this bug will be removed in future. This may be a duplicate of bug 137534 Can't reroduce the problem in KDE SC 4.10 by following the steps in comemnt #0, #1 and #2 and #4. Is this still a problem for all reporters in recent versions ? For me it's fixed in 4.10, thanks. |