Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18170 - [inkscape] 0.47 conflicts with clipboard managers
Attached to Project:
Arch Linux
Opened by Robbie Smith (zoqaeski) - Friday, 05 February 2010, 04:31 GMT
Last edited by Dan Griffiths (Ghost1227) - Saturday, 27 February 2010, 01:20 GMT
Opened by Robbie Smith (zoqaeski) - Friday, 05 February 2010, 04:31 GMT
Last edited by Dan Griffiths (Ghost1227) - Saturday, 27 February 2010, 01:20 GMT
|
DetailsDescription:
Inkscape makes an incorrect call to output plugins. This occurs when a clipboard manager, such as xfce4-clipman-plugin 1.1.3, is also running. Additional info: The bug was reported to Inkscape: https://bugs.launchpad.net/inkscape/+bug/418242 (Even though it's more of an upstream bug, this would probably be helpful for others to know.) Steps to reproduce: Select an object in Inkscape, and attempt to copy it. An error dialog pops up, complaining about either missing dependencies, or uniconvertor failing due to missing libraries, deprecation of modules, or something like that. Disabling the clipboard manager solves the problem. |
This task depends upon
Closed by Dan Griffiths (Ghost1227)
Saturday, 27 February 2010, 01:20 GMT
Reason for closing: Upstream
Additional comments about closing: Upstream devs know about it, we aren't going to patch it ourselves. This kind of information is probably better suited for the forums.
Saturday, 27 February 2010, 01:20 GMT
Reason for closing: Upstream
Additional comments about closing: Upstream devs know about it, we aren't going to patch it ourselves. This kind of information is probably better suited for the forums.