Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL
On Thu, 22 Feb 2024 22:19:21 +0100
Ulrich Windl wrote:
>On 2/22/24 22:15, Ulrich Windl wrote:
>> On 2/22/24 21:54, 'Stuart Perkins' via qubes-users wrote:
>>>
>>> On Thu, 22 Feb 2024 21:25:18 +0100
>>> Ulrich Windl wrote:
>>>
>>>> Hi!
>>>>
>>>>
>>>> I managed to configure Thunderbird to run any links via a DVM. However
>>>> today I realized that URLs with parameters are truncated (Qubes-OS 4.2)
>>>> after the first parameter it seem.
>>>>
>>>> For example I have the URL
>>>> ../viewtopic.php?f=21&t=196913&p=1023049&e=1023049
>>>>
>>>> When I view it in Firefox, the URL bar has only .../viewtopic.php?f=21
>>>>
>>>> Unfortunately I have no idea how to debug or fix that.
>>>>
>>>>
>>>> Kind regards,
>>>>
>>>> Ulrich
>>>>
>>> Easy work around. Setup your "default browser" to be "open in vm".
>>>
>> I'm confused: The URL _is_ opened in a VM; the issue is that the URL
>> being passed in truncated after the first parameter it seems.
>>
>> https and https content type is redirected to a "run-vm-firefox" that
>> contains:
>>
>> #!/bin/bash
>> qvm-run-vm '$dispvm' /bin/firefox "$1"
>>
>> I would guess that qvm-run-vm has a quoting problem.
>>
>>
>> I see that qvm-run-vm passes the parameter correctly to
>> /usr/lib/qubes/qrun-in-vm.
>>
>> I don't know python, but these lines seems to have a problem:
>>
>> cmd = ' '.join(sys.argv[1:])
>> sys.stdout.write("exec bash -c '%s' || exit 127\n" % cmd.replace("'",
>> "'\\''"))
>>
>
>Here's my test result:
>
>$ sh -x /usr/bin/qvm-run-vm @dispvm
>"../viewtopic.php?f=21&t=196913&p=1023049&e=1023049"
>+ getopt -o htd --long help,no-gui,dispvm -n /usr/bin/qvm-run-vm --
>@dispvm ../viewtopic.php?f=21&t=196913&p=1023049&e=1023049
>+ OPTS= -- '@dispvm' '../viewtopic.php?f=21&t=196913&p=1023049&e=1023049'
>+ eval set -- -- '@dispvm'
>'../viewtopic.php?f=21&t=196913&p=1023049&e=1023049'
>+ set -- -- @dispvm ../viewtopic.php?f=21&t=196913&p=1023049&e=1023049
>+ [ 3 -gt 0 ]
>+ shift
>+ break
>+ [ != 1 ]
>+ [ 2 -lt 2 ]
>+ [ = 1 ]
>+ [ != 1 ]
>+ VMNAME=@dispvm
>+ shift
>+ service=qubes.VMShell
>+ [ != 1 ]
>+ service=qubes.VMShell+WaitForSession
>+ exec /usr/lib/qubes/qrexec-client-vm @dispvm
>qubes.VMShell+WaitForSession /usr/lib/qubes/qrun-in-vm
>./viewtopic.php?f=21&t=196913&p=1023049&e=1023049
>bash: line 1: ../viewtopic.php?f=21: No such file or directory
>
Presuming xfce4...
bash-5.2# pwd
/home/user/.config
bash-5.2# cat mimeapps.list
[Default Applications]
text/html=qvm-open-in-dvm.desktop
x-scheme-handler/http=qvm-open-in-dvm.desktop
x-scheme-handler/https=qvm-open-in-dvm.desktop
x-scheme-handler/about=qvm-open-in-dvm.desktop
x-scheme-handler/unknown=qvm-open-in-dvm.desktop
application/pdf=org.gnome.Evince.desktop
application/sql=org.gnome.TextEditor.desktop
[Added Associations]
text/plain=org.gnome.gedit.desktop;
application/pdf=gimp.desktop;pdfmod.desktop;org.gnome.Evince.desktop;
image/jpeg=gimp.desktop;display-im6.q16.desktop;
image/png=gimp.desktop;
application/sql=org.gnome.TextEditor.desktop;
bash-5.2#
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/20240222174150.235b3f21%40yahoo.com.
Re: [qubes-users] issue with URL handler in Thunderbird: started VM receives truncated URL
On Thu, 22 Feb 2024 21:25:18 +0100 Ulrich Windl wrote: >Hi! > > >I managed to configure Thunderbird to run any links via a DVM. However >today I realized that URLs with parameters are truncated (Qubes-OS 4.2) >after the first parameter it seem. > >For example I have the URL >../viewtopic.php?f=21&t=196913&p=1023049&e=1023049 > >When I view it in Firefox, the URL bar has only .../viewtopic.php?f=21 > >Unfortunately I have no idea how to debug or fix that. > > >Kind regards, > >Ulrich > Easy work around. Setup your "default browser" to be "open in vm". -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20240222155458.67e22852%40yahoo.com.
Re: [qubes-users] Re: Beginner questions
Bottom post is the standard on this list. See my response at the bottom... :) On Thu, 25 May 2023 19:02:23 + "'sonnenfinsternis' via qubes-users" wrote: >Sounds helpful, I'll try it when I get a chance, thanks :) After reading this >[1], I can now even use my USB mouse directly after booting, without having to >assign it to dom0 first. So slowly but surely I'm warming up to QubesOS. A >wonderful system :) Now if I can just find a way to see how much processor >load and memory is currently being used globally, I'll have all the pressing >open construction sites taken care of for the time being. Over the weekend I >will switch to a QubesOS installation as my new device for daily use. I am >excited and glad that this project exists with this great community :) > >1: https://www.qubes-os.org/doc/usb-qubes/#usb-mice > >--- Original Message --- >On Thursday, May 25th, 2023 at 8:39 AM, haaber wrote: > > >> Hi >> >> > 5) The question about autocomplete in the terminal has been resolved. This >> > was indeed not due to QubesOS but to the fact that >> >> the bash-completion package is not pre-installed by default in Debian. >> But this can be easily fixed: >> https://unix.stackexchange.com/questions/312456/debian-apt-not-apt-get-autocompletion-not-working >> >> I have a nice working auto-complete for dom0. It allows usual >> qvm-commands (qvm-start, qvm-stop, etc) in dom0 terminal and >> distinguishes between running and non-running VM's according to what the >> command expects. Like: qvm-shutdown [TAB] proposes only running VM's to >> be shut down. etc. >> >> Works like charm since qubes 3.2. You find the code attached. >> >> Bernhard >> >> -- >> 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 view this discussion on the web visit >> https://groups.google.com/d/msgid/qubes-users/023ce574-96ab-7f94-21d6-4726c1801ce1%40web.de. >> > Welcome to Qubes OS. Personally, I love it. Even with the occasional awkward way of doing something which is "point and click" on other OS's. The added security of separation of programs and data plus template based VM's is great. I've been a Qubes OS fan since 3.2. Add in a coreboot'd platform and it is about the most secure PC available on the planet. A friend of mine who built me such a laptop...2 actually (Lenovo T520 and a T420) was asked by the country of Spain to build them 40. He has since dropped off the radar for some reason. My current platform is marginally Qubes compatible...a Lenovo W540...with no SSD it is very slow to come up, but works well once running. I don't believe it can be coreboot'd though, so I will be creating another T420 for daily use. I am limited to pre "blob" architectures if I want coreboot with no "blobs"...encrypted microcode "black box" portions of the BIOS, but that is really separate from Qubes OS. I actually wore out the T520 and previous T420 I had...but mine is "on" 16 hours a day or more...sometimes I just leave it on when I go to bed...that is not really a surprise. I found myself synthesizing the basic concept of template VM's manually with VirtualBox before I discovered Qubes. In a Dom0 terminal, the command "xentop" will list running qubes and the resources they are consuming. It is a faster refresh than the GUI Qube Manager. Stuart 42 years in IT. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20230525222440.694ef12c%40yahoo.com.
Re: [qubes-users] Fedora 36 reaches EOL on 2023-05-16
On Thu, 11 May 2023 15:20:17 -0700 Andrew David Wong wrote: >Dear Qubes Community, > >The Fedora Project has >[announced](https://lists.fedoraproject.org/archives/list/annou...@lists.fedoraproject.org/thread/4GXBZJSGQ2PEKIBM2APCTLXBS6IDKSOP/) > that Fedora 36 will reach EOL >([end-of-life](https://fedoraproject.org/wiki/End_of_life)) on 2023-05-16. We >strongly recommend that all users >[upgrade](https://www.qubes-os.org/doc/templates/fedora/#upgrading) their >Fedora templates and standalones to [Fedora >37](https://www.qubes-os.org/news/2023/03/03/fedora-37-templates-available/) >no later than 2023-05-16. > >We provide fresh Fedora 37 template packages through the official Qubes >repositories, which you can install in dom0 by following the standard >[installation >instructions](https://www.qubes-os.org/doc/templates/fedora/#installing). >Alternatively, we also provide step-by-step instructions for [performing an >in-place >upgrade](https://www.qubes-os.org/doc/templates/fedora/in-place-upgrade/) of >an existing Fedora template. After upgrading your templates, please remember >to [switch all qubes that were using the old template to use the new >one](https://www.qubes-os.org/doc/templates/#switching). > >For a complete list of template releases that are supported for your specific >Qubes release, see our [supported template >releases](https://www.qubes-os.org/doc/supported-releases/#templates). > >Please note that no user action is required regarding the OS version in dom0. >For details, please see our [note on dom0 and >EOL](https://www.qubes-os.org/doc/supported-releases/#note-on-dom0-and-eol). > > >This announcement is also available on the Qubes website: >https://www.qubes-os.org/news/2023/05/11/fedora-36-reaches-eol-on-2023-05-16/ > Wonderful warning. Nothing like advance notice. :/ Following the procedure here... https://www.qubes-os.org/doc/templates/fedora/in-place-upgrade/ It kind of works, but there is an issue. Trying to attach the cache space image gets the error that it is not "exposed" so I had to work around it. Perhaps due to the fact that I don't use LVM on my machine...and the install put the bulk of the available storage in /var/lib/qubes, which is NOT exposed. I don't wish to add the additional layer of LVM complication to an already encrypted system. I have a 700gb image I used to contain a 600gb image where I collect files for archive purposes. I mount the 700gb image in dom0 at a mount point in /mnt, and create the cache image in that space to attach to which ever Qube I desire. After doing the losetup, I use the device menu to attach it to the Qube. This works. Since I have modified the fedora-36 template to add claws-mail, gimp and dosbox-x (I use an old editor that requires it to be usable), it is best to upgrade in place after clone. I have two fedora-36 templates...one with no modifications and one with the aforementioned software additions. The unmodified one is used by sys-net, sys-firewall and such. Qubes 4.1 with Xfce desktop, Lenovo w540. Stuart -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20230512103948.4c7b7cd8%40yahoo.com.
Re: [qubes-users] Re: Task bar disappeared?
On Fri, 28 Oct 2022 09:55:18 -0700 (PDT) Scat wrote: >Update: >- I typed: xfce4-panel into the Dom0 terminal >- I received errors in the Dom0 terminal and as mentioned the Task bar >appeared > >It didn't survive a reboot of my computer. I typed: xfce4-panel into Dom0 >it appeared... > ... I had a similar problem with the desktop wallpaper under Qubes 4.0. It went away after doing something similar. Stuart -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20221028125240.7437273a%40yahoo.com.
Re: [qubes-users] Desktop changed to grey, won't change to anything else
On Wed, 27 Jul 2022 10:23:44 -0500 "'Stuart Perkins' via qubes-users" wrote: >My setup: > >Lenovo T420i >Coreboot >Qubes OS 4.0 >xfce4 desktop >fully encrypted disks, 250Gb SSD main, 2TBHD for the larger MV images. > >The problem cropped up the other day where my assigned solid color of black >background suddenly changed to gray. Using the system tools, desktop to >change it has no effect either on solid color or background image. Everything >else is working fine, but the sudden change is distressing. > >Stuart > Actually it is that xfdesktop stopped being started automatically. Starting it fixes the issue, but it has to be started manually. Stuart -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20220728124003.0057cee4%40yahoo.com.
[qubes-users] Desktop changed to grey, won't change to anything else
My setup: Lenovo T420i Coreboot Qubes OS 4.0 xfce4 desktop fully encrypted disks, 250Gb SSD main, 2TBHD for the larger MV images. The problem cropped up the other day where my assigned solid color of black background suddenly changed to gray. Using the system tools, desktop to change it has no effect either on solid color or background image. Everything else is working fine, but the sudden change is distressing. Stuart -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20220727102344.527b1d08%40yahoo.com.
Re: [qubes-users] Exported Volume Error.
On Thu, 28 Jan 2021 00:31:16 + Rusty Bird wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > >'Stuart Perkins' via qubes-users: >> Ok, now I'm afraid to turn off my computer or even stop any Debian template >> based VM's... > >Don't panic, it's just a bug* in qubes-core-dom0-4.0.56. Your VM data >is still okay. > >> Here is what happened. >> >> I was going to do a general update on Dom0 and my Debian-10 and >> Fedora-32 templates. >> >> As is my habit, I deleted the older clones of those template VM's >> and was creating new clones with qvm-clone from a Dom0 command >> window. >> >> While attempting to create a new clone of the Debian-10 template, it >> halted with an error: >> >> file pool cannot export dirty volumes. >> >> Searching for that issue suggested I start the template VM and exit >> it cleanly...although I don't have a recollection of a "dirty" exit >> (crash, kill etc...). >> >> I went to start the template with qvm-start and it won't, giving the >> error: >> >> file pool cannot start a VM with an exported volume. >> >> How in the world do I recover from this? > >If you restart your computer (or only qubesd), it will drop the >lingering export lock and you'll be able to start the original >template again, etc. > >Rusty I figured that out, eventually...after some sweat. I rely on this machine way too much. All critical data was backed up, but I was not looking forward to a reinstall and the time it would take out of my "way-too-busy" week. Aside: I found out the command line "qvm-clone" will NOT work. That is what left it in this state. Oddly enough, using the Qubes Manager gui it succeeds in the clone...but leaves it where you can't start the template to do the update until you reboot again. Just FYI. In my install I chose NOT to do the LVM as it adds an unnecessary layer of complexity to a laptop, which is already an encrypted installation. I want to add additional drive space ONCE, and do that with just formatting the second drive and symbolic links from the appvm directory to the "too large for my ssd" drives. SSD is 260G. Hard drive is 2TB. Like most Qubes users, I work the crap out of my machine...a coreboot Lenovo T420i. Now that I'm up to 5.4.88, is this fixed? Stuart -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20210127200238.161d72d0%40yahoo.com.
[qubes-users] Exported Volume Error.
Ok, now I'm afraid to turn off my computer or even stop any Debian template based VM's... Here is what happened. I was going to do a general update on Dom0 and my Debian-10 and Fedora-32 templates. As is my habit, I deleted the older clones of those template VM's and was creating new clones with qvm-clone from a Dom0 command window. While attempting to create a new clone of the Debian-10 template, it halted with an error: file pool cannot export dirty volumes. Searching for that issue suggested I start the template VM and exit it cleanly...although I don't have a recollection of a "dirty" exit (crash, kill etc...). I went to start the template with qvm-start and it won't, giving the error: file pool cannot start a VM with an exported volume. How in the world do I recover from this? Stuart -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20210127123934.562adad4%40yahoo.com.
