Bug 296388 - When rekonq is restored at login, selecting bookmark in the menu has no effect
Summary: When rekonq is restored at login, selecting bookmark in the menu has no effect
Status: RESOLVED FIXED
Alias: None
Product: rekonq
Classification: Applications
Component: general (show other bugs)
Version: 0.9.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 0.10
Assignee: Andrea Diamantini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-19 20:29 UTC by Guillaume DE BURE
Modified: 2012-12-04 00:26 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 Guillaume DE BURE 2012-03-19 20:29:23 UTC
I have my KDE settings set so that all applications previously opened at logout are restored at login. when rekonq is started this way, clicking on an item in the bookmark menu has no effect. Closing and reopening rekonq seems to fix the issue.

Please tell me if the bug is not clear, I'll do my best to refine :)

Guillaume
Comment 1 Andrea Diamantini 2012-03-20 08:47:11 UTC
The bookmark menu is the one on the toolbar with a yellow star?
Comment 2 Guillaume DE BURE 2012-03-20 12:24:39 UTC
Yes it is the one ! Anything I can provide to help ?
Comment 3 Andrea Diamantini 2012-03-20 14:53:25 UTC
No, thanks. Enough information to try reproducing :)
Comment 4 Manu 2012-07-09 11:47:35 UTC
I've got the same problem.
Comment 5 Andrea Diamantini 2012-07-09 16:06:27 UTC
Can confirm it. Targetting (again) 1.0...
Comment 6 Andrea Diamantini 2012-07-09 21:35:25 UTC
Git commit 050659a86bc4419ae0d9f67ea013f8657fc23c71 by Andrea Diamantini.
Committed on 09/07/2012 at 23:27.
Pushed by adjam into branch 'master'.

Fix session restore code

This let bookmark manager code properly load :)
Related: bug 298051

M  +81   -86   src/application.cpp
M  +3    -0    src/bookmarks/bookmarkmanager.cpp

http://commits.kde.org/rekonq/050659a86bc4419ae0d9f67ea013f8657fc23c71
Comment 7 Jekyll Wu 2012-12-04 00:26:45 UTC
*** Bug 311109 has been marked as a duplicate of this bug. ***