https://bugs.kde.org/show_bug.cgi?id=480104
--- Comment #5 from Balázs R. ---
(In reply to TraceyC from comment #4)
> This looks like a duplicate of 469440 based on the backtrace. If you would
> like to follow the progress of this bug, please follow that report. Thanks!
Ok. Thank you!
--
You a
https://bugs.kde.org/show_bug.cgi?id=480104
TraceyC changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=480104
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
See Also|
https://bugs.kde.org/show_bug.cgi?id=480104
TraceyC changed:
What|Removed |Added
CC||kde...@tlcnet.info
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=480104
Balázs R. changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=480104
--- Comment #3 from Bug Janitor Service ---
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 b
https://bugs.kde.org/show_bug.cgi?id=480104
--- Comment #2 from Balázs R. ---
(In reply to Akseli Lahtinen from comment #1)
> Hi, can you install debug symbols and try to reproduce the crash? Thanks!
>
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_repo
https://bugs.kde.org/show_bug.cgi?id=480104
Akseli Lahtinen changed:
What|Removed |Added
Resolution|--- |BACKTRACE
CC|