On one of my PCs (Debian) the Syncevolution GUI has become corrupted. The command line does work, though it prompts me for a password, which I find odd. I'm trying to attach screenshots but I'm not sure they'll reach the list, so let me describe the symptoms: - the left pane of the GUI is blank, with event the icon missing; - if I try "sync" or "change and modify...", I get a message box saying "cannot retrieve the list of services supported by Syncevolution" (do my best to translate from French);

- if I try "repair emergency...", I'm offered to replace data from "Zyb" (What's that? Should be Memotoo!)

Now on this PC, I recently "cherry-picked" the latest LibreOffice (from Sid), which triggered a bunch of updates. Could that be the explanation?

Le jeudi 07 mai 2015 à 10:47 +0200, Patrick Ohly a écrit : > On Thu, 2015-05-07 at 10:39 +0200, Daniel CLEMENT wrote: > > On one of my PCs (Debian) the Syncevolution GUI has become corrupted. > > The command line does work, though it prompts me for a password, which I > > find odd. > > > > I'm trying to attach screenshots but I'm not sure they'll reach the > > list, so let me describe the symptoms: > > - the left pane of the GUI is blank, with event the icon missing; > > - if I try "sync" or "change and modify...", I get a message box saying > > "cannot retrieve the list of services supported by Syncevolution" (do my > > best to translate from French); > > Sounds like syncevo-dbus-server is not running or having problems. Can > you kill it and then run it manually in a shell with > "/usr/libexec/syncevo-dbus-server --verbosity=3 -d unlimited --stdout > --no-syslog" before starting the UI? I'm getting this: daniel@e6330d ~ $ /usr/libexec/syncevo-dbus-server --verbosity=3 -d unlimited --stdout --no-syslog [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: (re)activating, currently inactive [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: activating signal handler(s) with fds 13->12 [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: catch signal 2 [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: catch signal 15 syncevo-dbus-server is not running afterwards.

Le jeudi 07 mai 2015 à 12:21 +0200, Patrick Ohly a écrit : > On Thu, 2015-05-07 at 11:09 +0200, Daniel CLEMENT wrote: > > Le jeudi 07 mai 2015 à 10:47 +0200, Patrick Ohly a écrit : > > > On Thu, 2015-05-07 at 10:39 +0200, Daniel CLEMENT wrote: > > > > On one of my PCs (Debian) the Syncevolution GUI has become corrupted. > > > > The command line does work, though it prompts me for a password, which I > > > > find odd. > > > > > > > > I'm trying to attach screenshots but I'm not sure they'll reach the > > > > list, so let me describe the symptoms: > > > > - the left pane of the GUI is blank, with event the icon missing; > > > > - if I try "sync" or "change and modify...", I get a message box saying > > > > "cannot retrieve the list of services supported by Syncevolution" (do my > > > > best to translate from French); > > > > > > Sounds like syncevo-dbus-server is not running or having problems. Can > > > you kill it and then run it manually in a shell with > > > "/usr/libexec/syncevo-dbus-server --verbosity=3 -d unlimited --stdout > > > --no-syslog" before starting the UI? > > > > I'm getting this: > > daniel@e6330d ~ $ /usr/libexec/syncevo-dbus-server --verbosity=3 -d > > unlimited --stdout --no-syslog > > [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: (re)activating, > > currently inactive > > [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: activating signal > > handler(s) with fds 13->12 > > [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: catch signal 2 > > [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: catch signal 15 > > > > syncevo-dbus-server is not running afterwards. > > You mean it quits immediately? It should continue running, unless there > was already a running instance. But you should get a message about that. > I've got the impression that it fails to start. I've kept an eye on the system monitor while issuing the above command line, I didn't see syncevo-dbus-server appear, even briefly.

Le jeudi 07 mai 2015 à 14:16 +0200, Patrick Ohly a écrit : > On Thu, 2015-05-07 at 13:23 +0200, Daniel CLEMENT wrote: > > Le jeudi 07 mai 2015 à 12:21 +0200, Patrick Ohly a écrit : > > > On Thu, 2015-05-07 at 11:09 +0200, Daniel CLEMENT wrote: > > > > Le jeudi 07 mai 2015 à 10:47 +0200, Patrick Ohly a écrit : > > > > > On Thu, 2015-05-07 at 10:39 +0200, Daniel CLEMENT wrote: > > > > > > On one of my PCs (Debian) the Syncevolution GUI has become corrupted. > > > > > > The command line does work, though it prompts me for a password, which I > > > > > > find odd. > > > > > > > > > > > > I'm trying to attach screenshots but I'm not sure they'll reach the > > > > > > list, so let me describe the symptoms: > > > > > > - the left pane of the GUI is blank, with event the icon missing; > > > > > > - if I try "sync" or "change and modify...", I get a message box saying > > > > > > "cannot retrieve the list of services supported by Syncevolution" (do my > > > > > > best to translate from French); > > > > > > > > > > Sounds like syncevo-dbus-server is not running or having problems. Can > > > > > you kill it and then run it manually in a shell with > > > > > "/usr/libexec/syncevo-dbus-server --verbosity=3 -d unlimited --stdout > > > > > --no-syslog" before starting the UI? > > > > > > > > I'm getting this: > > > > daniel@e6330d ~ $ /usr/libexec/syncevo-dbus-server --verbosity=3 -d > > > > unlimited --stdout --no-syslog > > > > [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: (re)activating, > > > > currently inactive > > > > [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: activating signal > > > > handler(s) with fds 13->12 > > > > [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: catch signal 2 > > > > [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: catch signal 15 > > > > > > > > syncevo-dbus-server is not running afterwards. > > > > > > You mean it quits immediately? It should continue running, unless there > > > was already a running instance. But you should get a message about that. > > > > > I've got the impression that it fails to start. I've kept an eye on the > > system monitor while issuing the above command line, I didn't see > > syncevo-dbus-server appear, even briefly. > > Please run under gdb to see where it fails: > > gdb --args /usr/libexec/syncevo-dbus-server --verbosity=3 -d unlimited --stdout --no-syslog > I assume: gdb -ex=r [...] if the program is to start directly? Here is what I get: daniel@e6330d ~ $ gdb -ex=r --args /usr/libexec/syncevo-dbus-server --verbosity=3 -d unlimited --stdout --no-syslog GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>;... Reading symbols from /usr/libexec/syncevo-dbus-server...done. Starting program: /usr/libexec/syncevo-dbus-server --verbosity=3 -d unlimited --stdout --no-syslog warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: (re)activating, currently inactive [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: activating signal handler(s) with fds 17->16 [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: catch signal 2 [DEBUG syncevo-dbus-server 00:00:00] SuspendFlags: catch signal 15 [New Thread 0x7fffecf8c700 (LWP 4353)] [Thread 0x7fffecf8c700 (LWP 4353) exited] [Inferior 1 (process 4348) exited with code 0177] (I believe the "linux-vdso.so.1" error pertains only to gdb, not the program being debugged.)

I really wonder if all this trouble was caused by my upgrading libreOffice. Everything worked flawlessly before and I can't see any other noticeable change on this system.