Your message dated Sun, 11 Sep 2016 20:57:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#837459: liferea: When the main window resized (bigger) 
Liferea doesn't save pane configuration
has caused the Debian Bug report #837459,
regarding liferea: When the main window resized (bigger) Liferea doesn't save 
pane configuration
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.)


-- 
837459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837459
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: liferea
Version: 1.10.12-1
Severity: important

Hello,

When the main window resized (bigger) Liferea doesn't save pane configuration
on startup.

Let's my new height of the itemlist pane be 150. In dconf-editor it is org->
gnome->liferea-> last-hpane-pos (150).

Log out -> log in. Lifera always starts in tray not dependent on settings and
the height of the itemlist is one line.

Looks like it is this case: https://github.com/lwindolf/liferea/issues/158

Best wishes,
John




-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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.8.20-0+deb8u1
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gir1.2-gtk-3.0                               3.14.5-1+deb8u1
ii  gir1.2-peas-1.0                              1.12.1-2
ii  libatk1.0-0                                  2.14.0-1
ii  libc6                                        2.19-18+deb8u4
ii  libcairo2                                    1.14.0-2.1+deb8u1
ii  libgdk-pixbuf2.0-0                           2.31.1-2+deb8u5
ii  libgirepository-1.0-1                        1.42.0-2.2
ii  libglib2.0-0                                 2.42.1-1+b1
ii  libgtk-3-0                                   3.14.5-1+deb8u1
ii  libindicate5                                 0.6.92-2
ii  libjson-glib-1.0-0                           1.0.2-1
ii  libnotify4                                   0.7.6-2
ii  libpango-1.0-0                               1.36.8-3
ii  libpeas-1.0-0                                1.12.1-2
ii  libsoup2.4-1                                 2.48.0-1
ii  libsqlite3-0                                 3.8.7.1-1+deb8u1
ii  libwebkitgtk-3.0-0                           2.4.9-1~deb8u1
ii  libxml2                                      2.9.1+dfsg1-5+deb8u2
ii  libxslt1.1                                   1.1.28-2+deb8u1
ii  liferea-data                                 1.10.12-1
ii  python-gi                                    3.14.0-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-1
ii  gnome-keyring            3.14.0-1+b1
ii  steadyflow               0.2.0-1.1

Versions of packages liferea suggests:
ii  network-manager  0.9.10.0-7

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.10.16-1

Hi John,

On 11-09-16 20:34, John Kirk wrote:
> Looks like it is this case: https://github.com/lwindolf/liferea/issues/158

As you could have seen, that bug is already closed for a year. In
Debian, we already have the version that this bug closed, so I close
this Debian bug.

But if you are interested, I could provide a backport of liferea via
jessie-backports.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to