One of the first things I did when getting serious about Kubuntu (about a month ago only) was to get serious about contributing via bug reporting. But I don't feel like I've got anywhere.
The KDE Crash Handler / Crash Reporting Assistant quickly gave me an opportunity when synaptiks, the control module for the touchpad in my notebook, crashed on bootup. I duly added all the debug symbols and opened a bug: Bug 288655 - synaptiks crash on bootup.
It was just as quickly closed as a duplicate of Bug 283173 - synaptiks-0.7 crashed after suspend with ALPS touchpad. That bug is closed, but I'm not sure if it's because it's out of scope for KDE or because it's believed fixed - comment #6 says version 0.8.0 of synaptiks fixes it.
What's my next step? Should I report it to Kubuntu or (possibly also) join the conversation at #21: Synaptiks crashes after resuming pc - Issues - lunaryorn/synaptiks - GitHub?
And what happens if the synaptiks developers believe they have a fix? I assume that getting the fix into Kubuntu is a packaging matter for Canonical, and not of any interest to kde.org?
The KDE Crash Handler / Crash Reporting Assistant quickly gave me an opportunity when synaptiks, the control module for the touchpad in my notebook, crashed on bootup. I duly added all the debug symbols and opened a bug: Bug 288655 - synaptiks crash on bootup.
It was just as quickly closed as a duplicate of Bug 283173 - synaptiks-0.7 crashed after suspend with ALPS touchpad. That bug is closed, but I'm not sure if it's because it's out of scope for KDE or because it's believed fixed - comment #6 says version 0.8.0 of synaptiks fixes it.
What's my next step? Should I report it to Kubuntu or (possibly also) join the conversation at #21: Synaptiks crashes after resuming pc - Issues - lunaryorn/synaptiks - GitHub?
And what happens if the synaptiks developers believe they have a fix? I assume that getting the fix into Kubuntu is a packaging matter for Canonical, and not of any interest to kde.org?
Comment