Ticket #845 (closed defect: fixed)

Opened 3 years ago

Last modified 17 months ago

A multipart SMS didn't merge into one.

Reported by: uzytkownik Owned by: ainulindale
Priority: major Milestone:
Component: shr-messages Version: SHR-unstable
Keywords: Cc:

Description (last modified by TAsn) (diff)

There's one SMS (at least) that didn't get merged into one and all of it's parts was shown as different messages.

Change History

comment:1 Changed 3 years ago by TAsn

  • Status changed from new to closed
  • Resolution set to invalid

It's there for ~6 months (in unstable) and it's in testing2009 since forever.

comment:2 Changed 3 years ago by uzytkownik

I recived an sms which was split. I have testing and it was updated a few days ago.

comment:3 Changed 3 years ago by TAsn

  • Status changed from closed to reopened
  • Resolution invalid deleted
  • Type changed from enhancement to defect
  • Description modified (diff)
  • Summary changed from Support for multipart SMS to A multipart SMS didn't merge into one.

Ok, so if anything, it's a defect, not an enhancement.
Though I really doubt it's something we did wrong, but it is possible, please install
opimd-utils-cli
and give me the parts concerning the split message.
You should probably just run:
opimd-cli m query
And get the relevant parts manually if you are not familiar with opimd-utils-cli.

comment:4 Changed 3 years ago by TAsn

We can't fix it if you don't provide this info...

comment:5 Changed 3 years ago by uzytkownik

I asked (by SMS) my friend to send my >160 char message as I know that his messages caused the problem.
I will send it ASAP.

comment:6 Changed 3 years ago by Heinervdm

  • Milestone set to MS1

comment:7 Changed 3 years ago by TAsn

  • Status changed from reopened to closed
  • Resolution set to fixed

Reported failed to provide needed information (8 weeks is more than enough), we have to assume it's fixed.

comment:8 Changed 17 months ago by morphis

  • Milestone MS1 deleted

Milestone MS1 deleted

Note: See TracTickets for help on using tickets.