GNOME Bugzilla – Bug 125700
gcm crashes when trying to edit a clipboard entry
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: gcm Severity: normal Version: unspecified Synopsis: gcm crashes when trying to edit a clipboard entry Bugzilla-Product: gcm Bugzilla-Component: gcmapplet Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Double-clicking on a clipboard entry in the "Clipboard" window causes a crash. Steps to reproduce the crash: 1. Copy something to the clipboard 2. Right-click on panel icon and select "Clipboard" 3. Double-click on the entry Expected Results: Editing window should pop up. How often does this happen? Everytime. Additional Information: 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 16384 (LWP 13476)] [New Thread 32769 (LWP 13479)] [New Thread 16384 (LWP 13476)] [New Thread 32769 (LWP 13479)] [New Thread 16384 (LWP 13476)] [New Thread 32769 (LWP 13479)] [New Thread 16386 (LWP 13480)] (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)... 0x408f7ab6 in waitpid () from /lib/libpthread.so.0
+ Trace 41249
Thread 1 (Thread 16384 (LWP 13476))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-28 11:48 ------- The original reporter (gberenfield@handhelds.org) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, me@freax.org.
If this bug still happens, please refer to bug 103742 *** This bug has been marked as a duplicate of 103742 ***