This guy solved the blank screen issue.
Just thought I’d throw another pointer out there on the Interwebs.
This guy solved the blank screen issue.
Just thought I’d throw another pointer out there on the Interwebs.
Quick Fix Up Front:
plugin.load_flash_only” and set it to False.
A Brief Write-Up:
So, Firefox 52 was just pushed to Fedora 25 and it immediately broke my F5 extension which I use to access my place of employment’s VPN on my Fedora 25 systems.
Ever so nicely, the update to Firefox doesn’t come with any useful information informing you why you are now being continually prompted for reinstallations of your NPAPI extensions. If you look in your “Add-Ons” menu in Firefox, it appears the extension is properly installed and in good shape. However, any attempt to use a site which requires it will cause the site to prompt you for reinstallation.
As it turns out, this is because Firefox 52 is attempting to remove all support for NPAPI extensions. This is theoretically a good thing due to the security risks of the NPAPI framework, but of course not every vendor out there will necessarily update their code accordingly (at least quickly enough to be helpful), and if you’re like me and relying on one of these extensions, you’ll need a work-around.
Very lamely, Firefox is still allowing the Adobe Flash NPAPI extension, but only that one (since they know removing support for it would kill their browser usage). So, that explains the name of the hidden configuration parameter you have to manually add into your about:config page to get this to work.
The proper solution here is, of course, for Firefox to permit explicitly-designated NPAPI extensions to be used for a good while. I understand that they’re trying to increase security with some tough love here, but it really just adversely impacts Linux-based end users rather than coerce organizations with little incentive to provide Linux distribution support in the first place.
I don’t know how this will pan out; hopefully F5 will up their game, but if they don’t, I guess I’ll have to have a back-versioned Firefox browser on my system just for my VPN..
Ok, I don’t usually post little “yay for me” articles ’round here, but I’ve been buried in work to the point of not being able to post much at all so at the risk of taking a solid step in a bad direction for the blog, I’ll provide some evidence of the value in running an arrangement as described in the Engineering Walden Technical Reference Model:
It’s pretty incredible to think that I’m typing this post on a GNU/Linux/KVM/QEMU-driven (Fedora, of course) Windows 10 guest domain which is sharing hardware with the FreeBSD guest domain which is using IOMMU-based PCI-passthrough to access and manage four 3 TB Seagate Barracuda hard disks arranged in a OpenZFS zpool as a striped set of mirrored pairs.
Right now, I am comfortably typing a blog post and gaming (Elite Dangerous is amazing, btw) in a Windows 10 guest domain hosted on the same rig which is simultaneously rebuilding my home server’s principal storage pool and hosting a home media server which is streaming Futurama to my now-sleeping family. Its uptime is relatively uninterrupted (I powered it down for the disk replacement just to be safe) thanks to the extreme awesomeness of OpenZFS on FreeBSD.
And today’s stalwart servant sent to that bitbucket in the sky, the great /dev/null from which all arise and to which all shall return, a Seagate Barracuda Desktop Edition who lived a long and steadfast life of service at 28,811 hours of uptime.
He will join his brother, who arrived before him after a staggering 38,000 hours of uptime.
So, anecdotally, these are some pretty good drives, I’d say.
More demonstrably, we have some amazing machines in these homes of ours, I’d say.
But most importantly: with OpenZFS, my data integrity is monitored by associated checksum values so I know the age of my disks isn’t causing me to lose any data. Because OpenZFS is designed to operate without trusting the individual underlying block devices, I can get the most time possible out of my consumer-grade hardware without worrying that the files I store with them are being corrupted.
And tranquility ensues. Engineering is a fine spiritual venture.
Well that was one hell of a circuitous problem solving tale of woe. So here’s the rundown:
After some upgrades, I ran into the following slew of errors on reboot (in reverse chronological order):
Jan 31 23:31:48 gdm: GLib: g_hash_table_find: assertion ‘version == hash_table->version’ failed
Jan 31 23:31:48 login: pam_systemd(login:session): Failed to release session: Interrupted system call
Jan 31 23:31:48 gnome-session-binary: GLib-GObject-CRITICAL: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed
Jan 31 23:31:48 gdm-x-session: GLib-GObject: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed
Jan 31 23:31:48 gdm-x-session: GLib-GIO: g_task_return_boolean: assertion ‘task->result_set == FALSE’ failed
Jan 31 22:22:16 gnome-settings-daemon.desktop: lock: No locks available
Jan 31 22:10:29 pulseaudio: Daemon already running.
Jan 31 22:08:37 abrt-hook-ccpp: Process 1888 (gnome-session-failed) of user 1000 killed by SIGSEGV – dumping core
Jan 31 22:08:37 gnome-session-binary: Unrecoverable failure in required component org.gnome.Shell.desktop
Jan 31 22:08:23 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote appl
Jan 31 22:08:23 pulseaudio: [pulseaudio] core-util.c: lock: No locks available
Jan 31 22:07:33 pulseaudio: [pulseaudio] core-util.c: lock: No locks available
Looking a little closer, I found:
Jan 31 22:20:07 gnome-shell: cogl-sampler-cache.c:200: GL error (1280): Invalid enumeration value
Jan 31 22:20:06 gnome-shell: clutter_input_device_get_device_id: assertion ‘CLUTTER_IS_INPUT_DEVICE (device)’ failed
Jan 31 22:20:06 gnome-shell: STACK_OP_ADD: window 0x1200001 already in stack
Jan 31 22:08:37 kernel: gnome-session-f: segfault at 0 ip 00007fe59d2e1899 sp 00007ffc1269b3f0 error 4 in libgtk-3.so.0.2200.7[7fe59d003000+6f6000]
Though I fixated on that segmentation fault like a narrow-minded fool, I also noted what I should have considered immediately as abnormal and important:
Jan 31 22:15:39 kernel: lockd: server 172.16.1.102 OK
Jan 31 22:15:39 kernel: lockd: server 172.16.1.102 not responding, still trying
And the reason that’s so abnormal and important, in particular, is not only that my lockd service is having trouble contacting my NFS server, but that I use NFSv4…which doesn’t use lockd.
After banging my head against these errors by reinstalling my NVidia drivers, attempting the use of KDE Plasma rather than GNOME, and the like, all to no avail. Finding the issue to be common to GNOME and KDE Plasma (which doesn’t make use of the segfaulting libgtk, obviously), and running down a bug report on bugzilla that shows the error is actually a failure of GDM which likely occurs long after the real culprit, I actually took note of the fact that a number of services (gnome-settings-daemon, pulseaudio above) were citing the absence of locks as problems.
And that, my friends, was the issue. I had been messing around with my NFS server, trying to get the Windows NFS client to make proper use of file locking, and in the course of doing so, I had inadvertently caused the NFSv4 service to stop, leaving only NFSv3 and a busted-up lockd arrangement for my poor Fedora system. It automatically downgraded to NFSv3 when it found NFSv4 to fail, and being stuck without file locking, this actually caused the entire problem.
So, the moral of the story is: When using NFS-mounted home directories, sometimes NFS problems can even look like graphics driver problems.
Now, I firmly believe the benefits of NFS-mounted home directories outweigh the added potential for issues such as the above, so I’ll be keeping mine, thanks, but just know you should check on that stuff at the first sign of trouble and make sure all is well. The issues that can be caused by a file system problem with your home directory can look like just about anything.
If you attempt to connect to a Windows 7 workstation using the RDP protocol TLS security, you may encounter the following error information from Remmina:
Dec 30 21:25:00 hostname remmina.desktop: [21:25:00:443] [4836:5478] [ERROR][com.freerdp.core] – freerdp_set_last_error ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x2000D]
Dec 30 21:25:00 hostname remmina.desktop: [21:25:00:443] [4836:5478] [ERROR][com.freerdp.core.transport] – BIO_read returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
To resolve the issue, you may simply need to edit the connection in Remmina, head to the Advanced tab, and choose TLS for Security (by default, it is “Negotiate”). I don’t know why the security negotiation appears to be failing in my case, but that resolved the issue for me.
MAN. That took hours to figure out. I simply ran a
dnf upgrade on my Fedora 25 system (using an NVidia GeForce GTX 960 with the proprietary drivers) and, when it rebooted, I was greeted with a failure to start GDM. The system would simply hang at the text list of services being started.
Switching into another terminal, I found error messages such as these repeated with every effort to start GDM:
Dec 01 15:07:04 hostname gdm: GLib: g_hash_table_find: assertion ‘version == hash_table->version’ failed
Dec 01 15:06:51 hostname abrt-hook-ccpp: Process 1455 (gnome-session-failed) of user 42 killed by SIGSEGV – dumping core
Being segmentation faults, I suspected I needed to reinstall my NVidia drivers (which seems to happen once in a while with kernel or mesa updates). I tried this to no avail. Many times.
Because I’m a moron and was filtering my journal for error-level messages only, I didn’t notice this helpful message was also being logged:
Dec 01 15:06:51 hostname kernel: gnome-session-f: segfault at 0 ip 00007f23d0001579 sp 00007ffd1a6248c0 error 4 in libgtk-3.so.0.2200.4[7f23cfd23000+6f0000]
So I started checking around for that same segmentation fault in other users, and lo and behold I hit upon this over at the Arch Linux forums. If I’m reading the tail end of the related bug report properly, it looks like a bug was fixed upstream, but given that Fedora 25 is still hosting mutter-3.22.2-1.fc25 for download, we may still be waiting on the package which includes the fix. Or, it may be that the fix included in package 3.22.2-1 is incomplete (a user at the tail end of the forum link reports just a few days ago using the package which includes the apparent fix to no avail).
So anyway, if you, too, are experiencing GDM/GNOME session failures with the proprietary NVidia drivers on Fedora 25, try simply downgrading mutter:
[you@yourplace ~]$ sudo dnf downgrade mutter
That brought me back to mutter-3.22.1-8.fc25.x86_64 and all is well for me.
Now to get rid of lightdm and roll back all my insane troubleshooting installations…
Well THAT was a hell of a learning experience. You know, I spent all this time learning about GRUB 2, the MBR, and bootloader operation in general, and just when I thought I really had the bootloader stuff down, I realized I had to learn about UEFI before I could consider myself to have mastered the area from a system administration perspective.
But that was a lot of junk to read, so I didn’t.
So then, I found I needed to swap out an SSD in my Fedora system so that I could replace it with a larger drive. Of course, it had to be my boot volume.
THUS BEGAN MY QUEST. I read quite a lot. I can recommend this guy for a high-quality informal read in BIOS and UEFI technology. But, I think I can make a quick and dirty SysAdmin overview for ya:
That last step there was what had me hung up for about an hour. Fedora, and GNU/Linux distributions in general, use a tool called
efibootmgr to control the UEFI firmware’s boot manager from within the operating system. That’s pretty sweet. Amazingly enough, your motherboard is not likely to provide as much capability in managing the UEFI boot manager as this handy tool. My motherboard doesn’t even seem to let me create boot entries within the UEFI interface, so I have to rely on
If you check out the man page, you’ll see some pretty standard options. Basically:
efibootmgr -vto list the boot manager entries in your UEFI firmware.
grep efibootmgr /var/log/anaconda/program.logto locate the command used by Fedora when your OS was installed. It will look something like this:
Now, armed with this super secret knowledge, you will be able to easily and handily create a new boot device on your Fedora system. Really, all you have to do is:
sudo cfdisk /dev/sdbor whatever and make a 200MB EFI partition and a 500MB boot partition.
sudo mkfs.ext4 /dev/sdb2
sudo mkdir /mnt/boot2 /mnt/efi2
sudo mount /dev/sdb1 /mnt/efi2 && sudo mount /dev/sdb2 /mnt/boot2
sudo rsync -a /boot/ /mnt/boot2
sudo rm -r /mnt/boot2/efi/EFI
sudo rsync -a /boot/efi/ /mnt/efi2
efibootmgrto create a new boot entry for your system which points to the proper boot device.
efibootmgr(sadly), so just delete the old entry after you prove that your system boots with the new entry.
And that is it! Fantastico.
So whereas with older MBR/BIOS systems, you need to reinstall GRUB after installing Microsoft Windows (if you installed onto the same disk as your Fedora system) in order to overwrite the Windows bootloader in the MBR (and then chainload Windows with GRUB, making GRUB the sole true bootloader for the system), with EFI, you have more options. You could create two separate EFI partitions for Windows and Fedora, or you could try to put all the bootloader code in a single EFI partition and use
efibootmgr to create separate boot entries in your UEFI firmware to point to the same disk and partition, but separate bootloader code for each OS.
It’s actually a lot easier to manage, but it requires this additional understanding to get it right. Once you know the sequence of events and the relationships between the components, managing issues becomes a lot easier. If you are no longer able to boot Microsoft Windows on a dual-boot system from within your UEFI firmware, for example, you now know you simply need to boot into your GNU/Linux OS and use
efibootmgr to create the appropriate entry. If your Windows EFI partition was overwritten or the code was lost, you can attempt the use of Microsoft utilities (as described here) to repair that matter.
You are likely to run into the following error during the upgrade process:
Windows 10 installation failed in SAFE_OS phas with error during boot
The error code reported to you when you reboot the system and it rolls back changes into the old OS is likely:
0xC1900101 – 0x20017
This appears to occur because Windows doesn’t care for the QEMU-provided CPU unless you’re using (as far as I am aware) the core2duo emulation option.
So, simply shut down the guest domain, choose “core2duo” as the CPU type, downgrade your processor count to 2 (if necessary), and retry the operation. It succeeded for me! After the upgrade, it seems you can reset the CPU to host (or whatever you use) and increase the processor count without issue.
Additional note: If you’re using the Red hat VirtIO drivers in Windows 7, Windows 10 will work with those drivers during the upgrade process without an issue.
Well that was significantly more painful than I had anticipated. Here’s the quick and dirty instruction set which involves multiple tools, perhaps needlessly, since I was investigating the issue for some time:
That is more of a pain than it should be. Silly Windows VDS.
You know, I actually said to the illustrious philosoraptor a while back, “If that guy found the Ring of Gyges, people would start disappearing.” And now we have a little insight into just how accurate that assessment seems to have been.
It is really pretty amazing how fervently trump supporters are defending his words as “locker room banter” or what the hell ever.
First, a wee, less important point: I have a hard time thinking most men aren’t garbage. That is my reflexive, perhaps largely emotional position on that general matter. Despite that, and despite having been exposed to my fair share of private interpersonal dialogue between men who were actually garbage, only once or twice did the content of those dialogues resemble trump’s speech. I guess I don’t find it incredibly hard to believe that a large portion of this country is defending his words by asserting abject disbelief in the possibility that other men don’t speak like this in private, given my general inclination towards the belief that most men are garbage, but given that trump’s particularly vile speech is an order of magnitude or so above that which I have typically felt earns men the classification of “garbage,” it is kinda surprising, actually.
The second, most important point, however, seems to be completely eclipsed by the fact that trump was speaking about his penchant for casual sexual assault. The most important point, I think, is that we have this guy, somehow being considered for the office of the President of the United States, on tape saying that he can freely express his penchant for sexual assault because he’s “a star” (loosely construed, apparently), and so he can do anything he wants.
Of course, it should have been an easy inference for anyone to make up until this point that trump is approximately this kind of person. He does not seem to care for anything other than his own aggrandizement and pleasure, and he has repeatedly voiced positions that would have disqualified him from mainstream Republican support were the Republicans not already self-whipped into a near-completely-irrational frenzy over the grossly exaggerated failings of HRC, but now we have actual, direct evidence that he takes whatever advantage conferred upon him by a (much) lower position of social power to do nothing less than sexually assault women for fun.
It is a testament in favor of all those great thinkers of history who thought democracy untenable that the completely irrational means by which so many of our country’s denizens make their decisions should be laid so plainly bare before us all.
HRC is not a great choice. I’ve even written that, were we a stronger nation, she would indeed face jail for her willful negligence in handling our national security. But, sadly, we have a simple choice: it’s her or far, far, unambiguously disastrously far worse. Trump has all the makings of the next Nixon, though without any of Nixon’s good qualities. You can rightfully bemoan the two-party system. You can bemoan the poor choice had in HRC. But in my estimation, the actually unprecedented risk to the nation posed by Trump merits extreme caution and discipline which mandates of us all a vote for HRC. And if she is evaluated objectively, again sadly, it will be found that she is not that far worse than a typical American political candidate.
I don’t like the status quo. I want to see something awesome happen, and I don’t think HRC will bring that about, but I’ll be damned if I fail to cast my vote in a way that does anything other than seek most efficaciously to prevent someone like trump from holding our nation’s highest office.