| Summary: | Segmentation fault when starting korganizer | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | H. Stoellinger <hc.stoellinger> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | grave | CC: | smartins, tpo_deb, winter |
| Priority: | NOR | ||
| Version: | 4.4.11 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
H. Stoellinger
2012-04-14 17:43:17 UTC
what -dbg-packages do I have to install to be able to produce a sensible backtrace? Might be that this is the same problem as this here: https://bugs.kde.org/show_bug.cgi?id=307026 Also reported in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1052813 @H. Stoellinger: Downgrading korganizer back to the previous version "fixed" the problem. See https://bugs.kde.org/show_bug.cgi?id=205491 (In reply to comment #3) > @H. Stoellinger: > > Downgrading korganizer back to the previous version "fixed" the problem. See > https://bugs.kde.org/show_bug.cgi?id=205491 That's a kwallet bug. Which bug number did you meant ? On Wed, 19 Sep 2012, Sergio Martins wrote: > https://bugs.kde.org/show_bug.cgi?id=298132 > > Sergio Martins <iamsergio@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |iamsergio@gmail.com > > --- Comment #4 from Sergio Martins <iamsergio@gmail.com> --- > (In reply to comment #3) >> @H. Stoellinger: >> >> Downgrading korganizer back to the previous version "fixed" the problem. See >> https://bugs.kde.org/show_bug.cgi?id=205491 > > That's a kwallet bug. Which bug number did you meant ? Argh! I'm sorry, I meant see https://bugs.kde.org/show_bug.cgi?id=307026 *t This is for a very old version of KOrganizer we no longer support. (In reply to comment #6) > This is for a very old version of KOrganizer we no longer support. That's a pitty, since that's the version in the current Ubuntu LTS and as such probably the version most (?) of your Ubuntu users - possibly even most of your users overall - will have to live with for the - say - next 5 years or so. Supposed I'm a luser, what would be the way forward from here? Accept that korganizer is not usable in its current form in Ubuntu Precise for me and keep it pinned to the old, working version? Is there anything else I can do as a luser, apart from compiling the whole latest stable KDE suite from scratch (and in the process possibly having to upgrade half of Ubuntu to newer libraries (say libx11) as well)? *t (In reply to comment #7) > (In reply to comment #6) > > This is for a very old version of KOrganizer we no longer support. > > That's a pitty, since that's the version in the current Ubuntu LTS and as > such probably the version most (?) of your Ubuntu users - possibly even most > of your users overall - will have to live with for the - say - next 5 years > or so. Then it's up to Ubuntu to fix these bugs. Releasing Long Term Support versions supposes that you're able to fix your users reports. Such issues should be reported on the ubuntu bug tracker. offtopic in this report anyway, the reporter was using mint. (In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > This is for a very old version of KOrganizer we no longer support. > > > > That's a pitty, since that's the version in the current Ubuntu LTS and as > > such probably the version most (?) of your Ubuntu users - possibly even most > > of your users overall - will have to live with for the - say - next 5 years > > or so. > > Then it's up to Ubuntu to fix these bugs. Releasing Long Term Support > versions supposes that you're able to fix your users reports. Such issues > should be reported on the ubuntu bug tracker. > offtopic in this report anyway, the reporter was using mint. Argh, I confused this bugreport with https://bugs.kde.org/show_bug.cgi?id=307026 *again*. Sorry. And yes the bug is reported to Ubuntu. |