p-e-w / finalterm

At last – a modern terminal emulator (NO LONGER MAINTAINED)
http://finalterm.org
GNU General Public License v3.0
3.84k stars 179 forks source link

Finalterm Crashing #401

Open norpol opened 9 years ago

norpol commented 9 years ago

Hi, compiled from git master branch using Fedora 21. Window Manager: awesomewm Happens when I type anything. Sorry if this is a duplicate :).

finalterm
** Message: TerminalOutput.vala:386: Command mode entered
** Message: Command updated: ''
** Message: Command updated: 'l'

(finalterm:1742): Gdk-ERROR **: The program 'finalterm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadDrawable'.
  (Details: serial 617 error_code 169 request_code 154 (GLX) minor_code 29)
  (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]    1742 trace trap (core dumped)  finalterm

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

rdodesigns commented 9 years ago

I am also having this problem. Ubuntu 14.04 using xfce. Compiled commit 39b078.

tlitovsk commented 9 years ago

same here

(finalterm:29017): Gdk-ERROR **: The program 'finalterm' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadDrawable'. (Details: serial 1066 error_code 169 request_code 154 (GLX) minor_code 29) (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.) Trace/breakpoint trap (core dumped)

AadityaNair commented 9 years ago

I have the same problem. I think the problem exists with the command auto-completion system. Whenever I type the command for the first time, It works OK. But type it for the second time, the auto-completion triggers a selection box and the whole application crashes.

norpol commented 9 years ago

Here is also some strace output:

ioctl(7, VIDIOC_INT_RESET, 0x7fff03442d10) = 0
ioctl(7, 0x4020645d, 0x7fff03442da0)    = 0
ioctl(7, 0xc010645b, 0x7fff03444c50)    = 0
ioctl(7, 0xc0086457, 0x7fff03444d10)    = 0
ioctl(7, 0xc020645e, 0x7fff03444c70)    = 0
ioctl(7, 0x400c645f, 0x7fff03444c70)    = 0
ioctl(7, 0x40046460, 0x7fff03444dc0)    = 0
ioctl(7, 0x40046460, 0x7fff03444e80)    = 0
ioctl(7, 0x40406469, 0x7fff03444e10)    = 0
ioctl(7, VIDIOC_INT_RESET, 0x7fff03444dd0) = 0
ioctl(7, VIDIOC_INT_RESET, 0x7fff03444dd0) = 0
ioctl(7, VIDIOC_INT_RESET, 0x7fff03444e00) = 0
ioctl(7, 0xc0086457, 0x7fff03444df0)    = 0
ioctl(7, VIDIOC_INT_RESET, 0x7fff03444de0) = 0
ioctl(7, 0x400c645f, 0x7fff03444df0)    = 0
poll([{fd=6, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=6, revents=POLLOUT}])
writev(6, [{"\223\1\22\0002\0`\0029\0`\2\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 72}], 1) = 72
open("/usr/share/X11/XErrorDB", O_RDONLY) = 15
fstat(15, {st_mode=S_IFREG|0644, st_size=41532, ...}) = 0
read(15, "!\n! Copyright 1993, 1995, 1998  "..., 41532) = 41532
close(15)                               = 0
write(2, "\n(finalterm:25595): Gdk-ERROR **"..., 597
(finalterm:25595): Gdk-ERROR **: The program 'finalterm' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadDrawable'.
  (Details: serial 679 error_code 169 request_code 154 (GLX) minor_code 29)
  (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.)
) = 597
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
[1]    25592 trace trap (core dumped)  strace ./finalterm
then3rd commented 9 years ago

I also have this problem when built on fedora 21. My trace is identical to @norpol replicated by typing: ls l This it briefly displays the auto-complete menu, but crashes.

Petahh commented 9 years ago

I have same problem, can someone advice here? Fedora 21 - 3.19.3-200.fc21.x86_64. Installed from https://copr.fedoraproject.org/coprs/mattdm/finalterm/ package finalterm-0.1-13.39b078b.x86_64

$ finalterm * Message: TerminalOutput.vala:386: Command mode entered * Message: Command updated: '' * Message: Command updated: 'l' * Message: Command updated: 'l' * Message: Command updated: 'ls' * Message: Command executed: 'ls' * Message: TerminalOutput.vala:386: Command mode entered * Message: Command updated: '' \ Message: Command updated: 'l'

(finalterm:4731): Gdk-ERROR **: The program 'finalterm' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadDrawable'. (Details: serial 686 error_code 169 request_code 154 (GLX) minor_code 29) (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.) Trace/breakpoint trap (core dumped)

ravanscafi commented 9 years ago

:+1:

tlitovsk commented 9 years ago

The problem is the pop up box creation.I traces it down that every pop up made the system crashes

daniviga commented 9 years ago

Same for me, on Fedora 21 with Intel HD4400 (with both F21 drivers and Intel upstream)