Bug 457786
Summary: | syndock: Could not find service 'ksynaptics'. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rex Dieter <rdieter> |
Component: | kdelibs3 | Assignee: | Than Ngo <than> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | kevin, ltinkl, rdieter, tuxbrewr |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-06 16:05:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rex Dieter
2008-08-04 16:36:59 UTC
Upstream is pretty much dead for this project. I've seriously considered dropping this from Fedora, but it is still useful (when it works). I may look into this if I have time, but not too likely. Attempts to ping upstream may be more useful though all of my email attempts bounce. Based on my research ksynaptics is indead dead. See http://qsynaptics.sourceforge.net/ this is the new app replacing it. Touchfreeze Looks like we should get this packaged up Is this really a ksynaptics bug? [orion@cynosure devel]$ kcmshell --list The following modules are available: [orion@cynosure devel]$ Or are KDE3 apps unsupported at this point? Oh cryin out loud -> kdeilbs3. anyone clueful here? kcmshell --list being empty is "normal": well, it's probably a bug, but it's not what keeps it from working, e.g. "kcmshell colors" works just fine. Ping... Bug or no? Keep open or close? The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance. |