Your message dated Mon, 3 Oct 2016 20:30:15 +0200
with message-id <[email protected]>
and subject line Re: Bug#827894: Segfault on start
has caused the Debian Bug report #827894,
regarding Segfault on start
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
827894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827894
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: liferea
Version: 1.10.19-2
Severity: normal

Hello,

liferea does not start: it shows the main window, and then segfaults:

  $ liferea
  
  (liferea:11306): libnotify-WARNING **: Failed to connect to proxy
  
  (liferea:11306): Gtk-WARNING **: Theme parsing error: gtk.css:10:17: The 
'gtk-key-bindings' property has been renamed to '-gtk-key-bindings'
  openjdk version "1.8.0_91"
  OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-2-b14)
  OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
  Segmentation fault
  
  (I wonder why a JDK output shows up)

This is the same under gdb:

  (gdb) run
  Starting program: /usr/bin/liferea 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffe1e6a700 (LWP 11510)]
  [New Thread 0x7fffe1669700 (LWP 11511)]
  [New Thread 0x7fffe0e68700 (LWP 11512)]
  
  (liferea:11505): libnotify-WARNING **: Failed to connect to proxy
  [New Thread 0x7fffd3fff700 (LWP 11513)]
  
  (liferea:11505): Gtk-WARNING **: Theme parsing error: gtk.css:10:17: The 
'gtk-key-bindings' property has been renamed to '-gtk-key-bindings'
  [New Thread 0x7fffcb9d5700 (LWP 11514)]
  [New Thread 0x7fff8b0d0700 (LWP 11515)]
  [New Thread 0x7fff890bc700 (LWP 11518)]
  [New Thread 0x7fff888bb700 (LWP 11519)]
  [New Thread 0x7fff83fff700 (LWP 11520)]
  [New Thread 0x7fff837fe700 (LWP 11522)]
  [New Thread 0x7fff82ffd700 (LWP 11530)]
  [New Thread 0x7fff827fc700 (LWP 11531)]
  [New Thread 0x7fff81ffb700 (LWP 11532)]
  [New Thread 0x7fff817fa700 (LWP 11533)]
  openjdk version "1.8.0_91"
  OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-2-b14)
  OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
  
  Program received signal SIGSEGV, Segmentation fault.
  0x00007ffff3a722a7 in gdk_pixbuf_get_from_surface () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0


I also tried purging all java packages from my system, and it still
segfaults.

If I remove ~/.local/share/liferea/liferea.db it doesn't segfault
anymore, but then I lose all my feeds.

The databse itself is not corrupted:

  $ sqlite3 liferea.db.backup .dump > /dev/null
  $ echo $?
  0

I can provide the database file privately. It's 58Mb and confidential,
though.


Enrico


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages liferea depends on:
ii  dbus-x11                                     1.10.8-1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  gir1.2-gtk-3.0                               3.20.6-1
ii  gir1.2-peas-1.0                              1.18.0-2
ii  libatk1.0-0                                  2.20.0-1
ii  libc6                                        2.22-11
ii  libcairo2                                    1.14.6-1+b1
ii  libgdk-pixbuf2.0-0                           2.34.0-1
ii  libgirepository-1.0-1                        1.48.0-2
ii  libglib2.0-0                                 2.48.1-1
ii  libgtk-3-0                                   3.20.6-1
ii  libindicate5                                 0.6.92-3
ii  libjson-glib-1.0-0                           1.2.0-1
ii  libnotify4                                   0.7.6-2
ii  libpango-1.0-0                               1.40.1-1
ii  libpeas-1.0-0                                1.18.0-2
ii  libpeas-1.0-python2loader                    1.18.0-2
ii  libsoup2.4-1                                 2.54.1-1
ii  libsqlite3-0                                 3.13.0-1
ii  libwebkitgtk-3.0-0                           2.4.11-1+b1
ii  libxml2                                      2.9.3+dfsg1-1.2
ii  libxslt1.1                                   1.1.28-4
ii  liferea-data                                 1.10.19-2
ii  python-gi                                    3.20.1-1
pn  python:any                                   <none>

Versions of packages liferea recommends:
ii  gir1.2-gnomekeyring-1.0  3.12.0-1+b1
ii  gnome-icon-theme         3.12.0-2
ii  gnome-keyring            3.20.0-1

Versions of packages liferea suggests:
pn  kget             <none>
ii  network-manager  1.2.2-2

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Enrico,

On 02-10-16 17:15, Enrico Zini wrote:
> On Sun, Oct 02, 2016 at 01:14:47PM +0200, Paul Gevers wrote:
>> On 12-08-16 22:55, Paul Gevers wrote:
>>> Upstream is requesting a backtrace with debugging symbols (for now,
>>> rather than having the database) because it can be shared publicly. Are
>>> you in the position to create that? (If you are fine with it, please
>>> follow-up directly in the upstream bug report).
>> Ping?
> 
> Probably not. The liferea config directory I backed up back then was
> ~/.liferea-1.8 while now in testing I have liferea 1.10 with
> configuration in .config/liferea and .cache/liferea.
> 
> I've restored what I thought were the right pieces from my backup in
> those directories, and I couldn't reproduce the crash.
> 
> Feel free to close this bug then, I'm not anymore in a position to
> reproduce it.

I asked upstream and without the backtrace and considering the 1.8
liferea (I am packaging 1.12 right now) they aren't really able to take
this on.

I am sorry we couldn't figure this segfault out, but closing the bug as
it doesn't help to keep it open.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to