[telepathy] [Bug 325957] New: Log viewer crash displaying conversations from multiple accounts on the same day

[Leon Handreke]

https://bugs.kde.org/show_bug.cgi?id=325957

            Bug ID: 325957
           Summary: Log viewer crash displaying conversations from
                    multiple accounts on the same day
    Classification: Unclassified
           Product: telepathy
           Version: git-latest
          Platform: unspecified
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: text-ui
          Assignee: kde-telepathy-bugs at kde.org
          Reporter: leonh at ndreke.de

When chatting with the same person with multiple accounts on the same day, the
date row in the log viewer can be expanded to reveal the accounts from which
conversations with this person were held on this day.

This situation can lead to crashes. Here are some examples:
1. The first row in the date list can be expanded to reveal the accounts. The
first account has an expansion arrow next to it and if expanded, it crashes.
The second account displays without such an arrow and clicking it reveals the
conversation.
2. The first an only row in the date list can be expanded and should reveal the
two accounts that conversations were held with on that date, but instead it
crashes.

Reproducible: Always

Steps to Reproduce:
Case 2 can easily be reproduced by doing the following:

1. Add two test contacts (test1 at test.com and test2 at test.com)
2. Send a message to each of them
3. Try to view these conversations in the log viewer
Actual Results:  
Crash

Expected Results:  
I can view the conversation

After going through it with a debugger, I have a hunch that it may be related
to rowCount not always returning 0 if the parent is an account but rather tries
to return the rowCount for the corresponding row index at the date level (and
either possibly wrongly displays expansion arrows or crashes because the date
level has less rows than the accounts level). No idea how to fix it though.

-- 
You are receiving this mail because:
You are the assignee for the bug.