Bug 83803 - ask user to recover lost session if konqueror crashed
Summary: ask user to recover lost session if konqueror crashed
Status: RESOLVED FIXED
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 98344 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-06-22 13:40 UTC by Eduardo Robles Elvira
Modified: 2008-06-26 10:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eduardo Robles Elvira 2004-06-22 13:40:46 UTC
Version:            (using KDE KDE 3.2.2)
Installed from:    RedHat RPMs

Naturally konqueror is not bug safe and as it's mostly a container application is probable that it might crash in some circunstances - it's inevitable.

A big feature that other web browsers such as Galeon or Epiphny already has is that they ask the user whether they want to recover the lost session or not. I belive that feature is very helpful, user-friendly, and tremendously useful. 

Konqueror should allow the user to recover the tabs the user had opened (no matter if it was showing video via kaffeine kpart, other tab browsing it's home dir and other one showing a certain webpage via khtml). 

But the most important part is that the user should never lost important information; For example, the typical case is that you were writting a post via a webform, and who knows why the web browser crashes and you feel like crap. That happened to me just a a moment ago so guess why I'm writting this wish report =).

So if it's imposible to show the form the user had filled, then we have to figure out the better way to show the user every piece of text that it had filled in a ordered, logical and user-friendly way. I think that the easier way might be a window with a tab per webpage, containing some textboxes, inputs, select boxes... with the input the user may want to recover.
Comment 1 Krishna Sethuraman 2005-06-08 07:30:31 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.
Comment 2 Sy Ali 2006-06-23 14:33:00 UTC
*** This bug has been confirmed by popular vote. ***
Comment 3 Sy Ali 2006-06-23 14:37:42 UTC
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?  =)
Comment 4 Sy Ali 2006-10-20 12:28:13 UTC
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.

Comment 5 lypanov 2006-10-31 14:09:53 UTC
Krishna, keditbookmarks lets you import crash sessions as bookmarks.
Comment 6 lypanov 2006-10-31 14:13:04 UTC
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...
Comment 7 John E 2006-12-26 01:04:40 UTC
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 ?
Comment 8 Eduardo Robles Elvira 2008-05-23 16:29:38 UTC
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
Comment 9 Eduardo Robles Elvira 2008-06-26 10:03:20 UTC
*** Bug 98344 has been marked as a duplicate of this bug. ***