xfce4-appfinder crashed with SIGSEGV in garcon_menu_process_file_changes()

Bug #983347 reported by Pavlov Dmitry
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfce4-appfinder (Fedora)
Won't Fix
Undecided
xfce4-appfinder (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

The system was installed in virtualbox v. 4.1.12. Host system is Ubuntu 10.10.
Nothing special was performed on the system. I ran updater and start exploring software.
At the time of crash appfinder was not used, it was just opened and hidden by other open applications.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xfce4-appfinder 4.8.0-3
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Mon Apr 16 22:56:00 2012
ExecutablePath: /usr/bin/xfce4-appfinder
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: xfce4-appfinder
ProcEnviron:
 LANGUAGE=ru:en
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-appfinder
Title: xfce4-appfinder crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
In , martux (martux-redhat-bugs) wrote :
Download full text (15.8 KiB)

Description of problem:

Core was generated by `xfce4-appfinder'.
Program terminated with signal 11, Segmentation fault.
#0 garcon_menu_process_file_changes (menu=0x24d0ac0) at garcon-menu.c:2144
2144 file = G_FILE (lp->data);

Thread 2 (Thread 0x7fcfa01c6700 (LWP 3063)):
#0 0x00007fcfb1c6060d in read () at ../sysdeps/unix/syscall-template.S:82
No locals.
#1 0x00007fcfb1eb292b in g_main_context_invoke_full (context=0x9, priority=-1608754224, function=0x14, data=0xffffffffffffffff, notify=0) at gmain.c:4714
        __PRETTY_FUNCTION__ = "g_main_context_invoke_full"
#2 0x00007fcfb2183448 in test_run_name () from /lib64/libglib-2.0.so.0
No symbol table info available.
#3 0x00007fcfb1c5bc80 in ?? () from /lib64/libpthread-2.13.90.so
No symbol table info available.
#4 0x00007fcfb1ed6664 in g_static_rec_mutex_unlock_full (mutex=0x0) at gthread.c:1552
        depth = <optimized out>
        __PRETTY_FUNCTION__ = "g_static_rec_mutex_unlock_full"
#5 0x00007fcfa01c69c0 in ?? ()
No symbol table info available.
#6 0x0000000000000000 in ?? ()
No symbol table info available.

Thread 1 (Thread 0x7fcfb36b49a0 (LWP 3059)):
#0 garcon_menu_process_file_changes (menu=0x24d0ac0) at garcon-menu.c:2144
        item = <optimized out>
        file_type = <optimized out>
        affects_the_outside = 0
        stop_processing = <optimized out>
        file = <optimized out>
        lp = 0x438
        path = <optimized out>
        __PRETTY_FUNCTION__ = "garcon_menu_process_file_changes"
#1 0x00007fcfb1eb0a9d in g_main_context_iterate (context=0x266ed40, block=38619056, dispatch=32719, self=<optimized out>) at gmain.c:3080
        max_priority = 0
        timeout = <optimized out>
        some_ready = <optimized out>
        nfds = -1307036976
        allocated_nfds = -1307036976
        fds = 0x0
        __PRETTY_FUNCTION__ = "g_main_context_iterate"
#2 0x0000000000000005 in ?? ()
No symbol table info available.
#3 0x0000000000000000 in ?? ()
No symbol table info available.
From To Syms Read Shared Object Library
0x00007fcfb32b0b60 0x00007fcfb32b78ec Yes /usr/lib64/libxfce4ui-1.so.0
0x00007fcfb2c9d300 0x00007fcfb2f4264c Yes /usr/lib64/libgtk-x11-2.0.so.0
0x00007fcfb2a26460 0x00007fcfb2a2cfdc Yes /usr/lib64/libxfce4util.so.4.1.1
0x00007fcfb2806270 0x00007fcfb2819c7c Yes /usr/lib64/libgdk_pixbuf-2.0.so.0
0x00007fcfb25eb440 0x00007fcfb25f83ec Yes /usr/lib64/libgarcon-1.so.0.0.0
0x00007fcfb23d6b30 0x00007fcfb23df92c Yes /usr/lib64/libxfconf-0.so.2.0.0
0x00007fcfb218d890 0x00007fcfb21bdd0c Yes /lib64/libgobject-2.0.so.0
0x00007fcfb1e842e0 0x00007fcfb1f1b59c Yes /lib64/libglib-2.0.so.0
0x00007fcfb1c57680 0x00007fcfb1c62b5c Yes /lib64/libpthread-2.13.90.so
0x00007fcfb18d3b60 0x00007fcfb19f78cc Yes /lib64/libc-2.13.90.so
0x00007fcfb16afad0 0x00007fcfb16b3d7c Yes /usr/lib64/libSM.so.6
0x00007fcfb1497cf0 0x00007fcfb14a5eac Yes /usr/lib64/libICE.so.6
0x00007fcfb1172ce0 0x00007fcfb11fe85c Yes /usr/lib64/libX11.so.6
0x00007fcfb0eb4740 0x00007fcfb0f17aec Yes /usr/lib64/libgdk-x11-2.0.so.0
0x00...

Revision history for this message
In , Kevin (kevin-redhat-bugs) wrote :

This looks like a garcon crash...

'rpm -q garcon xfce4-appfinder' please.

Also, can you duplicate the crash?

Revision history for this message
Pavlov Dmitry (pavlov-dmitry-n) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 garcon_menu_process_file_changes (menu=0x7f91e32778f0) at garcon-menu.c:2196
 g_main_dispatch (context=0x7f91e3092700) at /build/buildd/glib2.0-2.32.1/./glib/gmain.c:2515
 g_main_context_dispatch (context=0x7f91e3092700) at /build/buildd/glib2.0-2.32.1/./glib/gmain.c:3052
 g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x7f91e3092700, self=<optimized out>) at /build/buildd/glib2.0-2.32.1/./glib/gmain.c:3123
 g_main_context_iterate (context=0x7f91e3092700, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.32.1/./glib/gmain.c:3060

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xfce4-appfinder (Ubuntu):
importance: Undecided → Medium
summary: - xfce4-appfinder crashed with SIGSEGV in g_main_context_dispatch()
+ xfce4-appfinder crashed with SIGSEGV in
+ garcon_menu_process_file_changes()
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Changed in xfce4-appfinder (Fedora):
importance: Unknown → Undecided
status: Unknown → Won't Fix
Changed in xfce4-appfinder (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.