| Summary: | veracrypt crashes under GNOME | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Franz Holzinger <flink> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | davidwhodgins, fri, jani.valimaa, lewyssmith, mageia, pkg-bugs |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | veracrypt-1.24u7-7.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Franz Holzinger
2021-12-27 21:15:00 CET
Thank you for the report. I am looking into this with other desktops. Source RPM:
(none) =>
veracrypt-1.24u7-7.mga8.src.rpm I installed & tried (just launching) VeraCrypt on the following desktops, and it worked every time - including Gnome! Cinnamon, Gnome, LXDE, LxQt, Mate, Plasma, Xfce Given your other bug about GDM freezing bootup, bug 29801, there must be some anomaly in your system. CC'ing DaveH for suggestions. Status:
NEW =>
UNCONFIRMED It's a cauldron install where /etc/passwd does not match the rest of the installation. Easiest way to fix is a clean reinstall. Closing as invalid. Status:
UNCONFIRMED =>
RESOLVED In which way must Cauldron be reinstalled? This is already a fresh installation. Did you keep /var and/or other directories from a prior install? That's the only way I know of to have this situation arise. I have formatted the / root partition. However the /var and /home partitions remained. Can I repair the /var partition somehow? I have made a fresh installation with formatting the /var and root partitions. Then I have upgraded to Cauldron. All these error messsages are still there. What else must I do? Ever confirmed:
0 =>
1 For future, yes /var can be repaired, but it requires having a reference install of the same release of Mageia with the same packages running. Then use chown to fix the ownership of each and every file and directory in /var. When calling an install, "a clean install", that means nothing left over from other installs, or from personal or third party sources. Given that the error messages are about the wx symbols, it's likely that either the cauldron version of wxgtk needs to be relinked or the cauldron version of veracrypt needs to be relinked. Adding neoclust to cc list as registered maintainer of veracrypt. Adding all packagers as wxgtk does not have a registered maintainer. CC:
(none) =>
mageia, pkg-bugs I tried a couple of pkgs using wxgtk 3.1.5 and looks like all pkgs using it and built before wxgtk-3.1.5-1.mga9 needs a rebuild. I'll trigger rebuilds. CC:
(none) =>
jani.valimaa Related: We have a wxgtk 3.1.5 update sitting in mga8 updates testing, but installing it breaks a lot of packages. It is part of update bug of KiCad List of some packages that may need to be rebuilt in https://bugs.mageia.org/show_bug.cgi?id=28352#c24 CC:
(none) =>
fri Fixed with veracrypt-1.25.4-1.mga9. Resolution:
(none) =>
FIXED |