Re: [qubes-users] bug ?

On Mon, May 17, 2021 at 03:16:10PM +0200, haaber wrote: > Hello, I followed a link in my mailVM-thunderbird, which configured to > open links inside a new tempVM. When I reboot the parent mailVM, the > child-disp-VM dies with it. This is not what I expected. > > Is it some wanted behaviour or a

[qubes-users] bug ?

Hello, I followed a link in my mailVM-thunderbird, which configured to open links inside a new tempVM. When I reboot the parent mailVM, the child-disp-VM dies with it. This is not what I expected. Is it some wanted behaviour or a bug? Cheers -- You received this message because you are

[qubes-users] bug? after cloning fedora32 qube - gnome terminal stop working

Hello, After cloning fedora32 qube - gnome terminal stop working. Is it a bug? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [qubes-users] Bug Thunderbird: kills addons after last update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 scurge1tl: > > > scurge1tl: >> Today's upgrade of Thunderbird to 68.2.2 (64-bit) killed all >> addons in Whonix-ws-15 AppVMs. >> >> Enigmail seems to be already running, but Torbirdy and Qubes >> addon for Attachments opening in a DispVM

Re: [qubes-users] Bug Thunderbird: kills addons after last update

scurge1tl: > Today's upgrade of Thunderbird to 68.2.2 (64-bit) killed all addons in > Whonix-ws-15 AppVMs. > > Enigmail seems to be already running, but Torbirdy and Qubes addon > for Attachments opening in a DispVM disappeared. > > Update. Newly created anon-whonix through sudo qubesctl

[qubes-users] Bug Thunderbird: kills addons after last update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Today's upgrade of Thunderbird to 68.2.2 (64-bit) killed all addons in Whonix-ws-15 AppVMs. Enigmail seems to be already running, but Torbirdy and Qubes addon for Attachments opening in a DispVM disappeared. -BEGIN PGP SIGNATURE-

Re: [qubes-users] [bug] Backup restore: Modal success dialog should not use "Warning" icon

On Thu, May 23, 2019 at 05:07:00AM +, g80vmgm...@riseup.net wrote: > When restoring from backup, successful completion results in a modal > dialog labeled, "Finished successfully!". This dialog uses an > exclamation point-style "Warning" icon. This icon gives the user the > wrong

[qubes-users] [bug] Backup restore: Modal success dialog should not use "Warning" icon

When restoring from backup, successful completion results in a modal dialog labeled, "Finished successfully!". This dialog uses an exclamation point-style "Warning" icon. This icon gives the user the wrong impression. Instead, the icon should be a green checkmark or something similarly

Re: [qubes-users] [Bug?] whonix-ws clock out of synch after suspend (R4.0)

Hello, On 05/15 10:57, Dimitri wrote: > Hi, > I noticed that the clock in whonix-ws based VMs is not synchronized after > sleep mode. If I have my computer in sleep mode for 2h then the VMs clock is > 2h in the past. > To me this looks like a bug. > Large clock skews can potentially harm

Re: [qubes-users] [Bug?] whonix-ws clock out of synch after suspend (R4.0)

On Tue, May 15, 2018 8:47 pm, 799 wrote: > Hello, > > On 05/15 10:57, Dimitri wrote: >> Hi, >> I noticed that the clock in whonix-ws based VMs is not synchronized >> after > sleep mode. If I have my computer in sleep mode for 2h then the VMs clock > is 2h in the past. >> To me this looks like a

Re: [qubes-users] [Bug?] whonix-ws clock out of synch after suspend (R4.0)

Hello, On 05/15 10:57, Dimitri wrote: > Hi, > I noticed that the clock in whonix-ws based VMs is not synchronized after sleep mode. If I have my computer in sleep mode for 2h then the VMs clock is 2h in the past. > To me this looks like a bug. > Large clock skews can potentially harm anonymity.

[qubes-users] [Bug?] whonix-ws clock out of synch after suspend (R4.0)

Hi, I noticed that the clock in whonix-ws based VMs is not synchronized after sleep mode. If I have my computer in sleep mode for 2h then the VMs clock is 2h in the past. To me this looks like a bug. Large clock skews can potentially harm anonymity. -- You received this message because you

[qubes-users] [Bug] Windows closing immediately after opening them in jetbrains java based ide in Qubes 4

I am encountering a bug where the pop up window closes immediately after I open it in jetbrain's pycharm. It does this when I try the auto-correction(alt-enter). Is anyone else encountering this? This is happening in a fresh install of the latest version of Qube OS (4.0 - 5/4/18). -- You

Re: [qubes-users] Bug in qubes-input-sender

On Thu, April 5, 2018 9:38 pm, Andrzej Andrzej wrote: > any idea? Sorry, not specifically but you might want to search https://github.com/QubesOS/qubes-issues/issues for similar ones and/or open a new one if you don't see any. -- You received this message because you are subscribed to the

[qubes-users] Bug in qubes-input-sender

any idea? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to

Re: [qubes-users] Bug (R4.0): VM fail to start after hard power off

On 04/02/2018 05:42 AM, Dimitri wrote: Hi, I realized that some VMs refuse to start after a hard power-off (hold power button for 10s). When running 'qvm-start test' I get 'vm-test-private missing'. But this thin volume is actually there. Also the volume 'vm-test-private-snap' is still

[qubes-users] Bug (R4.0): VM fail to start after hard power off

