On Thu, 2020-04-30 at 09:32 +0200, Milan Crha via evolution-list wrote: On Wed, 2020-04-29 at 15:52 -0500, Anonymous Japhering viaevolution-list wrote:I built the current version stable version yesterday ( json fileattached if that helps ).However, today any time I see this message(evolution-addressbook-factory:25): GLib-GIO-WARNING **:15:28:02.223: Error calling GetManagedObjects() when name owner :1.74for name org.gnome.Evolution.org.gnome.evolution.dataserver.Sources5came back: Timeout was reachedHi,I see from the attached json that you use the 3.36 runtime, which isgood. Did you update it recently? I know of a problem in libsecret [1],which causes the evolution-source-registry to crash when readingpasswords from the service. The above D-Bus name is for theevolution-source-registry. I guess it's either stuck or it crashed forsome reason. You can check what your Platform uses with:$ flatpak run org.gnome.Platform//3.36(flatpak) $ cat /usr/manifest.json | grep libsecreYou may want to see there libsecret-0.20.3.tar.xz there. yes, I see that .. appear in the window where I started evolution, it hangs and hangshard.Right, it's waiting for a response from the source registry.pgrep -l evolution showsBetter use:ps ax | grep evolutionit shows also paths. Anything from /app/ comes from the Flatpak world(unless you compile into that prefix yourself). /app/libexec/evolution-source-registry /app/libexec/evolution-addressbook-factory -r /app/libexec/evolution-calendar-factory -r /app/libexec/evolution-data-server/evolution-alarm-notify /bin/sh /app/bin/evolution /app/bin/evolution.bin I would try to run evolution from a terminal. It can show someinformation there. The command is:$ flatpak run org.gnome.Evolution Precisely. I have a shell alias that runs said command. I can kill everything but the evolution.bin process.You should be able to kill it with:$ kill -9 PIDthat's a very powerful toy. I'm fully aware of kill -9. but by the time I'm trying to run it, the evolution.bin process, the parent process is init and repeated kill -9s have no effect. The only thing that kills the process is a reboot. I notice this most when trying to send an email with an attachment,I vaguely recall a bug about something similar in the Flatpak. I do notrecall any details, I'm sorry, but I'm afraid it's problem of theportal.There are ways to install debuginfo data for Flatpak applications andrun them with development tools. It's something like this:$ flatpak install flathub org.gnome.Evolution.Debug(replace 'flathub' with the repository you install evolution from). Done and ready for debug the next time things hang. $ flatpak run --devel --command=sh org.gnome.Evolution(flatpak) $ gdb /app/libexec/evolution-source-registry --ex rwhen it'll look like it's not doing anything, just break it with Ctrl+Cand then execute:(gdb) t a a bt(gdb) q(flatpak) $ exitThe backtrace will show what it does. In case it'll crash (you'd notneed to break it with Ctrl+C), you can just get the backtrace of thecrash. The 'q' command quits the gdb, possibly asking you to kill therunning process (the evolution-source-registry). You can use 'c' forcontinue, if you'd like to give it more time.Please check the backtrace for any private information, like passwords,email address, server addresses,... I usually search for "pass" atleast (quotes for clarity only), before sharing it anywhere.Bye,Milan[1]https://gitlab.gnome.org/GNOME/libsecret/-/merge_requests/52_______________________________________________evolution-list mailing listevolution-list gnome orgTo change your list options or unsubscribe, visit ...https://mail.gnome.org/mailman/listinfo/evolution-list |