Package: terminator
Version: 1.91-1
Severity: important

Dear Maintainer,

first off - thank you for your time and effort in maintatining this package!


* What led up to the situation?

        Trying to open an additional terminator window. This usually happens 
around the 4th window opened... typically after a resume from suspend but also 
without suspend&resume.  

* What exactly did you do (or not do) that was effective (or
     ineffective)?

        Using my xfce4-keyboard shortcut for "terminator"

* What was the outcome of this action?

        No new window, all existing terminator windows become unreactive. 
Breaks my suspend&resume lifestyle. 


Output when I try to start from another term-emulator; at least some lines have 
similarities with #706856. 


        USER@MACHINE:~$ terminator 
        ERROR:dbus.proxies:Introspect error on :1.370:/net/tenshu/Terminator2: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.
        Traceback (most recent call last):
          File "/usr/bin/terminator", line 107, in <module>
            ipc.new_window_cmdline(optionslist)
          File "/usr/share/terminator/terminatorlib/ipc.py", line 192, in _exec
            func(proxy, *args, **argd)
          File "/usr/share/terminator/terminatorlib/ipc.py", line 198, in 
new_window_cmdline
            session.new_window_cmdline(options)
          File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
            return self._proxy_method(*args, **keywords)
          File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
            **keywords)
          File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, 
in call_blocking
            message, timeout)
        dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did 
not receive a reply. Possible causes include: the remote application did not 
send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.



After a quick rollback to stable's "1.90+bzr-1705-1" ( with the hanging windows 
still open ) produced a new working terminator instance so I'll stick to stable 
for now. 

Thanks!
Michael

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (999, 'testing'), (500, 'stable-updates'), (500, 
'oldstable-updates'), (500, 'oldoldstable-updates'), (103, 'unstable'), (102, 
'stable'), (101, 'oldstable'), (100, 'oldoldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages terminator depends on:
ii  gir1.2-glib-2.0   1.56.1-1
ii  gir1.2-gtk-3.0    3.22.30-2
ii  gir1.2-pango-1.0  1.42.4-1
ii  gir1.2-vte-2.91   0.52.2-1
ii  python            2.7.15-3
ii  python-cairo      1.16.2-1+b1
ii  python-dbus       1.2.8-2+b1
ii  python-gi         3.28.3-1
ii  python-gi-cairo   3.28.3-1
ii  python-psutil     5.4.6-1+b1

Versions of packages terminator recommends:
ii  gir1.2-keybinder-3.0  0.3.2-1
ii  gir1.2-notify-0.7     0.7.7-3
ii  xdg-utils             1.1.3-1

terminator suggests no packages.

-- no debconf information

Reply via email to