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 485507 - crash in Text Editor: choosing print page size...
crash in Text Editor: choosing print page size...
Status: RESOLVED DUPLICATE of bug 405900
Product: gedit
Classification: Applications
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-10 20:20 UTC by RLJACK57
Modified: 2007-10-13 18:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description RLJACK57 2007-10-10 20:20:46 UTC
Version: 2.18.0

What were you doing when the application crashed?
choosing print page size.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 69226496 vsize: 69226496 resident: 22982656 share: 13606912 rss: 22982656 rss_rlim: 4294967295
CPU usage: start_time: 1192036382 rtime: 190 utime: 171 stime: 19 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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 -1208682784 (LWP 3847)]
(no debugging symbols found)
0x00323402 in __kernel_vsyscall ()

Thread 1 (Thread -1208682784 (LWP 3847))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gpa_node_set_path_value
    from /usr/lib/libgnomeprint-2-2.so.0
  • #5 gnome_print_config_set
    from /usr/lib/libgnomeprint-2-2.so.0
  • #6 gnome_print_config_set_int
    from /usr/lib/libgnomeprint-2-2.so.0
  • #7 ??
  • #8 g_cclosure_marshal_VOID__PARAM
    from /lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /lib/libgobject-2.0.so.0
  • #15 g_object_newv
    from /lib/libgobject-2.0.so.0
  • #16 g_object_new_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_object_new
    from /lib/libgobject-2.0.so.0
  • #18 gedit_print_job_new
  • #19 _gedit_cmd_file_print
  • #20 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #21 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #22 ??
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_action_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #28 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #29 ??
    from /lib/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #31 g_signal_emit_by_name
    from /lib/libgobject-2.0.so.0
  • #32 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #34 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #35 ??
    from /lib/libgobject-2.0.so.0
  • #36 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #37 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #38 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #41 ??
    from /lib/libgobject-2.0.so.0
  • #42 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #43 ??
    from /lib/libgobject-2.0.so.0
  • #44 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #45 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #46 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 ??
    from /lib/libgobject-2.0.so.0
  • #50 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #51 ??
    from /lib/libgobject-2.0.so.0
  • #52 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #53 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #54 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #56 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #57 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #58 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #59 ??
    from /lib/libglib-2.0.so.0
  • #60 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #61 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #62 main
  • #0 __kernel_vsyscall

No plugin installed in $HOME.





----------- .xsession-errors (21 sec old) ---------------------
** (gedit:3847): WARNING **: Writing output pipe failed
** (gedit:3847): WARNING **: Writing output pipe failed
** (gedit:3847): WARNING **: Writing output pipe failed
** (gedit:3847): WARNING **: Writing output pipe failed
** (gedit:3847): WARNING **: Writing output pipe failed
** (gedit:3847): WARNING **: Writing output pipe failed
** (gedit:3847): WARNING **: Writing output pipe failed
(gedit:3847): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GnomePrintConfig'
--------------------------------------------------
Comment 1 Christoph Wolk 2007-10-12 12:13:39 UTC
Thank you for reporting this bug. It look like a duplicate of bug 405900.
Comment 2 Christoph Wolk 2007-10-13 18:04:49 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 405900 ***