You are not logged in.

#1 2013-12-07 16:00:18

eigengrau
Member
Registered: 2013-09-19
Posts: 43

guake bash instances zombify upon exit

As of late, when I exit bash instances that are inside guake, the corresponding guake tab fails to close. An inspection of the process tree reveals that the original bash process remains lingering around in a zombified state.

The logs show a curious Python permissions exception.

Dez 07 14:34:27 wirrsal gnome-session[593]: Traceback (most recent call last):
Dez 07 14:34:27 wirrsal gnome-session[593]: File "/usr/bin/guake", line 917, in accel_add
Dez 07 14:34:27 wirrsal gnome-session[593]: self.add_tab()
Dez 07 14:34:27 wirrsal gnome-session[593]: File "/usr/bin/guake", line 1222, in add_tab
Dez 07 14:34:27 wirrsal gnome-session[593]: final_params = self.get_fork_params(default_params)
Dez 07 14:34:27 wirrsal gnome-session[593]: File "/usr/bin/guake", line 1150, in get_fork_params
Dez 07 14:34:27 wirrsal gnome-session[593]: params['directory'] = self.get_current_dir()
Dez 07 14:34:27 wirrsal gnome-session[593]: File "/usr/bin/guake", line 1125, in get_current_dir
Dez 07 14:34:27 wirrsal gnome-session[593]: cwd = os.readlink("/proc/%d/cwd" % self.pid_list[active_pagepos])
Dez 07 14:34:27 wirrsal gnome-session[593]: OSError: [Errno 13] Permission denied: '/proc/16266/cwd'

PID 16266 is the zombified bash instance. /proc/16266/cwd appears as a target-less symlink

Did anyone else notice these glitches? My guake hasn't been updated in ages. I vaguely recall the stock kernel saw some changes regarding process inspection capabilities. But even if this would affect the cwd, guake is a parent of the bash instance and should be able to read that file.

Is the project dead btw? The official guake site seems to be out of comission.

Last edited by eigengrau (2013-12-13 09:19:01)

Offline

#2 2013-12-09 16:44:39

eigengrau
Member
Registered: 2013-09-19
Posts: 43

Re: guake bash instances zombify upon exit

Weirdly, this comes up only when guake is autolaunched via the Gnome shell, and it never happens on my non-Nvidia rig. When I start guake from a terminal, the bug never triggers. This parallels the behavior described in https://bbs.archlinux.org/viewtopic.php?pid=1358498 for Mono-based applications, which only launch properly when started from the terminal, and which seems to concern only Nvidia-based machines.

Offline

#3 2013-12-09 17:58:06

eigengrau
Member
Registered: 2013-09-19
Posts: 43

Re: guake bash instances zombify upon exit

This seems to be resolved for me. It turned out to be due to the "maximus" window extension which undecorates full-screen windows.

Offline

#4 2013-12-13 09:20:33

eigengrau
Member
Registered: 2013-09-19
Posts: 43

Re: guake bash instances zombify upon exit

Turning Maximus off did get rid of some zombie processes, but the guake error intermittendly reappears.

This might be related to https://bbs.archlinux.org/viewtopic.php?pid=1354509 , where the same phenomenon is observed in the KDE Konsole, and the problem attributed to the Nvidia blob.

Offline

#5 2013-12-13 09:26:24

eigengrau
Member
Registered: 2013-09-19
Posts: 43

Re: guake bash instances zombify upon exit

Offline

Board footer

Powered by FluxBB