On 15 Jan 2017, at 00:47, James Clarke wrote:
> On 15 Jan 2017, at 00:37, Simon McVittie wrote:
>> On Sun, 15 Jan 2017 at 00:32:15 +, Simon McVittie wrote:
>>> I suspect that last line was intended to be a GetMultilinePage wrapper.
>>> But I can't actually test this, because the only use of g
On 15 Jan 2017, at 00:37, Simon McVittie wrote:
> On Sun, 15 Jan 2017 at 00:32:15 +, Simon McVittie wrote:
>> I suspect that last line was intended to be a GetMultilinePage wrapper.
>> But I can't actually test this, because the only use of get_multiline()
>> does have ENTER in its prompt (and
On Sun, 15 Jan 2017 at 00:32:15 +, Simon McVittie wrote:
> I suspect that last line was intended to be a GetMultilinePage wrapper.
> But I can't actually test this, because the only use of get_multiline()
> does have ENTER in its prompt (and it crashes - fix attached).
On testing it by hacking
On Sat, 14 Jan 2017 at 23:36:55 +, James Clarke wrote:
> It seems GetMultilinePage's get_value also has a call to get_text without
> the extra parameter, but a grep for GetMultilinePage only shows the class
> definition, with no uses... deletion candidate? From what I can tell, it
> was added i
On 14 Jan 2017, at 23:55, Simon McVittie wrote:
> On Sat, 14 Jan 2017 at 23:24:25 +, James Clarke wrote:
>> I'm not sure why it's working for me and not you.
>
> Ah, that would be because I have reportbug configured to use mutt to write
> the actual bug report, and that disables the Gtk edito
On Sat, 14 Jan 2017 at 23:24:25 +, James Clarke wrote:
> I'm not sure why it's working for me and not you.
Ah, that would be because I have reportbug configured to use mutt to write
the actual bug report, and that disables the Gtk editor.
Your change looks fine. I also needed to use the attac
On 14 Jan 2017, at 23:24, James Clarke wrote:
> On Sat, Jan 14, 2017 at 09:38:53PM +, Simon McVittie wrote:
>> On Sat, 14 Jan 2017 at 19:50:17 +, Simon McVittie wrote:
On Mon, Jan 9, 2017 at 2:21 PM, James Clarke wrote:
> I would guess there are some UI
> interactions happeni
On Sat, Jan 14, 2017 at 09:38:53PM +, Simon McVittie wrote:
> On Sat, 14 Jan 2017 at 19:50:17 +, Simon McVittie wrote:
> > > On Mon, Jan 9, 2017 at 2:21 PM, James Clarke wrote:
> > > > I would guess there are some UI
> > > > interactions happening not on the main UI thread.
> >
> > I foun
On Sat, 14 Jan 2017 at 19:50:17 +, Simon McVittie wrote:
> > On Mon, Jan 9, 2017 at 2:21 PM, James Clarke wrote:
> > > I would guess there are some UI
> > > interactions happening not on the main UI thread.
>
> I found a couple of places where this was done wrong. I'll send a
> patch series s
On Fri, 13 Jan 2017 at 15:18:26 -0500, Sandro Tosi wrote:
> would you be able to have a look at this? it looks like it's the
> current issue every user of the GTK interface has.
The patch from James looks correct, please apply it.
> On Mon, Jan 9, 2017 at 2:21 PM, James Clarke wrote:
> > This is
Control: tags -1 + patch
Hello all,
I have prepared a proof-of-concept patch for #836253. See 0003.patch in the
attachment. 0002-patch is some other improvement around desktop file.
Basically I moved /usr/share/reportbug/debian-swirl.svg to /usr/share/icons/
hicolor/scalable/places/debian-swirl
Processing control commands:
> tags -1 + patch
Bug #836253 [reportbug] reportbug: Do not hardcode icon in desktop file
Added tag(s) patch.
--
836253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
__
Source: reportbug
Severity: minor
Version: 7.1.2
Tags: patch
Hi,
Please the obsolete "debian/menu" file from the repository.
As decided by the Technical Committee [1], the Debian Menu System is obsolete
now. XDG desktop files should be used instead.
Reportbug has a working desktop file, so the
Package: reportbug
Version: 7.1.2
Severity: important
Crashes with different messages, one is:
michi@michis-toshiba:~/bin$ reportbug
(reportbug:27617): Gtk-CRITICAL **: gtk_text_attributes_ref: assertion 'values
!= NULL' failed
Traceback (most recent call last):
File "/usr/bin/reportbug", l
Package: reportbug
Version: 7.1.2
Severity: minor
Tags: patch
Dear Maintainer,
Another finding from playing with non-ascii characters in the
configuration: It would be nice to show the from address in a more
readable format than rfc 2047 encoding.
Proposed patch attached.
Before:
> Using '=?utf
Package: reportbug
Version: 7.1.2
Severity: minor
Tags: patch
Dear Maintainer,
Even in reportbug 7.1.2, the manpage still says:
> REPORTBUGEMAIL, EMAIL, DEBEMAIL
> Email address to use as your from address (in this order). If
> no environment variable exists, the default is taken from
16 matches
Mail list logo
