This bug was fixed in the package history-service -
0.1+15.10.20150828.1-0ubuntu1

---------------
history-service (0.1+15.10.20150828.1-0ubuntu1) wily; urgency=medium

  [ Gustavo Pichorim Boiko ]
  * Do not override the build type. Also remove a block of unused code
    from debian/rules.
  * Fix flags.
  * Prevent the history-daemon from crashing in the event of an ended
    call not having any remote member. (LP: #1458990)

  [ Tiago Salem Herrmann ]
  * Correctly set mCanFetchMore in the HistoryGroupedThreadsModel.
  * Generate eventId when there is none Set status to "Accepted" if the
    channel does not support delivery reports
  * Manually add self id to participants list if needed. (LP: #1486187)

 -- CI Train Bot <ci-train-...@canonical.com>  Fri, 28 Aug 2015 10:16:13
+0000

** Changed in: history-service (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to history-service in Ubuntu.
https://bugs.launchpad.net/bugs/1486187

Title:
  Sending an SMS to your own number triggers an empty row in messaging-
  app

Status in history-service package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  - open messaging-app
  - send an SMS to your own number

  Expected behavior:
  - a conversation with your own number is displayed

  What happens:
  - an empty row is shown in the conversation list

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1486187/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to