Package: dwb
Version: 20130503hg-1
Severity: normal
Tags: upstream

Dear Maintainer,

- NOTE
On this machine i'm using a self built dwb (linked against GTK2), so you see a 
strange version number, but it was built from the stock debian testing repo 
sources (v. 20130503hg-2) some time ago.
Anyways this bug affects the present default 20140307hg-2 as well (as tested on 
a different machine).


- DESCRIPTION
Opening an url with dwb from command line, when dwb is already started and 
running, this dbus error is returned:

GDBus.Error:org.freedesktop.DBus.Error.NotSupported: Application does not 
handle command line arguments


- TO REPRODUCE
Start dwb as you usually do, then try to open an url from the terminal (e.g. "$ 
dwb debian.org")


- UPSTREAM
I had a quick talk in the dwb irc support channel, and they explained to me 
that this error is due to the upgrade of glib2 from version 2.38 to 2.40.
They said the issue is now fixed in the project git repo.


- QUESTION
I see a 20140307hg-3 version entered the unstable, but in the changelog i see 
no trace of this bug fix (maybe it is not specified since there was no bug 
report about).
I'd like to know if you could tell us the estimated time for this fix to be 
applied in the debian repositories.
Maybe it's possible to integrate the fix before the migration of the 
20140307hg-3 from unstable to testing.


Thanks a lot.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.13-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dwb depends on:
ii  libc6               2.18-4
ii  libgdk-pixbuf2.0-0  2.30.6-1
ii  libglib2.0-0        2.40.0-2
ii  libgnutls26         2.12.23-13
ii  libpango1.0-0       1.36.3-1
ii  libsoup2.4-1        2.46.0-2
ii  libwebkitgtk-1.0-0  2.2.6-1

dwb recommends no packages.

dwb suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to