[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
This happened again yesterday. With GOOD network connection!!! But this time I was able to fetch the log file using the command Matthias posted. ** Description changed: + When sending text messages, Ubuntu displays the loading spinner forever. + In the provider's monthly reports, I can see that the message has been + sent multiple times, even though I only sent one message to one + recipient and the message was short enough not to be broken into + separate ones. + + + === Old description: === + When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). ** Summary changed: - High costs due to SMS being sent multiple times when having a bad network connection + High costs due to SMS being sent multiple times -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times Status in telephony-service package in Ubuntu: Confirmed Bug description: When sending text messages, Ubuntu displays the loading spinner forever. In the provider's monthly reports, I can see that the message has been sent multiple times, even though I only sent one message to one recipient and the message was short enough not to be broken into separate ones. === Old description: === When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
this is how the SMS could be monitored on sending to the modem, but only online or short after the sending: root@ubuntu-phablet:/home/phablet# /system/bin/logcat -b radio | tee /tmp/radio.out (btw: one should better use: /system/bin/logcat -b radio -v time to get as well the timestamps) ... I/use-Rlog/RLOG-AT( 1821): AT read start I/use-Rlog/RLOG-MUXD( 1234): [gsm0710muxd] 3557:main(): Frames received/dropped: 6560/0 I/use-Rlog/RLOG-MUXD( 1234): [gsm0710muxd] 1573:gsm0710_base_buffer_get_frame(): Get a complete frame. ch:2, ctrl:239, len:34 I/use-Rlog/RLOG-MUXD( 1234): [gsm0710muxd] 2162:extract_frames(): Writing 34 byte frame received on channel 2 to /dev/pts/5 I/use-Rlog/RLOG-MUXD( 1234): [gsm0710muxd] 2181:extract_frames(): write() returned. Written 34/34 bytes of frame to /dev/pts/5 D/use-Rlog/RLOG-AT( 1821): D/use-Rlog/RLOG-AT( 1821): +ECSQ: 11, 99, -368, -400, -28 D/use-Rlog/RLOG-AT( 1821): AT +ECSQ: 11, 99, -368, -400, -28 D/use-Rlog/RLOG-AT( 1821): RIL_URC_READER:+ECSQ: 11, 99, -368, -400, -28 D/use-Rlog/RLOG-AT( 1821): RIL_URC_READER Enter processLine D/use-Rlog/RLOG-RIL( 1821): Nw URC:+ECSQ: 11, 99, -368, -400, -28 I/use-Rlog/RLOG-RILC( 1821): RIL(1) UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:76 I/use-Rlog/RLOG-RILC( 1821): 01 00 00 00 F1 03 00 00 0B 00 00 00 63 00 00 00 I/use-Rlog/RLOG-RILC( 1821): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I/use-Rlog/RLOG-RILC( 1821): 00 00 00 00 63 00 00 00 FF FF FF 7F FF FF FF 7F I/use-Rlog/RLOG-RILC( 1821): 2D 01 00 00 FF FF FF 7F 01 00 00 00 00 00 00 00 I/use-Rlog/RLOG-RILC( 1821): 90 FE FF FF 70 FE FF FF E4 FF FF FF 0B 00 00 00 I/use-Rlog/RLOG-AT( 1821): AT read start I/use-Rlog/RLOG-MUXD( 1234): [gsm0710muxd] 1573:gsm0710_base_buffer_get_frame(): Get a complete frame. ch:2, ctrl:239, len:34 I/use-Rlog/RLOG-MUXD( 1234): [gsm0710muxd] 2162:extract_frames(): Writing 34 byte frame received on channel 2 to /dev/pts/5 I/use-Rlog/RLOG-MUXD( 1234): [gsm0710muxd] 2181:extract_frames(): write() returned. Written 34/34 bytes of frame to /dev/pts/5 D/use-Rlog/RLOG-AT( 1821): D/use-Rlog/RLOG-AT( 1821): +ECSQ: 11, 99, -372, -398, -24 D/use-Rlog/RLOG-AT( 1821): AT +ECSQ: 11, 99, -372, -398, -24 D/use-Rlog/RLOG-AT( 1821): RIL_URC_READER:+ECSQ: 11, 99, -372, -398, -24 D/use-Rlog/RLOG-AT( 1821): RIL_URC_READER Enter processLine D/use-Rlog/RLOG-RIL( 1821): Nw URC:+ECSQ: 11, 99, -372, -398, -24 I/use-Rlog/RLOG-RILC( 1821): RIL(1) UNSOLICITED: UNSOL_SIGNAL_STRENGTH length:76 I/use-Rlog/RLOG-RILC( 1821): 01 00 00 00 F1 03 00 00 0B 00 00 00 63 00 00 00 I/use-Rlog/RLOG-RILC( 1821): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I/use-Rlog/RLOG-RILC( 1821): 00 00 00 00 63 00 00 00 FF FF FF 7F FF FF FF 7F I/use-Rlog/RLOG-RILC( 1821): 2D 01 00 00 FF FF FF 7F 01 00 00 00 00 00 00 00 I/use-Rlog/RLOG-RILC( 1821): 8C FE FF FF 72 FE FF FF E8 FF FF FF 0B 00 00 00 I/use-Rlog/RLOG-AT( 1821): AT read start I/use-Rlog/RLOG-MUXD( 1234): [gsm0710muxd] 3557:main(): Frames received/dropped: 6562/0 I/use-Rlog/RLOG-RILC( 1821): RIL(1) SOCKET REQUEST: SEND_SMS length:348 I/use-Rlog/RLOG-RILC( 1821): 19 00 00 00 27 02 00 00 02 00 00 00 FF FF FF FF I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx I/use-Rlog/RLOG-RILC( 1821): xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx D/use-Rlog/RLOG-RILC( 1821): New command received from RIL(1) D/use-Rlog/RLOG-RIL( 1821): SEND_SMS dispatched to RIL_CMD_PROXY_1 I/use-Rlog/RLOG-RIL( 1821): RIL_CMD2_PROXY_4 wakeup I/use-Rlog/RLOG-RIL( 1821): RIL_CMD2_PROXY_4 sleep
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
What brings my attention here is that apparently the receiver is seeing only one message (comment #7). It is possible that the receiver phone detects receiving 2 messages that are exactly the same and shows only one, but I would say that is not usual. I would like to know if in some case the receiver shows more than one message. It is not impossible that the operator is wrongly charging for non-sent SMS. On the other hand, in the attached files it can be seen that messages are retried in quite regular intervals (between 5-7 seconds). It is possible that somewhere in the stack there is a 5 seconds time-out and the message is retried without actually waiting for some response from the modem, which is what should be done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: Confirmed Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
@Alfonso: Thank you very much for your response. I really hope that this will be fixed soon because I agree with your comment from the mailing list that this is worrying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: Confirmed Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
the AT chats can be monitored online from the ring buffers with: $ sudo /system/bin/logcat -b radio but this does not help to analyze weeks later what was going on :-( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: Confirmed Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
Thank you for your reply, Matthias! There is only one line in the database per message. Both rows have a messageStatus of 4 which seems to be correct. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: Confirmed Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
a) I sent one SMS every time. b) Those were short enough to be sent as one SMS by the provider. c) The receivers' phones are displaying only one SMS. d) The MySQL database has only one entry both times. For the first screenshot its timestamp is 2015-07-12T19:31:58.664 for the second one it says 2015-05-30T11:31:17.015. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: Confirmed Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
comparing the database timestamps and the provider times (from the screenshots) we see: databaseprovider 19:31:58.664 21:32:05 ... 21:32:45 11:31:17.015 13:31:21 ... 13:31:32 i.e. (ignoring the 2 hour diff due to TZ) it seems that the database timestamp is made when the SMS is queued for delivery and not from the last send attempt; are there other log files (the question goes to Canonical) about the send attempts? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: Confirmed Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
Yes, after converting it to the right time zone (UTC+2) it becomes 21:31:58.664 21:32:05 ... 21:32:45 13:31:17.015 13:31:21 ... 13:31:32. As I remember seeing the phone trying to send it for a relatively long time on July 12th, it really seems as if there is some issue with queueing the messages and recognizing when sending one failed. Btw, thank you for your help. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: Confirmed Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
The worst one. ** Attachment added: SMS.png https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4437379/+files/SMS.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: New Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
Another one. ** Attachment added: SMS2.png https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+attachment/4437380/+files/SMS2.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: New Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telephony-service (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: Confirmed Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
[Touch-packages] [Bug 1480554] Re: High costs due to SMS being sent multiple times when having a bad network connection
What I do not fully understand is: AFAIK SMS is sent upstream to the provider with AT cmds, like this example: AT+CMGF=1 OK AT+CMGS=+49170xx CRThis is the text message. +CMGS: 4711 OK (+CMGF=1 is text mode, =1 PDU mode). The response from the provider could be OK or ERROR. Have you looked into the MySQL database in the phone to see what is there about the messages. If you need how to look into, see here: http://www.unixarea.de/bq/bq-aquaris-e45-ubuntu.txt (chap. 15). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1480554 Title: High costs due to SMS being sent multiple times when having a bad network connection Status in telephony-service package in Ubuntu: Confirmed Bug description: When having a bad network connection, Ubuntu tries to send SMS multiple times but fails to recognize which messages have already been sent, resulting in very high costs due to the same message actually being sent several times. I found this when looking through my provider's monthly reports and I remember being on train journeys with very bad network connections on these days. See the attached screenshots. == This happened on a Nexus 4 running on the stable channel (with up-to- date images at the given times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1480554/+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
