Bug #295490 “Liferea doesn't start with “Aborted” error.” : Bugs : liferea package : Ubuntu

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2008-11-08: Re: [Bug 295490] [NEW] Liferea doesn't start with "Aborted" error.

#1

What architecture?

Can you run liferea with --debug-all and put here the output?

Revision history for this message

Ciso (cisoprogressivo) wrote on 2008-11-08:

#2

Download full text (5.7 KiB)

32bit

this is the output:
:~$ liferea --debug-all
TRACE: + rule_init
TRACE: - rule_init
TRACE: + db_init
DB: Opening DB file /home/ciso/.liferea_1.4/liferea.db...
DB: executing SQL: CREATE TABLE info ( name TEXT, value TEXT, PRIMARY KEY (name) );
DB: -> result: 0 (success)
DB: current DB schema version: -1
DB: executing SQL: CREATE TABLE items ( title TEXT, read INTEGER, new INTEGER, updated INTEGER, popup INTEGER, marked INTEGER, source TEXT, source_id TEXT, valid_guid INTEGER, real_source_url TEXT, real_source_title TEXT, description TEXT, date INTEGER, comment_feed_id TEXT, comment INTEGER);
DB: -> result: 0 (success)
DB: executing SQL: CREATE INDEX items_idx ON items (source_id);
DB: -> result: 0 (success)
DB: executing SQL: CREATE INDEX items_idx2 ON items (comment_feed_id);
DB: -> result: 0 (success)
DB: executing SQL: CREATE TABLE itemsets ( item_id INTEGER, parent_item_id INTEGER, node_id TEXT, parent_node_id TEXT, read INTEGER, comment INTEGER, PRIMARY KEY (item_id, node_id));
DB: -> result: 0 (success)
DB: executing SQL: CREATE INDEX itemset_idx ON itemsets (node_id);
DB: -> result: 0 (success)
DB: executing SQL: CREATE INDEX itemset_idx2 ON itemsets (item_id);
DB: -> result: 0 (success)
DB: executing SQL: CREATE TABLE metadata ( item_id INTEGER, nr INTEGER, key TEXT, value TEXT, PRIMARY KEY (item_id, nr));
DB: -> result: 0 (success)
DB: executing SQL: CREATE INDEX metadata_idx ON metadata (item_id);
DB: -> result: 0 (success)
DB: executing SQL: CREATE TABLE subscription ( node_id STRING, source STRING, orig_source STRING, filter_cmd STRING, update_interval INTEGER, default_interval INTEGER, discontinued INTEGER, available INTEGER, PRIMARY KEY (node_id));
DB: -> result: 0 (success)
DB: executing SQL: CREATE TABLE update_state ( node_id STRING, last_modified STRING, etag STRING, last_update INTEGER, last_favicon_update INTEGER, PRIMARY KEY (node_id));
DB: -> result: 0 (success)
DB: executing SQL: CREATE TABLE subscription_metadata ( node_id STRING, nr INTEGER, key TEXT, value TEXT, PRIMARY KEY (node_id, nr));
DB: -> result: 0 (success)
DB: executing SQL: CREATE INDEX subscription_metadata_idx ON subscription_metadata (node_id);
DB: -> result: 0 (success)
DB: executing SQL: CREATE TABLE node ( node_id STRING, parent_id STRING, title STRING, type INTEGER, expanded INTEGER, view_mode INTEGER, sort_column INTEGER, sort_reversed INTEGER, PRIMARY KEY (node_id));
DB: -> result: 0 (success)
DB: executing SQL: CREATE TABLE view_state ( node_id STRING, unread INTEGER, count INTEGER, PRIMARY KEY (node_id));
DB: -> result: 0 (success)
DB: table setup took 0,015s
DB: executing SQL: DROP TRIGGER item_insert;
DB: -> result: 1 (no such trigger: item_insert)
DB: executing SQL: DROP TRIGGER item_update;
DB: -> result: 1 (no such tri...

32bit

this is the output:
:~$ liferea --debug-all
TRACE: + rule_init
TRACE: - rule_init
TRACE: + db_init
DB: Opening DB file /home/ciso/.liferea_1.4/liferea.db...
DB: executing SQL: CREATE TABLE info (    name	TEXT,    value	TEXT,    PRIMARY KEY (name) );
DB:  -> result: 0 (success)
DB: current DB schema version: -1
DB: executing SQL: CREATE TABLE items (   title		TEXT,   read		INTEGER,   new		INTEGER,   updated		INTEGER,   popup	INTEGER,   marked		INTEGER,   source		TEXT,   source_id		TEXT,   valid_guid		INTEGER,   real_source_url	TEXT,   real_source_title	TEXT,   description	TEXT,   date		INTEGER,   comment_feed_id	TEXT,   comment            INTEGER);
DB:  -> result: 0 (success)
DB: executing SQL: CREATE INDEX items_idx ON items (source_id);
DB:  -> result: 0 (success)
DB: executing SQL: CREATE INDEX items_idx2 ON items (comment_feed_id);
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TABLE itemsets (   item_id		INTEGER,   parent_item_id     INTEGER,   node_id		TEXT,   parent_node_id     TEXT,   read		INTEGER,   comment            INTEGER,   PRIMARY KEY (item_id, node_id));
DB:  -> result: 0 (success)
DB: executing SQL: CREATE INDEX itemset_idx  ON itemsets (node_id);
DB:  -> result: 0 (success)
DB: executing SQL: CREATE INDEX itemset_idx2 ON itemsets (item_id);
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TABLE metadata (   item_id		INTEGER,   nr              	INTEGER,   key             	TEXT,   value           	TEXT,   PRIMARY KEY (item_id, nr));
DB:  -> result: 0 (success)
DB: executing SQL: CREATE INDEX metadata_idx ON metadata (item_id);
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TABLE subscription (   node_id            STRING,   source             STRING,   orig_source        STRING,   filter_cmd         STRING,   update_interval	INTEGER,   default_interval   INTEGER,   discontinued       INTEGER,   available          INTEGER,   PRIMARY KEY (node_id));
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TABLE update_state (   node_id            STRING,   last_modified      STRING,   etag               STRING,   last_update        INTEGER,   last_favicon_update INTEGER,   PRIMARY KEY (node_id));
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TABLE subscription_metadata (   node_id            STRING,   nr                 INTEGER,   key                TEXT,   value              TEXT,   PRIMARY KEY (node_id, nr));
DB:  -> result: 0 (success)
DB: executing SQL: CREATE INDEX subscription_metadata_idx ON subscription_metadata (node_id);
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TABLE node (   node_id		STRING,   parent_id		STRING,   title		STRING,   type		INTEGER,   expanded           INTEGER,   view_mode		INTEGER,   sort_column	INTEGER,   sort_reversed	INTEGER,   PRIMARY KEY (node_id));
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TABLE view_state (   node_id            STRING,   unread             INTEGER,   count              INTEGER,   PRIMARY KEY (node_id));
DB:  -> result: 0 (success)
DB: table setup took 0,015s
DB: executing SQL: DROP TRIGGER item_insert;
DB:  -> result: 1 (no such trigger: item_insert)
DB: executing SQL: DROP TRIGGER item_update;
DB:  -> result: 1 (no such trigger: item_update)
DB: executing SQL: DROP TRIGGER item_removal;
DB:  -> result: 1 (no such trigger: item_removal)
DB: executing SQL: DROP TRIGGER subscription_removal;
DB:  -> result: 1 (no such trigger: subscription_removal)
DB: Checking for items not referenced in table 'itemsets'...

DB: executing SQL: BEGIN;    CREATE TEMP TABLE tmp_id ( id );   INSERT INTO tmp_id SELECT ROWID FROM items WHERE ROWID NOT IN (SELECT item_id FROM itemsets);   DELETE FROM items WHERE ROWID IN (SELECT id FROM tmp_id LIMIT 1000);   DROP TABLE tmp_id;END;
DB:  -> result: 0 (success)
DB: Checking for invalid item ids in table 'itemsets'...

DB: executing SQL: BEGIN;    CREATE TEMP TABLE tmp_id ( id );   INSERT INTO tmp_id SELECT item_id FROM itemsets WHERE item_id NOT IN (SELECT ROWID FROM items);   DELETE FROM itemsets WHERE item_id IN (SELECT id FROM tmp_id LIMIT 1000);   DROP TABLE tmp_id;END;
DB:  -> result: 0 (success)
DB: Checking for items without a subscription...

DB: executing SQL: DELETE FROM itemsets WHERE comment = 0 AND node_id NOT IN (SELECT node_id FROM subscription);
DB:  -> result: 0 (success)
DB: DB cleanup finished. Continuing startup.

DB: executing SQL: CREATE TRIGGER item_insert INSERT ON items BEGIN    UPDATE itemsets SET read = new.read    WHERE item_id = new.ROWID; END;
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TRIGGER item_update UPDATE ON items BEGIN    UPDATE itemsets SET read = new.read    WHERE item_id = new.ROWID; END;
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TRIGGER item_removal DELETE ON itemsets BEGIN    DELETE FROM items WHERE ROWID = old.item_id;    DELETE FROM metadata WHERE item_id = old.item_id; END;
DB:  -> result: 0 (success)
DB: executing SQL: CREATE TRIGGER subscription_removal DELETE ON subscription BEGIN    DELETE FROM node WHERE node_id = old.node_id;    DELETE FROM update_state WHERE node_id = old.node_id;    DELETE FROM subscription_metadata WHERE node_id = old.node_id; END;
DB:  -> result: 0 (success)
TRACE: - db_init
CONF: proxy auto detect is configured
CONF: no proxy GNOME of $http_proxy configuration found...
CONF: Proxy settings are now NULL:0 NULL:NULL
TRACE: + plugin_mgmt_get_init
PLUGINS: Scanning for plugins (/usr/lib/liferea):
PLUGINS: -> libnotify notification (liblinotiflibnotify.so, type=3)
PLUGINS: -> XulRunner Rendering Plugin (liblihtmlx.so, type=0)
PLUGINS: -> LUA Scripting Support Plugin (libliscrlua.so, type=4)
PLUGINS: using "XulRunner" for HTML rendering...
TRACE: + mozembed_init (XPCOM_GLUE)
Aborted

I have both Firefox 3 and Firefox 3.1 (xulrunner 1.9 and xulrunner 1.9.1). I see it's about xulrunner from this output.

Revision history for this message

Fabien Tassin (fta) wrote on 2008-11-14:

#3

I'm getting the same Abort. I tracked it down to a sqlite3 version mismatch in xulrunner.
See http://mxr.mozilla.org/mozilla-central/source/storage/src/mozStorageService.cpp#68

The problem comes from both a/ xulrunner-1.9.1 and b/ liferea.
I guess those who don't have xulrunner-1.9.1 installed are not seeing this.

a/ Liferea is built with the xul "static glue", meaning it will use the newest xul engine registered in /etc/gre.d.
If you have both xulrunner-1.9 and xulrunner-1.9.1 installed, liferea will start with 1.9.1.

The problem is that while xulrunner-1.9 is built with *system* sqlite3 (3.5.9), xulrunner-1.9.1 is built with *in-source* sqlite3 (3.6.4).

3.6.* is needed for various reasons (mostly performance improvements) but unfortunately, 3.6.* is not in Ubuntu (yet). That's the reason I decided to go for in-source sqlite3 in xulrunner-1.9.1. As liferea is built with system sqlite3, but goes for xulrunner 1.9.1 at run time, it gets the version mismatch.

The problem could be solved in Jaunty by uploading sqlite >= 3.6.4 and rebuilding xulrunner 1.9.1 (so it automatically jumps back to system sqlite3 - there's a test at build time for that).
For Intrepid and Hardy (for which I provide xulrunner 1.9.1 through my PPA) I guess I can re-add a workaround we had at some point in xulrunner-1.9, which was to provide a libsqlite3.so.0 symlink toward the libsqlite3.so inside the xul libdir. The same work-around will work in jaunty too, while we {wait for,work on} the sqlite 3.6 update.

That's where the liferea issue kicks in. It will only work if liferea finds its libs (in particular sqlite) in the xul libdir.

b/ If you look at the /usr/bin/liferea wrapper, it tries to set LD_LIBRARY_PATH to the xul *devel* libdir, which is not supposed to exist in user setups. It gets that at build time using pkg-config --libs-only-L libxul-embedding.
This is wrong.

I have a fix for that, which is to identify the xul libdir at runtime, by asking xulrunner itself.

Here is attached the debdiff for Jaunty. It would be nice to update intrepid too.

I'm getting the same Abort. I tracked it down to a sqlite3 version mismatch in xulrunner.
See http://mxr.mozilla.org/mozilla-central/source/storage/src/mozStorageService.cpp#68

The problem comes from both a/ xulrunner-1.9.1 and b/ liferea.
I guess those who don't have xulrunner-1.9.1 installed are not seeing this.

a/ Liferea is built with the xul "static glue", meaning it will use the newest xul engine registered in /etc/gre.d.
If you have both xulrunner-1.9 and xulrunner-1.9.1 installed, liferea will start with 1.9.1.

The problem is that while xulrunner-1.9 is built with *system* sqlite3 (3.5.9), xulrunner-1.9.1 is built with *in-source* sqlite3 (3.6.4).

3.6.* is needed for various reasons (mostly performance improvements) but unfortunately, 3.6.* is not in Ubuntu (yet). That's the reason I decided to go for in-source sqlite3 in  xulrunner-1.9.1. As liferea is built with system sqlite3, but goes for xulrunner 1.9.1 at run time, it gets the version mismatch.

The problem could be solved in Jaunty by uploading sqlite >= 3.6.4 and rebuilding xulrunner 1.9.1 (so it automatically jumps back to system sqlite3 - there's a test at build time for that).
For Intrepid and Hardy (for which I provide xulrunner 1.9.1 through my PPA) I guess I can re-add a workaround we had at some point in xulrunner-1.9, which was to provide a libsqlite3.so.0 symlink toward the libsqlite3.so inside the xul libdir. The same work-around will work in jaunty too, while we {wait for,work on} the sqlite 3.6 update.

That's where the liferea issue kicks in. It will only work if liferea finds its libs (in particular sqlite) in the xul libdir.

b/ If you look at the /usr/bin/liferea wrapper, it tries to set LD_LIBRARY_PATH to the xul *devel* libdir, which is not supposed to exist in user setups. It gets that at build time using pkg-config --libs-only-L libxul-embedding.
This is wrong.

I have a fix for that, which is to identify the xul libdir at runtime, by asking xulrunner itself.

Here is attached the debdiff for Jaunty. It would be nice to update intrepid too.

Changed in liferea:
importance:	Undecided → Medium
status:	New → Confirmed

Revision history for this message

Fabien Tassin (fta) wrote on 2008-11-14:

#4

liferea_1.4.18-0ubuntu2--1.4.18-0ubuntu3.debdiff Edit (2.7 KiB, text/plain)

I updated the debdiff after further tests. The tricky part is that liferea must choose the right libdir, matching the one GRE prefers, but xulrunner* --gre-version only reports its own version, i.e. -1.9 will return 1.9.0.x while -1.9.1 will return 1.9.1x. It just means we have to try the newest first.

Both liferea and xulrunner-1.9.1 are in my PPA for testing, respectively 1.4.18-0ubuntu3~fta2 and 1.9.1~b2~hg20081113r21632+nobinonly-0ubuntu1~fta3

Revision history for this message

Hammermensch (hammermensch) wrote on 2008-11-16:

#5

liferea-fail.txt Edit (5.6 KiB, text/plain)

I can confirm this. I added also the http://ppa.launchpad.net/fta/ubuntu source for Firefox 3.04 % 3.1 and have both installed.

xulrunner was updated after just adding this source from this source.

I attached my "liferea --debug-all" message.

I couldnt understand if sth here is a workaround for this?!

Revision history for this message

Hammermensch (hammermensch) wrote on 2008-11-16:

#6

i have also ubuntu 8.10

Revision history for this message

Hammermensch (hammermensch) wrote on 2008-11-17:

#7

i have removed xulrunner-1.9.1 and the depencies firefox3.1 now it starts again fine.

Revision history for this message

Steve Langasek (vorlon) wrote on 2008-11-26:

#8

Patch looks good to me, sponsoring. Thanks, Fabien!

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-11-26:

#9

This bug was fixed in the package liferea - 1.4.18-1ubuntu2

---------------
liferea (1.4.18-1ubuntu2) jaunty; urgency=low

  * debian/patches/fix_launcher_script_calling_xul,
    debian/patches/series:
    - Don't hardcode the /usr/lib/xulrunner-devel-1.9.0.x path which is
      only available when the -dev package is installed. Get the libdir
      dynamically at runtime by asking xulrunner (LP: #295490)

-- Fabien Tassin <email address hidden> Wed, 26 Nov 2008 08:38:23 +0100

Changed in liferea:
status:	Confirmed → Fix Released

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2008-12-17:

#10

JFTR, the patch has been changed in bug 309108. It still fixes this bug, so no need to worry about it.

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2009-01-07:

#11

We should fix this in Intrepid too (see bug 309640).

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2009-01-15:

#12

intrepid.debdiff Edit (1.5 KiB, text/plain)

Proposed Intrepid debdiff. Thanks to Fabien Tassin for the patch.

Revision history for this message

Alexander Sack (asac) wrote on 2009-01-15:

#13

SRU candidate for intrepid; reason: can break lifearea when having preview xulrunner packages installed (1.9.2, 1.9.1).

Changed in liferea:
importance:	Undecided → Medium
status:	New → Triaged

Revision history for this message

Alexander Sack (asac) wrote on 2009-01-15:

#14

sponsored pochu's debdiff to intrepid-proposed

Changed in liferea:
status:	Triaged → In Progress

Revision history for this message

Martin Pitt (pitti) wrote on 2009-01-20:

#15

Accepted into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in liferea:
status:	In Progress → Fix Committed

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2009-01-20:

#16

Alex, Foppe: since you're running Intrepid with this setup, could you please test liferea from intrepid-proposed to see if this is fixed? If you don't know how to use intrepid-proposal, https://wiki.ubuntu.com/Testing/EnableProposed have instructions.

Thanks!

Revision history for this message

Alex Kavanagh (ajkavanagh) wrote on 2009-01-20: Re: [Bug 295490] Re: Liferea doesn't start with "Aborted" error.

#17

Will do, but it hasn't shown up in proposed yet (or there is something
wrong with my setup). As soon as it does I will test it.

Thanks for the fix!

Emilio Pozuelo Monfort wrote, On 20/01/09 10:06:
> Alex, Foppe: since you're running Intrepid with this setup, could you
> please test liferea from intrepid-proposed to see if this is fixed? If
> you don't know how to use intrepid-proposal,
> https://wiki.ubuntu.com/Testing/EnableProposed have instructions.
>
> Thanks!
>
>

--
Alex Kavanagh
Home: http://alex.kavanagh.name
Work: http://www.tinwood.com

Revision history for this message

Foppe Hemminga (foppe) wrote on 2009-01-20:

#18

Hi Emilio,

I found Liferea in proposed and upgraded. Current version 1.5.8. No
problems, however I didn't have issues with 1.5.7 either.
If there's anything specific you'd like me to test like running in debug
mode, please let me know.

Greetings,

Foppe

Op dinsdag 20-01-2009 om 10:06 uur [tijdzone +0000], schreef Emilio
Pozuelo Monfort:
> Alex, Foppe: since you're running Intrepid with this setup, could you
> please test liferea from intrepid-proposed to see if this is fixed? If
> you don't know how to use intrepid-proposal,
> https://wiki.ubuntu.com/Testing/EnableProposed have instructions.
>
> Thanks!
>

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2009-01-20:

#19

Foppe Hemminga wrote:
> Hi Emilio,
>
> I found Liferea in proposed and upgraded. Current version 1.5.8. No
> problems, however I didn't have issues with 1.5.7 either.

Well, the version from intrepid is 1.4.18-0ubuntu2 and the one from
intrepid-proposed is 1.4.18-0ubuntu2 :)

The one from intrepid (1.4.18-0ubuntu2) shouldn't work if you have installed
firefox 3.1 / 3.2, but the one from intrepid-proposed should. Could you check
that? You can directly run /usr/bin/liferea in case you have other Liferea
versions installed alongside.

Thanks,
Emilio

Revision history for this message

Alex Kavanagh (ajkavanagh) wrote on 2009-01-20:

#20

Hi

I still seem to have a problem:

$ liferea
Segmentation fault
$ apt-show-versions liferea
liferea/intrepid-proposed uptodate 1.4.18-0ubuntu2.1

Unfortunately, it is still segfaulting on me.

Anything I can do to help test it? Have I got the wrong version
installed still?
Cheers
Alex.

Foppe Hemminga wrote, On 20/01/09 11:54:
> Hi Emilio,
>
> I found Liferea in proposed and upgraded. Current version 1.5.8. No
> problems, however I didn't have issues with 1.5.7 either.
> If there's anything specific you'd like me to test like running in debug
> mode, please let me know.
>
> Greetings,
>
> Foppe
>
> Op dinsdag 20-01-2009 om 10:06 uur [tijdzone +0000], schreef Emilio
> Pozuelo Monfort:
>
>> Alex, Foppe: since you're running Intrepid with this setup, could you
>> please test liferea from intrepid-proposed to see if this is fixed? If
>> you don't know how to use intrepid-proposal,
>> https://wiki.ubuntu.com/Testing/EnableProposed have instructions.
>>
>> Thanks!
>>
>>
>
>

--
Alex Kavanagh
Home: http://alex.kavanagh.name
Work: http://www.tinwood.com

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2009-01-20:

#21

Weird. At least it doesn't happen here, without xulrunner 1.9.1.

Does it also happen if you launch /usr/bin/liferea-bin directly?

Revision history for this message

Foppe Hemminga (foppe) wrote on 2009-01-20:

#22

No problems here. Liferea 1.4.18 (upgraded), Firefox Shiretoko 3.1b3,
xulrunner 1.9 & xulrunner 1.9.1

--F

Op dinsdag 20-01-2009 om 14:59 uur [tijdzone +0000], schreef Emilio
Pozuelo Monfort:
> Weird. At least it doesn't happen here, without xulrunner 1.9.1.
>
> Does it also happen if you launch /usr/bin/liferea-bin directly?
>

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2009-01-20:

#23

Alex Kavanagh wrote:
> $ liferea
> Segmentation fault

Did you try running /usr/bin/liferea directly? Perhaps you installed another
liferea version in /usr/local/bin.

Revision history for this message

Alex Kavanagh (ajkavanagh) wrote on 2009-01-21:

#24

Emilio Pozuelo Monfort wrote, On 20/01/09 16:41:
> Alex Kavanagh wrote:
>
>> $ liferea
>> Segmentation fault
>>
>
> Did you try running /usr/bin/liferea directly? Perhaps you installed another
> liferea version in /usr/local/bin.
>
Yes, did run running liferea directly, and no there is no other version
installed on PATH:

$ which liferea
/usr/bin/liferea
$ /usr/bin/liferea
Segmentation fault

I think my error (bug 309640 -
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/309640) may be
slightly different?

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2009-01-21:

#25

I'll investigate this later. The update may be flawed (see bug 319508 too), so please don't copy this to -updates!

Revision history for this message

Roshan George (roshan-george) wrote on 2009-01-21:

#26

liferea backtrace Edit (17.8 KiB, text/plain)

Relating to the update and the bug 319508, I have attached a backtrace from gdb. Hope it helps.

As of now, is downgrading the package a good option? Which version should I downgrade to?

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2009-01-21:

#27

From the backtrace:

> 0x00007f48cf03c12c in _nss_wins_gethostbyname_r () from /lib/libnss_wins.so.2

That looks unrelated to this, and related to bug 214192.

Roshan, downgrade to 1.4.18-0ubuntu2 (from intrepid) and see if it still crashes.

Thanks for the feedback!

Revision history for this message

Vadim Peretokin (vperetokin) wrote on 2009-01-28:

#28

1.4.18-0ubuntu2 is starting fine here.

Revision history for this message

Martin Pitt (pitti) wrote on 2009-04-16:

#29

This has sat in -proposed for 3 months and is marked as regression-proposed and verification-failed. I removed the SRU from -proposed.

Changed in liferea (Ubuntu Intrepid):
status:	Fix Committed → Confirmed
tags:	removed: regression-proposed verification-failed

Revision history for this message

Darwin Survivor (darwinsurvivor) wrote on 2009-07-06:

#30

I am still getting "Aborted" in liferea 1.4.18-0ubuntu2
I am full updated with "proposed" enabled.

I take it this was only fixed for jaunty?

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2009-07-07:

#31

Darwin Survivor wrote:
> I am still getting "Aborted" in liferea 1.4.18-0ubuntu2
> I am full updated with "proposed" enabled.
>
> I take it this was only fixed for jaunty?

Karmic, actually. Will be fixed in the next few days.

Revision history for this message

Darwin Survivor (darwinsurvivor) wrote on 2009-07-23:

#32

Will this ever be fixed for Intrepid? Even on backports? Because it *used* to work fine on Intrepid...

If not, is it possible to roll-back certain packages to get it working again. I use liferea on a daily basis and it's the only news reader I've been able to stand using.

Revision history for this message

Corneil du Plessis (corneil-wbs) wrote on 2009-11-04:

#33

After updating firefox the default became 3.5 on my intrepid installation and it seems the xulrunner-1.9.1 is cause same problems.

Revision history for this message

Corneil du Plessis (corneil-tsctech) wrote on 2009-11-06:

#34

I upgrade to 1.6.x using:

sudo sh -c "echo 'deb http://ppa.launchpad.net/liferea/ppa/ubuntu intrepid main' >> /etc/apt/sources.list" && sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 412F055D
sudo sh -c "echo 'deb http://ppa.launchpad.net/webkit-team/ppa/ubuntu intrepid main' >> /etc/apt/sources.list" && sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 2D9A3C5B
sudo apt-get update
Then I used the Update Manager to complete the upgrade because sudo apt-get upgrade 'kept liferea back'

Martin Pitt (pitti) on 2010-02-04

Changed in liferea (Ubuntu Intrepid):
status:	Confirmed → Won't Fix

Revision history for this message

Wojtek Krawczak (coyot-na) wrote on 2010-04-29:

#35

As Corneil mentioned, in case someone is having problems with this lately, in my case it was the upgrade to the nightly build of Firefox 3.6
To solve this I rolled back to the older version (removed the nightly repository, removed Firefox and installed it again), then I had to find xulrunner, version 1.9.0 in the software manager, click on it and use the option "Force version". For me it was the version 1.9.0.19 that worked (I'm on Ubuntu 9.04).

Affects		Status	Importance	Assigned to	Milestone
	liferea (Ubuntu)	Fix Released	Medium	Unassigned
	Intrepid	Won't Fix	Medium	Unassigned

Ubuntu
liferea package

Liferea doesn't start with "Aborted" error.

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntuliferea package

Liferea doesn't start with "Aborted" error.

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntu
liferea package