Opened 17 years ago

Closed 17 years ago

Last modified 15 years ago

#573 closed defect (invalid)

upgrade to titan but it won't start as I get a segmentation fault

Reported by: bshcm03@… Owned by: homann
Priority: major: does not work as expected Milestone:
Component: Build/Install Version: 0.8
Keywords: segmentation fault Cc:
Must Fix for Release: No Platform: Fedora
Platform Version: fedora core 5 x64 Awaiting user input: no

Description

I have upgraded to titan but QGIS will no longer start - I get a segmentation fault on start up. I was able to use the previous version (with intermittent errors).

I have created (and attached) log files for configure, make and make install. I was getting a qt4 error but this was resolved after I chagned the qt4 installation directory from default to /usr/local/qt4

I ideally run qgis from within grass (grass 6.2.1) but cannot do this either.

I was getting some make install warnings,but not errors.

Do you have any thoughts?

If you need any further information etc, please do not hesitate to ask.

Thanks

Attachments (8)

config.log (40.7 KB ) - added by bshcm03@… 17 years ago.
make.log (16.9 KB ) - added by anonymous 17 years ago.
make.install.log (163.9 KB ) - added by bshcm03@… 17 years ago.
config.2.log (96.4 KB ) - added by homann 17 years ago.
My config.log
config.3.log (91.2 KB ) - added by bshcm03 17 years ago.
log file generated by ./configure
bh.make.check.log (164.0 KB ) - added by bshcm03 17 years ago.
make check output with error message
config.4.log (91.4 KB ) - added by bshcm03 17 years ago.
latest config.log
qgis error 8-2-07 (8.8 KB ) - added by bshcm03 17 years ago.
debug output at startup before segmentation fault

Download all attachments as: .zip

Change History (15)

by bshcm03@…, 17 years ago

Attachment: config.log added

by anonymous, 17 years ago

Attachment: make.log added

by bshcm03@…, 17 years ago

Attachment: make.install.log added

by homann, 17 years ago

Attachment: config.2.log added

My config.log

comment:1 by homann, 17 years ago

Milestone: Version 0.8 ReleaseVersion 0.8.1 Release
Owner: changed from nobody to homann
Priority: blockermajor
Status: newassigned
Version: HEAD0.8

When you run ./configure, a file named config.log is automatically created. This is my config.log which doesn't look like yours. Did you pipe the output of configure to config.log?

Around line 10, you can see how I configured it. QT and GRASS is probably needed. If you still have problems, use --enable-debug to give us some hints when running.

What is the revision of the source? Tar-ball or from SVN?

in reply to:  1 comment:2 by anonymous, 17 years ago

Platform Version: fedora core 5 x64

Replying to homann:

When you run ./configure, a file named config.log is automatically created. This is my config.log which doesn't look like yours. Did you pipe the output of configure to config.log?

Around line 10, you can see how I configured it. QT and GRASS is probably needed. If you still have problems, use --enable-debug to give us some hints when running.

What is the revision of the source? Tar-ball or from SVN?

Thanks for looking at this. The correct config.log is now attached - you were right about how the previous one was generated.

I am using Tar-ball source downloaded yesterday so the version is 0.8.0

I have checked the config.log file as best I can and can't seem to see any errors or warnings. I tried running make clean then make check after running ./configure again and I got errors. My piped log file for make check is also attached. At the end of this log file I have included the error message which was displayed.

Any more thoughts?

by bshcm03, 17 years ago

Attachment: config.3.log added

log file generated by ./configure

by bshcm03, 17 years ago

Attachment: bh.make.check.log added

make check output with error message

comment:3 by bshcm03, 17 years ago

I have progressed a little: configure now completes and config log is attached. Make also completes withour error and make install completes without errors. I fixed the paths to qt4 and installed gsl. But, when I run qgis from the command line, I still get a segmentation fault. The debug output is attached as qgis error 8-2-07

Can you have a look at this information and suggest some more things to try.

Thanks.

by bshcm03, 17 years ago

Attachment: config.4.log added

latest config.log

by bshcm03, 17 years ago

Attachment: qgis error 8-2-07 added

debug output at startup before segmentation fault

comment:4 by homann, 17 years ago

Hmm...

It crashes while loading plugins/providers/widgets from /usr/lib/qgis/. It loads them in alphabetical order, so you could try remove libqgsprojectionselector.so/.a and then proceed in alphabetical order... :-)

Have you double-checked you are using x64 version of all libs? Try ldd on both 'qgis' and all the plugins in /usr/lib/qgis/, to see what they link to.

Also try starting qgis in gdb, and supply backtrace.

You are not the only one with problems on x64, se #563

in reply to:  4 comment:5 by anonymous, 17 years ago

Replying to homann:

Hmm...

It crashes while loading plugins/providers/widgets from /usr/lib/qgis/. It loads them in alphabetical order, so you could try remove libqgsprojectionselector.so/.a and then proceed in alphabetical order... :-)

Have you double-checked you are using x64 version of all libs? Try ldd on both 'qgis' and all the plugins in /usr/lib/qgis/, to see what they link to.

Also try starting qgis in gdb, and supply backtrace.

You are not the only one with problems on x64, se #563

Thanks - it now works. This is what I did.

I followed all the steps you suggested above and using gdb helped me to identify the problem. This is what I did (for the benefit of others)

prompt> gdb

(gdb) run /usr/bin/qgis

the error occured when it tried to run something from the directory /usr/lib64/qt3-3

I renamed this directory /usr/lib64/qt3-3bu and then restared qgis. It loaded and now seems to be working fine.

I renamed to directory back to /usr/lib64/qt3-3 so that I could recreate the error to provide you with better feedback but I cannot recreate the problem.

Problem solved. Thanks for your help.

comment:6 by homann, 17 years ago

Resolution: invalid
Status: assignedclosed

Sounds like the wrong Qt runtime libraries got picked up. Not a bug in Qgis, but glad to help! :-)

comment:7 by (none), 15 years ago

Milestone: Version 0.8.1

Milestone Version 0.8.1 deleted

Note: See TracTickets for help on using tickets.