Hello Bruno,
On Sat, Feb 2, 2013 at 12:42 AM, Bruno Filipe Oliveira Ramos
brunoramos...@gmail.com wrote:
I have been looking at this problem and I think I might have some clues on
what
is causing the error.
From what I could find in my searches (gdb mainly) the problem is related to
the
Package: reportbug
Version: 6.4.3
Followup-For: Bug #620225
Dear Maintainer,
I have been looking at this problem and I think I might have some clues on what
is causing the error.
From what I could find in my searches (gdb mainly) the problem is related to
the fact the reportbug is updating the
Package: reportbug
Version: 6.4.3
Followup-For: Bug #620225
This bug is still present with the error below. You can reproduce it by
entering the package name and then hit enter instead of clicking on Next.
/usr/lib/pymodules/python2.7/reportbug/ui/gtk2_ui.py:453: PangoWarning:
Package: reportbug
Version: 6.3.1
Followup-For: Bug #620225
PLEASE FIX IT.
It is more than important. I often write bug report, and it is EXTREMALLY
annoying,
when you press Next/COntinue, and all your few page long bug report just
disappears!
It is more than a year now since first reports.
On Thu, Mar 29, 2012 at 15:44, Witold Baryluk bary...@smp.if.uj.edu.pl wrote:
PLEASE FIX IT.
Do you really expect it to expedite the bug resolution? You may
volunteer to debug the issue and point out where the problem is;
shouting won't get bug fixed.
It is more than important. I often write
On 03-29 23:48, Sandro Tosi wrote:
On Thu, Mar 29, 2012 at 15:44, Witold Baryluk bary...@smp.if.uj.edu.pl
wrote:
PLEASE FIX IT.
Do you really expect it to expedite the bug resolution? You may
volunteer to debug the issue and point out where the problem is;
shouting won't get bug fixed.
On Fri, Mar 30, 2012 at 00:22, Witold Baryluk bary...@smp.if.uj.edu.pl wrote:
I am just saying it is more than important, because novice users, will
stick to default settings. I also often says, It is for sure fixed
now, and then discover it isn't!
novice users (and we can also argue that
Package: reportbug
Followup-For: Bug #620225
Version: 6.3
Some people says here that it only happens to minority of users.
I disagree with such reasoning.
If any user tries to report some bug using reportbug to other package,
and it crashes (actually without any message, because message
is
Package: reportbug
Followup-For: Bug #620225
Version: 6.3
I was submitting a bug for the package gtg but this happened:
~$ reportbug
Gtk-Message: Failed to load module pk-gtk-module
/usr/lib/pymodules/python2.7/reportbug/ui/gtk2_ui.py:453: GtkWarning: Theme
file for default has no name
2011/10/14 Sandro Tosi mo...@debian.org:
On Fri, Oct 14, 2011 at 22:32, Camaleón noela...@gmail.com wrote:
[27738.795946] reportbug[5947]: segfault at b51fc000 ip b63d29ca sp bf968f98
error 4 in libgdk-x11-2.0.so.0.2400.4[b63a5000+98000]
As you can probably guess, a segfault in libgdk is none
GTK+ UI doesn't crash for anyone, but only for a minor part of its
users. So stop whining or do something to get this fixed. End of the
story.
On Sat, Oct 15, 2011 at 10:33, Camaleón noela...@gmail.com wrote:
2011/10/14 Sandro Tosi mo...@debian.org:
On Fri, Oct 14, 2011 at 22:32, Camaleón
El 2011-10-15 a las 10:42 +0200, Sandro Tosi escribió:
GTK+ UI doesn't crash for anyone, but only for a minor part of its
users. So stop whining or do something to get this fixed. End of the
story.
What can I do? It seems I'm part for that minority of users.
I'm not a GTK+ programmer but I
Package: reportbug
Version: 6.2.1
Followup-For: Bug #620225
GTK+2 version of reportbug is very unstable, it crashes 4 in 5 times.
The last crash happened 5 minutes ago (the interface simply closed by itself
with no additional messages).
The last trace I have is a segfault (it happened this same
On Fri, Oct 14, 2011 at 22:32, Camaleón noela...@gmail.com wrote:
[27738.795946] reportbug[5947]: segfault at b51fc000 ip b63d29ca sp bf968f98
error 4 in libgdk-x11-2.0.so.0.2400.4[b63a5000+98000]
As you can probably guess, a segfault in libgdk is none of reportbug
fault. GTK+ stack maintainers
14 matches
Mail list logo
