[dolphin] [Bug 383942] Application: Dolphin (kdeinit5), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=383942 Justin Zobel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||justin.zo...@gmail.com Resolution|--- |FIXED --- Comment #7 from Justin Zobel --- Marking as resolved as no other user has commented on this or marked a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383942] Application: Dolphin (kdeinit5), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=383942 Julian Schraner changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #6 from Julian Schraner --- Thanks for the update, changing the status until somebody experiences this bug again. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383942] Application: Dolphin (kdeinit5), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=383942 --- Comment #5 from Robert Laney --- Hi Julian, I "solved" the bug by re-installing completely mageia 6 distro including KDE. The problem disappeared so far. So, I can't redo a Valgrind log from this Dolphin crash. (I will do it if it occurs again :-( ) Sorry, BL Le 29/06/2018 à 21:34, Julian Schraner a écrit : > https://bugs.kde.org/show_bug.cgi?id=383942 > > Julian Schraner changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > CC||juliquad...@gmail.com > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #4 from Julian Schraner --- > First: Thanks for uploading the valgrind log! The version you were using to > originally report this bug is now severely outdated. Could you try to update > Dolphin and reproduce this crash again? If the bug does still occur, a new > valgrind log would be helpful as this would represent the current state of the > cod e better. Thanks! > -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383942] Application: Dolphin (kdeinit5), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=383942 Julian Schraner changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||juliquad...@gmail.com Status|UNCONFIRMED |NEEDSINFO --- Comment #4 from Julian Schraner --- First: Thanks for uploading the valgrind log! The version you were using to originally report this bug is now severely outdated. Could you try to update Dolphin and reproduce this crash again? If the bug does still occur, a new valgrind log would be helpful as this would represent the current state of the cod e better. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383942] Application: Dolphin (kdeinit5), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=383942 --- Comment #3 from Robert Laney--- Created attachment 109110 --> https://bugs.kde.org/attachment.cgi?id=109110=edit Valgrind output of the bug I'm new to Valgrind so I don't really know if this file can help to track this issue -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383942] Application: Dolphin (kdeinit5), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=383942 Christoph Feckchanged: What|Removed |Added Severity|normal |crash --- Comment #2 from Christoph Feck --- A valgrind log would help to understand if the the memory corruption is caused by the nvidia driver or KDE code. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383942] Application: Dolphin (kdeinit5), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=383942 --- Comment #1 from Elvis Angelaccio--- Yes, that's the nvidia driver. I'd suggest you to report this to your distribution or even upstream Nvidia. -- You are receiving this mail because: You are watching all bug changes.