GNOME Bugzilla – Bug 103742
When pressing the Edit-button on a selection, it crashes
Last modified: 2018-07-12 00:04:57 UTC
Package: gcm Severity: normal Version: 2.0.4 Synopsis: When pressing the Edit-button on a selection, it crashes Bugzilla-Product: gcm Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? Everytime. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gcm' (no debugging symbols found)...[New Thread 8192 (LWP 21555)] [New Thread 16385 (LWP 21556)] [New Thread 8194 (LWP 21557)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 32843
Thread 1 (Thread 8192 (LWP 21555))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-17 08:07 ------- Reassigning to the default owner of the component, me@freax.org.
I can confirm this bug - GNOME Clipboard Manager *always* crashes if I press "Edit" button :( I'm using gcm 2.0.4 on Debian 3.0 (Woody). Btw, maybe gcm can have "autosave" option ? I noticed, that gcm atomatically saves all clipboad history when I logout of Gnome and automatically restores when I login again. It would be nice if there would be an option in preferences "autosave when new clipboard item is added". Then crashes would not so irritating...
Also I think Severity of this bug should be set at least to major and priority should be at least High. Dag, it would be nice if you increase severity and priority.
*** Bug 117973 has been marked as a duplicate of this bug. ***
*** Bug 125700 has been marked as a duplicate of this bug. ***
# Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces. #
*** Bug 134946 has been marked as a duplicate of this bug. ***
Is there a point in having this report open still? I seem to remember the maintainer discontinuing work on gcm because there were larger issues that needed to be addressed wrt clipboard handling on the whole?
For me (former maintainer) there's no point. I wouldn't object to closing this bug
gcm is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gcm/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.