GNU TeXmacs - Bugs: bug #61163, guile3_branch_2.1: seg fault error...
You are not allowed to post comments on this tracker with your current authentication level.
bug #61163: guile3_branch_2.1: seg fault error when launching an interactive session on Debian 11
Submitter: | abft3kldp <abft3kldp> | ||
Submitted: | Wed 15 Sep 2021 11:10:18 AM UTC | ||
Category: | None | Priority: | 5 - Normal |
Item Group: | Error | Status: | Duplicate |
Privacy: | Public | Assigned to: | vdhoeven |
Originator Name: | Open/Closed: | Closed | |
Release: | None | Release: | |
Fixed Release: | None | Fixed Release: | |
Keywords: |
Mon 07 Aug 2023 04:12:24 PM UTC, comment #4: |
Joris van der Hoeven <vdhoeven> |
Thu 16 Sep 2021 01:17:55 PM UTC, comment #3: I have just recompiled source code from guile-3 branch with addition of --disable-qtpipes flag in configure and substitution
|
abft3kldp <abft3kldp> |
Thu 16 Sep 2021 11:50:44 AM UTC, comment #2: I confirm that the spell checking leads to a failure too. Here is the debug message
|
abft3kldp <abft3kldp> |
Thu 16 Sep 2021 07:07:04 AM UTC, comment #1: Although it's triggered differently, this is a duplicate of bug #60931, as it arises from the same calling of QProcess::start.
|
Philippe Joyez <pjoyez> |
Wed 15 Sep 2021 11:10:18 AM UTC, original submission:
First of all thanks to developers and contributors for such a fantastic piece of software!
|
abft3kldp <abft3kldp> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-08-07 | vdhoeven | Assigned to | None | vdhoeven | |
Open/Closed | Open | Closed | |||
2021-09-16 | pjoyez | Status | None | Duplicate |
Powered by Savane 3.13-d3ae.
Corresponding source code
I close this bug, since it duplicates bug #60931.
I added a pointer there to the present bug for reference.