Skip to main content
S
silent.creek
Known Participant
October 24, 2011

P: Scrolling over folders in library module doesn't work

  • October 24, 2011
  • 56 replies
  • 1165 views

Hi everybody,

I experienced a bug in LR scrolling behaviour within the library module. To describe the problem best, I recorded a screencast video with audio comment that I uploaded to my webserver:
http://www.silentcreek.de/lrbug/demo.avi
In short: Scrolling with the mousewheel over folders in LR's library module doesn't work properly.

Here is what I know:
1) The bug doesn't always occur. Sometimes scrolling works for a couple of days, but most times it doesn't, which is annoying, of course.
2) I could only reproduce this bug as shown in my demo video in the library module when trying to scroll with my mousewheel over the folders or publishing services. Everywhere else, it works fine.
3)The bug seems hardware independent: I experienced it on my laptop as well as my desktop (one Win 7 32bit, one Win 7 64bit; two different mice, one by MS one by Cherry).
4) I experienced this bug for quite a while with different versions of LR (currently 3.5, but the earliest version I used was 3.2)

I hope this helps to figure out the problem.

Thanks,

Timo

    This topic has been closed for replies.

    56 replies

    Show previous replies
    K
    krybik
    Participant
    November 27, 2011
    i've got exactly the same problem

    i run LR, switch to develop module, then back to lib module and then i cant scroll it.

    BUT, it occurs only if i'm in grid mode. i.e., when i switch to the Loupe mode, scrolling is working OK, then i go back to Grid and it stops working immediately.
    areohbee
    areohbee
    Legend
    November 10, 2011
    I still could not reproduce - maybe somebody else will try.
    S
    silent.creekAuthor
    Known Participant
    November 10, 2011
    I just downloaded LR 3.6RC and for a short moment I thought it was solved, because I could scroll over the folders. BUT: When I switched to the develop module and then back to the library, I couldn't scroll anymore.

    ADDITIONAL BUG INFO:
    I can now clearly reproduce a pattern! When I start LR, I can scroll over the folders in the library module. But as soon as I switched to the develop module once and then back to the library module, I can't scroll anymore. The other modules (print, web, slideshow) do not influence the scroll behaviour. It also does not matter whether I actually do something int he development module (i.e. apply adjustments on a raw file) or not. Just entering the develop module once and going back to the library is enough to trigger the bug.

    So, unfortunately, still not solved.
    areohbee
    areohbee
    Legend
    November 10, 2011
    I do not have this problem, so clearly identified by the video...

    Lightroom version: 3.6 RC [788152]
    Operating system: Windows 7 Ultimate Edition
    Version: 6.1 [7601]
    Application architecture: x64
    System architecture: x64
    Physical processor count: 4
    Processor speed: 3.4 GHz
    Built-in memory: 7934.1 MB
    Real memory available to Lightroom: 7934.1 MB
    Real memory used by Lightroom: 1849.5 MB (23.3%)
    Virtual memory used by Lightroom: 1997.8 MB
    Memory cache size: 1355.6 MB
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1200, 2) 1920x1200

    (Kensington Expert Mouse Trackball, model K264325)

    Was it fixed in 3.6RC?
    S
    silent.creekAuthor
    Known Participant
    November 9, 2011
    Is anybody at Adobe reading this? Is tehre a way I can provide additional information to help track down this issue?
    S
    silent.creekAuthor
    Known Participant
    October 24, 2011
    Just some more info:
    I did some research online and found that other users experience this problem, too. See this forum thread:
    http://www.lightroomforums.net/archiv...
    Here a user claims that he solved the problem by killing a Kaspersky software. But another user in the same thread says that he has the same issue but doesn't use the mentioned Kaspersky software. As for myself, I don't use any Kaspersky software. Maybe his solution was just a mere coincidence, because from my experience the problem seems to occur sporadically.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices