Le dimanche 09 juin 2019, David C. Rankin a écrit :
OK, now I understand. You mounted a partition, looked at a pdf, then saved the sesson (I guess with the pdf open?) and now when you open konqueror without the partition mounted, it crashes.
Also, when you say "I recorded the KDE3 session.", how exactly did you record it? Saving with session manager? Saving the konqueor profile filemanagement? Or, really recording some animation of what you did on your desktop? (if so -- with what?) If it was saving the konqueror profile, you can probably delete the [History] information from ~/.kde/share/config/konquerorrc
I don't know how much empty space you have on your drive, but it would help if you could load a few -debug packages so a complete backtrace can be captured. For example, everywhere you see '?" in the kcrash backtrace, that is missing information that would come from the -debug files. For example, this information is all missing:
#15 0x000000000040879d in ?? () #16 0x0000000000409371 in ?? () #17 0x000000000040991c in ?? () #18 0x0000000000405cd9 in ?? () #19 0x00007f137e854feb in __libc_start_main () from /lib64/libc.so.6 #20 0x00000000004065c9 in ?? ()
My guess is the installing following -debuginfo packages would probably fill in most of the missing information:
qt3-debuginfo kdebase3-apps-debuginfo kdebase3-debuginfo kdelibs3-debuginfo
The symbol files shouldn't be more than 50M or so, and you can remove them after you capture a clean kcrash backtrace. Let me know if this makes sense and if you can load the packages and try and capture a full backtrace.
-- David C. Rankin, J.D.,P.E.
-------------------------------------- Yes, this is correct. Of course, I solved the problem just puting a "mount /linux/7-samsung_sav/" in my .profile file.
The partition is the KDE3 partition, the KDE menu is changing when we activate the option like done in the snapshot jointed.
hoping it helps...