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 371362 - crash in Text Editor: i was trying to change t...
crash in Text Editor: i was trying to change t...
Status: RESOLVED DUPLICATE of bug 360792
Product: gedit
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-06 03:46 UTC by darthchunky
Modified: 2006-11-06 09:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description darthchunky 2006-11-06 03:46:11 UTC 
Version: 2.16.1

What were you doing when the application crashed?
i was trying to change the sudoers file in the etc folder so that firestarter firewall could be opened automatically on log in.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 45961216 vsize: 0 resident: 45961216 share: 0 rss: 22298624 rss_rlim: 0
CPU usage: start_time: 1162783757 rtime: 0 utime: 84 stime: 0 cutime:78 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227479376 (LWP 17236)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 83479

Thread 1 (Thread -1227479376 (LWP 17236))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 bacon_message_connection_new
  • #6 _gedit_app_get_window_in_workspace
  • #7 _start
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-11-06 09:16:37 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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