Bug#785472: closed by Hugo Lefeuvre (Non-bug)

2015-05-31 Thread Petr Pudlák
Sorry for not replying sooner. Although I have a solution, I'd definitely not mark it as solved. Parcellite had now an option which is documented in the man page etc, but doesn't work and produces weird error messages. Either the option needs to be fixed, or removed. So my suggestion would be to ke

Bug#785472: [g...@rickyrockrat.net: Bug#785472: parcellite: Parcellite fails to start after upgrading to Jessie]

2015-05-18 Thread Petr Pudlák
Removing '-d' indeed prevents the issue and parcellite works then as expected.

Bug#785472: Acknowledgement (parcellite: Parcellite fails to start after upgrading to Jessie)

2015-05-17 Thread Petr Pudlák
Thank you. One more comment: removing ~/.config/parcellite/parcelliterc has no effect on the issue, so most likely it's not dependent on user's configuration. In any case, I'm attaching mine below: [rc] RCVersion=1 use_copy=true use_primary=true synchronize=true save_history=true history_pos=false

Bug#785472: Acknowledgement (parcellite: Parcellite fails to start after upgrading to Jessie)

2015-05-16 Thread Petr Pudlák
Sorry, I probably somehow lost the detailed information I put into the reporting tool. If I run parcellite in the daemon mode, it prints the clipboard and then spits out errors, approximately 2-3 per second, and this goes on forever: $ parcellite -d Flag 0x0001, status 0, EXIT 1 STAT 0 (parcelli