Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 210958
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Linux Gnome Desktop Team <gnome@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Lukasz Goralczyk <lukasz.goralczyk@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 210958 depends on: Show dependency tree
Bug 210958 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-02-21 11:32 0000
gsynaptics, when started, crashes. There was time when gsynaptics worked on my
system, but for some time it doesn't (can't tell when). When installed *not*
from ebuild it works.

There's a patch (no-libgnome-patch) in gsynaptics ebuild which replaces
gnome_pixmap_file() with g_build_filename() (file: main.c, func:
setup_dialog()). When going deeper - crash is inside g_build_filename()
(glib-2.14.6). When looking into g_build_filename() - g_build_path_va() is
called (file: glib/gfileutils.c). Inside g_build_path_va() crash is in line "if
(!*element)", earlier va_arg() doesn't return 0 (end of arguments) but 1, that
causes element to hold invalid address. Perhaps there's something wrong with
g_build_path_va()?

Also there's no icon, but I'm not sure why (probably also cause by the patch).

Temporary solution: install gsynaptics from source, not by using
portage/ebuild.


Reproducible: Always

Steps to Reproduce:
1. Emerge gsynaptics (gsynaptics-0.9.13).
2. Start gsynaptics


Actual Results:  
For a short period of time a window appears, then there's SIGSEGV (Segmentation
fault).

Expected Results:  
gsynaptics is started.

------- Comment #1 From Rémi Cardona 2008-02-21 13:19:33 0000 -------
Could you run gsynaptics inside gdb and provide a proper backtrace?

Thanks

------- Comment #2 From Lukasz Goralczyk 2008-02-21 15:39:09 0000 -------
Backtrace for gsynaptics:

#0  g_build_path_va (separator=0x2b80cc13687b "/", first_element=0x4051b4 "g", 
    args=0x7fffe4134c20, str_array=0x0) at gfileutils.c:1478
#1  0x00002b80cc0dd1d9 in IA__g_build_filename (first_element=0x4051b5 "")
    at gfileutils.c:1794
#2  0x00000000004029f1 in main (argc=1, argv=0x7fffe4134e38) at main.c:686

Lukasz.

------- Comment #3 From Gilles Dartiguelongue 2008-07-14 13:15:26 0000 -------
I've just commited 0.9.14 with a fix from the debian folks, it runs here now.
Please reopen if it's not working for you.

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug