Opened 11 years ago
Last modified 11 years ago
#39372 new defect
xournal: copy and paste don't work
Reported by: | wally@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | cooljeanius (Eric Gallager) | |
Port: | xournal |
Description
Copy and paste don't for xournal. As a test tried inkscape which worked fine. After that xournal actually pasted inkscape's latest paste.
Change History (9)
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|---|
Summary: | copy and paste don't work → xournal: copy and paste don't work |
comment:2 follow-up: 5 Changed 11 years ago by wally@…
I checked, if I reboot it works fine, but the moment I cut and paste with any other application, xournal uses the most recent paste from that rather than its own.
comment:3 follow-up: 4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
I don't think I know how to help you with this. We just compile the software as distributed by its developers. If the software doesn't work, you should take that up with the developers.
comment:4 Changed 11 years ago by wally@…
Replying to ryandesign@…:
I don't think I know how to help you with this. We just compile the software as distributed by its developers. If the software doesn't work, you should take that up with the developers.
Thanx---that's just what the developer said but in reverse -- but fair enough;-)
comment:5 follow-up: 6 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to wally@…:
I checked, if I reboot it works fine, but the moment I cut and paste with any other application, xournal uses the most recent paste from that rather than its own.
It’s not entirely clear to me what behavior you’re expecting.
comment:6 follow-up: 7 Changed 11 years ago by wally@…
Replying to larryv@…:
Replying to wally@…:
I checked, if I reboot it works fine, but the moment I cut and paste with any other application, xournal uses the most recent paste from that rather than its own.
It’s not entirely clear to me what behavior you’re expecting.
If I copy an object in xournal, then that object is what I would like to paste (not whatever has most recently been copied by some other application). I think xournal is getting confused about where to save copied objects, for example, it was complaining that .share/... did not exist.
comment:7 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to wally@…:
Replying to ryandesign@…:
I don't think I know how to help you with this. We just compile the software as distributed by its developers. If the software doesn't work, you should take that up with the developers.
Thanx---that's just what the developer said but in reverse -- but fair enough;-)
Why did the developers think this was a MacPorts problem? Is there something they believe we should be doing to fix this?
Replying to wally@…:
If I copy an object in xournal, then that object is what I would like to paste (not whatever has most recently been copied by some other application). I think xournal is getting confused about where to save copied objects, for example, it was complaining that .share/... did not exist.
Is that a literal quote from the error message? If not, what is the actual path that it complained did not exist? Does that path in fact exist on your disk? If not, have you tried creating that directory, and if so, did that change the error message?
comment:8 Changed 11 years ago by wally@…
I did try creating that directory--didn't help. However, did find a workaround. In X11 preferences, if you disable syncing under pasteboard, then the issue goes away. (However, you do lose the ability to copy text with cmd c from a native apple app to an X one with ctrl v
Thanks for the ticket. In the future, please Cc relevant port maintainers.