After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640235 - crash in gedit: creating a new directory...
crash in gedit: creating a new directory...
Status: RESOLVED DUPLICATE of bug 630586
Product: gedit
Classification: Applications
Component: general
2.30.x
Other All
: Normal critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-22 02:44 UTC by ivank2139
Modified: 2011-01-22 12:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description ivank2139 2011-01-22 02:44:43 UTC
Version: 2.30.3

What were you doing when the application crashed?
creating a new directory to save a file into.


Distribution:                       Oracle Solaris 11 Express snv_151a X86
Gnome Release: 2.30.2 2010-10-21 (Oracle Corporation)
BugBuddy Version: 2.30.0

X Vendor: Oracle Corporation, based on X.Org Foundation sources
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: blueprint
Icon Theme: blueprint
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 151015424 vsize: 151015424 resident: 35905536 share: 892928 rss: 35905536 rss_rlim: 0
CPU usage: start_time: 1295664141 rtime: 156 utime: 1301614 stime: 261072 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gedit'

15805:	gedit
-----------------  lwp# 1 / thread# 1  --------------------
 feef23f7 waitid   (0, 3dbe, 80472d0, 3)
 feea1fd5 waitpid  (3dbe, 804737c, 0, fdb1125c) + 65
 fdb112aa __1cVrun_bug_buddy_solaris6F_v_ (feec76a9, fef70000, 80473b8, feeed9e5, 6, 0) + 66
 fdb11318 __1cUbugbuddy_segv_handle6Fi_v_ (6, 0, 804746c, feec7684, fe392a40, fef70000) + 64
 feeed9e5 __sighndlr (6, 0, 804746c, fdb112b4) + 15
 feee08be call_user_handler (6) + 2a2
 feee0b02 sigacthandler (6, 0, 804746c) + f2
 --- called from signal handler with signal 6 (SIGABRT) ---
 feef2177 _lwp_kill (1, 6, 80476a8, fee99f2e) + 7
 fee99f3a raise    (6, 6, 80476e0, fee71904) + 22
 fee7196c abort    (fe7d85b0, fe8d2964, 8047728, 870c488, 303233, 870c488) + 74
 fe83f9a0 g_assertion_message (fe58bc98, fe58bbe8, 140, fe57d1c4, 870c488) + 118
 fe83f9f0 g_assertion_message_expr (fe58bc98, fe58bbe8, 140, fe57d1c4, fe58bba8, fe58b940) + 40
 fe571a57 port_add (86eb780, 0, 1a, fe572eb2) + 83
 fe572f4b node_add_event (86eb780, 87060d8, 0, fe57163e) + a3
 fe5718ef port_events_process_cb (0, fe8d2964, 8047878, fe81b8a9) + 2bf
 fe81b8bf g_timeout_dispatch (827f9c0, fe571630, 0, 80478f0) + 23
 fe819b2a g_main_context_dispatch (811cbe8, 0, 82f57c0, d) + 262
 fe81a1d5 g_main_context_iterate (811cbe8, 1, 1, 80f6210) + 47d
 fe81a801 g_main_loop_run (82fb468, 82fb468, fef804d8, feb80dde) + 1dd
 feb80e87 gtk_main (8047a20, fefc0674, 0, 80fcf77, 29, fef78cd4) + b7
 0807d726 main     (1, 8047a60, 8047a68, 8047a1c) + 4c6
 0807c85d _start   (1, 8047b70, 0, 8047b76, 8047bb9, 8047bdd) + 7d
-----------------  lwp# 6 / thread# 6  --------------------
 feeed94b lwp_park (0, f5c8ee08, 0)
 feee6f3d cond_wait_queue (835efb8, 8150fd8, f5c8ee08, feee7186) + 60
 feee7363 cond_wait_common (835efb8, 8150fd8, f5c8ee08, feee75a6) + 1eb
 feee75fe __cond_timedwait (835efb8, 8150fd8, f5c8ee88, feee7690) + 66
 feee76a1 cond_timedwait (835efb8, 8150fd8, f5c8ee88, feee76d4) + 27
 feee76ec pthread_cond_timedwait (835efb8, 8150fd8, f5c8ee88, fe371afd) + 24
 fe371b47 g_cond_timed_wait_posix_impl (835efb8, 8150fd8, f5c8ef38, fe7f06b2) + 57
 fe7f0734 g_async_queue_pop_intern_unlocked (8150fb8, 0, f5c8ef38, fe7f0b62) + 90
 fe7f0bb8 g_async_queue_timed_pop (8150fb8, f5c8ef38, 86f4940, fe8439b2) + 64
 fe843a6e g_thread_pool_wait_for_new_pool (fe8d3a94, fe8d2964, 4d3a442c, 3181f, fe8d3aa4, 0) + ca
 fe843cc0 g_thread_pool_thread_proxy (8283c18, 86897e0, 208, fe84248a) + 180
 fe8425af g_thread_create_proxy (86897e0, fef70000, f5c8efe8, feeed60e) + 133
 feeed663 _thrp_setup (fdca1240) + 9b
 feeed910 _lwp_start (fdca1240, 0, 0, 0, 0, 0)
Output of custom script "/usr/lib/gedit-2/gedit-bugreport.sh":
Active plugins:
  - docinfo
  - modelines
  - filebrowser
  - spell
  - time

No plugin installed in $HOME.

Module versions:
-n   - -n glib 
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
2.25.1
-n   - -n gtk+ 
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
2.20.0
-n   - -n gtksourceview 
-n  
2.10.1
-n   - -n pygobject 
-n  
-n  
-n  
-n  
-n  
2.21.1
-n   - -n pygtk 
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
2.17.0
-n   - -n pygtksourceview 
2.10.1
-n   - -n enchant 
-n  
-n  
-n  
-n  
-n  
-n  
-n  
1.6.0
-n   - -n iso-codes 
-n  
-n  
-n  
-n  
-n  
3.16

Python module versions:
-n   - python 
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
2.6.4
-n   - pygtk 
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
-n  
2.17.0 (GTK+ 2.20.0)





----------- .xsession-errors ---------------------
(gnome-system-monitor:6118): GdkPixbuf-CRITICAL **: file gdk-pixbuf.c: line 470: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gnome-system-monitor:6118): GdkPixbuf-CRITICAL **: file gdk-pixbuf.c: line 470: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gnome-system-monitor:6118): GdkPixbuf-CRITICAL **: file gdk-pixbuf.c: line 470: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gnome-system-monitor:6118): Gdk-CRITICAL **: file gdkdraw.c: line 781: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(evolution-alarm-notify:1660): evolution-alarm-notify-WARNING **: alarm.c:252: Requested removal of nonexistent alarm!
(nautilus:1635): Eel-WARNING **: Trying to add a callback for preferences/enable_time_slider that already exists.
Client shut down the connection owned by im_id(1).
**
GLib-GIO:ERROR:fen-kernel.c:320:port_add: assertion failed: (NODE_HAS_FLAG(f, NODE_FLAG_STAT_UPDATED))
--------------------------------------------------
Comment 1 André Klapper 2011-01-22 12:03:17 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 630586 ***