Bug 667900 – no clipboard editing in release 2.4.9

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 667900 - no clipboard editing in release 2.4.9


Summary:	no clipboard editing in release 2.4.9


Status:	RESOLVED FIXED

Product:	GnuCash
Classification:	Other
Component:	User Interface General
Version:	unspecified
Hardware:	Other Windows

Importance:	Normal blocker
Target Milestone:	---
Assigned To:	Christian Stimming
QA Contact:	Geert Janssens

URL:
Whiteboard:

Duplicates:	620968 665699 667923 667988 668177 668303 668354 (view as bug list)
Depends on:
Blocks:

Reported:	2012-01-13 23:07 UTC by David Carlson
Modified:	2018-06-29 23:04 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Trace when editing failed (393 bytes, text/plain) 2012-01-13 23:38 UTC, David Carlson	Details

Description David Carlson 2012-01-13 23:07:59 UTC

I cannot use ctrl-x, ctrl-c, or ctrl-v in the register pane of 2.4.9 in windows XP

using the 'edit' menu at the top menubar, the 'cut' will remove text but copy does not produce paste-able text  If I try to paste to an outside document, there is nothing 'copied'.

This also applies to the scheduled transaction editor.  I do not know if anything appears in the stack trace.  I will check and report if I find something.

Comment 1 David Carlson 2012-01-13 23:38:01 UTC

Created attachment 205231 [details]
Trace when editing failed

I started GnuCash release 2.4.9, highlighted an existing line in an existing transaction, used the up arrow to select the line above, ctrl-c, then arrow down.  Then I tried ctrl-v, saw no change, then arrow up until I left the transaction to the one above.  There was no indication the the transaction had been edited.  Then I closed Gnucash and I am now submitting the automatic trace file from c:\documents and settings\username\local Settings\Temp

Comment 2 David Carlson 2012-01-13 23:42:12 UTC

You can see that there is still no highcolor theme, but I am sure that is not the problem, as that is also missing from build 2.4.8.

Comment 3 André Klapper 2012-01-14 13:27:50 UTC

(In reply to comment #1)
> Created an attachment (id=205231) [details]
> Trace when editing failed

That's not a trace, just a log.

Comment 4 David Carlson 2012-01-14 13:56:56 UTC

I was trying to fol;low the instructions in <http://wiki.gnucash.org/wiki/Windows#gdb>, section 2, Notes.  I quote:
'In the GnuCash application, all error messages are redirected to a trace file. There will be one trace file for each time GnuCash is run. For a user named "myname" these files are located in the folder

    c:\Documents and Settings\myname\Local Settings\Temp (Windows XP) or
    C:\Users\myname\AppData\Local\Temp (Windows Vista/7). 

They are named

    gnucash.trace.ABCDEF (GnuCash 2.2.9 and older) or
    gnucash.trace.ABCDEF.log (GnuCash 2.4.0 and newer) 

where the ABCDEF part is changed randomly on each start of gnucash. See also Tracefile.

If you experience crashes or unexpected behavior, check the latest of these files (or the one created when the problem started) and add all interesting-looking lines of that file to your error reports, at least the lines with the keywords WARNing and CRITical warning. '

The stuff after that gets a little too complicated for me.

Comment 5 David Carlson 2012-01-14 15:50:47 UTC

I tried to run c:\mingw\bin\gdb "C:\Program Files\gnucash\bin\gnucash" but gdb crashed after filling the command window with
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=EXCEPTION_DEBUG_EVENT)
gdb: Target exception EXCEPTION_BREAKPOINT at 0x7c90120e
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=16dc code=CREATE_THREAD_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x16dc
ContinueDebugEvent (cpid=2296, ctid=5852, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=UNLOAD_DLL_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=5852 code=UNLOAD_DLL_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=5852, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=5852 code=EXIT_THREAD_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=5852, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1050 code=CREATE_THREAD_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x1050
ContinueDebugEvent (cpid=2296, ctid=4176, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=4176 code=LOAD_DLL_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=4176, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=4176 code=UNLOAD_DLL_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=4176, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=4176 code=LOAD_DLL_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=4176, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=4176 code=LOAD_DLL_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=4176, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=4176 code=LOAD_DLL_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=4176, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=4176 code=LOAD_DLL_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=4176, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=4176 code=LOAD_DLL_DEBUG_EVENT)
ContinueDebugEvent (cpid=2296, ctid=4176, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 2296.0x700
ContinueDebugEvent (cpid=2296, ctid=1792, DBG_CONTINUE);
gdb: kernel event for pid=2296 tid=1792 code=LOAD_DLL_DEBUG_EVENT)

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

C:\MinGW\bin>

Comment 6 David Carlson 2012-01-14 15:54:45 UTC

now what?

Comment 7 David Carlson 2012-01-14 17:08:42 UTC

That is from the 2005 gdb 6.3-1 referenced in the gnucash wiki.  If I go to mingw there are scads of variations available, mostly way too technical for me.  Is mingw-get-inst-20111118.exe good for a semi-non-technical-but college-educated person to play with?

Comment 8 Geert Janssens 2012-01-15 15:07:39 UTC

*** Bug 667923 has been marked as a duplicate of this bug. ***

Comment 9 Geert Janssens 2012-01-15 15:13:12 UTC

As mentioned in the duplicate bug, the cause is most likely that one of the libraries GnuCash depends on (gtk) has been upgraded in this release. Gtk 2.24.0 unfortunately has some issues on Windows (see also related bug 653995).

The most recent version 2.24.8 should fix this. We should try to get GnuCash on Windows use this version instead.

Comment 10 Geert Janssens 2012-01-15 15:14:07 UTC

@David: for this bug we won't need a backtrace anymore, but thank you for trying to create one.

Comment 11 John Ralls 2012-01-15 21:16:11 UTC

Well, nice theory, but I just tried it out and no joy.

And it isn't exactly the problem from bug 653995, either: I found that the clipboard example in gtk-demo works fine, and that I can successfully copy from Gnucash's register to the clipboard and paste somewhere else (I did emacs, gtk-demo, and Notepad).

Some more experimenting: I can copy from Gnucash's register and paste somewhere else -- but not anywhere in Gnucash. But I can also copy from somewhere else (emacs or gnucash's edit account dialog) and paste back into Gnucash, including into the register.

