** Tags added: jaunty karmic
--
scite crashes on startup: scite crashed with SIGSEGV in __kernel_vsyscall()
https://bugs.launchpad.net/bugs/373506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yes, that's the bug I'm facing.
Thank you for investigating.
So, is this a bug with Scite (and the other applications crashing in a
similar way), or is it a glib bug (where fork_exec_with_pipes) appears
to come from?
** Changed in: scite (Ubuntu)
Status: New = Triaged
--
scite crashes
Can be reproduced with karmic and kde netbook desktop.
No crash occurs with gnome.
Call stack:
signal_handler_called
fork_exec_with_pipes (glib2.0-2.22.3/glib/gspawn.c:1199)
IA__g_spawn_sync
fork_exec_with_pipes creates a new process kde4-config.
scite obviously gets a signal (which signal?)
scite receives a SIGCHLD signal and crashes in the handler.
Running scite from gdb with SIGCHLD not passed to the program
makes it work.
--
scite crashes on startup: scite crashed with SIGSEGV in __kernel_vsyscall()
https://bugs.launchpad.net/bugs/373506
You received this bug notification
The crash can be avoided by unsetting GTK2_RC_FILES:
GTK2_RC_FILES= scite
It can be forced by setting it to a certain value:
GTK2_RC_FILES=/usr/share/themes/QtCurve/gtk-2.0/gtkrc scite
Of course you must have installed /usr/share/themes/QtCurve/gtk-2.0/gtkrc
to get a crash.
--
scite
Unable to reproduce the crash with scite_1.76-1 with kernel
2.6.31-8-generic
--
scite crashes on startup: scite crashed with SIGSEGV in __kernel_vsyscall()
https://bugs.launchpad.net/bugs/373506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've tried rebuilding scite, but it still segfaults.
** Changed in: scite (Ubuntu)
Importance: Medium = High
--
scite crashes on startup: scite crashed with SIGSEGV in __kernel_vsyscall()
https://bugs.launchpad.net/bugs/373506
You received this bug notification because you are a member of
