https://bugs.meego.com/show_bug.cgi?id=13513

           Summary: Sync history tries to load the wrong file (no such
                    file name)
    Classification: MeeGo Projects
           Product: SyncEvolution
           Version: unspecified
          Platform: All
      Architecture: ---
            Status: NEW
          Severity: normal
          Priority: Undecided
         Component: Maemo 5
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]
                CC: [email protected],
                    [email protected]
   Estimated Hours: 0.0


HARDWARE MODEL (on what HW this bug is uncovered): Nokia N900

BUG DETAILED DESCRIPTIONS
===========================================================

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. doing a sync using the Synchronize! button
2. tap on the View Synchronization History button
3. choose the entry 10.02.2011 10:45:12 [Success]
4. the browser shows an error: file
/home/user/.cache/syncevolution/memotoo/2011-02-10-10-45/sysynclib_linux.html#H1
not found

EXPECTED OUTCOME:
===================
The synchronization history from 10.02.2011 14:45:12 is showing.

ACTUAL OUTCOME:
===================
Error message from the browser.

USER IMPACT:
===================

REPRODUCIBILITY:
always
=====================================

EXTRA SOFTWARE INSTALLED:
============================

OTHER COMMENTS:
===================
The name of the file on this directory is not sysynclib_linux.html, instead its
name is syncevolution-log.html.

-- 
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to