Bug 375080 - Crash when trying tu use every to-do action and New-Event or New-Journal
Summary: Crash when trying tu use every to-do action and New-Event or New-Journal
Status: RESOLVED WORKSFORME
Alias: None
Product: korganizer
Classification: Applications
Component: todoview (show other bugs)
Version: 5.1.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-15 09:39 UTC by tiare2002-compras
Modified: 2021-01-16 04:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tiare2002-compras 2017-01-15 09:39:07 UTC
Under Ubuntu 16.04 LTS

Every time I try to use "TO-do" and/or "New-event" and/or "New-Journal", or trying to consult the "To-Do list" the application crashes when the other functions work.
Comment 1 tiare2002-compras 2017-01-15 09:41:44 UTC
I forgot to mention that I try to use Korganizer under Gnome and that I had not This trouble with previous versions of Ubuntu under Gnome
Comment 2 Christoph Feck 2017-01-19 13:57:34 UTC
If the crash is reproducible, please add the backtrace. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 3 Pierre Maraval 2017-05-05 20:00:43 UTC
Kubuntu 17.04
Kontact 5.2.3

Steps to reproduce:
1. Open Kontact
2. Go to Calendar
3. Add New Event to remote or local calendar
(Crash)
4. Open Kontact again
5. Go to Calendar
(Crash)

Using Akonadi-console or Kontact Settings one can delete the bugging resource to stop Steps 4 and 5 to lead to a crash.
Comment 4 Pierre Maraval 2017-05-05 20:24:47 UTC
Workaround found for Kubuntu 17.04:

Update to PIM 16.12.3 (Kontact 5.4.3) by using the backports as described here:

http://kubuntu.org/news/kde-pim-update-now-available-for-zesty-zapus-17-04/

Downside: Sorry no backtrace :\
Comment 5 Justin Zobel 2020-12-17 05:31:24 UTC
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 6 Bug Janitor Service 2021-01-01 04:36:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2021-01-16 04:35:20 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!