Summary: | konqueror 4.14.0 on 10.6.8 homebrew file browser scroll is unresponsive | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | peterwong <petep0p> |
Component: | file list view | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 4.14.0 | ||
Target Milestone: | --- | ||
Platform: | Homebrew (macOS) | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
peterwong
2014-10-22 05:37:46 UTC
Hi, Does it make any difference if you change graphics system? QT_GRAPHICSSYSTEM=raster konqueror QT_GRAPHICSSYSTEM=native konqueror (In reply to Tommi Tervo from comment #1) > Hi, > > Does it make any difference if you change graphics system? > > QT_GRAPHICSSYSTEM=raster konqueror > QT_GRAPHICSSYSTEM=native konqueror I can check, but...how do I set that? is it just an environment var i can set in my .bashrc? or is that a build option? actually, google helped me with that. i tried this: $ konqueror --graphicssystem raster & but it did not change the scrolling behavior. this makes sense, though because the scrolling behaves well in other qt/kde apps and in the web view in konqueror. also, it seems like it may be unrelated to the too-many-scroll-events bug i mentioned in the OP. the problem seems consistently to be that any slow scrolling does not register. only scrolling at a swipe gesture speed has any effect. so...kind of the opposite. UPDATE: i just upgraded my OS to Mavericks 10.9.5, and reinstalled my whole homebrew prefix. fresh install of konqueror included. The issue persists, and the --graphicssystem option still does not have any effect. is anyone able to help? thanks for reading! UPDATE #2: i have since discovered that the issue is not actually as I originally thought. If I hover the cursor over the scroll bar, then the two-finger scroll gesture works smoothly and beautifully. hovering the cursor over any other part of the file view gives the choppy/unresponsive scroll behavior that I described originally. Does anyone have any insight into this new development? Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |