https://bugs.kde.org/show_bug.cgi?id=520407

            Bug ID: 520407
           Summary: fasttext crashed multiple times
    Classification: I don't know
           Product: kde
      Version First unspecified
       Reported In:
          Platform: KDE Linux
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

***
If you're not sure this is actually a bug or valid feature request, instead
post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

DESCRIPTION


STEPS TO REPRODUCE
1. Discovery downloads new updates, restarts to install updates, then restarts
finishes.
2. Then when restart finishes, the abt-applet dialogs, three of them, shows up
saying fasttext crashed.
3. Attempted to report this but unable to. Now I registered and logged in to
report this.

OBSERVED RESULT
Overview - Crashed Processes Viewer:

           PID: 4924 (fasttext)
           UID: 1000 (NAME)
           GID: 1000 (NAME)
        Signal: 4 (ILL)
     Timestamp: Tue 2026-05-19 22:06:05 AWST (32min ago)
  Command Line: /app/fastText/fasttext predict-prob /app/fastText/lid.176.bin -
5
    Executable: /app/fastText/fasttext
 Control Group:
/user.slice/user-1000.slice/[email protected]/app.slice/app-flatpak-re.sonny.Eloquent-3632134788.scope
          Unit: [email protected]
     User Unit: app-flatpak-re.sonny.Eloquent-3632134788.scope
         Slice: user-1000.slice
     Owner UID: 1000 (NAME)
       Boot ID: 060e8e94e77b489caae96c92929b2228
    Machine ID: 682236cfcacc47d99cf633269472ba52
      Hostname: fedora
       Storage:
/var/lib/systemd/coredump/core.fasttext.1000.060e8e94e77b489caae96c92929b2228.4924.1779199565000000.zst
(present)
  Size on Disk: 2.6M
       Message: Process 4924 (fasttext) of user 1000 dumped core.

                Stack trace of thread 53:
                #0  0x0000564e199a444a n/a (/app/fastText/fasttext + 0xc44a)
                #1  0x00007f81bff00975 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6
+ 0x2b975)
                #2  0x00007f81bff00a28 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6
+ 0x2ba28)
                #3  0x0000564e199a4a95 n/a (/app/fastText/fasttext + 0xca95)
                ELF object binary architecture: AMD x86-64

Then click on Run Interactive Debugger:

Executable /app/fastText/fasttext doesn't seem to be a flatpaked application.
Running: `"flatpak" "run" "--filesystem=home" "--filesystem=/tmp"
"--command=gdb" "--devel" "re.sonny.Eloquent" "/app/fastText/fasttext"
"/tmp/tmpqxemyq1i"`
error: runtime/org.gnome.Sdk/x86_64/49 not installed
Traceback (most recent call last):
  File "/usr/bin/flatpak-coredumpctl", line 83, in <module>
    coredumper.run()
    ~~~~~~~~~~~~~~^^
  File "/usr/bin/flatpak-coredumpctl", line 58, in run
    subprocess.check_call(flatpak_command)
    ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.14/subprocess.py", line 420, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['flatpak', 'run', '--filesystem=home',
'--filesystem=/tmp', '--command=gdb', '--devel', 're.sonny.Eloquent',
'/app/fastText/fasttext', '/tmp/tmpqxemyq1i']' returned non-zero exit status 1.

Restarted again, and then this time only two abt-applets shows up. 

One says something about crashed process....

We're sorry, it looks like “fasttext” crashed. Please contact the developer if
you want to report the issue. 

Problem Reporting software shows up, lots of lists of crashes... mostly
fasttext problem.

"fasttext quit unexpectedly"
"The application encountered a problem and could not continue."
Name: N/A
Version: N/A
First detected: 50 minutes ago
Reported: No.

Clicked on "Details"
Problem Details:
Exploitable: Likely crash reason: Illegal instruction (jump to a random
address?)
Exploitable rating (0-9 scale): 5
Reason: fasttext killed by SIGILL
Backtrace: 
: No such file or directory.
/app/fastText/fasttext: No such file or directory.
[New LWP 53]
Downloading 59.47 K separate debug info for system-supplied DSO at
0x7f81c04cf000...
Core was generated by `/app/fastText/fasttext predict-prob
/app/fastText/lid.176.bin - 5'.
Program terminated with signal SIGILL, Illegal instruction.
Too much to copy and paste here.

Click on REPORT:
fasttext killed by SIGILL - org.freedesktop.GnomeAbrt
Problem reporting
Processing finished.
Reporting is disabled because the generated backtrace has low informational
value.
Show log:

--- Running report_uReport ---
Error: Unable to open './coredump': No such file or directory

--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_vimrc_user ---
No matching actions found for this event.

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Generating backtrace
Backtrace is generated and saved, 12830 bytes
Can't open file 'component' for reading: No such file or directory

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla

How to fix this?

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 7.0.8-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7730U with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics


ADDITIONAL INFORMATION

I'm a newbie at this Linux Fedora stuff. I like it. I escaped Windows, I had
enough of Microsoft's insanity. I'm learning Linux in small doses. This problem
keeps happening and I really would like to have help if available to fix this,
and any future problems that might arises, if that's ok. 

Thank you,
Sincerely Yours,
Alexander

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

Reply via email to