nevfel / qgvdial

Automatically exported from code.google.com/p/qgvdial
GNU Lesser General Public License v2.1
0 stars 0 forks source link

issue between qgvdial and caldav #23

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. install qgvdial_0.3.894_armel.deb
2. create CalDav to google apps calendar
3. login to calendar service fails

What is the expected output? What do you see instead?
CalDav works flawlessly after uninstall of qgvdial

What version of the product are you using? On what operating system?
Harmattan 1.2 latest

Please provide any additional information below.
Love the project please make it work!

Original issue reported on code.google.com by ebloem...@imoinvest.net on 4 Mar 2012 at 1:25

GoogleCodeExporter commented 8 years ago
qgvdial should not have ANY effect on any other service. qgvdial doesn't use or 
touch/modify any settings in the rest of the system.
It cannot afford to because it is mostly agnostic of the OS it runs on.

This is extremely strange.

Original comment by yuvr...@gmail.com on 6 Mar 2012 at 4:39

GoogleCodeExporter commented 8 years ago
Possibility:
- It tries to login to Google service under one account and whilst it does
not succeed it does not allow simultaneous login with a google apps account
on e.g. CalDav.

egbert bloemsma
www.imoinvest.com.br
m: +55 (71) 86224916

Original comment by ebloem...@imoinvest.net on 6 Mar 2012 at 5:23

GoogleCodeExporter commented 8 years ago
Even whether you're using the same or different accounts for caldav and 
qgvdial, one app shouldn't interfere with the other.
qgvdial doesn't use a shared cookies model or even the system browser.

Original comment by yuvr...@gmail.com on 7 Mar 2012 at 3:37

GoogleCodeExporter commented 8 years ago
Fantastic! Problems disappeared since version 917. I am now logging in. Still 
some issues though.... will open a new issue later

Original comment by ebloem...@imoinvest.net on 7 Mar 2012 at 8:49

GoogleCodeExporter commented 8 years ago
Not sure what was the problem, but it looks like its been fixed...

Original comment by yuvr...@gmail.com on 14 Mar 2012 at 1:00