Summary: | ask user to recover lost session if konqueror crashed | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Eduardo Robles Elvira <edulix> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | Dexter.Filmore, travisgevans |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | RedHat Enterprise Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Eduardo Robles Elvira
2004-06-22 13:40:46 UTC
Firefox's SessionSaver (http://extensionroom.mozdev.org/more-info/sessionsaver) provides some of these features; as a result, I feel like I have a 'safety net' while using it for day-to-day work. Find-as-you-type kept me on Firefox for a long time; now that I'm again using Konqueror for day-to-day work, this feature holds second place for me. I'd feel more comfortable in pushing Konqueror hard and flushing out bugs when I know that clicking on that link/button again won't cause me to lose all my browsing context in all my tabs, and would let me spend the time filing a complete bug (with the site owner or with kde) instead of recreating all my tabs. I would feel (psychologically; technically speaking, konqueror appears incredibly stable of late) more secure knowing I can visit many possibly poorly-coded or resource-intensive sites without losing my context -- in the other tabs I'm working/researching -- to a wayward applet/javascript/plugin. I can log out and log back in, and konqueror restores my tabs; but sometimes I'd like to just quit konqueror, restart it, and have it start up with my previous set of tabs. This helps work around memory leaks (of which there appear to be vanishingly few in kde 3.3.2, under Debian Sarge). Sometimes I run into crashes as well, and would like my previous tab setup restored on restart. For example, one might extend the 'previous crashes' menu to group urls by which browser window they appeared in tabs, and have an option to open them all in tabs in a new window. Again, though, Konqueror is surprisingly stable, so I rarely see crashes. *** This bug has been confirmed by popular vote. *** There are only a few issues which prevent me from using Konqueror full-time, and this is on the top of the list. Konqueror can be made to crash under various circumstances, most of which are outside its control. Some mechanism does need to exist to regularly cache what the user has been doing: tabs open, pages open, desktops those pages are on, information in forms .. Some sort of Firefox-style "Session Saver" would be wonderful. Who can I fund to work on this wish? =) http://bugs.kde.org/show_bug.cgi?id=84802#c17 ------- Additional Comment #18 From jos poortvliet 2006-10-20 07:57 ------- @16 yes, being able to recover a lost session after a crash is very nice as well. there is already the 'crashes' plugin, it seems to be logical to ask to do it automatically... needs some work on the bug dialog, i guess, but still. anyway, let's hope someone has time for this for KDE 4 :D --+ http://docs.kde.org/stable/en/kdeaddons/konq-plugins/crashes/index.html I can't find a 'homepage' for this plugin, nor a reference as to how to get it. Some pages say it's part of the 'kdeaddons' package. I don't think that plugin would solve this problem. Would it capture the text a user was typing in editable fields? Would it save the scroll-position on each page in each tab/window? I'll email the author of that plugin to see if he'd be willing to comment. Krishna, keditbookmarks lets you import crash sessions as bookmarks. Sy Ali: the log is text and nothing is done to decrease the size of it when the browsing session continues for a long period iirc. in summary, if you were to add text change events to the logging, the log itself would be unbearably large. any solution would be relatively difficult and would require a rewrite of the existing plugin. (and the code in konqi that acts as the log) even worse, i'm no longer involved in kde as you probably realize, and noone else appeared to ever have any interest in this code... I agree with what has been said, it is a must for today's browsing. And somehow it's already there as mentioned before, if we reboot without closing Konq all is left good, so it should not be too hard no ? Hey, fixed this myself in KDE 4 :D So being the reporter of this bug. I fixed a bug I reported when I wasn't a KDE developer yayy |