search

lanoxx / tilda

A Gtk based drop down terminal for Linux and Unix
GNU General Public License v2.0
1.28k stars 161 forks source link

Segmentation fault (core dumped) #196

Closed Mimalef closed 8 years ago

Mimalef commented 9 years ago

I tried to open "Tilda" from menu icon, and nothing happened. I tried it from terminal and i get:

$ tilda
Segmentation fault (core dumped)

I also tried it with "gksudo", "gksu", "sudo":

$ gksudo tilda
$ gksu tilda
No protocol specified

** (tilda:6491): WARNING **: Could not open X display
$ sudo tilda
No protocol specified
Unable to init server: Could not connect: Connection refused
Error parsing command-line options. Try "tilda --help"
to see all possible options.

Error message: Cannot open display:

as you saw "gksudo" did nothing. and "gksu" and "sudo" show strange errors aboat "Could not open X display".

My system

I use 64 bit Arch Linux with Gnome on it.

$ uname -srvm
Linux 4.2.3-1-ARCH #1 SMP PREEMPT Sat Oct 3 18:52:50 CEST 2015 x86_64
$  ldd --version
ldd (GNU libc) 2.22
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
$ gnome-shell --version
GNOME Shell 3.18.1
lanoxx commented 9 years ago

Which version of tilda are you using. It looks like tilda cannot open your X display.

Mimalef commented 9 years ago

Sorry I forgot about the version. I use 1.2.4

$ tilda -v
Tilda 1.2.4

Copyright (c) 2012-2013 Sebastian Geiger (lanoxx@gmx.net)
Copyright (c) 2005-2009 Tristan Sloughter (sloutri@iit.edu)
Copyright (c) 2005-2009 Ira W. Snyder (tilda@irasnyder.com)

General Information: https://github.com/lanoxx/tilda
Bug Reports: https://github.com/lanoxx/tilda/issues?state=open

This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.
Mimalef commented 9 years ago

The weirdest part is that everything works fine for me for a long time. But one day suddenly I face this error! The only thing that I can say is I installed some new packages the night before it. I cant's name those, becuse I can't remember.

Mimalef commented 9 years ago

I found these lines in log file:

Oct 24 02:08:21 roya kernel: tilda[3148]: segfault at 21 ip 00007fbdb7849009 sp 00007ffc5abad6b0 error 4 in libX11.so.6.3.0[7fbdb7818000+13b000]
Oct 24 02:08:21 roya systemd-coredump[3154]: Process 3148 (tilda) of user 1000 dumped core.

There is something wrong with "libX11"!

lanoxx commented 9 years ago

Then its probably not a problem of tilda. Can you produce a stack trace.

Mimalef commented 9 years ago

Did you mean something like this:

