On Thursday, 21 July 2016 08:28:29 UTC+10, Andrew David Wong wrote:
> > Also, are there other known problems with running Qubes with a such a
> > "long" uptime?
> >
>
> This and the Qubes Manager memory leak are the only two I know of.
>
> https://github.com/QubesOS/qubes-issues/issues/860
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-07-20 01:23, Holger Levsen wrote:
> Hi,
>
> On Tue, Jul 19, 2016 at 09:54:19PM +0200, Marek Marczykowski-Górecki
> wrote:
>>> I have one particular Qubes instance with an uptime >60 days. Aside
> [...]
>>> Any suggestions on how to debug?
Hi,
On Tue, Jul 19, 2016 at 09:54:19PM +0200, Marek Marczykowski-Górecki wrote:
> > I have one particular Qubes instance with an uptime >60 days. Aside
[...]
> > Any suggestions on how to debug?
>
> Yes, remove /var/run/qubes/qubes-clipboard.bin.xevent
>
> The file contains X event timestamp
Marek Marczykowski-Górecki:
> On Tue, Jul 19, 2016 at 01:13:22PM +, Andrew wrote:
>> Hello,
>
>> I have one particular Qubes instance with an uptime >60 days.
>> Aside from needing to occasionally restart Qubes Manager to deal
>> with the memory leak problem, this works fine.
>
>> However,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Jul 19, 2016 at 01:13:22PM +, Andrew wrote:
> Hello,
>
> I have one particular Qubes instance with an uptime >60 days. Aside
> from needing to occasionally restart Qubes Manager to deal with the
> memory leak problem, this works fine.
Hello,
I have one particular Qubes instance with an uptime >60 days. Aside
from needing to occasionally restart Qubes Manager to deal with the
memory leak problem, this works fine.
However, recently, I have become unable to copy and paste between VMs.
Pressing the key combination appears to do
