Summary: | Plasma Coredump after installation of openjph/libopenjph | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Gerald Cox <gbcox> |
Component: | Startup process | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | normal | CC: | aous72, kde |
Priority: | NOR | ||
Version: | 6.1.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | plasmashell kcrash |
Description
Gerald Cox
2024-08-26 15:08:27 UTC
It's an illegal instruction, so a packaging issue in the openjph package (compiled with march=native) (In reply to Antonio Rojas from comment #1) > It's an illegal instruction, so a packaging issue in the openjph package > (compiled with march=native) Hi Antonio, Do you know what the illegal instruction is that is causing the problem? Also, what is the CPU the code is running on? Pointers on how to identify the problem from my side. OpenJPH has multiple code paths, supporting different SIMD instructions. It looks like the problem is happening during the loading of the library, so it it the library initializing code. Am I correct? Thank you. Aous. (In reply to Aous Naman from comment #2) > > (In reply to Antonio Rojas from comment #1) > > It's an illegal instruction, so a packaging issue in the openjph package > > (compiled with march=native) > > Hi Antonio, > > Do you know what the illegal instruction is that is causing the problem? > Also, what is the CPU the code is running on? > Pointers on how to identify the problem from my side. > > OpenJPH has multiple code paths, supporting different SIMD instructions. > It looks like the problem is happening during the loading of the library, so > it it the library initializing code. Am I correct? > > Thank you. > Aous. Gerald Cox closed the case. Thank you. |