On Tuesday, September 11, 2018 at 5:06:49 PM UTC-4, awokd wrote: > On Tue, September 11, 2018 2:49 pm, John Maher wrote: > > On Tuesday, September 11, 2018 at 9:02:53 AM UTC-4, awokd wrote: > > > >> On Tue, September 11, 2018 12:27 pm, John Maher wrote: > >> > >>> On Tuesday, September 11, 2018 at 8:15:50 AM UTC-4, John Maher wrote: > >>> > >>> > >>>> On Tuesday, September 11, 2018 at 6:15:43 AM UTC-4, awokd wrote: > >>>> > >> > >>>>> > >>>>> I don't get it either, especially with a fresh install. Did you > >>>>> test before running any updates? If you enable debug mode, any > >>>>> hints in the console or related VM log files? > >>>> > >>>> awokd, I did test before running updates. The template definitely > >>>> starts out appearing (or having?) no applications. > >>>> > >>>> I don't know how to enable debug mode, and I don't see anything in > >>>> the official documentation. I'm also not familiar with the console, > >>>> unless you're referring to a dom0 terminal. Any guidance would be > >>>> wonderful. Thanks. > >>>> > >>>> > >>>> > >>>> John > >>>> > >>>> > >>> > >>> I decided to see if I could install the debian-8 template with > >>> different results from the debian-9 template. Sure enough, by default > >>> terminal if displayed as an available app under debian-8, and within > >>> debian-8 Qubes Settings there are plenty of expected apps in the > >>> Applications tab. I'll > >>> now try to upgrade debian-8 to debian-9 (using a different name) and > >>> see what I get. > >> > >> Same behaviour on a fresh install of 4.0, right? Try this in dom0: > >> > > > > Yes, this all started with a fresh install of 4.0 on new hardware. > > > > > >> > >> 1) qvm-run debian-9 gnome-terminal > >> > > > > output: > > > > > > Running 'gnome-terminal' on debian-9 > > > > > > Very odd behavior. I have never gotten a terminal windows when running > > the above command, but the time I ran the command in response to your > > suggestion I actually ended up with a terminal window! Subsequent > > attempts have resulted in no terminal window. > > Have you ever been able to update that debian-9 template? Maybe it's ok on > first boot but not the rest. > > > > > > > Waiting for /dev/xvdd device... > > mount: /dev/xvdd is write-protected, mounting read-only > > [ 5.836088] EXT4-fs (xvdd): mounting ext3 file system using the ext4 > > subsystem [ 5.840428] EXT4-fs (xvdd): mounted filesystem with ordered > > data mode. Opts: (null) switch_root: failed to mount moving /dev to > > /sysroot/dev: Invalid argument > > switch_root: forcing unmount of /dev > > switch_root: failed to mount moving /proc to /sysroot/proc: Invalid > > argument switch_root: forcing unmount of /proc > > switch_root: failed to mount moving /sys to /sysroot/sys: Invalid argument > > switch_root: forcing unmount of /sys > > switch_root: failed to mount moving /run to /sysroot/run: Invalid argument > > switch_root: forcing unmount of /run > > Mine shows this too- xvdd is the kernel. > > > Starting udev Kernel Device Manager... > > [ 6.243442] systemd-journald[205]: Received request to flush runtime > > journal from PID 1 [ 6.245978] qubesdb-daemon[264]: segfault at > > 76d6ff72eff8 ip 000076d6ff51bf64 sp 000076d6ff72f000 error 6 in > > ld-2.24.so[76d6ff512000+23000] [.[0;1;31mFAILED.[0m] Failed to start Qubes > > DB agent. > > See 'systemctl status qubes-db.service' for details. > > [.[0;32m OK .[0m] Started Flush Journal to Persistent Storage. > > Starting Load/Save Random Seed... > > Starting Init Qubes Services settings... > > [.[0;32m OK .[0m] Started udev Coldplug all Devices. > > [.[0;1;31mFAILED.[0m] Failed to start Load/Save Random Seed. > > See 'systemctl status systemd-random-seed.service' for details. > > > > > > . > > > > > > Starting Permit User Sessions... > > Starting /etc/rc.local Compatibility... > > Starting Qubes misc post-boot actions... > > [.[0;32m OK .[0m] Started Permit User Sessions. > > [.[0;32m OK .[0m] Started /etc/rc.local Compatibility. > > [ 9.738613] qrexec-agent[537]: segfault at 7a9f3456bff8 ip > > 00007a9f34368355 sp 00007a9f3456c000 error 6 in > > ld-2.24.so[7a9f34352000+23000] [.[0;32m OK .[0m] Started Serial Getty on > > hvc0. [.[0;32m OK .[0m] Started Getty on tty1. > > [.[0;32m OK .[0m] Reached target Login Prompts. > > [.[0;32m OK .[0m] Started Qubes misc post-boot actions. > > [.[0;32m OK .[0m] Reached target Multi-User System. > > Starting Update UTMP about System Runlevel Changes... > > [.[0;32m OK .[0m] Started Update UTMP about System Runlevel Changes. > > [ 9.928387] qrexec-agent[572]: segfault at 7a9f3456bff8 ip > > 00007a9f34368355 sp 00007a9f3456c000 error 6 in > > ld-2.24.so[7a9f34352000+23000] > > > > Debian GNU/Linux 9 localhost hvc0 > > > > > > localhost login: [ 14.777457] qrexec-fork-ser[703]: segfault at > > 71772c9d3ff8 ip 000071772c7cd355 sp 000071772c9d4000 error 6 in > > ld-2.24.so[71772c7b7000+23000] > > All those segfaults are probably causing your problems, but the question > is what is causing them!? I'm not sure what to suggest for those. Maybe > disable power management? Check for a BIOS/EFI update? Test RAM? When you > installed, did you let Qubes set up the partitions, including swap?
Yeah, it's probably some piece of hardware that doesn't play well with debian-9. I'll try those things above. I did let Qubes set up the partitions entirely. > > > Pretty much the same as above. Why would debian segfault? Incompatible > > hardware? Hard to imagine since the system came with Ubuntu 16.04 > > installed on it. > > > > I can get by with debian-8, but when it's EOL I'll be in a pickle. > > There's an old post out here about locale causing segfaults somehow; did > you change yours from the default? > https://groups.google.com/forum/#!search/qubes$20segfault/qubes-users/mOfb-hYJD08/9EWKwyL2AgAJ No, I didn't change from the default. Thanks so much for your suggestions. I may have to give up and run without Debian. Any new results I'll post here. John -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c4f8d78e-ea65-4064-b938-18f12248dafb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
