Liferea won't run (only within a second)

[Unknow]

Binary package hint: liferea

Ubuntu:
Description: Ubuntu 8.10
Release: 8.10

Liferea:
  Installato: 1.4.18-0ubuntu2
  Candidato: 1.4.18-0ubuntu2
  Tabella versione:
 *** 1.4.18-0ubuntu2 0
        500 http://ports.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

When i open liferea, i can see it's window for a second, then it close suddenly.

Output from shell:

(liferea-bin:5741): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
Segmentation fault

[Emilio Pozuelo Monfort (pochu)]

How are you launching it?

Can you get a backtrace following https://wiki.ubuntu.com/Backtrace ?

[Unknow (unknow-deactivatedaccount)]

Simply click on it's link or typing "liferea-bin" in a shell.

For the backtrace, I'll try, but I've trouble installing debugging symbols.

[Emilio Pozuelo Monfort (pochu)]

KeyofBlueS wrote:
> Simply click on it's link or typing "liferea-bin" in a shell.

You should use liferea and not liferea-bin. Does the crash still happens if you
launch it via the /usr/bin/liferea wrapper script?

[Unknow (unknow-deactivatedaccount)]

Yes i've try "liferea" yet, but it still crash.

For my problem with debugging symbols, when i try to install gdb-dbgsym:

$ sudo apt-get install gdb-dbgsym
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  gdb-dbgsym: Depends: gdb (= 6.8-1ubuntu3) but 6.8-3ubuntu2 is to be installed
E: Broken packages

Must i report a new bug for this also? or am I doing something wrong?

[Emilio Pozuelo Monfort (pochu)]

KeyofBlueS wrote:
> For my problem with debugging symbols, when i try to install gdb-dbgsym:

You don't need debugging symbols for dbg. Try installing them for libgtk2.0-0
and xulrunner-1.9

[Unknow (unknow-deactivatedaccount)]

> You don't need debugging symbols for dbg. Try installing them for libgtk2.0-0 and xulrunner-1.9

I can't find debugging symbols for xulrunner. Instead for libgtk2.0-0-dbgsym i've the same problem as before:

$ sudo apt-get install libgtk2.0-0-dbgsym
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  libgtk2.0-0-dbgsym: Depends: libgtk2.0-0 (= 2.12.9-3ubuntu5) but 2.14.4-0ubuntu1 is to be installed
E: Broken packages

Sorry if I'am missing something.

[Emilio Pozuelo Monfort (pochu)]

KeyofBlueS wrote:
> I can't find debugging symbols for xulrunner. Instead for
> libgtk2.0-0-dbgsym i've the same problem as before:

You have Intrepid, but your dbgsym deb lines in /etc/apt/sources.list are for
Hardy, am I right? You should change that to intrepid.

Anyway, there is a libgtk2.0-0-dbg package in the archive (although you will
need the xulrunner-1.9 dbgsym, if one exists).

[Unknow (unknow-deactivatedaccount)]

Ooooops! what a shame... sorry! yeah that's the problem!

Ok then, I've installed libgtk2.0-0-dbgsym & xulrunner-1.9-dbgsym (anyway, gdb still say "no debugging symbols found")

The backtrace in attachment

Thanks

[Emilio Pozuelo Monfort (pochu)]

Can you install libglib2.0-0-dbg too, and get a new backtrace?

Also, what architecture do you have?

Thanks

[Unknow (unknow-deactivatedaccount)]

Done!

I'm on PowerPC (PlayStation3), is this a problem?

[Emilio Pozuelo Monfort (pochu)]

> I'm on PowerPC (PlayStation3), is this a problem?

Possibly, the bug may be specific to that platform. I wish I had a PS3 to test
if I could reproduce it ;)

[Unknow (unknow-deactivatedaccount)]

Ok, thanks Emilio :)

[Emilio Pozuelo Monfort (pochu)]

Marked as affecting the Ubuntu PS3 port project, let's see if someone from the port team can have a look at this.

[Josh Wood (ninjaschwa)]

I'm having a similar problem, just upgraded to Ibex via update manager, however my problem is Thunar, starts for a few seconds then dies with Segmentation fault output in the terminal, will try get a backtrace attached sometime for this afternoon.

[Unknow (unknow-deactivatedaccount)]

Installed liferea-dbg and get a new backtrace (no message "no debugging symbols found" anymore).

and, if you need, I get the output of "strace -f -eopen liferea-bin".

Let me know if you need something else.

[Rothril Ustelm (rothril)]

I can confirm this on ppc (not PS3).

[Rothril Ustelm (rothril)]

I think that this is a duplicate of bug #281146 (yelp crashed with SIGSEGV in signal_emit_unlocked_R()).

[Unknow (unknow-deactivatedaccount)]

aMule has the same problem, probably also other programs have, too.

I think this bug is related to GTK port for PPC.

Hope someone resolve it.

[Emilio Pozuelo Monfort (pochu)]

Not a Liferea bug

[atany (ye-gorshkov)]

I solved this problem by removing Firefox 3.1 and xulrunner 1.9.1 packages installed from https://launchpad.net/~fta/+archive PPA.

With xulrunner 1.9.1 installed I had the same problem on liferea 1.5.5 beta compiled from sources with xulrunner backend enabled. Liferea with WebKit backend enabled (and xulrunner disabled) did not crash.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Emilio Pozuelo Monfort, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs