[notification] all received messages are not always played back

@Ren Can you clarify a bit more. Sounds like a nice service

Do you actually receive the SMS and its just the audible notification you are missing?
Does the message itself contain any clues, is it formatted differently?
To confirm other SMS messages trigger an audible notification?

1. Yes I receive the SMS, just the sound is not played on the phone BQ 4.5.
2. No the SMS is very simple it is used just to alert me that a service has gone down for example
3. Yes other SMS are notified by an audible sound, the one that has been configured in system parameters.
Remember that everything about SMS notifications was running ok before OTA-9.

Steps to reproduce the problem:
1- I send a message inside a URL to the mobile operator server, I used "wget" to do so:
wget -O /dev/null --quiet --no-check-certificate 'https://smsapi.free-mobile.fr/sendmsg?user=21462625&pass=EecGm6kuwWyVBX&msg=This-Is-A-Test-Message'

2- The message is received on the phone, without the sound notification,
nor the green notification icon.

I've put a screenshot showing the messages list display
after the test message has arrived.

Screenshot added: filename is: bug1547462-screenshot.png

Issue is the same with the new OTA9.1 image.

Hi, can you check if you have any telephony-service-indicator crash file in /var/crash ?

Also, check if you get any suspicious message in $HOME/.cache/upstart/telephony-service-indicator.log by the time you receive those sms's.

Thank you.

1- Yes there are 2 files in dir /var/crash :

phablet@ubuntu-phablet:/var/crash$ ls -l
total 21940
-rw-r----- 1 phablet whoopsie 6262199 f�vr. 23 21:42 _usr_bin_dialer-app.32011.crash
-rw-r--r-- 1 phablet whoopsie 0 f�vr. 23 21:42 _usr_bin_dialer-app.32011.upload
-rw------- 1 whoopsie whoopsie 0 f�vr. 23 21:42 _usr_bin_dialer-app.32011.uploaded
-rw-r----- 1 root whoopsie 16063013 f�vr. 23 21:43 _usr_bin_gdb.0.crash
-rw-r--r-- 1 root whoopsie 0 f�vr. 23 21:43 _usr_bin_gdb.0.upload
-rw------- 1 whoopsie whoopsie 0 f�vr. 23 21:43 _usr_bin_gdb.0.uploaded
-rw-r----- 1 root whoopsie 130681 f�vr. 23 20:59 _usr_bin_lxc-stop.0.crash
-rw-r--r-- 1 root whoopsie 0 f�vr. 23 20:59 _usr_bin_lxc-stop.0.upload
-rw------- 1 whoopsie whoopsie 0 f�vr. 23 20:59 _usr_bin_lxc-stop.0.uploaded
phablet@ubuntu-phablet:/var/crash$

I had a look ,and the crashes seem related to OTA9 release.

2- Ok I see the issue : the telephony service tries to play a file that does not exists anymore!
So, it would be good, if the file does not exist, that the telephony service plays the initial default sound file...
So users would not think that this is a bug ?

setMedia() media: QUrl( "file:///usr/share/sounds/ubuntu/notifications/Melody-piano-short4sec.ogg" )
Tell me if you want I attach the 3 files. Thank you.

Sorry : in fact this sound file does exist in the phone (Melody-piano-short4sec.ogg).
The error messages that I can see in the file $HOME/.cache/upstart/telephony-service-indicator.log
seems related for another reason.
I am going to attach the 3 files in a while.

Attached to my comments the files containing the 4 files related to crashes (not 3):
bug1547462-crash-4files.tgz

Thank you!

from the logs I can't tell much yet where the problem is,

could you run "dbus-monitor > dbus.log" as phablet user and after you reproduce the issue just press ctrl+c and attach dbus.log file here?

You can remove the phone number from the logs before attaching it if you wish.

ok Tiago, now here is the file dbus.log
I've changed phone number to +33123456789 and the SMS message is "NEW-TEST"
and it has arrived in the phone at time 9:52 .

Thank you.

I have some more questions:

1) Does the phone vibrate even you get the message?
2) Is messaging-app open? Can you reproduce it also with messaging-app closed?
3) Once you reproduce the bug, can you check if telephony-service-indicator is running with "ps -aux | grep telephony-service-indicator"

Thank you

Ok Tiago, Here are the results of the test.

First I check that the telephony service is running, and this is the case:

phablet@ubuntu-phablet:~$ ps -aux | grep telephony-service-indicator
phablet 2261 0.0 0.5 177012 5564 ? Ssl févr.24 0:39 /usr/bin/telephony-service-indicator
phablet 22490 0.0 0.0 4852 676 pts/29 S+ 20:26 0:00 grep telephony-service-indicator
phablet@ubuntu-phablet:~$

Now the test without messaging-app window opened and the screen already has auto-shut.

The message is sent from my alert server to the FreeMobile SMS server.
After about 10 seconds...
The phone does not vibrate (answer 1) but its own screen opens during about ~15 seconds,
then the phone screen switches off.
From that point, I enter the phone,
I can realize that the message-app window is not open,
I check that the telephony service is still running (answer 2):

phablet@ubuntu-phablet:~$
phablet@ubuntu-phablet:~$ ps -aux | grep telephony-service-indicator
phablet 2261 0.0 0.5 177012 5564 ? Ssl févr.24 0:39 /usr/bin/telephony-service-indicator
phablet 23387 0.0 0.0 4852 676 pts/29 S+ 20:28 0:00 grep telephony-service-indicator
phablet@ubuntu-phablet:~$

In my previous tests I remember that the messaging-app window was opened(answer 3)
with the same issue.

Do not hesitate to ask me to make more tests. Thanks again. Good evening.

Thank you.

Could you also run the following commands as soon as the bug is reproduced and then attach the output files here (indicator_observer.log and indicator_backtrace.log) ?

1) dbus-send --print-reply --dest=com.canonical.TelephonyServiceIndicator /org/freedesktop/Telepathy/Client/TelephonyServiceIndicator org.freedesktop.DBus.Properties.Get string:org.freedesktop.Telepathy.Client.Observer string:ObserverChannelFilter &> indicator_observer.log

2) sudo gdb --batch -ex "thread apply all bt full" -p $(pidof telephony-service-indicator) > indicator_backtrace.log

Some more questions:

1) what happens if you receive an sms from any other number after the bug is reproduced? Does it behave correctly? or once the bug is reproduced it always happens until you reboot?

2) Can you check if the count of received sms's in the welcome screen increase when you get these messages?

3) When you get the message from your operator, is the recipient number in messaging-app the same as your own sim card phone number? Or is this a carrier service phone number?

Attached are the 2 files: indicator_observer.log and indicator_backtrace.log .

indicator_observer.log

indicator_backtrace.log

Answers to your questions:

1- After the bug is reproduced, all other SMS coming from other contacts are correctly notified by the sound and by a green icon.
Always. The problem occurs for the SMS coming from my own number (in fact it is the FreeMobile server) to my own number .
Other SMS/MMS received are not impacted. Even when I reboot : the problem is still the same.

2- In the welcome message I have no received SMS count...
I only get in my own language something like : "No SMS sent today"

3- Yes, the recipient number in messaging-app is the same one as in the SIM 1.

I have noticed today that the Telegram received messages are not notified by a notification sound.
This can be a path to find the cause.

The real cause is that we skip notifications when the sender phone number matches the sim card number that received that message.
The fix is on the way.

Thanks for all the information and for taking time to help us fix this bug.

Muito obrigado Tiago - I'm happy that you succeeded to find the cause, congratulations!

This bug was fixed in the package telephony-service - 0.1+16.04.20160307-0ubuntu1

---------------
telephony-service (0.1+16.04.20160307-0ubuntu1) xenial; urgency=medium

  * Compare target id to check if this is a channel to the self contact.
    (LP: #1546369)
  * Display notifications for sms's where sender phone number matches
    the sim card phone number that received the message. (LP: #1547462)
  * Only add notifications to messaging-menu if ack didn't happen in the
    meantime.

 -- Tiago Salem Herrmann <email address hidden> Mon, 07 Mar 2016 20:13:48 +0000