Skip to main content
Topic: tint2 and tint2conf craash after last update (Read 1093 times) previous topic - next topic
0 Members and 6 Guests are viewing this topic.

tint2 and tint2conf craash after last update

After the last tint2  update to version  17.0.2-4, if any .desktop file in /usr/share/applications has a "%F" in the exec statement (geany.desktop for example), tint2 crashes reporting this error:
*** buffer overflow detected ***: terminated

this happens with default tintrc. Tint2 crashes also with my customized tint2rc, with no launcher.

tint2conf also crash with the same error.

I already reported this bug to  arch forum here and the problem seems affect only artix.

 

Re: tint2 and tint2conf craash after last update

Reply #1
I have tint2-17.0.2-4 running in a pure openbox environment and I don't seem to have this problem in Arch or Artix. I'm not sure that the desktop files are being used though. I did have the buffer overflow issue a while back, but that was to do with conky and I thought there were mitigations put into tint2 to address that.

Edit: I retested in Arch and Artix using
Code: [Select]
xdg-open /usr/share/applications/vim.desktop
and see no issues with tint2.

Re: tint2 and tint2conf craash after last update

Reply #2
I am using tint2 17.0.2-4 about 3 weeks now and I don't have any troubles. Did you try to downgrade tint2 to be sure that's the problem?

Re: tint2 and tint2conf craash after last update

Reply #3
I am using tint2 17.0.2-4 about 3 weeks now and I don't have any troubles. Did you try to downgrade tint2 to be sure that's the problem?
I downgraded and with previous version i have no problems.

I encountered this problem with 2 pc, the first one is running artix for about two years, the second is a fresh install i made last week.

Re: tint2 and tint2conf craash after last update

Reply #4
I have tint2-17.0.2-4 running in a pure openbox environment and I don't seem to have this problem in Arch or Artix. I'm not sure that the desktop files are being used though. I did have the buffer overflow issue a while back, but that was to do with conky and I thought there were mitigations put into tint2 to address that.

Edit: I retested in Arch and Artix using
Code: [Select]
xdg-open /usr/share/applications/vim.desktop
and see no issues with tint2.


The desktop file are used by tint2 launchers. Tint2 crash at starup if there are some launchers  referring to desktop file containg the %F string, when tint2 parse them at startup.

I'm not using conky, and the patch applied to the last tint2 update was intended to correct also this  problem.

Anyway in the post in the Arch forum there are all the information needed by developers to address this issue.

Re: tint2 and tint2conf craash after last update

Reply #5
Yes, when I choose one of conf files in tint2conf it crashes with "buffer overflow". I don't use launchers in my conf though so tint2 is working all right. Maybe it's build issue.

Re: tint2 and tint2conf craash after last update

Reply #6
i suppose it crashes because to make available the applications list to configure the launchers it parses the /usr/share/applications dir.

Re: tint2 and tint2conf craash after last update

Reply #7
I tried the default tint2rc ie /etc/xdg/tint2/tint2rc with various desktop launchers with exec lines

Code: [Select]
Exec=tint2conf
Exec=/usr/lib/firefox/firefox %u
Exec=xfce4-terminal
Exec=/usr/bin/google-chrome-stable %U

Of these only tint2conf causes a crash; the launch fails, but tint2 carries on.

As an experiment I tried using the Arch linux binary package tint2-17.0.2-4-x86_64.pkg.tar.zst in Artix. This seems to work fine and I did not observe a crash with tint2conf. I compared ldds for artix & arch /bin/tint2 I saw no lib version changes (but addresses were different).

I cannot see any difference in the applied fix_segfault.patch. Since tint2conf is part of tint2 perhaps tint2conf is bad in Artix.

Re: tint2 and tint2conf craash after last update

Reply #8
Arch's Tint2 also crashes within 1 or 2 minutes on some Artix.systems.
A while ago I did a lot of checking and patching but could never get it stable. These patches work for some use cases but not for others as reported by many, also on non-Arch derivatives.

"The report of my death was an exaggeration." Mark Twain once said; we should not expect to hear the same from Tint2.

artist


Re: tint2 and tint2conf craash after last update

Reply #9
Arch's Tint2 also crashes within 1 or 2 minutes on some Artix.systems.
.......
artist
well I cloned the artix tint2 repository and installed a newly built pkg. I did not see the crash I saw in the artix built version when clicking on the tint2conf launcher. So far as I know, I have not altered any of the makepkg config. My system is up to date. A difference might be that I am using a ryzen 7 system.

This seems to indicate that the problem lies in the build environment somehow.

Re: tint2 and tint2conf craash after last update

Reply #10
I also rebuild tint2 but in my case the "buffer overflow detected" segfault in tint2conf still there. I have an old AMD FX cpu though,

Re: tint2 and tint2conf craash after last update

Reply #11
The problem, as suggested by seth in the arch forum, could be in some artix toolchain. I also expicitly installed the arch word repository tint2 package, and it works flawlessy.

Re: tint2 and tint2conf craash after last update

Reply #12
The build server has been known to differ slightly from a local build. But never in a way that would affect some users but not others, from what I've seen.

Re: tint2 and tint2conf craash after last update

Reply #13
The build server has been known to differ slightly from a local build. But never in a way that would affect some users but not others, from what I've seen.
The problem is the the build server now; if the local build could differs for one or all users i think could be a minor problem.
If there is a corruption in some library, like seth suggest in the arch forum post, it is more alarming.....

Re: tint2 and tint2conf craash after last update

Reply #14
I have tested the following on two platforms with up to date artix good means that launcher tint2conf did not crash I did not observe crashes with other apps eg firefox xfce4-terminal etc etc.

arch tint2 amd-ryzen7 good intel-i5 good
artix tint2 amd-ryzen7 bad intel-i5 bad
artix ryzen7 build amd-ryzen7 good intel-i5 good
artix i5 build amd-ryzen7 good intel-i5 good

so it seems that the crashes only occur with the artix built package. I did not change any other software except the test launcher app itself which is part of tint2.

EDIT: as an experiment I extracted the artix pkg version of /usr/bin/tint2conf from the artix pkgs. If I do that the tint2conf launch fails.

EDIT:the artix tint2 will not even run if I add the geany.desktop as a launcher. I see the buffer overflow when tint2 is reading the desktop file and tint2 crashes. Artix pkg does not crrash launching a 'good (home built)' tint2conf. Home built pkgs have no problem with geany.