Summary: | Quanta crashes when VPL or VPL and Source Editor are chosen | ||
---|---|---|---|
Product: | [Unmaintained] quanta | Reporter: | Steve Taylor <sgtaylor> |
Component: | VPL | Assignee: | Paulo Moura Guedes <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandrake RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Steve Taylor
2005-03-11 20:07:14 UTC
Cannot reproduce on 3.3.2 compiled from sources, Fedora Core 3. A Mandrake problem maybe ? On Friday March 11, 2005 18:16, Philippe Rigault wrote: [bugs.kde.org quoted mail] Philippe, It might be. I reported it because I could crash Quanta *every* time doing this. Would reporting it here be enough for the Mandrake team to see it, or should I talk to them directly? > Would reporting it here be enough for the Mandrake team to see it, or should
> I talk to them directly?
In general, when using a package from your distro (as opposed to building from sources), it is a good idea to report bugs to your distro first:
- if the bug is specific to your distro, it avoids clogging KDE with bugs that are not their problem. Many crash bugs can be distro-specific, given the dependencies on glibc/gcc/kernel and so on.
- if the but is really from KDE, then your distro maintainer will file a bug in KDE (or tell you to do so yourself), so it eventually gets to the right place (here).
In this case, now that you suspect a distro-specific behaviour, you should absolutely file a bug in your distro.
Remember, a bug not filed does not exist, so don't count on Mandrake eyes to magically see it and act on it. Report the bug, then it exists.
Cheers.
|