Bug 174841

Summary:	Scrollbars blinking when displaying particular image size
Product:	[Applications] okular	Reporter:	Ruchir Brahmbhatt <ruchir.brahmbhatt>
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	CLOSED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	jpg file causing resize issue

Description Ruchir Brahmbhatt 2008-11-11 08:26:01 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Okular 0.7.3
Screen resolution: 1280X800
File type: jpg

Today I opened one jpg file in okular having size 1050X678. Left panel having bookmarks, content, review, etc. was also open. Okular continuously resizing image and scrollbars appear and disappear. This keeps going on. It is reproducible with any image of this size. I'll attach sample blank image I created.

Comment 1 Ruchir Brahmbhatt 2008-11-11 08:26:38 UTC

Created attachment 28486 [details]
jpg file causing resize issue

Comment 2 Ruchir Brahmbhatt 2008-11-11 08:31:01 UTC

When I reported this bug, I got bounce mail from okular-devel-bounces@kde.org as below:

[Bug 174841] Scrollbars blinking when displaying particular image
size

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Post by non-member to a members-only list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:

    https://mail.kde.org/mailman/confirm/okular-devel/<key hidden>

I'm not sure if that should happen. J

Comment 3 Pino Toscano 2008-11-12 01:09:24 UTC

(In reply to comment #2)
> When I reported this bug, I got bounce mail from okular-devel-bounces@kde.org
> as below:
> [...]
> I'm not sure if that should happen. J

The mailing list is moderated, so unless I can make mailman's filters to work, you get that.

Anyway, this was already reported.

*** This bug has been marked as a duplicate of bug 160628 ***