Liferea segmentation fault on start

Bug #319508 reported by Roshan George
2
Affects Status Importance Assigned to Milestone
liferea (Ubuntu)
New
Undecided
Unassigned

Bug Description

Liferea crashes with a segmentation fault when started. It used to work, but then started having trouble updating. Now, with no .liferea-1.4 directory (and hence, no database), it crashes instantly on start (output is attached).

Versions:
Liferea 1.4.14
Ubuntu Hardy 8.04.1 x86_64, 2.6.24-23-generic
Python 2.5.2 (package version 2.5.2-2ubuntu4.1)

Revision history for this message
Roshan George (roshan-george) wrote :
Revision history for this message
Roshan George (roshan-george) wrote :

I have also attached the output to the command liferea --debug-all. This is all I can manage to do. I tried installing the liferea-dbg package and tried running gdb on the program /usr/lib/debug/usr/bin/liferea-bin but I got this output: (chmodding that file to executable did not help)

---------
Starting program: /usr/lib/debug/usr/bin/liferea-bin
/bin/bash: /usr/lib/debug/usr/bin/liferea-bin: Permission denied
/bin/bash: line 0: exec: /usr/lib/debug/usr/bin/liferea-bin: cannot execute: Success

Program exited with code 0176.
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
You can't do that without a process to debug.
-------

The Ubuntu Wiki Debugging instructions don't seem to be helpful here. How can I provide more information?

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Thanks for the report! This is likely cuased due to the update in bug 295490, so I'm marking this as a duplicate.

By the way, you need to run gdb with /usr/bin/liferea-bin, then it will automatically load the debugging symbols from /usr/lib/debug/usr/bin/liferea-bin.

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.