search

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

Crash on launch (Ubuntu 14.04) #396

Open Paludan opened 9 years ago

Paludan commented 9 years ago

I installed Final Term using the following commands:

git clone https://github.com/p-e-w/finalterm.git cd finalterm/ mkdir build cd build/ cmake .. make sudo make install

However when I launch it it crashes and gives me the following error message:

(finalterm:10703): Gdk-ERROR **: The program 'finalterm' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 410 error_code 3 request_code 3 (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.) Trace/breakpoint trap (core dumped)

How can I fix this?

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

p-e-w commented 9 years ago

Could be a GPU driver issue. I'm afraid I do not have a better guess given the information available.

Atem18 commented 9 years ago

Hi, I have a similar error on Fedora 21:

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

(finalterm:26953): 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 698 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] 26953 trace trap (core dumped) finalterm

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)