Package: xfce4-clipman
Version: 2:1.4.1-1
Severity: important
Dear Maintainer,
Dear Maintainer,
First and as always, #ThankYOU for the work you do!!
Now for the *potential* bug: I don't know when this started occurring. I copy
and paste so many things that it could have been existing for a while, and I'd
never know because Xfce4-Clipman is always already quite full when I need to
use it, grin.
Expected behavior *for me* is that CTRL+C history remain viable from one reboot
to the next. I *thought* it used to do that at some point, but it's possible
I'm confusing it with something else.
Just now I right clicked over its icon and quickly found an option to toggle
being able to save current history upon *QUIT*. I do see the distinction
between manually shutting it down versus letting it have its own mind when
rebooting.
My potentially naive expectation is that Xfce4-Clipman would retain a current
session's history without the further intervention of having to remember to
shut it down just before rebooting. That expectation is primarily because
Xfce4-Clipman works so *visually* silent in the background that shutting it
down is easy to overlook as a checkpoint just prior to rebooting.
For the record k/t many years of experience, I do, yes, know well, sometimes
quite painfully, grin, how many, if not most, clipboards working behind the
scenes notoriously purge on reboots. To that end, you're welcome to shift this
over to a wish list item if it seems more appropriate k/t Xfce4-Clipman's
history of design and intended features.
If you go that route, something just occurred to me
For *me*, it would be nice to have Xfce4-Clipman *ask* if I want to save a
current session's history just prior to rebooting. Just as many things do, that
could be... something that could be toggled on and off just as QUIT is now.
In a perfect World, Xfce4-Clipman could provide the opportunity to have a popup
"save or don't to save" message the way some other programs do. Existing
example is how a browser just halted being closed down while it waited for me
to decide "yes or no" if I wanted to close down one tab of many where I had
started to write a message that was never completed and sent.
Thank you again. Best wishes in all you do!
PS I'll try to remember to manually shut it down for the next reboot in the
next few days. If it does *not* retain history then, I'll come back and update.
I anticipate that I will probably not have to update in that case. :)
PPS Reportbug proffered that there are potential updates available, BUT those
are from testing and unstable. What I will do is... leave it as is for the next
reboot when I hope to remember to use QUIT first.
For some reboot after that, I'll try to THEN remember to test the other
releases' versions to see how they handle for the above. That crosses into that
whole mixing and matching between releases which starts that snowball rolling
of having to update other packages/dependencies, too, but who knows, maybe
something will come of it. I'm game. The fix is always only one backup or new
debootstrap installation away. :)
Cindy Sue Causey
Talking Rock, Pickens County, Georgia
* runs with duct tape *
-- System Information:
Debian Release: 9.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages xfce4-clipman depends on:
ii libc6 2.24-11+deb9u1
ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u1
ii libglib2.0-02.50.3-2
ii libgtk-3-0 3.22.11-1
ii libqrencode33.4.4-1+b2
ii libx11-62:1.6.4-3
ii libxfce4ui-2-0 4.12.1-2
ii libxfce4util7 4.12.1-3
ii libxfconf-0-2 4.12.1-1
ii libxtst62:1.2.3-1
xfce4-clipman recommends no packages.
xfce4-clipman suggests no packages.
-- no debconf information
