Bug 156706 - TAR/BZCAT always finish with 'abort' within KDE4 environment
Summary: TAR/BZCAT always finish with 'abort' within KDE4 environment
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-26 13:18 UTC by Nick Warne
Modified: 2008-01-27 00:31 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Warne 2008-01-26 13:18:09 UTC 
Version:           4.00.80 (KDE 4.0.80 >= 20080104) (using 4.00.80 (KDE 4.0.80 >= 20080104), compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-g9b73e76f

I lumped this under KDE general, as I do not know where the issue is.

I have noticed since moving to KDE4, that whenever I use tar or bzcat within konsole (or any other term), tar/bzcat untarball sucessfully, but always finish with an 'aborted' signal:

tar zxvf claws-mail-theme_ZX.tar.gz
...
...
...
...
ZX-0_1.1/clip.xpm
ZX-0_1.1/queue_open.xpm
ZX-0_1.1/properties.xpm
Aborted

If I drop out of X, or Ctrl+Alt+Fn to another terminal, tar/bzcat works fine (as before).  Remember though, the operation is still SUCCESSFUL so no issues with function.

I have never seen this behaviour until starting to use the KDE4 environment.

Nick
Comment 1 Maksim Orlovich 2008-01-26 17:44:13 UTC 
Do they do that outside of KDE if you 'export MALLOC_CHECK_=2" before running them?
Comment 2 Nick Warne 2008-01-26 17:52:29 UTC 
Heh.  Clever man, Maksim.

YES, they then exhibit same issue.

Nick
Comment 3 Maksim Orlovich 2008-01-26 19:16:40 UTC 
Thanks. Then it's not a KDE bug --- the start script is enabling extra protection, and it seems to detect a problem with those apps.
Comment 4 Nick Warne 2008-01-27 00:31:18 UTC 
OK, to complete this, my fix is to issue:

unset MALLOC_CHECK_

in a the terminal before using tar/bzcat

Nick