Public bug report changed: https://launchpad.net/malone/bugs/28567
Comment: Your comment about how the system works is not fair. The situation is easy. You have an issue, we are happy to work on fixing it but we need informations on what happen because we don't have the issue. It may be to some special .png that causes issue to the rendering library or something else. Does it make sense to you than for resolving an issue you need to know what happens? Now we don't "cancel" the bug, but we declare it useless because nobody can reproduce it and nobody can provides informations on what happen ... that's not really possible to figure what to fix what is broken. Providing a backtrace or a broken .png would allow use to have those informations and to track it. You don't need to be a martian and what is martian about attaching the files your have in your folder the next time it happens? Do you know how to open a command line and move a file if that happens again, so you can locate which one you have to move and is creating that? If you don't know I'm happy to explain that to you, just let me know. For the backtrace it's a bit technical but you don't need to be a programmer, I gave you the step for it. Open a command line (applications menu, accessories, terminal) and type in it: gdb -p $(pidof nautilus) you get a line starting by "(gdb)" and waiting on your input, you type "thread apply all bt". Then you get the backtrace, you just have to copy it to a command. To copy you can use the items of the right click menu. Bug needs efforts of both parts to be fixed and I don't think than people waste their time making that working as it does at the moment -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs