mc from hardy crashes when tryied to open bad *.cpio

Asked by crypt on 2009-05-27

Binary package hint: mc

reproduce steps:
start mc
select bad.cpio
hit enter

mc doesn't crash in later versions of ubuntu (intrepid), it shows warning.

Description: Ubuntu 8.04.2
Release: 8.04

  Installed: 1:4.6.1-8ubuntu1
  Candidate: 1:4.6.1-8ubuntu1
  Version table:
 *** 1:4.6.1-8ubuntu1 0
        990 hardy/universe Packages
        100 /var/lib/dpkg/status
Program received signal SIGABRT, Aborted.
0x00007f56f88de095 in raise () from /lib/
#0 0x00007f56f88de095 in raise () from /lib/
#1 0x00007f56f88dfaf0 in abort () from /lib/
#2 0x00007f56f93b8090 in IA__g_logv (log_domain=0x0,
    format=0x7f56f93eb8e8 "file %s: line %d (%s): assertion failed: (%s)",
    args1=0x7fff01852e00) at /build/buildd/glib2.0-2.16.6/glib/gmessages.c:497
#3 0x00007f56f93b8123 in IA__g_log (
    log_domain=0x6902 <Address 0x6902 out of bounds>, log_level=26882,
    format=0x6 <Address 0x6 out of bounds>)
    at /build/buildd/glib2.0-2.16.6/glib/gmessages.c:517
#4 0x00007f56f93b81a6 in g_assert_warning (log_domain=0x0,
    file=0x49562e "cpio.c", line=273,
    pretty_function=0x4956d0 "cpio_read_bin_head",
    expression=0x49565f "u.buf.c_magic == 070707")
    at /build/buildd/glib2.0-2.16.6/glib/gmessages.c:573
#5 0x000000000046a21e in ?? ()
#6 0x0000000000462184 in ?? ()
#7 0x000000000046228b in ?? ()
#8 0x0000000000462331 in ?? ()
#9 0x00000000004624d3 in ?? ()
#10 0x0000000000462529 in ?? ()
#11 0x000000000046513f in ?? ()
#12 0x0000000000427e44 in ?? ()
#13 0x0000000000428126 in ?? ()
#14 0x00000000004155b6 in ?? ()
#15 0x0000000000430177 in ?? ()
#16 0x000000000043200f in ?? ()
#17 0x0000000000412310 in ?? ()
#18 0x0000000000412652 in ?? ()
#19 0x0000000000426c73 in ?? ()
#20 0x000000000042759a in ?? ()
#21 0x00007f56f88ca1c4 in __libc_start_main () from /lib/
#22 0x0000000000406e69 in ?? ()
#23 0x00007fff01855f08 in ?? ()
#24 0x0000000000000000 in ?? ()

Question information

English Edit question
Ubuntu mc Edit question
No assignee Edit question
Last query:
Last reply:
Yury V. Zaytsev (zyv) said : #1

Use the backports fom my PPA or upgrade to a more recent version of Ubuntu. Closing as fixed.

crypt (cryptogranny1) said : #2

 Sorry, I didn't get it. What sense in posting a bug, which is replied more then a year after it was reported and the only answer is "use new version". Ofcause, I could wait for new version without spending my time for bugreporting.

crypt (cryptogranny1) said : #3

Hardy is LTS release. Shouldn't this bug be fixed anyway?

Yury V. Zaytsev (zyv) said : #4

Maybe you are thinking I'm getting money from Canonical for triaging bugs and not doing my job as I looked at your report one year later? Bad luck, I am not even involved in Ubuntu, I'm an upstream developer and made a bugzilla-cleanup raid against Ubuntu just to see what we already fixed and what we yet have to fix.

If you wanted your report to be dealt with in a timely manner, maybe you should have better submitted this upstream directly as obviously Ubuntu doesn't have the manpower to triage the bugs and escalate them upstream on time.

In what concerns Hardy, let's see. A normal sync request from Debian unstable into Maverick took about half a year to get processed. Am I so much interested in Ubuntu to start pinging backport people to get it uploaded just before EOL???

I just use my own packages from my PPA. They are just as official as anything, because I maintain mc in Debian and am an upstream developer.

Can you help with this problem?

Provide an answer of your own, or ask crypt for more information if necessary.

To post a message you must log in.