Thunar can not paste, if xclipboard is running

Bugs without a package

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME = thunar.

But how do you classify a bug once you know the associated package?

I found the input field on the bug report dialog, but it doesn't help if you want to change/set the package name afterwards.

Thank you for your bug report. I'll investigate this. To change the package affected, click on the Arrow in the status field, a few fields will appear. Among them there is a "package" field.

Waht do you mean by Thunar cannot paste ? You can't copy/paste a file ? It happens with every file ? Is there something about this in ~/.xsession-errors ?

Actually, I suppose Thunar can not copy and cut files, so there is nothing to paste. No success with any file I have tried. I just tried that it is the same thing with Nautilus, but emelfm can copy and move. So the problem may be in xclipboards way to interfere to clipboard system. I think there is nothing about it in ~/.xsession-errors.

This seems to be a bug in xclipboard, if it also fails in nautilus. Assigning this to xclipboard.

Hi jarnos,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.