[Touch-packages] [Bug 1614943] Re: No ringtone on incoming calls

2017-01-09 Thread Marek Greško
I believe this is the common problem with bug:

https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1612367

But I agree marking bug as critical is more appropriate. Maybe it would
be better to merge and raise the importance of the original bug to
Critical?

-- 
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/1614943

Title:
  No ringtone on incoming calls

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  current build number: 405
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Regularly on incoming calls, there is no ringtone or just a click.
  Apart from that, the notification is displayed, I can answer the call
  normally.

  Phone is not muted, sound is close to the max, and if I reboot it
  works again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614943/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-10-13 Thread Marek Greško
Not sure whether it is same bug, but today there was no ringing on
incoming call. Just only seen incoming call on a display. BQ E4.5 with
OTA13.

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in qtmultimedia-opensource-src package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1591174] Re: No sound notification after receiving a new message

2016-06-21 Thread Marek Greško
I never used headphones, music applications nor bluetooth and I
experience it also. It should not be related to the above.

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

Title:
  No sound notification after receiving a new message

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Unfortunately I can't give you any clues bit it happens in my bq4.5 for the 
second time. I sit next to my phone in silence und suddendly see that the green 
notification LED is blinking. I take the phone into my hand and see in a 
notification area a new sms message that came a few second ago without letting 
me know with a tone. I put the phone down and send another sms from another 
device. Again no sound notification after message arrival.
  This situation happens to me already for the second time. The first time 
rebboting helped. For the second time rebooted helped as well. What I was doing 
before was using uRadio but after rebbot i turned the radio on and off and 
everything worked fine. I was also using Music app with earphones. If it 
happens to me again I provide more information what could be the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1591174/+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 1452291] Re: Browser cannot use system proxy settings

2016-04-29 Thread Marek Greško
I would recommend not to have system-wide proxy settings, but proxy
setting for every connection. Since there could be different proxy
servers in different locations. Each WiFi AP should have his own proxy
settings saved. This also implies gui setup for proxy.

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

Title:
  Browser cannot use system proxy settings

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  While I can create successfully system proxy settings using

  gsettings set org.gnome.system.proxy use-same-proxy false
  gsettings set org.gnome.system.proxy mode "'manual'"
  gsettings set org.gnome.system.proxy ignore-hosts "['localhost',
  '127.0.0.0/8', '192.168.0.0/16', '::1']"
  gsettings set org.gnome.system.proxy.ftp host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.ftp port 800
  gsettings set org.gnome.system.proxy.socks host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.socks port 800
  gsettings set org.gnome.system.proxy.http host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.http port 800
  gsettings set org.gnome.system.proxy.http use-authentication false
  gsettings set org.gnome.system.proxy.http enabled true
  gsettings set org.gnome.system.proxy.https host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.https port 800

  those settings are currently not being used by the browser app.
  Accordingly I would like to request the addition of a feature to use the 
system proxy settings in the browser app.

  I have tested this on an by Aquaris E4.5 with Ubuntu 14.10 (r21).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452291/+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 1485803] Re: [system settings] No notification for which Sim card call is received from

2016-04-29 Thread Marek Greško
I agree this bug was partially solved by OTA-9. But only the part
concerning displaying SIM when call is received. The part concerning
different ringtones per SIM (or ideally per contact per SIM) was not
solved. Also the information I would expect to be seen in call log in
the first sight, not to click info button for this information. The
suggestion for colour differentiation was awesome, if it is not possible
to put the text information due to space reasons.

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

Title:
  [system settings] No notification for which Sim card call is received
  from

Status in Ubuntu UX:
  Triaged
Status in dialer-app package in Ubuntu:
  Incomplete

Bug description:
  When using the dual sim feature of the BQ Aquaris 4.5, there is no
  indication of which sim card a call is being received from. I.e., I
  run two businesses, and when my phone rings I have no idea which
  number someone is calling. Ideally there would be a different ringtone
  per sim card, as well as text notification on the answer call panel.
  There should also be the option of setting a different message tone
  for incoming messages per sim card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1485803/+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 1462090] Re: Calling to numbers formatted with slash results in Call failed

