https://bugs.kde.org/show_bug.cgi?id=444793
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=444793
--- Comment #12 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
https://bugs.kde.org/show_bug.cgi?id=444793
--- Comment #11 from Michail Vourlakos ---
(In reply to Alex Dewar from comment #10)
> Sorry, you're totally right. The backtrace was completely different this
> time:
>
No it isnt. It is the same crash and based on the last backtrace you have not
https://bugs.kde.org/show_bug.cgi?id=444793
--- Comment #10 from Alex Dewar ---
Sorry, you're totally right. The backtrace was completely different this time:
Thread 1 "latte-dock" received signal SIGSEGV, Segmentation fault.
0x779b3700 in Plasma::Applet::actions() const () from
https://bugs.kde.org/show_bug.cgi?id=444793
Michail Vourlakos changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=444793
--- Comment #8 from Michail Vourlakos ---
Show me the new crash report please because it might be a different one.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444793
--- Comment #7 from Michail Vourlakos ---
(In reply to Alex Dewar from comment #6)
> I just built v0.10.3 and I'm getting exactly the same error.
No idea what is wrong in your build, install system then. The crash is
identifiable and comes from
https://bugs.kde.org/show_bug.cgi?id=444793
--- Comment #6 from Alex Dewar ---
I just built v0.10.3 and I'm getting exactly the same error.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444793
Alex Dewar changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=444793
Michail Vourlakos changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=444793
--- Comment #4 from Michail Vourlakos ---
run in cmd, latte-dock -v
what is your latte version?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444793
--- Comment #3 from Alex Dewar ---
Sorry for the slow reply. I haven't had a chance to look at this again until
now. In answer to your question, yes latte-dock is configured as specified. The
backtrace is below.
Thread 1 "latte-dock" received signal
https://bugs.kde.org/show_bug.cgi?id=444793
Michail Vourlakos changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=444793
--- Comment #1 from Michail Vourlakos ---
The line you are mentioning could crash only in the following scenario:
1. Latte is loading and layouts manager (m_manager) is created
2. synchronizer is created from m_manager because synchronizer is a child
14 matches
Mail list logo
