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 137852 - gcm crash after pasting with recently emptied clipboard
gcm crash after pasting with recently emptied clipboard
Status: RESOLVED DUPLICATE of bug 123725
Product: gcm
Classification: Deprecated
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Philip Van Hoof
Philip Van Hoof
Depends on:
Blocks:
 
 
Reported: 2004-03-21 14:36 UTC by Erik Meitner
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Erik Meitner 2004-03-21 14:36:41 UTC
Distribution: Debian testing/unstable
Package: gcm
Severity: major
Version: GNOME2.4.1 unspecified
Gnome-Distributor: Debian
Synopsis: gcm crash after pasting with recently emptied clipboard
Bugzilla-Product: gcm
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
Gcm crashes when a paste operation is performed right after emptying the
clipboard of all entries.

Steps to reproduce the crash:
1. In an application, select some text and copy it
2. Open gcmui
3. Select all entries and delete them
4. In an application do a paste

Expected Results:
Gcm ignores the paste from an empty clipboard

How often does this happen?
Every time.

Additional Information:
Debian(testing)
Gnome 2.4.1
Gcm package version: 2.1.0+20031016.1-2



Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1087131776 (LWP 3317)]
[New Thread 1095723952 (LWP 3318)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x408e3411 in __waitpid_nocancel ()
   from /lib/tls/libpthread.so.0

Thread 1 (Thread 1087131776 (LWP 3317))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 valid
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_list_copy
    from /usr/lib/libglib-2.0.so.0
  • #4 gcm_decompress_selection
    from /usr/lib/libgcm.so.0
  • #5 clipboard_get_selection_cb
  • #6 gtk_clipboard_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 _gtk_marshal_VOID__BOXED_UINT_UINT
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #12 _gtk_selection_property_notify
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 _gtk_selection_request
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 gtk_widget_send_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #23 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 main
  • #29 __libc_start_main
    from /lib/tls/libc.so.6
  • #30 ??
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-21 09:36 -------

Reassigning to the default owner of the component, me@freax.org.

Comment 1 Olav Vitters 2004-07-27 19:22:56 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 123725 ***