Bug 11737 – Hermes contact images blurry

Bug 11737 - Hermes contact images blurry


Summary:	Hermes contact images blurry

Status:	RESOLVED DUPLICATE of bug 11736

Product:	Hermes
Component:	General
Version:	unspecified
Platform:	N900 Maemo

Importance:	Unspecified enhancement (vote)
Target Milestone:	---
Assigned To:	unassigned
QA Contact:	general

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2011-01-02 03:40 UTC by timothy.stephen.webb
Modified:	2011-01-02 04:00 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description timothy.stephen.webb (reporter) 2011-01-02 03:40:20 UTC

SOFTWARE VERSION: 
(Settings > General > About product)

EXACT STEPS LEADING TO PROBLEM: 
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. Autp update Hermes from version 0.8.7 to current 0.8.8
2. Reboot N900
3. Open Hermes from desktop shortcut
4. Validate Facebook by diabling account, saving, then re-enabling and saving
again
5. Click Refresh
6. Normal Hermes updating FB behavious (pre-processing, finalising, etc)
7. Hermes displays results (xx contacts matched, xx contacts updated, xx
contacts unmatched)
8. Close Hermes
9. Desktop contact shortcut and address book images blurry

EXPECTED OUTCOME: Normal behaviour of previous version 0.8.7 with clearly
defined images.

ACTUAL OUTCOME: 

REPRODUCIBILITY: Always

EXTRA SOFTWARE INSTALLED: Kernel Power v46, running @ 1000MHz, 8Gb MicroSD
(blank), no other account active besides Facebook.

OTHER COMMENTS: Facebook was also disabled, contact images set back to no
image, enabled, refreshed contacts again and the bug is replicated.

Comment 1 Andre Klapper maemo.org

2011-01-02 04:00:00 UTC

Hi, thanks for reporting this!
This particular issue has already been reported in our bug tracking system, but
please feel free to report any further bugs you find.

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