gedit crashed with SIGSEGV in g_slice_alloc()

Bug #188428 reported by razor1394
58
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

1. Latest Hardy heron alpha
2. razor1394@basestar:~$ dpkg -l gedit
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Namn Version Beskrivning
+++-==============-==============-============================================
ii gedit 2.21.1-0ubuntu official text editor of the GNOME desktop en

3. Gedit crashed as soon as I opened a text file. I hoped for it to open my document without crashing.

Since a Hardy update yesterday many gtk apps are crashing with either segfault or sigsegv. Examples are Firefox-3.0, Transmission and Deluge.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Feb 2 20:31:56 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: nvidia
Package: gedit 2.21.1-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: gedit file:///home/razor1394/passpack.txt
ProcCwd: /home/razor1394
ProcEnviron:
 PATH=/home/razor1394/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gedit
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 g_list_prepend () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_hash_table_foreach ()
 gtk_action_group_list_actions ()
Title: gedit crashed with SIGSEGV in g_slice_alloc()
Uname: Linux basestar 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

Tags: apport-crash
Revision history for this message
razor1394 (razor1394) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_list_prepend (list=0xbbd960, data=0x7f1c5fd817d0)
add_single_action (key=<value optimized out>, value=0x7f1c5fd817d0,
IA__g_hash_table_foreach (hash_table=0x854380,
IA__gtk_action_group_list_actions (action_group=0x861770)
update_languages_menu (window=0x75e100) at gedit-window.c:999

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gedit:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gedit:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
razor1394 (razor1394) wrote :

I hope I'm doing right because It's not crashing when using it through valgrind. Without it it crashes instantly.

Revision history for this message
Caroline Ford (secretlondon) wrote : Re: [Bug 188428] Re: gedit crashed with SIGSEGV in g_slice_alloc()

On 04/02/2008, razor1394 <email address hidden> wrote:
> I hope I'm doing right because It's not crashing when using it through
> valgrind. Without it it crashes instantly.

I've had the same issue. I think it doesn't crash if you open gedit
with a file, but does crash if you don't.

I will try and get a trace once I can get the debug symbols -
currently they are out of sync with the version of gedit in the
archive.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

May you tell us a few steps in order to trigger the crash then? thanks in advance.

Revision history for this message
Caroline Ford (secretlondon) wrote :

Open gedit from the applications menu.

Press the Open icon and open a text file. Gedit will then close.

Go to the file menu and open a file using Open. Gedit will then close.

Go to the file menu and open a file from the list of recent opened
files at the bottom. Gedit will *not* close.

Open it from the command line using gedit and then open a file using
the open icon. gedit will *not* close.

Open it from the command line using gedit and then open a file using
the file menu and open. gedit will *not* close.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Does running gconf-editor and changing the /desktop/gnome/interface/file_chooser_backend key value to gnome-vfs solve the issue?

Revision history for this message
razor1394 (razor1394) wrote :

Yes it does. Thanks.

Revision history for this message
razor1394 (razor1394) wrote :

I can also report that Deluge is working a lot smoother and the hard drive usage ain't insane as before.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you install gvfs-dbgsym libglib2.0-0-dbgsym libgtk2.0-0-dbgsym, set the key value to gio again and get a valgrind log of the issue? You can also open an another bug on libgnomeui about the disk usage issue

Revision history for this message
razor1394 (razor1394) wrote :

I can't install those packages with my current sources. I have tried
enabling proposed and backports as well.

2008/2/6, Sebastien Bacher <email address hidden>:
>
> Could you install gvfs-dbgsym libglib2.0-0-dbgsym libgtk2.0-0-dbgsym,
> set the key value to gio again and get a valgrind log of the issue? You
> can also open an another bug on libgnomeui about the disk usage issue
>
>
> --
> gedit crashed with SIGSEGV in g_slice_alloc()
> https://bugs.launchpad.net/bugs/188428
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
RaZoR1394 - Alexander Bracquemont

Revision history for this message
Sebastien Bacher (seb128) wrote :
Revision history for this message
mystictim (timgillibrand-yahoo) wrote :

Latest Hardy Heron
Kernel Linux 2.6.24-5 Generic
Gnome 2.21.90
gedit 2.21.1-Oubunttu2
Hi not sure if this is the same bug as only gedit appears to be crashing. Should I report a seperate bug?
When I changed /desktop/gnome/interface/file_chooser_backend key value to gnome-vfs the crash still occured. However on installing gvfs-dbgsym libglib2.0-0-dbgsym libgtk2.0-0-dbgsym the crashes appear to have stoped. However on running $sudo gedit I get this error message.

$ sudo gedit
[sudo] password for visitor:
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0

** (gedit:9998): CRITICAL **: Error opening file: No such file or directory

** (gedit:9998): CRITICAL **: Error opening file: No such file or directory

gedit still works though. I've attached the valgrind log for $gedit but valgrind wont run with $sudo gedit get error

$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log sudo gedit
==10057==
==10057== Warning: Can't execute setuid/setgid executable: /usr/bin/sudo
==10057== Possible workaround: remove --trace-children=yes, if in effect
==10057==
valgrind: /usr/bin/sudo: Permission denied

Revision history for this message
LCID Fire (lcid-fire) wrote :

Same here. A dozend apps crash at g_slice_alloc - could be a bug in glib

Revision history for this message
ashdigg (ashdigg) wrote :

After installing the latest Ubuntu updates this evening, I no longer have this problem.

Revision history for this message
linuxatico88 (simo88-47) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

does anybody still get the issue on current hardy?

Revision history for this message
razor1394 (razor1394) wrote :

Yes, I still get this on current Hardy unfortunately. Nerolinux 3.1.1.0 and
firefox-3 beta 5 keeps crashing. If I set file_chooser_backend to gnome-vfs
instead of gio both apps work fine. With gio Nero crashes when removing
files from the compilation and Firefox crashes (sometimes) when closing a
tab.

2008/3/26, Sebastien Bacher <email address hidden>:
>
> does anybody still get the issue on current hardy?
>
>
> --
> gedit crashed with SIGSEGV in g_slice_alloc()
> https://bugs.launchpad.net/bugs/188428
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
RaZoR1394 - Alexander Bracquemont

Revision history for this message
Sebastien Bacher (seb128) wrote :

could anybody getting the issue on current hardy get a stacktrace and a valgrind log?

Revision history for this message
razor1394 (razor1394) wrote :
  • unnamed Edit (936 bytes, text/html; charset=ISO-8859-1)

I can't reproduce this with neither Firefox, Gedit nor Nero. I guess it has
been fixed?

2008/4/22, Sebastien Bacher <email address hidden>:
>
> could anybody getting the issue on current hardy get a stacktrace and a
> valgrind log?
>
>
> --
> gedit crashed with SIGSEGV in g_slice_alloc()
> https://bugs.launchpad.net/bugs/188428
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
RaZoR1394 - Alexander Bracquemont

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing since that's working correctly now, feel free to reopen if you get the issue again though

Changed in gedit:
status: Incomplete → Fix Released
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.