[digikam] [Bug 457662] Error while mapping shared library sections: `/usr/lib64': not in executable format: file format not recognized

2022-08-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=457662

[email protected] changed:

   What|Removed |Added

  Component|Plugin-DImg-Magick  |general

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 457662] Error while mapping shared library sections: `/usr/lib64': not in executable format: file format not recognized

2022-08-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=457662

--- Comment #4 from [email protected] ---
QTWEBENGINE_DISABLE_SANDBOX=1 fixed it for me.

Alright, you can close it.

At first, I was perplexed because it was crashing all the time but often at
different places. So i rebuilt digiKam with almost everything turned off, then
it began crashing rather consistently at the same place.
And then I noticed the message that it did not like running as UID=0 (root)
without --no-sandbox.

Thus, QtWebEngine was exiting and letting the rest of digiKam implode. At first
it was crashing at seemingly random places; digKam being multithreaded, the
first victim was essentially a random thread that wanted to have something to
do with QtWebEngine, which had crapped out. It is broken by design and digiKam
is its innocent victim.

I am awfully sorry to have wasted your time. It has been my fault all along.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 457662] Error while mapping shared library sections: `/usr/lib64': not in executable format: file format not recognized

2022-08-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=457662

--- Comment #3 from [email protected] ---
Well, I put this here as a sort of placeholder, because it looks really weird.
An even weirder thing is that this was a native build in a pure amd64 system,
no multilib. I am going to rebuild binutils, binutils-libs and gdb with the
multitarget USE flag disabled, as it is not needed anyway.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 457662] Error while mapping shared library sections: `/usr/lib64': not in executable format: file format not recognized

2022-08-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=457662

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #2 from [email protected] ---
Perhaps a mixing 32 and 64 bits binaries ?

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 457662] Error while mapping shared library sections: `/usr/lib64': not in executable format: file format not recognized

2022-08-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=457662

Maik Qualmann  changed:

   What|Removed |Added

  Component|general |Plugin-DImg-Magick
   Platform|Compiled Sources|Gentoo Packages

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 457662] Error while mapping shared library sections: `/usr/lib64': not in executable format: file format not recognized

2022-08-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=457662

Maik Qualmann  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #1 from Maik Qualmann  ---
The bug title indicates that you didn't install GDB in 64 bit. Can you have a
similar problem with ImageMagick? The crash occurs in ImageMagick and is also
unknown until now.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.