Liferea crasches at start

Bug #531464 reported by Hund
This bug report is a duplicate of:  Bug #369274: SIGSEGV in _nss_wins_gethostbyname_r. Edit Remove
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
liferea (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: liferea

When I start Liferea it just crashes with this output:

"set zoom: 1.21

Liferea did receive signal 11 (Segmentation fault)."

I did try to do a backtrace but then Liferea just hangs and I cant close it with "Ctrl + C"?

I'm using a Lucid with Liferea 1.6.2-1ubuntu4.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote : Re: [Bug 531464] [NEW] Liferea crasches at start

On 03/03/10 18:03, Hund wrote:
> I did try to do a backtrace but then Liferea just hangs and I cant close
> it with "Ctrl + C"?

Without a backtrace or specific instructions on how to reproduce the crash this
report is useless.

Can you give us instructions on how to reproduce this, and run liferea with
--debug-all and past the backtrace that should be printed in the terminal when
liferea crashes?

Revision history for this message
Hund (hund) wrote :
Download full text (22.0 KiB)

I'll just have to start Liferea and it will crash a few seconds later.

"liferea --debug-all" gave me this:

CONF: proxy auto detect is configured
CONF: no proxy GNOME of $http_proxy configuration found...
CONF: Proxy settings are now NULL:0 NULL:NULL
NET: proxy set to http://(null):(null)@(null):0
UPDATE: network manager: registering network state change callback
DB: Opening DB file /home/johan/.liferea_1.6/liferea.db...
DB: current DB schema version: 7
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: 1 (table items already exists)
DB: executing SQL: CREATE INDEX items_idx ON items (source_id);
DB: -> result: 1 (index items_idx already exists)
DB: executing SQL: CREATE INDEX items_idx2 ON items (comment_feed_id);
DB: -> result: 1 (index items_idx2 already exists)
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: 1 (table itemsets already exists)
DB: executing SQL: CREATE INDEX itemset_idx ON itemsets (node_id);
DB: -> result: 1 (index itemset_idx already exists)
DB: executing SQL: CREATE INDEX itemset_idx2 ON itemsets (item_id);
DB: -> result: 1 (index itemset_idx2 already exists)
DB: executing SQL: CREATE TABLE metadata ( item_id INTEGER, nr INTEGER, key TEXT, value TEXT, PRIMARY KEY (item_id, nr));
DB: -> result: 1 (table metadata already exists)
DB: executing SQL: CREATE INDEX metadata_idx ON metadata (item_id);
DB: -> result: 1 (index metadata_idx already exists)
DB: executing SQL: CREATE TABLE attention_stats ( category_id TEXT, category_name TEXT, count INTEGER, PRIMARY KEY (category_id));
DB: -> result: 1 (table attention_stats already exists)
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: 1 (table subscription already exists)
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: 1 (table update_state already exists)
DB: executing SQL: CREATE TABLE subscription_metadata ( node_id STRING, nr INTEGER, key TEXT, value TEXT, PRIMARY KEY (node_id, nr));
DB: -> result: 1 (table subscription_metadata already exists)
DB: executing SQL: CREATE INDEX subscription_metadata_idx ON subscription_metadata (node_id);
DB: -> result: 1 (index subscription_metadata_idx alrea...

Revision history for this message
Hund (hund) wrote :

Anyone? :( I'm handicapped without a proper feed reader.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote : Re: [Bug 531464] Re: Liferea crasches at start

On 16/03/10 06:50, Hund wrote:
> Anyone? :( I'm handicapped without a proper feed reader.

Unfortunately that didn't get a backtrace, so you will have to get one with gdb.
See https://wiki.ubuntu.com/Backtrace for instructions.

Revision history for this message
Hund (hund) wrote :

I can run a full backtrace as I said before. This is the only output I can get:

GNU gdb (GDB) 7.0.90.20100309-ubuntu
Copyright (C) 2010 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-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/liferea...(no debugging symbols found)...done.
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run 
Starting program: /usr/bin/liferea
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffe7a4a710 (LWP 31723)]
[New Thread 0x7fffe6bfa710 (LWP 31724)]
[Thread 0x7fffe6bfa710 (LWP 31724) exited]
[New Thread 0x7fffe6bfa710 (LWP 31726)]
[New Thread 0x7fffe3611710 (LWP 31727)]
set zoom: 1.21
[New Thread 0x7fffe2e10710 (LWP 31728)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe2e10710 (LWP 31728)]
0x00007fffe1fd1e4c in _nss_wins_gethostbyname_r () from /lib/libnss_wins.so.2
(gdb)

Revision history for this message
John Franklin (hondaman-nc) wrote :
Revision history for this message
Felix H. Dahlke (fhd) wrote :

I'm experiencing the same problem on two different boxes.

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.