TCC Input Actions module segfaults #162

Open
opened 4 years ago by jstolarek · 12 comments
Collaborator

Basic information

  • TDE version: R14.0.9
  • Distribution: Debian Buster
  • Hardware: amd64

Steps to reproduce

  1. Open TCC -> Input Actions module
  2. Click on the first group of actions on the list. It is important that you click on the first group right after opening the module, not on any other group.
  3. Click on "Reset" button. (The button is erronously enabled due to #161)
  4. Get a segfault
## Basic information - TDE version: R14.0.9 - Distribution: Debian Buster - Hardware: amd64 ## Steps to reproduce 1. Open TCC -> Input Actions module 2. Click on the first group of actions on the list. It is important that you click on the first group right after opening the module, not on any other group. 3. Click on "Reset" button. (The button is erronously enabled due to #161) 4. Get a segfault
jstolarek added the SL/normal label 4 years ago
Owner

Confirmed. I tried deleting the "Examples" group. It gives SEGV.

Confirmed. I tried deleting the "Examples" group. It gives SEGV.
Poster
Collaborator

On my machine it is possible to get a segfault even without attempting to delete anything, at least as long as #161 isn't fixed and it is possible to click the Reset button without actually introducing any changes.

(I fixed the reproduction instructions in original report since I messed them up with reckless editing.)

On my machine it is possible to get a segfault even without attempting to delete anything, at least as long as #161 isn't fixed and it is possible to click the Reset button without actually introducing any changes. (I fixed the reproduction instructions in original report since I messed them up with reckless editing.)
Owner

Uhm.... the second SEGV produced by clicking the reset button doesn't happen here, at least not in English language

Uhm.... the second SEGV produced by clicking the reset button doesn't happen here, at least not in English language
Poster
Collaborator

Interesting. I wonder whether the profile name can be relevant in any way? In my case the first profile is called "Ctrl + Q". Also, it is important that nothing else is clicked/selected after opening the module - the first element on the list of profiles has to be the exact first thing that is clicked once the module is opened.

Interesting. I wonder whether the profile name can be relevant in any way? In my case the first profile is called "Ctrl + Q". Also, it is important that nothing else is clicked/selected after opening the module - the first element on the list of profiles has to be the exact first thing that is clicked once the module is opened.
Owner

I opened the TCC -> Input Actions module, clicked on "Examples" (first item in the list). This enable the "Reset" button. Clcked the button but I don't have a SEGV.

You could try swithing to English and see what happens. Also you could try with a fresh new account.

I opened the TCC -> Input Actions module, clicked on "Examples" (first item in the list). This enable the "Reset" button. Clcked the button but I don't have a SEGV. You could try swithing to English and see what happens. Also you could try with a fresh new account.
Poster
Collaborator

I opened the TCC -> Input Actions module, clicked on “Examples” (first item in the list). This enable the “Reset” button. Clcked the button but I don’t have a SEGV.

I can actually confirm this. If Examples is the first element on the list I don't get a segfault. What happens if you add your own group of actions named "Ctrl" and later try to remove it?

It also seems important to restart TCC every time. Concretely, if I:

  1. Go to Input Actions
  2. Select any group (can be the first one)
  3. Go to other module
  4. Go back to Input Actions, select first group, and click "Reset"

then nothing happens, i.e. I don't get a segfault.

Attaching a stacktrace. It's probably incomplete - let me know if I need to install any additional debugging packages.

> I opened the TCC -> Input Actions module, clicked on “Examples” (first item in the list). This enable the “Reset” button. Clcked the button but I don’t have a SEGV. I can actually confirm this. If Examples is the first element on the list I don't get a segfault. What happens if you add your own group of actions named "Ctrl" and later try to remove it? It also seems important to restart TCC every time. Concretely, if I: 1. Go to Input Actions 2. Select any group (can be the first one) 3. Go to other module 4. Go back to Input Actions, select first group, and click "Reset" then nothing happens, i.e. I don't get a segfault. Attaching a stacktrace. It's probably incomplete - let me know if I need to install any additional debugging packages.
Owner

I think the stack trace is missing 😄

I think the stack trace is missing :smile:
Owner

I can actually confirm this. If Examples is the first element on the list I don't get a segfault. What happens if you add your own group of actions named "Ctrl" and later try to remove it?

If I add a Ctrl group at the top (empty group), exit and relaunch TCC, I get SEGV as described

> I can actually confirm this. If Examples is the first element on the list I don't get a segfault. What happens if you add your own group of actions named "Ctrl" and later try to remove it? If I add a Ctrl group at the top (empty group), exit and relaunch TCC, I get SEGV as described
Poster
Collaborator

I think the stack trace is missing

Good point. It looks like gitea is preventing me from uploading anything different than an image. I had the problem before with uploading mp3 files and had to make a bugreport on bugzilla.

> I think the stack trace is missing Good point. It looks like gitea is preventing me from uploading anything different than an image. I had the problem before with uploading mp3 files and had to make a bugreport on bugzilla.
Owner

You should be able to make a zip file and attach that here.

You should be able to make a zip file and attach that here.
Poster
Collaborator

Yup, that seems to work.

Yup, that seems to work.
Owner

Thanks Janek, when I have time to look at this, I will check your crash dump is similar to the SEGV on my computer or not. Hopefully it is the same thing 😄

Thanks Janek, when I have time to look at this, I will check your crash dump is similar to the SEGV on my computer or not. Hopefully it is the same thing :smile:
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: TDE/tdebase#162
Loading…
There is no content yet.