Based on the backtrace and the fact that GCC 14 refuse to build the code,
I suspect the problem is in this code from debian.patch:
/* Also draw country code if we don't have flag */
gchar **xkb_rules;
if (current_flag == flag_xpm_unknown &&
(xkb_rules = parse_xk
At Thu, 7 Jun 2012 13:43:31 +0200,
Toni Mueller wrote:
>
>
> Hi,
>
> On Thu, Jun 07, 2012 at 01:06:01PM +0200, Adam Sloboda wrote:
> > At Thu, 7 Jun 2012 11:56:38 +0200, Toni Mueller wrote:
> > > what do you want me to do?
> > I need to debug it and fix the code but I need test case first.
>
>
Hi,
On Thu, Jun 07, 2012 at 01:06:01PM +0200, Adam Sloboda wrote:
> At Thu, 7 Jun 2012 11:56:38 +0200, Toni Mueller wrote:
> > what do you want me to do?
> I need to debug it and fix the code but I need test case first.
ok.
> Can you try turning off SCIM?
Tough call - I can't do that for long.
At Thu, 7 Jun 2012 11:56:38 +0200,
Toni Mueller wrote:
>
>
> Hi,
>
> On Thu, Jun 07, 2012 at 10:12:23AM +0200, Adam Sloboda wrote:
> > I tried this also on testing and couldn't reproduce it. It seems like
> > there is a strange problem with data xkb supplies but I'm just
> > guessing now, test
Hi,
On Thu, Jun 07, 2012 at 10:12:23AM +0200, Adam Sloboda wrote:
> I tried this also on testing and couldn't reproduce it. It seems like
> there is a strange problem with data xkb supplies but I'm just
> guessing now, test case would really help.
what do you want me to do?
> In the meantime m
At Wed, 6 Jun 2012 17:00:16 +0200,
Toni Mueller wrote:
>
>
> Hi Adam,
>
> On Wed, Jun 06, 2012 at 04:10:25PM +0200, Adam Sloboda wrote:
> > At Tue, 5 Jun 2012 20:40:58 +0200, Toni Mueller wrote:
> > > On Tue, Jun 05, 2012 at 05:45:01PM +0200, Adam Sloboda wrote:
> > > > This might help to shed a
Hi Adam,
On Wed, Jun 06, 2012 at 04:10:25PM +0200, Adam Sloboda wrote:
> At Tue, 5 Jun 2012 20:40:58 +0200, Toni Mueller wrote:
> > On Tue, Jun 05, 2012 at 05:45:01PM +0200, Adam Sloboda wrote:
> > > This might help to shed a little light on where it's crashing.
> > here you are:
> >
> > Program
At Tue, 5 Jun 2012 20:40:58 +0200,
Toni Mueller wrote:
>
>
> Hi Adam,
>
> On Tue, Jun 05, 2012 at 05:45:01PM +0200, Adam Sloboda wrote:
> > gkrellm will stop updating, type "cont" command and then just wait for
> > another crash (it will again stop updating). Then type "bt" or
> > "backtrace" c
Hi Adam,
On Tue, Jun 05, 2012 at 05:45:01PM +0200, Adam Sloboda wrote:
> gkrellm will stop updating, type "cont" command and then just wait for
> another crash (it will again stop updating). Then type "bt" or
> "backtrace" command and send it to me.
>
> This might help to shed a little light on
At Tue, 05 Jun 2012 15:37:37 +0200,
Toni Mueller wrote:
>
> Package: gkrellm-xkb
> Version: 1.05-5
> Severity: normal
>
> Dear Maintainer,
>
> I'm not sure that this is the right package to report against, but my
> gkrellm crashes frequently with this error (from .xsession-errors):
>
> sensorgk
Package: gkrellm-xkb
Version: 1.05-5
Severity: normal
Dear Maintainer,
I'm not sure that this is the right package to report against, but my
gkrellm crashes frequently with this error (from .xsession-errors):
sensorgkrellm segmentation fault: xkb (update_monitor)
I am open to suggestions on h
11 matches
Mail list logo