That offers a workaround, though it's a PITA.

Comment 12 Geert Janssens 2012-01-18 13:06:34 UTC

*** Bug 668177 has been marked as a duplicate of this bug. ***

Comment 13 Geert Janssens 2012-01-19 16:41:14 UTC

(In reply to comment #11)
> Well, nice theory, but I just tried it out and no joy.
> 
> And it isn't exactly the problem from bug 653995, either: I found that the
> clipboard example in gtk-demo works fine, and that I can successfully copy from
> Gnucash's register to the clipboard and paste somewhere else (I did emacs,
> gtk-demo, and Notepad).
> 
> Some more experimenting: I can copy from Gnucash's register and paste somewhere
> else -- but not anywhere in Gnucash. But I can also copy from somewhere else
> (emacs or gnucash's edit account dialog) and paste back into Gnucash, including
> into the register.
> 
Are these experiments all with Gtk 2.24.8 ?

At least for me here with the stock GnuCash 2.4.9 (which uses Gtk 2.24.0), I have a slightly different experience:
- I can't copy *from* the GnuCash register to anywhere at all.
- I can copy and paste to/from any other field found in gnucash (for example the text fields in File->Properties->Business, text fields in the various dialogs).
- I can copy from anywhere (except to registers) *to* a register.

So for me only the copy action in the register isn't working as it should. Pasting into the register is fine as is copying in any other part of gnucash.

Comment 14 John Ralls 2012-01-19 18:12:17 UTC

Yes, with Gtk 2.24.8, to get the fix for 653995.

Comment 15 Geert Janssens 2012-01-20 13:18:58 UTC

*** Bug 668303 has been marked as a duplicate of this bug. ***

Comment 16 Geert Janssens 2012-01-20 16:33:07 UTC

*** Bug 668354 has been marked as a duplicate of this bug. ***

Comment 17 Geert Janssens 2012-01-20 23:25:22 UTC

*** Bug 667988 has been marked as a duplicate of this bug. ***

Comment 18 Geert Janssens 2012-01-22 21:05:15 UTC

*** Bug 665699 has been marked as a duplicate of this bug. ***

Comment 19 Geert Janssens 2012-01-22 21:06:16 UTC

Note that although this bug was reported against 2.4.9, bug 655699 show the problem also exists on trunk, so we have to deal with it in both branches.

Comment 20 John Ralls 2012-01-22 22:03:17 UTC

No surprise there. This is code that hasn't been touched in years.

So far I've figured out that the GtkSelectionData which has its data and type set in gnc_item_edit_selection_get() isn't the same one received in gnc_item_edit_selection_received(), and that while the latter one has the data set correctly the first time I try it in the debugger, the type is never right, and that's what's causing the paste to fail.

Beyond that I'm struggling because I can't debug into Gtk and Gdk to see what's actually going wrong (no symbols or sources in the downloaded binaries).

Comment 21 John Ralls 2012-01-25 06:18:15 UTC

Fixed, I think, in r21886. I hope I made it in time for tonight's build.

The underlying problem is a bit complicated: First off, there was a Gtk bug that was fixed last June. Then, in Win32, a clipboard save is transferred to the Win32 clipboard (good), but when it comes time to retrieve it, gtk_selection_convert first looks to see if there's a valid selection owner for the clipboard. The catch is that when a register edit cell gets focus it calls gtk_editable_set_selection, which resets the selection to itself (this is the widget we want to copy *to*, remember), and it doesn't have a valid clipboard selection, so there's nothing to transfer. (There are timing issues involved as well, apparently, because I did manage to get it to work a couple of times in the debugger.)

I finessed the problem by switching the implementation for the clipboard from using gtk_selection directly to using the gtk_clipboard wrapper, which is what all of the Gtk widgets do as well. It seems to work, but I didn't test it very hard, so grab the nightly tomorrow morning (sure hope it makes it in) and wring it out a bit while I work on remodeling a house for Habitat. If it does indeed work I'll convert the GDK_SELECTION_PRIMARY parts as well.

Comment 22 Christian Stimming 2012-01-25 07:13:13 UTC

(In reply to comment #21)
> Fixed, I think, in r21886. I hope I made it in time for tonight's build.

Thanks a lot! Does this issue also need to be changed in trunk? However, I guess you've already been watching out for necessary changes in trunk, so I guess you will do that if necessary.

Comment 23 John Ralls 2012-01-25 14:31:06 UTC

In the nightly build, it picked up the change to Gtk+-2.24.8, but doesn't appear from the log to have rebuilt gnc-item-edit.c

Comment 24 John Ralls 2012-01-25 14:37:50 UTC

Never mind, I looked in the wrong place. It built, so please D/L the nightly from http://code.gnucash.org/builds/win32/2.4/gnucash-2.4.9-svn-r21886-setup.exe
and give it a go.

Comment 25 Ian K 2012-01-25 20:39:38 UTC

(In reply to comment #24)
> Never mind, I looked in the wrong place. It built, so please D/L the nightly
> from
> http://code.gnucash.org/builds/win32/2.4/gnucash-2.4.9-svn-r21886-setup.exe
> and give it a go.

I have installed this build and cut/copy/paste seems to work fine now for me, thanks.
Incidentally, the blacking out of tabs on the MS-Windows theme reported in my bug (marked as duplicate of this) seems to have been fixed too.

Comment 26 John Ralls 2012-01-26 19:23:05 UTC

*** Bug 620968 has been marked as a duplicate of this bug. ***

Comment 27 cmgd 2012-01-29 10:36:46 UTC

(In reply to comment #25)
> (In reply to comment #24)
> > Never mind, I looked in the wrong place. It built, so please D/L the nightly
> > from
> > http://code.gnucash.org/builds/win32/2.4/gnucash-2.4.9-svn-r21886-setup.exe
> > and give it a go.
> 
> I have installed this build and cut/copy/paste seems to work fine now for me,
> thanks.
> Incidentally, the blacking out of tabs on the MS-Windows theme reported in my
> bug (marked as duplicate of this) seems to have been fixed too.

I made several tests with this build, not only with the cut/paste, and everything seems to work fine.

Comment 28 David Carlson 2012-01-29 16:40:19 UTC

The build http://code.gnucash.org/builds/win32/2.4/gnucash-2.4.9-svn-r21886-setup.exe still causes the duplicate report error message when installed over release 2.4.8 without uninstalling first.  I do not know if that build was intended to address that issue.

David C

Comment 29 John Ralls 2012-01-29 17:16:42 UTC

It wasn't, but the latest one, http://code.gnucash.org/builds/win32/2.4/gnucash-2.4.10-svn-r21911-setup.exe, should. Please test it.

Comment 30 John Ralls 2012-01-30 01:57:51 UTC

Fix has been forward-ported to trunk (r21918).

Comment 31 David Carlson 2012-01-30 04:49:50 UTC

It did not trigger the duplicate report error.  I like the option to stop before deleting the old install.  Hopefully that is the one for this issue.

Comment 32 Ian K 2012-01-30 10:25:01 UTC

(In reply to comment #29)
> It wasn't, but the latest one,
> http://code.gnucash.org/builds/win32/2.4/gnucash-2.4.10-svn-r21911-setup.exe,
> should. Please test it.

I installed this version over the top of 2.4.8 on Windows XP Pro x86. Everything fine - got the 'previous version found' message, proceeded and uninstalled/installed. No errors, and clipboard editing working.

Comment 33 Geert Janssens 2012-02-02 14:00:10 UTC

(In reply to comment #31)
> It did not trigger the duplicate report error.  I like the option to stop
> before deleting the old install.  Hopefully that is the one for this issue.

This issue was fixed exactly by automatically deleting the old version. If you want an option to stop (which I can partly understand), that would be a new enhancement request. Please create a new bug report for it. Thank you.

Comment 34 John Ralls 2018-06-29 23:04:55 UTC

GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=667900. Please update any external references or bookmarks.