https://bugs.kde.org/show_bug.cgi?id=463358
--- Comment #5 from Stefano Crocco <stefano.cro...@alice.it> --- I tried looking at your backtrace, and while I think I might have found the condition causing your crash, I can't really understand why that condition happens and why it isn't caught by a check which is there exactly for doing that. Unfortunately, given the dynamic nature of Konqueror, it's difficult to find out exactly what is happening without more information. The first thing I noticed in your backtrace is the mention of lines of code which are only called when you try loading a session from the command line, using the --open-session option. Can you confirm this is what you actually are doing? From the title of your bug report, I assumed you were launching Konqueror without special options, but the backtrace seems to say otherwise. Also, how are you starting Konqueror? From a terminal emulator, from KRunner, clicking on its icon? If you are indeed trying to open a session, is there any chance you could upload the session data, of course provided it doesn't contain any sensitive information? You can find that data in the in ~/.local/share/konqueror/sessions directory: there's a subdirectory for each session. Thanks -- You are receiving this mail because: You are watching all bug changes.
