scite crashes on startup: scite crashed with SIGSEGV in __kernel_vsyscall()

Bug #373506 reported by Daniel Hahler
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
scite (Ubuntu)
Triaged
High
Unassigned

Bug Description

Binary package hint: scite

Do not remember what happened, just wanted to report it.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/scite
NonfreeKernelModules: nvidia
Package: scite 1.76-1
ProcCmdline: /usr/bin/scite
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
Signal: 11
SourcePackage: scite
StacktraceTop:
 __kernel_vsyscall ()
 __waitpid_nocancel () from /lib/tls/i686/cmov/libpthread.so.0
 g_spawn_sync () from /usr/lib/libglib-2.0.so.0
 g_spawn_command_line_sync () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so
Title: scite crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare scanner src video

Revision history for this message
Daniel Hahler (blueyed) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()
__waitpid_nocancel ()
IA__g_spawn_sync (working_directory=0x0, argv=0x99cc408,
IA__g_spawn_command_line_sync (
getKdeHome ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in scite (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Daniel Hahler (blueyed)
visibility: private → public
summary: - scite crashed with SIGSEGV in __kernel_vsyscall()
+ scite crashes on startup: scite crashed with SIGSEGV in
+ __kernel_vsyscall()
Revision history for this message
Daniel Hahler (blueyed) wrote :

I've tried rebuilding scite, but it still segfaults.

Changed in scite (Ubuntu):
importance: Medium → High
Revision history for this message
arky (arky) wrote :

Unable to reproduce the crash with scite_1.76-1 with kernel 2.6.31-8-generic

Revision history for this message
Stefan Weil (ubuntu-weilnetz) wrote :

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?) when this
new process terminates (?) and fails in the signal handling
with SIGSEGV. This explains why the stack below
IA__g_spawn_sync is not always the same (sometimes
the crash comes a little later).

There seem to be other packages affected by the same kind of
bug, just look for fork_exec_with_pipes.

Revision history for this message
Stefan Weil (ubuntu-weilnetz) wrote :

scite receives a SIGCHLD signal and crashes in the handler.

Running scite from gdb with SIGCHLD not passed to the program
makes it work.

Revision history for this message
Stefan Weil (ubuntu-weilnetz) wrote :

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.

Revision history for this message
Daniel Hahler (blueyed) wrote :

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
Gary M (garym)
tags: added: jaunty karmic
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.