Re: [qubes-users] Re: qvm-run multimedia nautilus nothing happens
On Fri, Dec 25, 2020 at 3:44 PM Steve Coleman wrote: > > > On Tue, Dec 22, 2020, 5:12 AM Franz <169...@gmail.com> wrote: > >> >> > No, checking again if I put multimedia dependent from another template >>> > works, so the problem is the template. >>> > >>> > Last thing I did with the template was install a custom disposable VM >>> > connected with the template. I did not know that this may end damaging >>> the >>> > template. >>> > >>> Disposable VM settings shouldn't affect the template. What happens if >>> you try to run nautilus from a terminal session to "multimedia"? If it >>> doesn't start, that's the issue. >>> >>> >> Cannot test it because neither gnome-terminal nor term start, so? Anyway >> I prepared a new template, reinstalled everything, even the printer, and it >> works, but now I am scared by the custom dvm thing. >> > > The way to test things like this is to use "qvm-run -p > program-name" and watch what errors bome back through that pipe. Usually > you will see something like "program not found" or some error finding some > basic resource that is required. > > With dvm's this *is* more of a problem, but doing that same command > against its base templatevm might also give some insightful clues. > > Thanks Steve, I already tried qvm-run at the beginning of this thread, but it gives to reply, no error, nothing. it just froze trying to do that. Only CTRL c works to go on. Now tried to add -p as you suggested, but the result is the same. Tried xterm, term, gnome-terminal, nothing works. Well the problem is solved because I prepared a new template, but it is good to remember to make a copy of the template before doing things that can break 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/CAPzH-qDedCFemHP8etSiC%2BZsOq67JbKwpTH9fLXwOde%3DAxPN%2BQ%40mail.gmail.com.
Re: [qubes-users] boot loop after recent xen-updates in dom0
On 1/1/21 7:30 PM, gluonium via qubes-users wrote:
>> Maybe your initramfs is corrupt? Try live booting and recreating it.
>
> Do you have a hint for me how to recreate it?
You need to boot from some live system and chroot your Qubes root
partition which properly mounted EFI partition. Then run:
'dracut -f /boot/efi/EFI/qubes/initramfs-{version}.img {version}'
Maybe a better option is just modifying xen.cfg for booting an older
kernel and then try to reinstall last kernel package after properly
freeing some space.
This way you only need to mount your EFI partition (no LUKS, no LVM,
etc) and edit the file xen.cfg.
--
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/211d824b-4181-575a-977b-f75c5238e001%40riseup.net.
OpenPGP_signature
Description: OpenPGP digital signature
[qubes-users] boot loop after recent xen-updates in dom0
> Maybe your initramfs is corrupt? Try live booting and recreating it. Do you have a hint for me how to recreate it? I‘ve found this issue: https://github.com/QubesOS/qubes-issues/issues/6210 Seems to be related. Will try this. -- 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/MPzCld4--3-2%40tuta.io.
Re: [qubes-users] Still not able to install rofi in dom0? (getting "ERROR: could not verify one or more packages" for multiple packages, not only rofi)
On 12/27/20 11:50 AM, Stumpy wrote: I was trying to install rofi earlier and ended up giving up hoping an update might change things? Well I just tried again and got a different error (before I was getting an error that was something like rofi not found i think). Now I am getting: sudo qubes-dom0-update rofi Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time... --> Running transaction check ---> Package rofi.x86_64 0:1.6.0-1.fc25 will be installed --> Processing Dependency: rofi-themes = 1.6.0-1.fc25 for package: rofi-1.6.0-1.fc25.x86_64 --> Processing Dependency: libxkbcommon-x11.so.0(V_0.5.0)(64bit) for package: rofi-1.6.0-1.fc25.x86_64 --> Processing Dependency: libxcb-ewmh.so.2()(64bit) for package: rofi-1.6.0-1.fc25.x86_64 --> Processing Dependency: libxcb-icccm.so.4()(64bit) for package: rofi-1.6.0-1.fc25.x86_64 --> Processing Dependency: libxcb-xrm.so.0()(64bit) for package: rofi-1.6.0-1.fc25.x86_64 --> Processing Dependency: libxkbcommon-x11.so.0()(64bit) for package: rofi-1.6.0-1.fc25.x86_64 --> Running transaction check ---> Package libxkbcommon-x11.x86_64 0:0.7.1-1.fc25 will be installed ---> Package rofi-themes.noarch 0:1.6.0-1.fc25 will be installed ---> Package xcb-util-wm.x86_64 0:0.4.1-8.fc24 will be installed ---> Package xcb-util-xrm.x86_64 0:1.2-1.fc25 will be installed --> Finished Dependency Resolution rofi-1.6.0-1.fc25.x86_64.rpm | 196 kB 00:01 xcb-util-xrm-1.2-1.fc25.x86_64.rpm | 18 kB 00:00 xcb-util-wm-0.4.1-8.fc24.x86_64.rpm | 29 kB 00:00 libxkbcommon-x11-0.7.1-1.fc25.x86_64.rpm | 22 kB 00:00 rofi-themes-1.6.0-1.fc25.noarch.rpm | 19 kB 00:00 Successfully verified /var/lib/qubes/dom0-updates/packages/libxkbcommon-x11-0.7.1-1.fc25.x86_64.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/python3-xen-4.8.5-28.fc25.x86_64.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/qubes-gpg-split-dom0-2.0.50-1.fc25.x86_64.rpm ERROR: could not verify /var/lib/qubes/dom0-updates/packages/rofi-1.6.0-1.fc25.x86_64.rpm ERROR: could not verify /var/lib/qubes/dom0-updates/packages/rofi-themes-1.6.0-1.fc25.noarch.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/xcb-util-wm-0.4.1-8.fc24.x86_64.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/xcb-util-xrm-1.2-1.fc25.x86_64.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/xen-4.8.5-28.fc25.x86_64.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/xen-hvm-4.8.5-28.fc25.x86_64.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/xen-hypervisor-4.8.5-28.fc25.x86_64.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/xen-libs-4.8.5-28.fc25.x86_64.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/xen-licenses-4.8.5-28.fc25.x86_64.rpm Successfully verified /var/lib/qubes/dom0-updates/packages/xen-runtime-4.8.5-28.fc25.x86_64.rpm ERROR: could not verify one or more packages Thoughts? Alittle additional information, it seems that not only am i getting verification errors for rofi related packages but I also tried (just to see what would happen) installing other packages like: sudo qubes-dom0-update --clean qvm-screenshot-tool Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time... Cleaning repos: fedora qubes-contrib-dom0-r4.0-current qubes-dom0-current : qubes-templates-itl updates Cleaning up Everything fedora/metalink | 3.2 kB 00:00 fedora | 4.3 kB 00:00 fedora-32-minimal: command failed with code: 143 ] 242 kB/s | 4.4 MB 01:30 ETA fedora/primary_db | 26 MB 01:47 qubes-contrib-dom0-r4.0-current | 3.0 kB 00:00 qubes-contrib-dom0-r4.0-current/primary_db | 16 kB 00:00 qubes-dom0-current/metalink | 2.7 kB 00:00 https://mirror.linux.pizza/qubes-os.org/repo/yum/r4.0/current/dom0/fc25/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. qubes-dom0-current | 3.8 kB 00:00 qubes-dom0-current/primary_db | 483 kB 00:02 qubes-templates-itl/metalink| 2.7 kB 00:00 qubes-templates-itl | 3.0 kB 00:00 qubes-templates-itl/primary_db | 6.9 kB 00:00 updates/metalink| 3.0 kB 00:00 updates | 4.7 kB 00:00 updates/primary_db | 12 MB 00:51 --> Running transaction check ---> Package qvm-screenshot-tool.x86_64 0:0.7-0.fc25 will be installed --> Processing Dependency:
