[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #11 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 --- Comment #10 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 bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 Davide Gianforte changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||dav...@gengisdave.org Resolution|--- |WAITINGFORINFO --- Comment #9 from Davide Gianforte --- Does it still happens? Thank you -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 --- Comment #8 from pointl...@maildrop.cc --- Thanks for reply, Nikita! Now I know what to do If I will see that often. Yeah, for now this several-days-ago issue is the most recent issue that was on my PC. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 --- Comment #7 from Nikita Melnichenko --- > May be there are some additional tools/wrappers You can run it under gdb and check for backtrace (bt command) once it crashes again. You may need to install debug symbol packages in your distribution to have meaningful backtraces. If you encounter this often, it may be worthwhile. If it happened only once, we are out of luck. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 --- Comment #6 from pointl...@maildrop.cc --- if we are completely out of game with bug already happened, may be there are log settings of KDE/Krusader? May be there are some additional tools/wrappers to execute krusader with, for example --executeapp krusader -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 --- Comment #5 from pointl...@maildrop.cc --- Toni, Nikita thanks for explanation! So may be that will helps to others in future. Nikita, I believe if we can not reproduce a lack in app than there is not enough/detailed information about it: if I can provide you all information (which may can be shortened analogue of your step-by-step debug process in your IDE) than may be you can also fix it without ability to reproduce it - just theoretical fix as you done before if you have enough information about bug and skills in programming. I want to try to do it, and if you want to try it too: may be we can fix the bug? What information to collect (and how to do it)? The simplest information increase can be in journalctl -pX -bY where X is greater than previous value of 3. But what is another ways to collect info? But it can be a long-long way to do it but again with no result guarantee. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 Nikita Melnichenko changed: What|Removed |Added Component|general |krviewer -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 Nikita Melnichenko changed: What|Removed |Added Keywords||triaged --- Comment #4 from Nikita Melnichenko --- Reports like this are important. Please don't feel like you're wasting your or my time. In case other people encounter it, we'll know it's a problem related to some libs or actions and eventually we may narrow down the possibilities and even fix it. At this point, I agree with Toni, there is not much we can do but we'll keep an eye on it. I wonder why KCrash handler (aka DrKonqi) didn't catch this crash... P.S. Reproducibility is very desired but not always required. I fixed a few crashes in my life that I couldn't reproduce. This is one of them: bug #389413. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #3 from Toni Asensi Esteve --- > No, I tried but I can not reproduce the issue on the same files. > So what is that mean? If I can not reproduce then to report bug is > pointless? > > Please explain bug report system to let me and you to do less pointless > work. Sometimes a problem happens because of a particular problem in a particular computer, and therefore the bug is not reproducible by a developer, and so there's not much he can do about it, he sees that the system is working correctly :-( Anyway, thanks for your interest. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 --- Comment #2 from pointl...@maildrop.cc --- No, I tried but I can not reproduce the issue on the same files. So what is that mean? If I can not reproduce then to report bug is pointless? Please explain bug report system to let me and you to do less pointless work. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 Nikita Melnichenko changed: What|Removed |Added CC||nikita+...@melnichenko.name --- Comment #1 from Nikita Melnichenko --- It seems like a libexiv2 crash (library for reading image tags). Can you repro this crash consistently? -- You are receiving this mail because: You are watching all bug changes.
