Control: tags -1 moreinfo Hi,
On Sa 22 Jul 2017 16:47:20 CEST, treaki wrote:
Package: mate-terminal Version: 1.8.1+dfsg1-4 Severity: important Dear Maintainer, * What led up to the situation? My system is running as always uptime 16:37:39 up 11 days, 5:10, 12 users, load average: 0.42, 0.82, 1.25with a huge amount of terminals opened as always, but suddenly, without a terminal in the foreground they all where gone (and thereby also the application in the foreground and all other applications running in terminal which broke a bunch of processes/transfers/etc like a half system crash)* What exactly did you do (or not do) that was effective (or ineffective)? nothing within the terminal * What was the outcome of this action?a lot was gone but others where still running (that i didn't started inside mate-terminals) and i was first wondering what the hell has happened because this was the first and hopefully last time that such an essential application like the terminal emulator crashes without a given reason.* What outcome did you expect instead? that everything else but the terminal emulator would crashhere are the last lines of my .xsession-errors, i hope they can help you. ive got no way to reproduce the problem because i dont know the reason, maybe someone got an idea on that...Window manager warning: No rect to clip to found! Window manager warning: No rect to clip to found! Window manager warning: No rect to clip to found! Window manager warning: No rect to clip to found! Window manager warning: No rect to shove into found! Window manager warning: No rect to shove into found! Window manager warning: No rect to shove into found! Window manager warning: No rect to shove into found! Window manager warning: No rect to shove into found!Window manager warning: Log level 8: Source ID 78861 was not found when attempting to remove itThe program 'mate-terminal' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 5265511 error_code 9 request_code 139 minor_code 4) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)Window manager warning: Log level 8: Source ID 79953 was not found when attempting to remove it Window manager warning: Log level 8: Source ID 80291 was not found when attempting to remove it Window manager warning: Log level 8: Source ID 80295 was not found when attempting to remove it(caja:1769): GLib-GObject-WARNING **: /build/glib2.0-y6934K/glib2.0-2.42.1/./gobject/gsignal.c:2579: instance '0x59d2c70' has no handler with id '623505'(caja:1769): GLib-GObject-WARNING **: /build/glib2.0-y6934K/glib2.0-2.42.1/./gobject/gsignal.c:2579: instance '0x24024a0' has no handler with id '613558'nothing relevant in dmesg/Xorg.0.log ant thats all i could think of to be relevent. Maybe someone can give me some advices what to do to get more debug output on such errors.thanks a lot in advance
I assume this issue is hard to reproduce. Upstream solved an issue with segfaulting mate-terminal during handling DBus method calls.
I will not mark this bug as resolved. Rather, I'd be happy, if you could re-test the above with upcoming mate-terminal 1.20.0-1 (or newer) and report back after some time, if you have seen this issue once more.
If we don't hear back from you within the next coupld of months on this, I will close this bug report and consider it resolved by 1.20.0-1.
Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgpRxDUtn6rPU.pgp
Description: Digitale PGP-Signatur