menu-cached crashed with SIGSEGV in malloc()

StacktraceTop:
 malloc_consolidate (av=av@entry=0x7fcc66988740 <main_arena>) at malloc.c:4128
 _int_malloc (av=av@entry=0x7fcc66988740 <main_arena>, bytes=bytes@entry=32640) at malloc.c:3421
 __GI___libc_malloc (bytes=32640) at malloc.c:2858
 __gconv_open (toset=0x0, toset@entry=0x7fff9d9598e0 "ANSI_X3.4-1968//", fromset=0x133cb80 "\002", fromset@entry=0x7fff9d9598c0 "UTF-8//", handle=handle@entry=0x7fff9d959900, flags=flags@entry=0) at gconv_open.c:283
 iconv_open (tocode=0x7fff9d9598e0 "ANSI_X3.4-1968//", tocode@entry=0x1348730 "ANSI_X3.4-1968", fromcode=0x7fff9d9598c0 "UTF-8//", fromcode@entry=0x7fcc66a19587 "UTF-8") at iconv_open.c:71

Status changed to 'Confirmed' because the bug affects multiple users.

Normally this report would get upstream to LXDE project, but regarding to the reporters description the unity desctop is affected by the menu-cache library.

In respect to this I add the unity project and because two users are affected I set the status there to confiremed.

Александр (sash0k-v),

has you installed the LXDE desktop additional?

The information would help to triage the report.

Regarding to dublicate

https://bugs.launchpad.net/ubuntu/+source/menu-cache/+bug/1099693

this crasher is also observable by LXDE desktop alone.

Anyway,

unity should not get freezed by this.

Status changed to 'Confirmed' because the bug affects multiple users.

In respect to

https://bugs.launchpad.net/ubuntu/+source/menu-cache/+bug/1099693

which shows that the crasher is observable on pure LXDE(but with not so strange consequences as described here) the LXDE ubuntu package is added.

melchiaros (melchiaros), yes, I have LXDE installed as second environment. Cause Unity is unusable on my hardware (see my bug description above). I post this bug on first apport crash notification after install LXDE and Unity freeze. In fact, system report and my report is 2 different bugs.

Didn't know, how to post report on my problem. On today's build (3.8.0-5-generic #10-Ubuntu SMP Thu Feb 7 17:57:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux) Unity still unusable for me. Seems, its a problem at Nouveau for my hardware.

Aha, when I unserstand you correct that you have mixed it up.

The crash was detected by the system and you gave it a from the crash different summary and description.

o.K. in this case we have to adapt the report. I give the crash the focus, because apport collected files are related to this.

For reporting the unity problem you can use from terminal or with a command line called with

ALT + F2

ubuntu-bug unity

or when you want to report against the kernel directly(int the case you think it is more on the driver)

ubuntu-bug linux

I also adapt the summary.

You can find your old one under old summary(for copy past to your new report).

I know this gives extra work to you, but see it from the other side. It is very hard to work on a report when the parts of it do not fit to each other.

This is the prefered style.

This gives you your original description directly:

https://bugs.launchpad.net/ubuntu/+source/menu-cache/+bug/1098732/comments/0

Removind project Unity, because of

https://bugs.launchpad.net/ubuntu/+source/menu-cache/+bug/1098732/comments/12

melchiaros (melchiaros), thanks!
I posted my problem here now: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1121715
Apport suggest to post problem for Xorg. Screenshot attached.
Can you check, is my report right this time?

Yes, looks good.

I'm using Lubuntu 13.04 (amd64) with kernel version of 3.8.0-generic-3.8.0-16-26; just after I logged in Lubuntu today, an apport dialogue appeared.

In respect that b00507031 has used a pure Lubuntu, the crash is definitivly not caused by the Unity desktop system in any way.

It is a little bit evil behave, but for those who comes new here, it might help more to get to the upstream report at

http://sourceforge.net/tracker/index.php?func=detail&aid=3603920&group_id=180858&atid=894869

and give it a ping or +1 or whatever.

Happened after closing synaptic in Gnome 3.8 session in Ubuntu 13.10 (Saucy) kernel 3.10 Previous session was LXDE

This bug was fixed in the package menu-cache - 0.5.0-0ubuntu1

---------------
menu-cache (0.5.0-0ubuntu1) saucy; urgency=low

  * New upstream release.
   - menu-cached crashed with SIGSEGV in malloc() (LP: #1098732)
  * debian/conrol:
   - Soname bump to libmenu-cache3
  * debian/libmenu-cache3.install
   - Soname bump to libmenu-cache3
  * debian/rules:
   - Update with the soname change.
   - Enable hardening flags.
 -- Julien Lavergne <email address hidden> Tue, 09 Jul 2013 00:51:39 +0200

Upon reading these posts I decided to ad, just in case it is of help to anyone that I was also using LXDE ( Lubuntu) when this ocurred.