MantisBT - MEGA | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0006540 | MEGA | Installation | public | 2024-04-08 14:17 | 2024-04-08 14:17 |
Reporter | guest | ||||
Assigned To | |||||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Platform | PC | OS | Linux | OS Version | Debian |
Product Version | MEGA 11 (Graphical Interface version) | ||||
Target Version | Fixed in Version | ||||
First Name | Chris | ||||
Last Name | Ribe | ||||
chrisribe@ufl.edu | |||||
Confirm Email | chrisribe@ufl.edu | ||||
Summary | 0006540: failed to initialize Chromium error at startup | ||||
Description | I am attempting to install MEGA 11 in a Ubuntu 22.04 based container which is to be run on a RHEL 8.8 based computing cluster. When launching mega, an error box pops up with the message, "failed to initialize Chromium: System error, (OS Code 2): No such file or directory" Searches of the help system suggest installing libgconf-2-4 as a solution, but the behavior remains the same with that package installed. | ||||
Steps To Reproduce | Create an apptainer container based on the following definition file and attempt to run mega from the container: Bootstrap: docker From: ubuntu:22.04 %files mega_11.0.13-1_amd64.deb %post export DEBIAN_FRONTEND=noninteractive apt update -y apt install -y libgtk2.0-0 libgtk2.0-bin libgconf-2-4 wget dpkg -i mega_11.0.13-1_amd64.deb | ||||
Additional Information | I have also tried building a container built on Ubuntu 20.04, but in that case MEGA fails to start due to a GLIBC version error. | ||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2024-04-08 14:17 | guest | New Issue |
There are no notes attached to this issue. |