Public bug reported:

Binary package hint: alacarte

Here is a description of what happened.

I'm using Ubuntu 8.04.2. I recently installed the Konqueror browser
(package konqueror) that depends on a good number of KDE packages. When
I looked at the Applications menu, there were lots of new KDE-related
items under the Other submenu. I don't need them at all, so I opened the
menu editor (alacarte) and started to remove the items from the Other
category one by one, after examining their properties. It took several
seconds to alacarte to apply each change when I was unchecking the
entries. If I tried to uncheck another menu item while it was still
processing the first, the second change did nothing. So when I had
already done a dozen or two of those menu items, alacarte crashed. I
think it was removing another menu item from the Other menu immediately
before the crash.

My machine is relatively slow nowadays, it's Pentium III 666 MHz.

ProblemType: Crash
Architecture: i386
Date: Mon Jan 26 20:01:19 2009
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/alacarte
InterpreterPath: /usr/bin/python2.5
Package: alacarte 0.11.5-0ubuntu1.1
PackageArchitecture: all
ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte
ProcEnviron:
 
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: alacarte
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: alacarte crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.24-23-generic i686
UserGroups: adm admin audio cdrom floppy fuse lpadmin plugdev sambashare video

** Affects: alacarte (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-crash

-- 
alacarte crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/321460
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to alacarte in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to