Bug 534138 - Mapnik viewer segfaults on startup
Summary: Mapnik viewer segfaults on startup
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: mapnik
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christopher Brown
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-10 17:26 UTC by ajs
Modified: 2010-05-03 15:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-03 15:53:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description ajs 2009-11-10 17:26:42 UTC
Description of problem:
Mapnik viewer segfaults on startup


Version-Release number of selected component (if applicable):
mapnik-0.5.2-0.13.svn780.fc11.x86_64

How reproducible:
Always

Steps to Reproduce:
1. /usr/bin/viewer
  or
1. /usr/bin/viewer mapfile.xml

Actual results:
Segmentation fault


Expected results:
Mapkik viewer GUI starts up

Additional info:
Results of 'rpm -qa qt*'

qt-x11-4.5.3-7.fc11.x86_64
qt-sqlite-4.5.3-7.fc11.x86_64
qt3-3.3.8b-25.fc11.x86_64
qt-4.5.3-7.fc11.x86_64

Comment 1 ajs 2009-11-10 19:10:24 UTC
I rebuilt mapnik-0.6.1-3.fc12.src.rpm for F11 and this fixed the segfault on my machine.

Please update the F11 mapnik to mapnik-0.6.1-3

Comment 2 Christopher Brown 2009-11-11 12:50:02 UTC
Hi Anthony,

Thanks for the bug report.

Mapnik 0.6.1 is available in the Fedora 12 repositories.

Updating mapnik in F11 involves a soname change and rebuilding of dependencies which we wouldn't normally do just to fix the viewer module. I'll see if I can trace the segfault and apply a fix to the 0.5.2 branch to resolve this. No promises I'm afraid as my time is extremely limited and mapnik's current maintainer is AWOL.

If you can debug and patch in the meantime I'm happy to apply.

Regards

Comment 3 ajs 2009-11-11 17:28:02 UTC
Not updating due to the soname change makes sense.

I found a couple of hardcoded paths in the 0.6.1 version of viewer that were causing problems loading the input plugins.  I have fixed those in the .spec file that I used to build mapnik.  I was going to open another bug for f12 and attach it there.

A quick look at 0.5.2 shows similar problems, but I have not gotten around to fixing them and seeing if that fixes the segfault.

Comment 4 ajs 2009-11-11 22:11:51 UTC
Fixing the path problem did not fix the segfault.

After downloading the debuginfo packages, running viewer through gdb results in:

GNU gdb (GDB) Fedora (6.8.50.20090302-38.fc11)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(gdb) run
Starting program: /usr/bin/viewer 
[Thread debugging using libthread_db enabled]
warning: "/usr/lib/debug/usr/lib64/libicudata.so.40.1.debug": The separate debug info file has no debug info
registered datasource : raster
registered datasource : shape
registered datasource : gdal
registered datasource : postgis

Program received signal SIGSEGV, Segmentation fault.
x11EventSourcePrepare (this=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:79
79	                && !source->d->queuedUserInputEvents.isEmpty()));
(gdb) bt
#0  0x00000035f6022275 in x11EventSourcePrepare (this=<value optimized out>) from /usr/lib64/libQtGui.so.4
#1  0x00000035f6022230 in ?? () from /usr/lib64/libQtGui.so.4
#2  0x0000000000000020 in ?? ()
#3  0x0000000000686068 in ?? ()
#4  0x00007fffffffd6fc in ?? ()
#5  0x0000000000686068 in ?? ()
#6  0xffffffff80a7a8e2 in ?? ()
#7  0x0000000000686060 in ?? ()
#8  0x0000000000686060 in ?? ()
#9  0x00000000006ebe50 in ?? ()
#10 0x0000000000000004 in ?? ()
#11 0x000000343bedd5a0 in ?? () from /lib64/libglib-2.0.so.0
#12 0x000000368120a400 in ?? () at pthread_mutex_unlock.c:71 from /lib64/libpthread.so.0
#13 0x0000000000686068 in ?? ()
#14 0x000000343bc3ace1 in g_main_context_iterate (context=0x343bc3a90a, block=<value optimized out>, dispatch=<value optimized out>, 
    self=<value optimized out>) at gmain.c:2435
