Your message dated Thu, 11 Feb 2010 15:09:13 +0100
with message-id <[email protected]>
and subject line Re: Bug#569331: reportbug: GtkWarning: could not open display
has caused the Debian Bug report #569331,
regarding reportbug: GtkWarning: could not open display
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.)


-- 
569331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569331
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 4.10.2
Severity: minor

Despite the presence of the 'ui text' option in .reportbugrc, running
reportbug while not in X results in the following warning:

$ reportbug
/usr/lib/pymodules/python2.5/gtk-2.0/gtk/__init__.py:57: GtkWarning:
could not open display
  warnings.warn(str(e), _gtk.Warning)
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>

Please do not display the warning with this configuration.


-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/stoner/.reportbugrc:
reportbug_version "4.10.2"
mode advanced
ui text
offline

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.33-rc7 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages reportbug depends on:
ii  apt                           0.7.25.3   Advanced front-end for dpkg
ii  python                        2.5.4-9    An interactive high-level object-o
ii  python-reportbug              4.10.2     Python modules for interacting wit

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  debconf-utils              1.5.28        debconf utilities
pn  debsums                    <none>        (no description available)
pn  dlocate                    <none>        (no description available)
pn  emacs22-bin-common | emacs <none>        (no description available)
ii  file                       5.03-5+b1     Determines file type using "magic"
ii  gnupg                      1.4.10-2      GNU privacy guard - a free PGP rep
ii  postfix [mail-transport-ag 2.6.5-3       High-performance mail transport ag
ii  python-gtk2                2.16.0-2      Python bindings for the GTK+ widge
ii  python-gtkspell            2.25.3-4.1+b3 Python bindings for the GtkSpell l
pn  python-urwid               <none>        (no description available)
ii  python-vte                 1:0.23.5-3    Python bindings for the VTE widget
pn  xdg-utils                  <none>        (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Hello Piotr,
thanks for your report.

On Thu, Feb 11, 2010 at 14:56, Piotr Engelking <[email protected]> wrote:
> Package: reportbug
> Version: 4.10.2
> Severity: minor
>
> Despite the presence of the 'ui text' option in .reportbugrc, running
> reportbug while not in X results in the following warning:
>
> $ reportbug
> /usr/lib/pymodules/python2.5/gtk-2.0/gtk/__init__.py:57: GtkWarning:
> could not open display
>  warnings.warn(str(e), _gtk.Warning)

this is a bug in python-gtk2 as you can see just running "import gtk2"
from a python interpreter shell (we already reported that).

The reason we import the module is because we need to know what UIs
are available.

> Please enter the name of the package in which you have found a problem,
> or type 'other' to report a more general problem.
>>
>
> Please do not display the warning with this configuration.

It's something that needs to be fixed in python-gtk2: simply importing
the modules shouldn't warn that message, but only the moment you're
accessing a method that needs DISPLAY set.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint

Reply via email to