How to fix "An error ocurred while loading the archive." in Archive Manager in RHEL 7.6 when opening ZIP files? - zip

When I try to open a ZIP file in the Archive Manager, I get this error: "An error ocurred while loading the archive."
This issue is happening on a virtual machine running Red Hat Enterprise Linux 7.6.
Oddly, this did not happen to me prior to this year 2022. Things worked OK in 2021 and each year before.
How do I fix this error "An error ocurred while loading the archive?"
I reverted to an old snapshot of my RHEL 7.6 virtual machine and I can now open ZIP files in the Archive Manager with zero errors. I think a system setting was edited OR a newly installed program is causing the issue.

This is probably bug in Archive Manager which was previously called File Roller.
I encountered it when were trying to unzip password protected zip file under Ubuntu 20.04 and GNOME Archive Manager 3.36.3.
I created the corresponding issue on issues tracker of Archive Manager:
Archive Manager: An error occurred while loading the archive.

Related

File watcher failed repeatedly and has been disabled

Since an unexpected power loss a while back (my computer just went off) I'm getting this pesky warning from Android Studio at launch:
/!\ External file changes sync may be slow
File watcher failed repeatedly and has been disabled
I understand the message, but I have no idea what I should do about it. Apart from that warning I have not experienced system instability. Running on Ubuntu 20.04.
If you go to Help - Collect Logs and Diagnostic Data you'll get a zip file containing (among others) idea.log, which should contain the error.
Probably you'll find this: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.33' not found` which indicates some component is compiled against a libc version newer than what is in Ubuntu 20.04.
If this is the error you get there's not much you can do except upgrading Ubuntu to a newer version.

FreeNas can't load kernel

My freeNAS Server has runned about 1.5 years now but over night it crashed and was not available anymore. No WebGUI, no Network Connection, no reaction on the console.
After resetting and autobooting i get the error "Can't load Kernel".
load /boot/kernel
throw's the error "don't know how to load module '/boot/kernel'"
the directory '/boot/kernel' exists, but no copy or backup like '/boot/kernel.old' or something else
What can I do now? Is there some tool to repair the kernel or can i paste 'kernel'-fiels from another installation?
freeNAS is installed on USB-Stick
FreeNas version 8 (how can i get the correct version, because it's not written in console)
I'm sorry I'm an absolute linux rookie.

Clearcase client installation issue- Linux RHEL5

I am not sure if it is the right place to ask this question. I have been trying to install clearcase client 8015 on a new machine with RHEL5u8 image. Tried googling a lot but could not resolve the issue as per suggestions on other forums.
It gets installed successfully. (As per the prompt)
listing of the views is done properly. (cleartool lsview)
When I do cleartool mount -all,
cleartool: Error: The MVFS file system is not installed or not loaded,
or the 'viewroot' is not mounted or is inaccessible: not a ClearCase
object.
logging in as root then starting clearcase, executing "/opt/rational/clearcase/etc/clearcase start"
OUTPUT:-
ClearCase is stopped Starting ClearCase ClearCase daemons: albd_server
FATAL: Error inserting mvfs
(/lib/modules/2.6.18-308.4.1.0.1.el5/kernel/fs/mvfs/mvfs.ko): Unknown
symbol in module, or unknown parameter (see dmesg) Loading the MVFS
was unsuccessful(8:1) /opt/rational/clearcase/etc/clearcase: Loading
MVFS failed
---- Please review /var/log/messages for information on the problem.
---- You may need to rebuild your kernel, rebuild your mvfs module,
---- and reboot your system. Information on how to do this can be found in
---- your Release Notes and file /var/adm/rational/clearcase/mvfs/mvfs_src/README.txt.
I have followed all the steps in /var/adm/rational/clearcase/mvfs/mvfs_src/README.txt but still cannot achieve anything.
Uninstallation also fails as:-
./linux_8015_uninstall
ERROR: Installation data has incompatible version 1.8.0; expected
1.7.0. Newer version of the Installation Manager was used on this system.
java.io.IOException: Installation data has incompatible version 1.8.0;
expected 1.7.0. Newer version of the Installation Manager was used on
this system.
00:01.33 ERROR [main]
com.ibm.cic.agent.core.application.HeadlessApplication run
Installation data has incompatible version 1.8.0; expected 1.7.0.
Newer version of the Installation Manager was used on this system.
java.io.IOException: Installation data has incompatible version 1.8.0;
expected 1.7.0. Newer version of the Installation Manager was used on
this system. java.io.IOException: Installation data has incompatible
version 1.8.0; expected 1.7.0. Newer version of the Installation
Manager was used on this system.
at com.ibm.cic.agent.internal.core.InstallRegistryParser.parse(InstallRegistryParser.java:160)
at com.ibm.cic.agent.internal.core.InstallRegistry.load(InstallRegistry.java:679)
at com.ibm.cic.agent.internal.core.InstallRegistry.openFile(InstallRegistry.java:485)
at com.ibm.cic.agent.internal.core.InstallRegistry.open(InstallRegistry.java:429)
Cannot proceed with installation, cannot uninstall either to try another version of clearcase, tried googling for the version mismatch of IBM installation manager but could not find anything addressing the issue properly for Linux.
Any suggestions on how to proceed? I am new to clearcase tool.
Usually, when I see only snapshot views are supported, and MVFS (for dynamic views) hasn't installed properly, I uninstall everything and try the all process from the start again.
In your case, that means installing or downgrading the IBM IM Installation Manager to the right version (similar to this issue).
It can be an IM update issue, as seen in this technote.
Further to #VonC's comment re: incompatible IM install,
review the following doc: MVFS not loading after kernel upgrade or is missing after installation on Linux.
I encountered a similar problem after an incompatible kernel path / ClearCase version. In my case, the error was similar to what is documented here in the post MVFS not installed - RHEL6 and I had to edit the kernel source to the same as the patch and rebuild. Then things stared up fine.
Review also the link How to manually restore a pre-built MVFS on Linux.
If the corresponding kerenl level is not provided it will not start and you will have to patch and make your own.

Legacy Cywgin Installation Using Cywgin Time Machine Failing (Unable to get setup-2.ini)

I am attempting to download an older version of Cygwin (1.7.16) in order to compile an open source project (Dummynet - windows port).
The only way i found of doing so is by using a project known as Cygwin Time Machine.
In order to use this i downloaded the cygwin 1.7 installer from 'ftp://www.fruitbat.org/pub/cygwin/setup/1.7/setup-1.7.exe', and when prompted for a download site, added 'ftp://www.fruitbat.org/pub/cygwin/circa/2012/08/20/222043'. However, the download fails with the following error :
Unable to get setup-2.ini from
ftp://www.fruitbat.org/pub/cygwin/circa/2012/08/20/222043
Im looking for help in getting past this error, or any other alternative way of installing Cywgin 1.7.16 (Aug 20, 2012).
The Admin at Cygwin Time Machine was kind enough to point me to the solution. The issue can be resolved by downloading the cygwin setup exe from cygwin.com/setup-x86.exe and starting it with the -X option. Once started, one may choose any cygwin 1.7.* snapshot url from the cygwin time machine site and add that as the mirror to download and install cygwin from.

vmware player unable to start services in kubuntu

my environment:
kubuntu : 3.2.0-generic-pae
vmware player: VMware-Player-4.0.4-744019.i386.bundle
And i have been installed it.
$sh VMware-Player-4.0.4-744019.i386.bundle
I have a problem, when i launch "menu->system->VMware Player"
it launch a window and start compiling:
[ok] Virtual Machine Monitor
[failed] Virtual Network Device
[ok] VMware Blocking Filesystem
[ok] Virtual Machine Communication Interface
[ok] VMCI Sockets
[result fail]Starting Vmare Services
See log file /tmp/vmware-root/modconfig-2722.log for detail
from log file:
[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences"
No such file or directory.
Failed to find /lib/modules/preferred/build/include/linux/version.h
Failed to compile module vmnet!
Could some people tell me what's wrong ?
I suppose that there are no linux headers installed on your machine, that is why it is impossible to build the vmnet module. You must install headers and then try once again.
Ok, I've had the same problem this evening when upgrading from 4.0.3 to 4.0.4. What I've found to work is to first download the patch from this VMWare community thread - http://communities.vmware.com/thread/344213
Unzip it and then open the patch-modules_3.2.0.sh in gedit. There will be three lines at the top that read:
fpatch=vmware3.2.0.patch
vmreqver=8.0.2
plreqver=4.0.2
You have to change the plreqver=4.0.2 to plreqver=4.0.4
Then, open your terminal and run
sudo ./patch-modules_3.2.0.sh
As a side note, keep that file handy, because I found that I had to do the same thing when upgrading from 4.0.2 to 4.0.3 in Ubuntu 12.04. However, when you try the same again in the next upgrade (e.g. change the plreqver to 4.0.5 and run the script), it will say that the file is already patched and it won't work.
To get around this, you need to go to the "/usr/lib/vmware/modules/source/" folder, find the hidden file called ".patched", and delete it (easiest option is to "sudo nautilus" in terminal and hunt through the folder structure). Then it thinks that it hasn't been patched and does the process again.
Hope this gets your VMWare back up and running.

Resources