https://bugs.kde.org/show_bug.cgi?id=460066
--- Comment #12 from Fushan Wen ---
Created attachment 155140
--> https://bugs.kde.org/attachment.cgi?id=155140&action=edit
New crash information added by DrKonqi
plasma-discover (5.26.80) using Qt 5.15.7
Crashed again after closing Discover
-- Bac
https://bugs.kde.org/show_bug.cgi?id=460066
Fushan Wen changed:
What|Removed |Added
Resolution|WORKSFORME |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=460066
--- Comment #11 from Fushan Wen ---
Created attachment 155103
--> https://bugs.kde.org/attachment.cgi?id=155103&action=edit
New crash information added by DrKonqi
plasma-discover (5.26.80) using Qt 5.15.7
Discover crashed after the window is closed.
https://bugs.kde.org/show_bug.cgi?id=460066
Fushan Wen changed:
What|Removed |Added
CC||qydwhotm...@gmail.com
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=460066
--- Comment #10 from Nate Graham ---
Indeed, unfortunately some distros don't make it easy. I wish they all did.
No, the stack trace is not enough if it's missing debug symbols. That makes it
impossible to debug, except for *maybe* identifying the issu
https://bugs.kde.org/show_bug.cgi?id=460066
--- Comment #9 from Adrian R ---
(In reply to Nate Graham from comment #8)
> That probably means you don't have debug symbols installed.
That stack trace isn't enough?
Seems like an uphill fight just to do the right thing and report a bug. :/
--
Yo
https://bugs.kde.org/show_bug.cgi?id=460066
--- Comment #8 from Nate Graham ---
That probably means you don't have debug symbols installed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460066
--- Comment #7 from Adrian ---
(In reply to Nate Graham from comment #6)
> Adrian, your backtrace looks different so I think it's a different crash. If
> you can truly reproduce it 100%, please do file a new bug report for it.
> Thanks!
I've tired to u
https://bugs.kde.org/show_bug.cgi?id=460066
--- Comment #6 from Nate Graham ---
Adrian, your backtrace looks different so I think it's a different crash. If
you can truly reproduce it 100%, please do file a new bug report for it.
Thanks!
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=460066
Adrian changed:
What|Removed |Added
CC||k...@romanelli.info
--- Comment #5 from Adrian ---
(I
https://bugs.kde.org/show_bug.cgi?id=460066
Rodrigo Pedra Brum changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=460066
--- Comment #3 from Rodrigo Pedra Brum ---
Hey Nate,
Sorry for not responding earlier, somehow the e-mails for this but report got
sent to a different tag in my GMail.
I often update through CLI and seldom through Discover, but I will try to
replicat
https://bugs.kde.org/show_bug.cgi?id=460066
--- Comment #2 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=460066
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC|
14 matches
Mail list logo
