After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 743115 - crashing application caused terminal to die
crashing application caused terminal to die
Status: RESOLVED DUPLICATE of bug 740613
Product: gnome-terminal
Classification: Core
Component: general
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-01-18 08:16 UTC by Florian Pelz
Modified: 2015-01-21 14:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace from said function from gdb gedit (2.73 KB, text/plain)
2015-01-21 14:42 UTC, Florian Pelz
Details

Description Florian Pelz 2015-01-18 08:16:08 UTC
I'm not sure if this is the terminal's fault, but when supertuxkart (started from terminal) crashed, it took down the terminal as well. Other open terminal tabs were lost.

dmesg output:

[10678.466897] supertuxkart[2583]: segfault at 0 ip 000000000077807f sp 00007fff7c21e780 error 4 in supertuxkart[400000+b7a000]
[10922.997940] traps: gnome-terminal-[1050] trap int3 ip:7fa0503a9ae0 sp:7fffd53d5470 error:0

This is reproducible by trying to Ctrl+V into a supertuxkart beta online log-in and having it crash. Terminating a program with pkill -TRAP does not cause the terminal to crash.
Comment 1 Egmont Koblinger 2015-01-18 17:30:05 UTC
Could you please provide these details:

- Your OS, gnome-terminal version, supertuxkart version

- Redirect supertuxcart's output or error to devnull, do these still crash?
supertuxkart >/dev/null
and
supertuxkart 2>/dev/null

- Try running "script -f" in the terminal and start supertuxkart from within that. Does it still crash? If so, please attach the resulting "typescript" file.
Comment 2 Christian Persch 2015-01-18 17:38:37 UTC
As per https://wiki.gnome.org/Apps/Terminal/ReportingBugs we need at the very least a stack trace here.
Comment 3 Egmont Koblinger 2015-01-18 17:43:52 UTC
I managed to reproduce.  It crashes whichever Gtk+ app is the source of copy-paste.

Probably a dupe of the recently fixed bug 740613.
Comment 4 Florian Pelz 2015-01-18 21:33:57 UTC
@Egmont Koblinger: I just tested with pasting from gedit, it crashes too. You are probably right, no terminal error here and probably a duplicate. I'll tell the supertuxkart people not to worry about the crash.

OS is Arch Linux, using Intel's graphics driver. GNOME terminal is 3.14.2. supertuxkart is the 0.8.2 beta. Neither /dev/null nor script helps.
Comment 5 Egmont Koblinger 2015-01-19 14:50:01 UTC
As seen in the other bug (which may not have been fixed after all), supertuxkart is probably using an obsolete X method.  Florian, seems that you're already in touch with them, it would be great if you could point them to that bug, and ask them to use a non-deprecated method instead.
Comment 6 Florian Pelz 2015-01-20 12:12:49 UTC
I've posted the problem here[1] on the supertuxkart forums. When I have time I'll try if a current git Gtk version fixes the problem on the Gtk side.

[1] http://forum.freegamedev.net/viewtopic.php?f=17&t=6045&start=50
Comment 7 Florian Pelz 2015-01-21 14:42:55 UTC
Created attachment 295105 [details]
backtrace from said function from gdb gedit

This is the backtrace when breaking on gdk_x_error in gedit when trying to paste from it.
Comment 8 Florian Pelz 2015-01-21 14:46:49 UTC
This post should have come before the attachment:

I installed gtk3-git and the problem persists. pkg-config --print-provides tells me gtk+-3.0 = 3.15.4, so I assume it really is the current git version.

(gedit:804): Gdk-ERROR **: The program 'gedit' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 5602 error_code 5 request_code 18 (core protocol) minor_code 0)
  (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 GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[1]  + trace trap (core dumped)  gedit

Only gedit crashes, not supertuxkart or the terminal. I've uploaded a backtrace from doing what the error message says.
Comment 9 Egmont Koblinger 2015-01-21 14:50:35 UTC
Could you please file these to the other bug?  I'm not sure Matthias sees them here.  Thanks!  I'm closing this one.

*** This bug has been marked as a duplicate of bug 740613 ***