Version: (using Devel) Installed from: Compiled sources The kde egroupware integration works very well, but there is one nagging bug. The problem is session timeout and no ability to re-authorize without completely shutting down the kde app (kontact, kmail, etc..) What appears to be happening when you leave kmail or kontact up for an hour or so (I guess beyond the session timeout) is that the next time you try and add or update a contact or calendar entry, you are then presented with the normal kde Auth dialog, but the user name shown is something like: Username: lbhaljadsgn;iohvgnklsejfnbsdkflsdk Password: Instead of the original Username/Password used to define the groupware connection, like: Username: Joe Password: If you enter the password that you defined in the "groupware connection" wizard, authentication fails. If you change the Username to the username that you defined in the "groupware connection" wizard, authentication still fails. At this point, you have no choice but to kill and restart the app which I guess starts a new session. There should be a way to fix the Auth dialog that you are presented with in kmail, etc. so that it prompts for the correct username and password allowing you to reestablish the connection/session without having to completely restart the application. Let me know if you need any additional information. Thanks.
Here is a screenshot of the auth dialog presented after session timeout. http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/groupware-auth.jpeg
Any progress here? Anything else I can send you? The egroupware server has a 2 hour session limit, so when you have your computer running more than 2 hours (like 99% of all users) kde4 can't handle the session timeout and restart of another session so all apps that rely on the kdeGroupware wizard settings: kmail, addressbook, kontact, korganizers all go on the fritz when they can no longer read or write information to the egroupware server. Then something as simple as right-clicking an email address to add to the local addressbook is broken because the Add Address dialog times out because it doesn't have a current session with the groupware server. eGroupware integration is fantastic, all we need to do is get this session issue fixed. Thanks.
Created attachment 35526 [details] screenshot showing kmail stuck in authentication loop preventing address entry A further consequence of this bug is that once a session timeout has occurred, you are prevented from adding any email addresses to the addressbook (even the default addressbook) because kmail's authentication system goes into a loop trying to reattach to the server using incorrect credentials (apparently some kind of session name) which fails prompting repeated error and preventing adding any addresses. Even if you enter the correct user/pass, kmail's auth fails. You should be able to add addresses in the default address book (local address book) regardless of the state of the connection to the groupware address book. The groupware integration feature is a FANTASTIC feature and one of the primary reasons I committed to use kmail in kde4. Once we get some of these bugs ironed out, kmail will be the mailer of choice compared to thunderbird, etc. I have attached a screenshot of this behavior
Created attachment 36568 [details] Unknown XML markup Error when accessing kaddressbook - (xmlrpc related??) Devs, There have evidently been some changes made in the code to address the groupware integration timeouts as of Version 4.3.00 (KDE 4.3.0) "release 158". Now you get error messages, but you can ultimately get to the default addressbook if the session times out - after closing the error dialogs. The error is: "Server sent error 1: Unknown type of XML markup received" It isn't simply a single error though, because you get "3" error dialogs stacked up on top of each other. (See subsequent attachment). The errors are received immediately upon opening kaddressbook. After clicking to close 3 times, then editing of the address book is normal. Let me know if I can send anything else. Thanks.
Created attachment 36569 [details] Screenshot showing the "3" error dialogs received at kaddressbook start As mentioned when posting attachment 36568 [details], you get 3 error dialogs on kaddressbook start (see screenshot). You can then use kaddressbook as normal. But, then again, when you close kaddressbook you get the same error "once" more. (pretty cool screenshot -- eh?)
The current recommendation from EGroupware is to use GroupDAV. It's the only actively developed access method to EGroupware supported by KDE! Ralf
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!