Problem description: Jump Lists disappeared after installation (and now they do not appare anymore) Steps to reproduce: 1. I've installed the new version of libreoffice 2. In the menu start I had writer and calc, each one with a jump list of latest file, and some (most used) were pinned 3. Everything has disappered Current behavior: 1. I'm using writer and calc, opening files in several ways (from the folder, from the recent list inside the program, dragging and dropping on the application icon...) 2. Still, no jump list beside the program in the Start menu. Expected behavior: see an use jump lists beside the Libreoffice programs Platform (if different from the browser): Win 7 64 bit Browser: Chrome
See Bug 50913, Bug 53019, Bug 54009.
I've got exactly the same problem. Due to annoyance with the new date-rules I only moved to LO 3.6(.3.2) recently on my Windows 7 64bit. 1. I did an upgrade from 3.5 to 3.6 2. In the menu start the separate office products were gone 3. After opening Calc several times it did appear on the menu start list, but without the jumplist @ bfoman Although the mentioned bugs may be linked to a similar problem they do not address this problem. Bug 50913 does not apply since it concerns the task bar and not the menu start Bug 53019 does not apply since it concerns the task bar and not the menu start Bug 54009 without a jump list there is nothing to pin ...
Hi, I can confirm this bug. It still exists in 3.6.5.2. The jump lists used to work fine with 3.5.
p.s.: This bug seems to be a duplicate of bug 35785. I tried to mark this one as duplicate but it did not seem to work. Maybe it will work now with this submission. :-)
(In reply to comment #3) > Hi, I can confirm this bug. It still exists in 3.6.5.2. > > The jump lists used to work fine with 3.5. I've installed 3.6.5.2 today and tested it. The bug still exists Giovanni
(In reply to comment #4) > p.s.: This bug seems to be a duplicate of bug 35785. I tried to mark this > one as duplicate but it did not seem to work. > > Maybe it will work now with this submission. :-) Indeed, thanks! *** This bug has been marked as a duplicate of bug 35785 ***