https://bugs.kde.org/show_bug.cgi?id=440769
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=440769
--- Comment #6 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=440769
--- Comment #5 from Michail Vourlakos ---
Without detailed backtrace having a traceable fault is not possible.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440769
--- Comment #4 from vanda...@gmail.com ---
On default dock the crash also persist. As earlier, removing QT cache prevent
next startup crash.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440769
--- Comment #3 from vanda...@gmail.com ---
Clearing cache helped for one restart, on next one the bug persisted. Using ddd
looks hard, as i would have to start ddd and execute run backtrace before
latte-dock - and it's startup crash.I set up env, does it
https://bugs.kde.org/show_bug.cgi?id=440769
Michail Vourlakos changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=440769
--- Comment #1 from vanda...@gmail.com ---
It was present in earlier versions too, i think 0.9.8 and 0.9.9 or something
(the two versions before 0.10.0)
--
You are receiving this mail because:
You are watching all bug changes.
