Bug 474072 - Segfault when running nushell
Summary: Segfault when running nushell
Status: RESOLVED FIXED
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 23.08.0
Platform: Manjaro Linux
: NOR crash
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-02 23:54 UTC by nighteule5
Modified: 2023-10-23 03:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Backtrace obtained with GDB (99.69 KB, text/plain)
2023-09-02 23:54 UTC, nighteule5
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nighteule5 2023-09-02 23:54:56 UTC
Created attachment 161345 [details]
Backtrace obtained with GDB

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Install Nushell with `cargo install nu`
2. Create a default profile with the "command" set to `/home/<user>/.cargo/bin/nu`
3. Run Yakuake

OBSERVED RESULT
Yakuake opens for a second, then exits from a segmentation fault

EXPECTED RESULT
Yakuake should work normally

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro, kernel version 6.4.12
(available in About System)
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Comment 1 AceLan Kao 2023-09-26 05:45:56 UTC
yakuake                                                     23.08.1-0xneon+22.04+jammy+release+build22

Can't reproduce this issue on ubuntu, and here is what I got when pressing F12 to call yakuake
Not sure why there are some errors, I just built nu by `cargo install nu`

Maybe you can run `nu` manually to see if it works.

```
Error: nu::parser::unknown_flag

  × The `str replace` command doesn't have flag `string`.
    ╭─[/home/acelan/.config/nushell/env.nu:15:1]
 15 │     let dir = ([
 16 │         ($env.PWD | str substring 0..($home | str length) | str replace --string $home "~"),
    ·                                                                         ────┬───
    ·                                                                             ╰── unknown flag
 17 │         ($env.PWD | str substring ($home | str length)..)
    ╰────
  help: Available flags: --help(-h), --all(-a), --no-expand(-n), --regex(-r), --multiline(-m). Use `--help` for more information.

Error: nu::shell::removed_command

  × Removed command: let-env
     ╭─[/home/acelan/.config/nushell/config.nu:185:1]
 185 │ # The default config record. This is where much of your global configuration is setup.
 186 │ let-env config = {
     · ───┬───
     ·    ╰── 'let-env' has been removed from Nushell. Please use '$env.<environment variable> = ...' instead.
 187 │   # true or false to enable or disable the welcome banner at startup
     ╰────

     __  ,
 .--()°'.' Welcome to Nushell,
'|, . ,'   based on the nu language,
 !_-(_\    where all data is structured!

Please join our Discord community at https://discord.gg/NtAbbGn
Our GitHub repository is at https://github.com/nushell/nushell
Our Documentation is located at https://nushell.sh
Tweet us at @nu_shell
Learn how to remove this at: https://nushell.sh/book/configuration.html#remove-welcome-message

It's been this long since Nushell's first commit:
4yrs 4months 15days 12hrs 42mins 33secs 691ms 853µs 185ns 

Startup Time: 47ms 598µs 734ns

/home/acelan>
```
Comment 2 nighteule5 2023-10-23 03:32:24 UTC
As of 23.08.1, this is working. I forgot to update the issue