#15 0x000000343bc3b20a in IA__g_main_context_iteration (context=0x686060, may_block=1) at gmain.c:2518
#16 0x000000344042c244 in giop_recv_buffer_get (ent=0x7fffffffd7f0, timeout=0x7fffffffd82c) at giop-recv-buffer.c:727
#17 0x0000003440430cc0 in ORBit_small_invoke_stub (obj=0x6eab60, m_data=0x343fe3c3a0, ret=<value optimized out>, args=0x0, 
    ctx=<value optimized out>, ev=0x7fffffffd8b0) at orbit-small.c:660
#18 0x000000343fc2c8cb in ConfigServer_ping (_obj=0x69fb40, ev=<value optimized out>) at GConfX-stubs.c:279
#19 0x000000343fc121b3 in gconf_activate_server (start_if_not_found=0, error=0x0) at gconf-internals.c:2859
#20 0x000000343fc1f814 in try_to_contact_server (err=<value optimized out>, start_if_not_found=<value optimized out>) at gconf.c:2234
#21 gconf_get_config_server (err=<value optimized out>, start_if_not_found=<value optimized out>) at gconf.c:2278
#22 0x000000343fc20319 in gconf_engine_connect (conf=0x6e5440, start_if_not_found=<value optimized out>, err=0x0) at gconf.c:364
#23 0x000000343fc2096c in gconf_engine_get_default () at gconf.c:575
#24 0x000000343fc287f4 in gconf_client_get_default () at gconf-client.c:433
#25 0x00000035f62bcd03 in getGConfString (value=<value optimized out>) at styles/gtksymbols.cpp:346
#26 getThemeName (value=<value optimized out>) at styles/gtksymbols.cpp:393
#27 0x00000035f62bcfad in init_gtk_window () at styles/gtksymbols.cpp:402
#28 0x00000035f62bdfc2 in QGtk::initGtkWidgets () at styles/gtksymbols.cpp:651
#29 0x00000035f62b0938 in QGtkStylePrivate (this=<value optimized out>) at styles/qgtkstyle.cpp:168
#30 QGtkStyle::QGtkStyle (this=<value optimized out>) at styles/qgtkstyle.cpp:246
#31 0x00000035f622c5e3 in QStyleFactory::create (key=<value optimized out>) at styles/qstylefactory.cpp:169
#32 0x00000035f5f93910 in QApplication::style () at kernel/qapplication.cpp:1332
#33 0x00000035f5f93bad in QApplicationPrivate::initialize (this=0x682650) at kernel/qapplication.cpp:847
#34 0x00000035f5f93c4b in QApplicationPrivate::construct (this=0x682650, dpy=0x0, visual=0, cmap=0) at kernel/qapplication.cpp:750
#35 0x00000035f5f94ad1 in QApplication::QApplication (this=0x7fffffffe050, argc=@0x7fffffffdefc, argv=0x7fffffffe208, _internal=263427)
    at kernel/qapplication.cpp:671
---Type <return> to continue, or q <return> to quit---
#36 0x0000000000413a01 in main (argc=1, argv=0x7fffffffe208) at main.cpp:40
(gdb) 


This doesn't mean much to me.

Comment 5 Christopher Brown 2009-11-29 18:39:41 UTC
Hi Anthony,

This works in F-12.

I'm not very good with debugging backtraces (but thanks for taking the time to generate one) however it seems to me that the problem lies with the qt libraries than mapnik. Unfortunately I don't have an F-11 to look at this on.

Could I ask you to temporarily change theme on your desktop from default to "clearlooks" and tell me if this allows the viewer to launch. This is as per:

https://bugzilla.redhat.com/show_bug.cgi?id=498111

Thanks

Comment 6 Christopher Brown 2009-12-23 22:40:53 UTC
Hi Anthony,

Have you been able to test with clearlooks as requested?

Thanks

Comment 7 Bug Zapper 2010-04-28 11:12:31 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

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 prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Christopher Brown 2010-05-03 15:53:39 UTC
Closing this as works for me and no response from reporter.


Note You need to log in before you can comment on or make changes to this bug.