2015-07-21 Thread Marek Greško
I confirm the bug is fixed in OTA-5.

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

Title:
  Calling to numbers formatted with slash results in Call failed

Status in Canonical System Image:
  Fix Released
Status in One Hundred Papercuts:
  New
Status in telephony-service:
  New
Status in telepathy-ofono package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released

Bug description:
  When I call to numbers which are formatted with slash '/', I get call
  failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx
  xxx I get call failed, because numbers are automatically formatted as
  +421 2/xxx xxx xx or 02/xxx xxx xx.

  This is probably caused by incorrect regular expression in
  libtelephonyservice/phoneutils.cpp for nondialable digits removal,
  which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-].

  Please, consider this bug critical, since I cannot place any call to
  any fixed line in Slovakia, which is basic function of phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462090/+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 1453942] Re: Calling to some numbers results in Call failed

2015-07-21 Thread Marek Greško
The bug is concerning telephony-service. See https://bugs.launchpad.net
/canonical-devices-system-image/+bug/1462090. It is fixed in OTA-5.


** Changed in: dialer-app (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Calling to some numbers results in Call failed

Status in dialer-app package in Ubuntu:
  Fix Released

Bug description:
  When I try to call some numbers I cannot place the call and get Call
  failed message.

  After some investigation a think this is related to automatically adding the 
slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is 
formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which 
is in VPN and I should use 0 to call out or use international format, I get 
these results when calling the same station:
  When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the 
call is successfully placed.
  When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and 
the call is failing.

  You probably remove displayed spaces when placing a call but do not
  remove slash signs. The formatting slash cannot be manually deleted.

  I am using:
  Description: Ubuntu Utopic Unicorn (development branch)
  Release: 14.10

  dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1446054] Re: syncevolution and all day events synchronize from owncloud

2015-06-17 Thread Marek Greško
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  syncevolution and all day events synchronize from owncloud

Status in the base for Ubuntu mobile products:
  New
Status in Calendar application for Ubuntu devices:
  New
Status in qtorganizer5-eds package in Ubuntu:
  Confirmed

Bug description:
  Hi.

  I have noticed a problem with synchronization between Onwcloud (vCal)
  and calendar app.

  All day events always appear today and the next day.

  The problem seems to be with DTSTART et DTEND :

   before sync | after sync
 removed during sync 
  added during sync
  
---
  BEGIN:VCALENDAR  BEGIN:VCALENDAR  
 
  VERSION:2.0  VERSION:2.0  
 
BEGIN:VEVENT BEGIN:VEVENT   
 
SUMMARY:@@@ Rencontre (1997) @@@ SUMMARY:@@@ Rencontre (1997) @@@   
 
DTEND;VALUE=DATE:20150419|   DTEND;VALUE=DATE:20150420  
 
DTSTART;VALUE=DATE:20150419  DTSTART;VALUE=DATE:20150419
 
RRULE:BYMONTH=3;FREQ=YEARLY  
UID:20150420T051538Z-4109-32011-149  
UID:20150420T051538Z-4109-32011-149 
 9-11@ubuntu-phablet  9-11@ubuntu-phablet   
 
END:VEVENT   END:VEVENT 
 
  END:VCALENDAREND:VCALENDAR
 
  
---

  Any ideas ?

  Thank.

  My configuration :

  Nexus 4
  Ubuntu Touch 14.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1446054/+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 1462090] Re: Calling to numbers formatted with slash results in Call failed

2015-06-17 Thread Marek Greško
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

-- 
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/1462090

Title:
  Calling to numbers formatted with slash results in Call failed

Status in the base for Ubuntu mobile products:
  New
Status in One Hundred Papercuts:
  New
Status in Telephony Service:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  When I call to numbers which are formatted with slash '/', I get call
  failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx
  xxx I get call failed, because numbers are automatically formatted as
  +421 2/xxx xxx xx or 02/xxx xxx xx.

  This is probably caused by incorrect regular expression in
  libtelephonyservice/phoneutils.cpp for nondialable digits removal,
  which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-].

  Please, consider this bug critical, since I cannot place any call to
  any fixed line in Slovakia, which is basic function of phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462090/+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 1462090] Re: Calling to numbers formatted with slash results in Call failed