(gdb) run
Starting program: /usr/bin/tilda 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffeb9c2700 (LWP 2360)]
[New Thread 0x7fffeb1c1700 (LWP 2361)]
[New Thread 0x7fffea9c0700 (LWP 2362)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5ee5009 in XGetModifierMapping () from /usr/lib/libX11.so.6

I'm not good at debugging, so if I'm wrong, please correct me.

lanoxx commented 9 years ago

Just type backtrace and post the output after you receive the sigsegv.

Mimalef commented 8 years ago

Here the backtrace outputs:

(gdb) backtrace
#0  0x00007ffff5ee5009 in XGetModifierMapping () from /usr/lib/libX11.so.6
#1  0x0000000000409ef0 in ?? ()
#2  0x000000000040a12d in ?? ()
#3  0x000000000040db83 in ?? ()
#4  0x000000000040df4e in ?? ()
#5  0x0000000000408ce5 in ?? ()
#6  0x00007ffff5707610 in __libc_start_main () from /usr/lib/libc.so.6
#7  0x0000000000409039 in ?? ()
lanoxx commented 8 years ago

Thats not too muc help since all the debug symbols are missing (??). Either send me the coredump or install the debug symbols/source code for tilda and X11.

Mimalef commented 8 years ago

Sorry That was an accident

Mimalef commented 8 years ago

I reported it as a bug to Arch community: https://bugs.archlinux.org/task/46854

You can find my coredump there: https://bugs.archlinux.org/task/46854?getfile=13510

And how can I "install the debug symbols/source code"?

Mimalef commented 8 years ago

100% It's not a "tilda" bug. after reinstalling the OS, it's works like a charm, just like before. Probably I accidently removed an important file (that unfortunately I couldn't found it) or somethings like that.

Thank you for your kind attention

nini commented 8 years ago

Funny, I just got the same problem, with same OS and coredump :) Tilda is not working for me anymore.

ecthiender commented 8 years ago

I updated my Arch 2 days back and since then I also have the exact same problem. I have already tried things like removing the ~/.config/tilda and ~/.config/cache directories, but that doesn't help.

Below is the coredump:

Oct 17 18:25:36 x89 kernel: tilda[6517]: segfault at 38 ip 00007f173427b3f2 sp 00007ffc2e1d1150 error 4 in libX11.so.6.3.0[7f1734239000+139000]
Oct 17 18:25:36 x89 systemd[1]: Started Process Core Dump (PID 6530/UID 0).
-- Subject: Unit systemd-coredump@9-6530-0.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-coredump@9-6530-0.service has finished starting up.
-- 
-- The start-up result is done.
Oct 17 18:25:36 x89 systemd-coredump[6531]: Process 6517 (tilda) of user 1000 dumped core.

                                            Stack trace of thread 6517:
                                            #0  0x00007f173427b3f2 _XReply (libX11.so.6)
                                            #1  0x00007f1734269edf XGetModifierMapping (libX11.so.6)
                                            #2  0x000000000040a9d0 n/a (tilda)
                                            #3  0x000000000040ac0d n/a (tilda)
                                            #4  0x000000000040f603 n/a (tilda)
                                            #5  0x000000000040f9ce n/a (tilda)
                                            #6  0x0000000000409557 n/a (tilda)
                                            #7  0x00007f1733c9e291 __libc_start_main (libc.so.6)
                                            #8  0x0000000000409a99 n/a (tilda)

                                            Stack trace of thread 6519:
                                            #0  0x00007f1733d5d48d poll (libc.so.6)
                                            #1  0x00007f1734a24786 n/a (libglib-2.0.so.0)
                                            #2  0x00007f1734a2489c g_main_context_iteration (libglib-2.0.so.0)
                                            #3  0x00007f1728e584bd n/a (libdconfsettings.so)
                                            #4  0x00007f1734a4c0d5 n/a (libglib-2.0.so.0)
                                            #5  0x00007f1734023454 start_thread (libpthread.so.0)
                                            #6  0x00007f1733d667df __clone (libc.so.6)

                                            Stack trace of thread 6520:
                                            #0  0x00007f1733d5d48d poll (libc.so.6)
                                            #1  0x00007f1734a24786 n/a (libglib-2.0.so.0)
                                            #2  0x00007f1734a2489c g_main_context_iteration (libglib-2.0.so.0)
                                            #3  0x00007f1734a248e1 n/a (libglib-2.0.so.0)
                                            #4  0x00007f1734a4c0d5 n/a (libglib-2.0.so.0)
                                            #5  0x00007f1734023454 start_thread (libpthread.so.0)
                                            #6  0x00007f1733d667df __clone (libc.so.6)

                                            Stack trace of thread 6525:
                                            #0  0x00007f1733d61f19 syscall (libc.so.6)
                                            #1  0x00007f1734a6a03a g_cond_wait_until (libglib-2.0.so.0)
                                            #2  0x00007f17349f8e89 n/a (libglib-2.0.so.0)
                                            #3  0x00007f1734a4caa6 n/a (libglib-2.0.so.0)
                                            #4  0x00007f1734a4c0d5 n/a (libglib-2.0.so.0)
                                            #5  0x00007f1734023454 start_thread (libpthread.so.0)
                                            #6  0x00007f1733d667df __clone (libc.so.6)

                                            Stack trace of thread 6524:
                                            #0  0x00007f1733d61f19 syscall (libc.so.6)
                                            #1  0x00007f1734a6a03a g_cond_wait_until (libglib-2.0.so.0)
                                            #2  0x00007f17349f8e89 n/a (libglib-2.0.so.0)
                                            #3  0x00007f1734a4caa6 n/a (libglib-2.0.so.0)
                                            #4  0x00007f1734a4c0d5 n/a (libglib-2.0.so.0)
                                            #5  0x00007f1734023454 start_thread (libpthread.so.0)
                                            #6  0x00007f1733d667df __clone (libc.so.6)

                                            Stack trace of thread 6521:
                                            #0  0x00007f1733d5d48d poll (libc.so.6)
                                            #1  0x00007f1734a24786 n/a (libglib-2.0.so.0)
                                            #2  0x00007f1734a24b12 g_main_loop_run (libglib-2.0.so.0)
                                            #3  0x00007f173500a316 n/a (libgio-2.0.so.0)
                                            #4  0x00007f1734a4c0d5 n/a (libglib-2.0.so.0)
                                            #5  0x00007f1734023454 start_thread (libpthread.so.0)
                                            #6  0x00007f1733d667df __clone (libc.so.6)

                                            Stack trace of thread 6523:
                                            #0  0x00007f1733d61f19 syscall (libc.so.6)
                                            #1  0x00007f1734a6a03a g_cond_wait_until (libglib-2.0.so.0)
                                            #2  0x00007f17349f8e89 n/a (libglib-2.0.so.0)
                                            #3  0x00007f1734a4caa6 n/a (libglib-2.0.so.0)
                                            #4  0x00007f1734a4c0d5 n/a (libglib-2.0.so.0)
                                            #5  0x00007f1734023454 start_thread (libpthread.so.0)
                                            #6  0x00007f1733d667df __clone (libc.so.6)

                                            Stack trace of thread 6526:
                                            #0  0x00007f1733d61f19 syscall (libc.so.6)
                                            #1  0x00007f1734a6a03a g_cond_wait_until (libglib-2.0.so.0)
                                            #2  0x00007f17349f8e89 n/a (libglib-2.0.so.0)
                                            #3  0x00007f1734a4caa6 n/a (libglib-2.0.so.0)
                                            #4  0x00007f1734a4c0d5 n/a (libglib-2.0.so.0)
                                            #5  0x00007f1734023454 start_thread (libpthread.so.0)
                                            #6  0x00007f1733d667df __clone (libc.so.6)
-- Subject: Process 6517 (tilda) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 6517 (tilda) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
ecthiender commented 8 years ago

Sorry please ignore the above report. My issue is related to #262

skobkin commented 7 years ago

Same error happened to me when I moved to Wayland.

yellowmegaman commented 6 years ago

Same here with wayland and pixelbook linux. Tilda is the sexiest terminal emulators, so i don't even know what to use now)

ecthiender commented 6 years ago

@yellowmegaman Yeah, tilda does not work on Wayland. There are no plans to fix this also soon. https://github.com/lanoxx/tilda/issues/262#issuecomment-253527961

geckon commented 4 years ago

FWIW, running tilda like this seems to work for me: env GDK_BACKEND=x11 /usr/bin/tilda

ecthiender commented 4 years ago

I have found kitty to be a good replacement. It is not perfect because it is not a drop-down terminal emulator. So that was the hardest part for me to migrate away to. But otherwise its actually a better experience. I have been using x11 just so that I can keep running tilda. Lately, tilda keeps crashing randomly (on x11). Often, more than 10 times in day. I am really sorry, that I can't be bothered about finding relevant logs, and filing bug reports, when the author of this project does not welcome much user feedback. Which kind of forced me to find a substitute. After switching, I also realized that the color rendering in tilda is quite bad. I am happy to move away from tilda. But I still wish that tilda had kept evolving and done better.

nini commented 4 years ago

I've moved away to terminator a while ago and changed my work behavior. It was convenient with tilda, but now I use terminator and Super+3 shortcut to switch to it (fixed position in Gnome3).