Create Task
Maniphest T13417

Failed synchronizaton with server?
Open, NormalPublic
Actions

Description

I seem to be able to set up the app correctly but get these errors when synchronizing for the first time. I'm unsure if it's a bug or user error. All of the server info is correct.
Maybe related to T11193 ?

Log:     {e6256f90-c44d-4653-a7bc-e54318f9a7fe}.mailtransportresource : Looking for mails to send. 
Log:     {e6256f90-c44d-4653-a7bc-e54318f9a7fe}.mailtransportresource : Found  0  mails to send 
Log:     {e6256f90-c44d-4653-a7bc-e54318f9a7fe}.synchronizer          : Done Synchronizing 
Log:     {e6256f90-c44d-4653-a7bc-e54318f9a7fe}.synchronizer          : All requests processed. 
Log:     {df1482ff-f54f-4afa-b607-8f6af746611f}.org.kde.pim.kimap2 : "Socket connected." 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.org.kde.pim.kimap2 : "Aborting on socket timeout.  40000" 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.org.kde.pim.kimap2 : "Current job:  KIMAP2::LoginJob" 
Log:     {df1482ff-f54f-4afa-b607-8f6af746611f}.org.kde.pim.kimap2 : "Socket disconnected." 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.org.kde.pim.kimap2 : "Connection to server lost  QAbstractSocket::UnknownSocketError" 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.imapserverproxy    : Job failed:  "Connection to server lost." KIMAP2::LoginJob 103 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.synchronizer       : Synchronization failed:  Error:  3 Msg:  "Connection to server lost." 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.synchronizer       : Error during sync:  Error:  3 Msg:  "Connection to server lost." 
......
..........
Warning: {789b4610-9bca-4a78-a5c6-a913efbe37dc}.synchronizer : Synchronization failed:  Error:  5 Msg:  "Invalid server url: " 
Log:     {e6256f90-c44d-4653-a7bc-e54318f9a7fe}.synchronizer          : Done Synchronizing 
Warning: {789b4610-9bca-4a78-a5c6-a913efbe37dc}.synchronizer : Error during sync:  Error:  5 Msg:  "Invalid server url: " 
Log:     {e6256f90-c44d-4653-a7bc-e54318f9a7fe}.synchronizer          : All requests processed. 
Log:     {789b4610-9bca-4a78-a5c6-a913efbe37dc}.synchronizer : All requests processed. 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.org.kde.pim.kimap2 : "Aborting on socket timeout.  40000" 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.org.kde.pim.kimap2 : "Current job:  KIMAP2::LoginJob" 
Log:     {df1482ff-f54f-4afa-b607-8f6af746611f}.org.kde.pim.kimap2 : "Socket disconnected." 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.org.kde.pim.kimap2 : "Connection to server lost  QAbstractSocket::UnknownSocketError" 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.imapserverproxy    : Job failed:  "Connection to server lost." KIMAP2::LoginJob 103 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.synchronizer       : Synchronization failed:  Error:  3 Msg:  "Connection to server lost." 
Warning: {df1482ff-f54f-4afa-b607-8f6af746611f}.synchronizer       : Error during sync:  Error:  3 Msg:  "Connection to server lost." 
Log:     {df1482ff-f54f-4afa-b607-8f6af746611f}.synchronizer       : All requests processed.

EDIT: Oh! Port number on the end of server is necessary?

Appended port numbers and tried again. ( imaps://............................:993 & smtps://...................................:465 ) but same error.

Related Objects

bushranger updated the task description. (Show Details)Jul 19 2020, 5:23 AM
bushranger updated the task description. (Show Details)Jul 19 2020, 5:34 AM
bushranger updated the task description. (Show Details)Jul 19 2020, 5:36 AM
bushranger updated the task description. (Show Details)Jul 19 2020, 5:41 AM
bushranger updated the task description. (Show Details)Jul 20 2020, 2:49 PM
cmollekopf added a subscriber: cmollekopf.Aug 6 2020, 11:42 AM

This looks like the resource has no server url whatsoever configured... Are you running the flatpak?

cmollekopf moved this task from New to Triaged on the Kube: Bugs board.Aug 6 2020, 11:42 AM
cmollekopf triaged this task as Normal priority.
bushranger added a comment.Aug 7 2020, 9:04 AM

Yes, I'm running the flatpak.

cmollekopf added a comment.Aug 8 2020, 11:36 AM

With the latest flatpak you can run a connection test like so

$ flatpak run --command=/bin/bash com.kubeproject.kube                                                                                                                                                                     
$ sinksh list resource                                                                                                                                                                                                                    
Resource | Identifier                           | account                              | server                        | type                                                                                                                                  
...                                                                                                                
         | d361c6b8-a9a4-4960-80f1-4cbcc426ce16 | ca497089-5d18-492d-bab8-0949dc6475df | imaps://imap.kolabsys.com:993 | sink.imap                                                                                                                             
...                                                                                                          
$ sinksh connectiontest d361c6b8-a9a4-4960-80f1-4cbcc426ce16 --password mysecret

And you can list your configuration like so

$ sinksh list resource --id d361c6b8-a9a4-4960-80f1-4cbcc426ce16  --showall

Resource:    |                                                                                     
Identifier:  | d361c6b8-a9a4-4960-80f1-4cbcc426ce16                                                
account      | ca497089-5d18-492d-bab8-0949dc6475df                                                
capabilities | mail, folder, mail.storage, mail.drafts, mail.folderhierarchy, mail.trash, mail.sent
server       | imaps://imap.kolabsys.com:993                                                       
status       | 0                                                                                   
type         | sink.imap                                                                           
username     | mollekopf@kolabsystems.com

This might give use some more info on what is going on.

bushranger added a comment.EditedAug 9 2020, 9:22 AM

Thank you.
Does this help at all?

[.....]$ flatpak run --command=/bin/sh com.kubeproject.kube
(flatpak run:27609): dconf-WARNING **: 18:12:50.818: Unable to open /root/.local/share/flatpak/exports/share/dconf/profile/user: Permission denied
ERROR: ld.so: object '/usr/lib64/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

[.....]# flatpak run --command=/bin/sh com.kubeproject.kube
error: app/com.kubeproject.kube/x86_64/master not installed

$ flatpak list
Name Application ID Version Branch Origin Installation
Kube com.kubeproject.kube master kube-origin user

cmollekopf added a comment.Aug 9 2020, 11:35 AM

This looks like something on your system is broken and you can't launch the shell in the flatpak at all. You should definitely be running the command as user (it's not installed as root),
but it looks like that LD_PRELOAD error is fatal, and a quick google search pointed me to some ubuntu related issues (I didn't find anything directly related to flatpak though).

Maybe some pointers here can help: https://stackoverflow.com/questions/53825857/error-ld-so-object-libgtk3-nocsd-so-0-from-ld-preload-cannot-be-preloaded