Hi, I realized that some VMs refuse to start after a hard power-off (hold power button for 10s). When running 'qvm-start test' I get 'vm-test-private missing'. But this thin volume is actually there. Also the volume 'vm-test-private-snap' is still present. Does the snapshot not get written back

[qubes-users] Bug in qubes-input-sender

The problem is that after connecting the mouse to the computer, the mouse can run for 10 minutes, then the system disconnects it from sys-usb, and then connects it again without any user interaction. The second problem is that after connecting the keyboard via usb to sys-usb the keyboard does

[qubes-users] bug: qubes vm-manager qubes 3.2 current: Unable to rename VM to "ReactOS-Reference"

bug: qubes vm-manager qubes 3.2 current: Unable to rename VM to "ReactOS-Reference" Problem: I installed reactos into a new standalone template vm and thought I could derive user vms as in linux based. But this did not work, maybe I dont know howto do. So as a work-around I wanted to make a

Re: [qubes-users] Bug in qubes-backup or tar?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 svenssona...@gmail.com: > Emergency recovery of backups as described in > https://www.qubes-os.org/doc/backup-emergency-restore-v3/ states > that tar should be able to unpack a qubes backup file. > > [...] > tar tvf bu/qubes-* > # Shows only

[qubes-users] Bug in qubes-backup or tar?

qvm-backup has a different syntax and vms are excluded from rather than included in a backup. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[qubes-users] Bug in qubes-backup or tar?

Emergency recovery of backups as described in https://www.qubes-os.org/doc/backup-emergency-restore-v3/ states that tar should be able to unpack a qubes backup file. It seems that qvm-backup produces a corrupt tar file, or the included tar has a bug. It seems to include data, but only one file

Re: [qubes-users] Bug with copy and paste to different window

On Fri, Apr 21, 2017 at 5:22 AM, evo wrote: > I have a problem with an appVM based on Fedora24. > I open LibreOffice and Scribus, then i want to copy and paste from > office. But if i copy it from office and go to the scribus-window the > window is not activated... it just

[qubes-users] Bug with copy and paste to different window

Hello! I have a problem with an appVM based on Fedora24. I open LibreOffice and Scribus, then i want to copy and paste from office. But if i copy it from office and go to the scribus-window the window is not activated... it just still acts with the office-window behind the scribus-window... just

[qubes-users] Bug: Qubes installer will not continue beyond probing install media

I believe I have solved this issue, but it was a frustrating experience for me. I tried several USB drives, different OS installs (which worked just fine), and removal of the hardware in the expansion slots to try and figure out the issue. Turns out it was very simple, and I just had to be

Re: [qubes-users] [bug, 3.2, qubes manager] sys-whonix restart

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-04-02 13:45, Eva Star wrote: > Trying to restart running sys-whonix constantly give us this > assert: https://i.imgur.com/YU8sv3H.png > Known issue: https://github.com/QubesOS/qubes-issues/issues/2438 - -- Andrew David Wong (Axon)

[qubes-users] [bug, 3.2, qubes manager] sys-whonix restart

Trying to restart running sys-whonix constantly give us this assert: https://i.imgur.com/YU8sv3H.png -- Regards -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[qubes-users] [bug] qubes-guid crashes when putting debian-9 VM in true XFCE fullscreen

Hi, Sorry for the verbose title. If I put a debian-9 VM in true fullscreen in XFCE, I get a short hang, then the window disappears. The VM then goes 'yellow', and while I can xl console into the VM, I lose all windows. The GUID log has: ErrorHandler: BadAccess (attempt to access private

Re: [qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC

On Sunday, January 8, 2017 at 12:14:17 PM UTC-5, Grzesiek Chodzicki wrote: > W dniu niedziela, 8 stycznia 2017 18:03:47 UTC+1 użytkownik Andrew David Wong > napisał: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > On 2017-01-08 08:30, Grzesiek Chodzicki wrote: > > > I know that

Re: [qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC

W dniu niedziela, 8 stycznia 2017 18:03:47 UTC+1 użytkownik Andrew David Wong napisał: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2017-01-08 08:30, Grzesiek Chodzicki wrote: > > I know that this sounds rather bizarre, but my Qubes instance > > consistently gets stuck after GRUB

Re: [qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-08 08:30, Grzesiek Chodzicki wrote: > I know that this sounds rather bizarre, but my Qubes instance > consistently gets stuck after GRUB menu if a USB Audio device is > connected to the computer. So far I have a 3/3 repro rate on that. >

[qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC

I know that this sounds rather bizarre, but my Qubes instance consistently gets stuck after GRUB menu if a USB Audio device is connected to the computer. So far I have a 3/3 repro rate on that. What type of logs/information should I gather from my machine in order to troubleshoot that? XL dmesg

Re: [qubes-users] Bug or Feature? DispVM inherits settings from calling VM

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-12 01:50, Robert Mittendorf wrote: > If I use /usr/bin/qvm-run to open an application in an disposible VM, the > dispVM inherits some setings from the calling VM > > example: I use > > /usr/bin/qvm-run --dispvm firefox > > In work-VM.

[qubes-users] Bug or Feature? DispVM inherits settings from calling VM

If I use /usr/bin/qvm-run to open an application in an disposible VM, the dispVM inherits some setings from the calling VM example: I use /usr/bin/qvm-run --dispvm firefox In work-VM. My work-VM is configured to allow intranet IPs only. The starting dispVM is blue like the work VM, even

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

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 >

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

-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?

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

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

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

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,

Re: [qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

-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.

[qubes-users] [bug] Inter-VM Copy/Paste Broken After Long Uptime

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