Created attachment 104863 [details] a screenshot of my Kate Hello, I do not know what I clicked wrong but I cannot see any file I open with Kate. As you see in the attachment it shows a blank gray area instead of the text. I tried removing kate and install it again .. restarted my system .. did not help. Thanks in advance for your help, Hosam
Confirming same problem on kernel 4.4.0-72-generic, 64-bit. If I load a saved session, I get a blank grey screen with the files listed in the tree on left, but no editor windows. If I open a file manually, sometimes I get that file in editor, but usually (and now constantly) the same grey background with a file tree at left.
Reinstalling packages never fixes configuration issues. Please try with a freshly created user account, or manually remove Kate configuration files.
Can you specify which Kate config files are needed? I renamed .katerc without any effect.
Just test with a freshly created user account. There may be multiple configuration files that could cause this issue, even some unrelated to Kate.
Bug 379008 suggests it is related to session restoration. Please also test a recent version, 15.12 is quite old already.
Yeah, I just upgraded twice to 17.04. Now it won't even load, which I guess is a separate bug... Trace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa100b7a900 (LWP 24073))] Thread 3 (Thread 0x7fa0d277d700 (LWP 24076)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fa0d699652b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x00007fa0d6996257 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x00007fa0f7da06da in start_thread (arg=0x7fa0d277d700) at pthread_create.c:456 #4 0x00007fa0fb32c17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fa0eb554700 (LWP 24074)): #0 0x00007fa0fb32018d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fa0f5c6f576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fa0f5c6f68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fa0fbf4cf2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007fa0fbef688a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fa0fbd23fe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007fa0fc35f5c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007fa0fbd28c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007fa0f7da06da in start_thread (arg=0x7fa0eb554700) at pthread_create.c:456 #9 0x00007fa0fb32c17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fa100b7a900 (LWP 24073)): [KCrash Handler] #6 0x00007fa0fd4ba810 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x00005569c21f03c4 in ?? () #8 0x00005569c21f08a2 in ?? () #9 0x00005569c21f2250 in ?? () #10 0x00005569c21e30e7 in ?? () #11 0x00005569c21cdab2 in ?? () #12 0x00005569c22039d5 in ?? () #13 0x00005569c22049db in ?? () #14 0x00005569c2204e66 in ?? () #15 0x00005569c220552c in ?? () #16 0x00005569c21d053c in ?? () #17 0x00005569c21d08f5 in ?? () #18 0x00005569c21c9008 in ?? () #19 0x00007fa0fb2443f1 in __libc_start_main (main=0x5569c21c6fd0, argc=1, argv=0x7ffecc1147d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffecc1147c8) at ../csu/libc-start.c:291 #20 0x00005569c21cac6a in _start ()
Yes, please report crashes separately. Install debug symbols to make the backtrace useful.
Should be fixed in master, see bug 381433 *** This bug has been marked as a duplicate of bug 381433 ***