[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#608732: stack trace ?



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


hello rene,

On 01/24/2011 07:38 PM, Rene Engelhard wrote:
> On Mon, Jan 24, 2011 at 06:59:59PM +0200, alex bodnaru wrote:
>> the problem seems to live in the way lio is installed in debian distribution,
>> maybe in the packages (or versions thereof) lio is using.
> 
i came to this conclusion after installing today the deb provided upstream.
debian packagers allways try to reuse libraries and data available on the
system, rather than adopting some third party libraries that upstream include in
their source.

moreover, upstream are changing not a few strings in their source for the fork
in the name.

> Maybe.
> 
>> of course, i'm sure that rene and his team will find the problem.
> 
> Doubt that unless we get more info.
> (Besides that, there is no team...)
i'm here to help for your wonderful work.
> 
> And can you goddamn keep the bug in the CC? How often should I tell that?
> All your replies since Jan, 19 did *not* end up being recorded in the BTS...
> 
i'm realy sorry. i should get more organized myself.

now that it is cc, i'd dare summarizing that lio is constantly crashing upon
closing after i've run a macro (whether the macro exists or not, crashes or
not). doesn't matter whether the homedir is local or not.

related or not, after installing the extension attached with the bug
(immediately), the extensions window doesn't repaint.

> I bounced them all there, but...
> 
> Grüße/Regards,
> 
> René

- -- 
- --
best regards,
alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iJwEAQECAAYFAk09vjwACgkQ2nA3WyrfyeOXRwP/eHnzXeaH60//gaBPv/rWaBS1
QGureYyrVrLdVY1ILM5y5+NKDN3FJD6cWnsBMiNEwDxHBnjQLwBHzsfcv70M7e2Y
+tDLX6SG4JNvkvdqVfgrG+cu+oWp8o2ouzTO949NfIvxyKFbkQ94TbpyoXeg4/1j
7QjJo/MdFYaWWftlNrI=
=A3DO
-----END PGP SIGNATURE-----




Reply to: