Hanging processes

Anonymous Japhering japhering at gmail.com
Wed Nov 25 15:50:17 UTC 2020


On Mon, 2020-11-23 at 09:40 +0100, Alexander Larsson wrote:
> On Sat, 2020-11-21 at 14:33 -0600, Anonymous Japhering wrote:
> > Flatpak v 1.9.2Linux 5.4.0-54-generic #60~18.04.1-Ubuntu SMP
> > DISTRIB_ID=LinuxMint
> > DISTRIB_RELEASE=19.3
> > DISTRIB_CODENAME=tricia
> > DISTRIB_DESCRIPTION="Linux Mint 19.3 Tricia"
> > 
> > Building and running the latest flatpak version of Evolution.
> > 
> > I'm seeing issues where various bits and pieces either die or a
> > communication event
> > fails which leaves Evolution in a none functioning state.
> > 
> > At this point,  first attempt is to  try to get Evolution to exit
> > normally ( File->exit ) after which
> > flatpak ps  which usually shows 1-N  copies of  org.gnome.Evolution.
> 
> This all seems to somehow indicate some issue with dbus. Thats whats
> used to communicate, in particular for the "one instance" part.

Definitely  some dbus issues as indicated by my lack of ability to attach
documents to emails.

   (evolution.bin:54): Gtk-WARNING **: 09:09:48.433: no trigger event for menu
   popup
   
   ** (evolution.bin:54): WARNING **: 16:26:14.649: Couldn't connect to D-Bus
   system bus, Could not connect: No such file or directory
   
   (evolution.bin:54): Gtk-WARNING **: 16:54:55.156: no trigger event for menu
   popup
   
   ** (evolution.bin:54): WARNING **: 09:03:27.069: Couldn't connect to D-Bus
   system bus, Could not connect: No such file or directory

> 
> > Followed by  flatpak kill org.gnome.Evolution,  which frequently
> > causes my problem.. a slew
> > of  flatpak-bwrap and flatpak-spawn processes which prevent the next
> > flatpak run org.gnome.Evolution from running.
> > 
> > kill and kill -9  have no effect on the processes, thus a reboot is
> > required to once again be able to start Evolution.
> 
> However, this is just weird. Kill should always work, there is nothing
> flatpak can do to make it not. Can you get some kind of pstree output
> from when this is happening?

Kill, in all it variants, never works for processes in a defunct (zombie) 
state.

   mhm        954  5824  0 Nov23 pts/4    00:00:00 [flatpak-spawn] <defunct>
   mhm       9960  5824  0 Nov23 pts/4    00:00:00 [flatpak-spawn] <defunct>
   mhm      11025  5824  0 Nov23 pts/4    00:00:00 [flatpak-spawn] <defunct>
   mhm      14174  5824  0 Nov24 pts/4    00:00:00 [flatpak-spawn] <defunct>
   mhm      17291  5824  0 Nov23 pts/4    00:00:00 [flatpak-spawn] <defunct>
   mhm      17630  5824  0 Nov23 pts/4    00:00:00 [flatpak-spawn] <defunct>
   mhm      23662  5824  0 09:07 pts/4    00:00:00 [flatpak-spawn] <defunct>
   mhm      32766  5824  0 Nov24 pts/4    00:00:00 [flatpak-spawn] <defunct>
   
current list of zombie flatpak processes since the last reboot




More information about the Flatpak mailing list