touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #24598
[Bug 1378811] [NEW] If a SIM slot with no signal is selected as the default SIM then replying via the indicator fails silently
Public bug reported:
Prerquisites:
The 'For messages use' option in System Settings Cellular panel should
be set to a slot that contains a SIM card with no signal
Steps to reproduce:
1. Send a message to the SUT (with the messaging-app closed)
2. Wait for the snap notification to disappear
3. Open the messaging indicator and press anywhere on the message (except on the message icon which will open the messaging app)
4. Enter your reply in the text field that appears (keeping in mind that there may be a bug that stops the Send button from being enabled if the keyboard is in the middle of autocorrecting a word)
5.) Hit the send button when it is enabled
Expected result:
I'm either informed that sending failed because the SIM had no signal,
or better, offered the option to rectify this by choosing a SIM for that
action.
Actual result:
The message disappears from the menu, the same as if it was successfully
sent, but it was not successfully sent (as it was not received on the
other end).
Note that if the 'For messages use' option is set to nothing, or 'Ask me
each time' then the user will be prompted to choose a SIM
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-messages 13.10.1+14.10.20140925-0ubuntu1 [origin: unknown]
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu3
Architecture: armhf
Date: Wed Oct 8 12:49:00 2014
InstallationDate: Installed on 2014-10-08 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141008-030204)
SourcePackage: indicator-messages
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: indicator-messages (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug armhf exploratory qa-daily-testing rtm14 third-party-packages utopic
** Tags added: exploratory qa-daily-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-messages in
Ubuntu.
https://bugs.launchpad.net/bugs/1378811
Title:
If a SIM slot with no signal is selected as the default SIM then
replying via the indicator fails silently
Status in “indicator-messages” package in Ubuntu:
New
Bug description:
Prerquisites:
The 'For messages use' option in System Settings Cellular panel should
be set to a slot that contains a SIM card with no signal
Steps to reproduce:
1. Send a message to the SUT (with the messaging-app closed)
2. Wait for the snap notification to disappear
3. Open the messaging indicator and press anywhere on the message (except on the message icon which will open the messaging app)
4. Enter your reply in the text field that appears (keeping in mind that there may be a bug that stops the Send button from being enabled if the keyboard is in the middle of autocorrecting a word)
5.) Hit the send button when it is enabled
Expected result:
I'm either informed that sending failed because the SIM had no signal,
or better, offered the option to rectify this by choosing a SIM for
that action.
Actual result:
The message disappears from the menu, the same as if it was
successfully sent, but it was not successfully sent (as it was not
received on the other end).
Note that if the 'For messages use' option is set to nothing, or 'Ask
me each time' then the user will be prompted to choose a SIM
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-messages 13.10.1+14.10.20140925-0ubuntu1 [origin: unknown]
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu3
Architecture: armhf
Date: Wed Oct 8 12:49:00 2014
InstallationDate: Installed on 2014-10-08 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141008-030204)
SourcePackage: indicator-messages
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378811/+subscriptions
Follow ups
References