GNOME Bugzilla – Bug 375496
crash in Text Editor: I was trying to open a f...
Last modified: 2007-09-25 15:11:35 UTC
Version: 2.15.9 What were you doing when the application crashed? I was trying to open a file Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- ** (gnome-terminal:2307): WARNING **: Nie zdefiniowano obsługi dla sekwencji sterującej "device-control-string" ** (gnome-terminal:2307): WARNING **: Nie zdefiniowano obsługi dla sekwencji sterującej "device-control-string" ** (gnome-terminal:2307): WARNING **: Nie zdefiniowano obsługi dla sekwencji sterującej "device-control-string" ** (gnome-terminal:2307): WARNING **: Nie zdefiniowano obsługi dla sekwencji sterującej "device-control-string" ** (gnome-terminal:2307): WARNING **: Nie zdefiniowano obsługi dla sekwencji sterującej "device-control-string" Ostrzeżenie menedżera okien: Invalid WM_TRANSIENT_FOR window 0x0 specified for 0x2c00b9d (Historia). Loading "installonlyn" plugin Ostrzeżenie menedżera okien: Invalid WM_TRANSIENT_FOR window 0x0 specified for 0x2c00f47 (Historia). ** (bug-buddy:3989): WARNING **: Nie można wczytać ikony dla Open Folder -------------------------------------------------- Memory status: size: 115294208 vsize: 0 resident: 115294208 share: 0 rss: 25214976 rss_rlim: 0 CPU usage: start_time: 1163588369 rtime: 0 utime: 232 stime: 0 cutime:196 cstime: 0 timeout: 36 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208400176 (LWP 2433)] (no debugging symbols found) 0x0080f402 in __kernel_vsyscall ()
+ Trace 86644
Thread 1 (Thread -1208400176 (LWP 2433))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 374408 has been marked as a duplicate of this bug. ***
*** Bug 379303 has been marked as a duplicate of this bug. ***
*** Bug 375783 has been marked as a duplicate of this bug. ***
*** Bug 383748 has been marked as a duplicate of this bug. ***
*** Bug 385944 has been marked as a duplicate of this bug. ***
*** Bug 389744 has been marked as a duplicate of this bug. ***
*** Bug 391921 has been marked as a duplicate of this bug. ***
*** Bug 392345 has been marked as a duplicate of this bug. ***
*** Bug 399063 has been marked as a duplicate of this bug. ***
Created attachment 80855 [details] Relevant portion of terminal session when bug-buddy took over
*** Bug 400088 has been marked as a duplicate of this bug. ***
*** Bug 402176 has been marked as a duplicate of this bug. ***
Even after installing gedit-dbgsym, as described in http://live.gnome.org/GettingTraces for Ubuntu Edgy, I keep getting the error message that "the stack trace of your report is missing some elements blah blah blah". Any other suggestions?
*** Bug 404405 has been marked as a duplicate of this bug. ***
*** Bug 396895 has been marked as a duplicate of this bug. ***
*** Bug 408118 has been marked as a duplicate of this bug. ***
Please install the gedit, glib, gtk+ and gnome-vfs debug packages and retrigger the crash. Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I downloaded the relevant debugging-info modules as suggested by Christian Kirbach. But after installing the debug symbols rpms, I cannot reproduce the bug! I was using a ~16-MB text file (2-step created by 1) /ls -l -R > /Trash, 2) gedit /Trash & on my FC6 1 GB RAM, 2 Pentium 4 @ 3.2 Ghz box) to reproduce the error at whim, and I'd been doing that for weeks, convinced it was a huge-file memory problem. I never saw the crash on any file smaller than 400K. Now gedit handles that same file plus variously-pathed C, PL/SQL and Pro*C headers and code modules, all fast and beautifully, simultaneously or singly. My favorite code editor is back! ...but I don't know *why*, which annoys me... :-) Christian (and everybody else too), I'm sorry I can't be more helpful. But thank you for the suggestion!
1529 CST is this any help? [root@junicorn ~]# gedit /Trash & [1] 11456 [root@junicorn ~]# connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!!
*** Bug 417472 has been marked as a duplicate of this bug. ***
*** Bug 430383 has been marked as a duplicate of this bug. ***
*** Bug 437498 has been marked as a duplicate of this bug. ***
*** Bug 437619 has been marked as a duplicate of this bug. ***
*** Bug 437769 has been marked as a duplicate of this bug. ***
*** Bug 438371 has been marked as a duplicate of this bug. ***
*** Bug 441227 has been marked as a duplicate of this bug. ***
*** Bug 441348 has been marked as a duplicate of this bug. ***
*** Bug 441352 has been marked as a duplicate of this bug. ***
*** Bug 443398 has been marked as a duplicate of this bug. ***
*** Bug 445423 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
I'm the reporter of this bug ,I'm a Chinese, my English is very bad,and I'm not good at linux ,so I have no abilities to help you so I feel very sorry.The only thing I can help you is that (please let me speak Chinese) : 这个bug是我用root权限在图形界面 使用鼠标操作时产生的.
*** Bug 462865 has been marked as a duplicate of this bug. ***
*** Bug 463461 has been marked as a duplicate of this bug. ***
*** Bug 464091 has been marked as a duplicate of this bug. ***
*** Bug 469984 has been marked as a duplicate of this bug. ***
*** Bug 476868 has been marked as a duplicate of this bug. ***
*** Bug 480241 has been marked as a duplicate of this bug. ***