2015-06-04 Thread Marek Greško
** Also affects: telephony-service
   Importance: Undecided
   Status: New

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

-- 
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/1462090

Title:
  Calling to numbers formatted with slash results in Call failed

Status in One Hundred Papercuts:
  New
Status in Telephony Service:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  When I call to numbers which are formatted with slash '/', I get call
  failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx
  xxx I get call failed, because numbers are automatically formatted as
  +421 2/xxx xxx xx or 02/xxx xxx xx.

  This is probably caused by incorrect regular expression in
  libtelephonyservice/phoneutils.cpp for nondialable digits removal,
  which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-].

  Please, consider this bug critical, since I cannot place any call to
  any fixed line in Slovakia, which is basic function of phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1462090/+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 1462090] [NEW] Calling to numbers formatted with slash results in Call failed

2015-06-04 Thread Marek Greško
Public bug reported:

When I call to numbers which are formatted with slash '/', I get call
failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx
xxx I get call failed, because numbers are automatically formatted as
+421 2/xxx xxx xx or 02/xxx xxx xx.

This is probably caused by incorrect regular expression in
libtelephonyservice/phoneutils.cpp for nondialable digits removal, which
reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-].

Please, consider this bug critical, since I cannot place any call to any
fixed line in Slovakia, which is basic function of phone.

** Affects: telephony-service
 Importance: Undecided
 Status: New

** Affects: telephony-service (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1462090

Title:
  Calling to numbers formatted with slash results in Call failed

Status in Telephony Service:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  When I call to numbers which are formatted with slash '/', I get call
  failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx
  xxx I get call failed, because numbers are automatically formatted as
  +421 2/xxx xxx xx or 02/xxx xxx xx.

  This is probably caused by incorrect regular expression in
  libtelephonyservice/phoneutils.cpp for nondialable digits removal,
  which reads [p+*#(),;-]. I am pretty sure it should read [p+*#/(),;-].

  Please, consider this bug critical, since I cannot place any call to
  any fixed line in Slovakia, which is basic function of phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1462090/+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 1453942] Re: Calling to some numbers results in Call failed

2015-06-04 Thread Marek Greško
This is probably on telephony-service to handle the slash character,
since I found regexp [p+*#(),;-] in libtelephonyservice/phoneutils.cpp
for nondialable digits removal, which should probably read [p+*#/(),;-].
I am going to file a bug against telephony-service.

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

Title:
  Calling to some numbers results in Call failed

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  When I try to call some numbers I cannot place the call and get Call
  failed message.

  After some investigation a think this is related to automatically adding the 
slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is 
formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which 
is in VPN and I should use 0 to call out or use international format, I get 
these results when calling the same station:
  When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the 
call is successfully placed.
  When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and 
the call is failing.

  You probably remove displayed spaces when placing a call but do not
  remove slash signs. The formatting slash cannot be manually deleted.

  I am using:
  Description: Ubuntu Utopic Unicorn (development branch)
  Release: 14.10

  dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1453942] Re: Calling to some numbers results in Call failed

2015-06-01 Thread Marek Greško
Could someone assign the Critical importance to this bug? It is basic
functionality to place a calls. If I did not have a SIM card in VPN and
use the hack above I would not be able place calls to Slovak fixed line
numbers. Not everybody has such SIM. It is 100% reproducible and
probably caused by pretty print telephone number function. I would not
mind of disallowing this function, since it is not needed and does not
follow standard either.

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

Title:
  Calling to some numbers results in Call failed

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  When I try to call some numbers I cannot place the call and get Call
  failed message.

  After some investigation a think this is related to automatically adding the 
slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is 
formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which 
is in VPN and I should use 0 to call out or use international format, I get 
these results when calling the same station:
  When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the 
call is successfully placed.
  When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and 
the call is failing.

  You probably remove displayed spaces when placing a call but do not
  remove slash signs. The formatting slash cannot be manually deleted.

  I am using:
  Description: Ubuntu Utopic Unicorn (development branch)
  Release: 14.10

  dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1453942] Re: Calling to some numbers results in Call failed

2015-05-18 Thread Marek Greško
** Changed in: dialer-app (Ubuntu)
   Status: New = Confirmed

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

Title:
  Calling to some numbers results in Call failed

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  When I try to call some numbers I cannot place the call and get Call
  failed message.

  After some investigation a think this is related to automatically adding the 
slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is 
formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which 
is in VPN and I should use 0 to call out or use international format, I get 
these results when calling the same station:
  When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the 
call is successfully placed.
  When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and 
the call is failing.

  You probably remove displayed spaces when placing a call but do not
  remove slash signs. The formatting slash cannot be manually deleted.

  I am using:
  Description: Ubuntu Utopic Unicorn (development branch)
  Release: 14.10

  dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1453506] Re: cannot pick incoming call

2015-05-18 Thread Marek Greško
** Changed in: dialer-app (Ubuntu)
   Status: New = Confirmed

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

Title:
  cannot pick incoming call

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  aquaris bq phone. from suspend / lockscreen i am unable to select
  incoming call. no visual inteface appears, even if going to phone-app
  manually while phone rings. please fix soon. this is a basic phone
  function! thank you...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453506/+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 1453942] [NEW] Calling to some numbers results in Call failed

2015-05-11 Thread Marek Greško
Public bug reported:

When I try to call some numbers I cannot place the call and get Call
failed message.

After some investigation a think this is related to automatically adding the 
slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is 
formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which 
is in VPN and I should use 0 to call out or use international format, I get 
these results when calling the same station:
When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the 
call is successfully placed.
When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and 
the call is failing.

You probably remove displayed spaces when placing a call but do not
remove slash signs. The formatting slash cannot be manually deleted.

I am using:
Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10

dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Calling to some numbers results in Call failed

Status in dialer-app package in Ubuntu:
  New

Bug description:
  When I try to call some numbers I cannot place the call and get Call
  failed message.

  After some investigation a think this is related to automatically adding the 
slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is 
formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which 
is in VPN and I should use 0 to call out or use international format, I get 
these results when calling the same station:
  When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the 
call is successfully placed.
  When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and 
the call is failing.

  You probably remove displayed spaces when placing a call but do not
  remove slash signs. The formatting slash cannot be manually deleted.

  I am using:
  Description: Ubuntu Utopic Unicorn (development branch)
  Release: 14.10

  dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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 1453506] Re: cannot pick incoming call

2015-05-11 Thread Marek Greško
I am also affected.

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

Title:
  cannot pick incoming call

Status in dialer-app package in Ubuntu:
  New

Bug description:
  aquaris bq phone. from suspend / lockscreen i am unable to select
  incoming call. no visual inteface appears, even if going to phone-app
  manually while phone rings. please fix soon. this is a basic phone
  function! thank you...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453506/+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 1453942] Re: Calling to some numbers results in Call failed

2015-05-11 Thread Marek Greško
Moreover the dialed number is not added to the recent call list.

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

Title:
  Calling to some numbers results in Call failed

Status in dialer-app package in Ubuntu:
  New

Bug description:
  When I try to call some numbers I cannot place the call and get Call
  failed message.

  After some investigation a think this is related to automatically adding the 
slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is 
formatted 02/xxx xxx xx and the call is not placed. When I use second SIM which 
is in VPN and I should use 0 to call out or use international format, I get 
these results when calling the same station:
  When calling 0 02 xxx xx xxx, the number is formatted 00 2xx xx xxx x and the 
call is successfully placed.
  When calling +421 2 xxx xx xxx, the number is formatted +421 2/xxx xxx xx and 
the call is failing.

  You probably remove displayed spaces when placing a call but do not
  remove slash signs. The formatting slash cannot be manually deleted.

  I am using:
  Description: Ubuntu Utopic Unicorn (development branch)
  Release: 14.10

  dialer-app: 0.1+15.04.20150216-rtm-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1453942/+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