| Summary: | Could not start process Unable to create io-slave klauncher said: Unknown protocol '' | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | J. Becker <jamie> |
| Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | finex |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Hi! As Konqueror on KDE 3 is no more mantained, would you like to check the new Konqueror on KDE 4.2 beta2 and let us know if you can reproduce the issue on it too? It is excellent that the KDE teams are focused on KDE 4. Splitting developer resources is often a bad thing, and with the work-around described above this bug has much more limited importance, but is there a period of maintenance after a new version of KDE is released, at least for critical bugs (which this is not)? Many distributions are heavily relying on KDE 3 for the next several years. For example, Debian Lenny, due out this month or next, will be released with KDE 3. Probably other distributions or UNIXes that are focused on long-term stability will also be releasing with KDE 3 for at least another year*. "Notes for KDE 4.1 packages" "KDE 4 packages are currently in the experimental branch and are not intended to be installed on a production system. We are not accepting bug reports against the KDE 4 packages at the moment, since they have many known problems." (http://pkg-kde.alioth.debian.org/kde4.html) Of course, it says the [Debian] KDE 4 packages have many known problems, not that KDE itself does. It appear to be mainly a packaging issue, because KDE has many dependencies and the upgrade required significant changes during a major release cycle for Debian. We are all patiently looking forward to KDE 4 but KDE 3 still works pretty well. Nobody wants to create more work for KDE maintainers, and this bug report is perhaps not the correct forum to ask this question, but if we did run into any really massive bugs (rather unlikely, given the stability and age of the code base), would any support or assistance be extended? Thanks! * Discussion from June for Debian's KDE release team: http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2008-June/000888.html |
Version: 3.5.9 (using 3.5.10, Debian Package 4:3.5.10.dfsg.1-0lenny1 (lenny/sid)) Compiler: Target: x86_64-linux-gnu OS: Linux (x86_64) release 2.6.26-1-amd64 Upon pressing "reload" on a page, or on an automatic-reload page such as foxnews.com, or when pressing F5, the following error message is displayed: Could not start process Unable to create io-slave: klauncher said: Unknown protocol '' I was able to narrow this down to the following settings in ~/.kde/share/config/konquerorrc: [HTML Settings] UserStyleSheet=default.css UserStyleSheetEnabled=true Although I had used an override style sheet at one time, I had moved it and the path was no longer valid. Reproduce: Add the following settings to [HTML Settings] in konquerorrc: UserStyleSheet=somethingnotfound.css UserStyleSheetEnabled=true Then restart (from scratch) Konqueror and visit any site. Then press reload or F5. Work-around Remove UserStyleSheet and UserStyleSheetEnabled from konquerorrc, or change it to the correct path in the menu ("Settings" > "Configure Konqueror" > "Stylesheets" > "Use default stylesheet".) Resolution Konqueror should check, either at start or each page load when UserStyleSheetEnabled == true, if the UserStyleSheet still exists, and/or klauncher should provide a more accurate error message. Potentially related to http://bugs.kde.org/show_bug.cgi?id=141815