Your message dated Tue, 18 Mar 2014 15:56:50 +0100
with message-id <53285eb2.80...@ralfj.de>
and subject line Re: [Pkg-kde-extras] Bug#740078: Bug#740078: 
[gtk3-engines-oxygen] can't go up directories in file open dialog
has caused the Debian Bug report #740078,
regarding [gtk3-engines-oxygen] can't go up directories in file open dialog
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 ow...@bugs.debian.org
immediately.)


-- 
740078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtk3-engines-oxygen
Version: 1.2.0-1
Severity: normal

--- Please enter the report below this line. ---
On the top of the dialog there is a series of buttons, one for each parent directory. Clicking on those does nothing at first glance, but you can in fact move the dialog by grabbing any of them. This is not what those buttons should do.

--- System information. ---
Architecture: amd64
Kernel: Linux 3.12.4-fxa

Debian Release: jessie/sid
500 unstable ftp.uni-kl.de
500 unstable ftp.de.debian.org
1 experimental ftp.de.debian.org

--- Package information. ---
Depends (Version) | Installed
====================================-+-=============
libc6 (>= 2.14) |
libcairo-gobject2 (>= 1.10.0) |
libcairo2 (>= 1.10.0) |
libgcc1 (>= 1:4.1.1) |
libgdk-pixbuf2.0-0 (>= 2.22.0) |
libglib2.0-0 (>= 2.18.0) |
libgtk-3-0 (>= 3.0.0) |
libpango-1.0-0 (>= 1.18.0) |
libpangocairo-1.0-0 (>= 1.14.0) |
libstdc++6 (>= 4.6) |
libx11-6 |


Package's Recommends field is empty.

Package's Suggests field is empty.

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

> Anyways, this report can be closed, because the new
> version 1.3.4 seems to fix this issue.
I just tested this here, and I do not see this issue either, so I am
closing this bugreport.

Kind regards
Ralf

--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

Reply via email to