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


** Attachment added: "gedit.valgrind.log"
   http://launchpadlibrarian.net/11817116/gedit.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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to