I switched to a non-murrine theme and still got the same crash. The valgrind
output
is below. I subsequently switched from my Openbox session to an XFCE session
and
got the same crash, too. I don't intend to burn a ton of discs with this
machine, so
I can adapt to burn's command line
Hi,
I can adapt to burn's command line interface. A terminal's progress bar is
much cooler, anyway :)
(Hopping up and down waving with 4660 lines of xorriso manual)
Do i get it right that this is 32 bit code ?
Yes.
So we seem to have some problem in the core GLib/GTK stuff
that is linked
Hi,
Sorry I took so long. Debian's bugtracker didn't forward me the emails, so I
just saw this yesterday. Here's the contents of /tmp/valgrind_messages:
==2799== Memcheck, a memory error detector
==2799== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==2799== Using
Hi,
Debian's bugtracker didn't forward me the emails,
This has happened to me, too. But today it worked for me.
==2799== Conditional jump or move depends on uninitialised value(s)
==2799==at 0x7201FC8: ??? (in
/usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so)
Hard to
Hi,
as one can see, there is not much xfburn code active when the
SIGSEGV happens. I guess it is thread 1 which suffers it.
Now while there is still the possibility that xfburn started
the problem by subtle corruption of memory management, it
is strange that this does not happen on arch amd64.
Package: xfburn
Version: 0.5.2-1
Severity: important
Dear Maintainer,
I get a segmentation fault after choosing New Data Composition, clicking on
the add button, selecting a file and clicking Add. It crashes right when
I click Add. Here's what gdb gives me:
Starting program: /usr/bin/xfburn
Hi,
i'm not the maintainer of xfburn and not even a
frequent user of it, but nevertheless interested
in seeing it work properly. (That's because it
uses my libburn and libisofs as burn backend.)
Kernel: Linux 3.16-3-powerpc
This might cause a problem with reproducing the
problem by xfburn's
7 matches
Mail list logo
