reassign 840430 nitroshare-nemo
retitle 840430 installing nitroshare-nemo makes nemo crash on opening files
from desktop
thanks
Hi Jason,
after long playing around I found that nitroshare-nemo is the culprit. I first
thought it is nemo-python seeing all the python warnings, but even recompiling
HI Jason,
thanks for your email.
> You could try setting the environment variable G_SLICE=debug-blocks so
> glib will abort if it detects invalid memory releases. That will
Ok, tried that, started nemo, made it crash, got
GSlice: MemChecker: attempt to release non-allocated block: 0x2dc
On Wed, Oct 12, 2016 at 10:18:53AM +0900, Norbert Preining wrote:
> Hi Jason,
>
> > It's a little bit suspicious that in frame 1, the _object pointer is
> > invalid (0x2). Anyway, the debug packages for gtk are now automatic
>
> Hmm, I retried, and now a get a different backtrace. It segfaults
>
Hi Jason,
> It's a little bit suspicious that in frame 1, the _object pointer is
> invalid (0x2). Anyway, the debug packages for gtk are now automatic
Hmm, I retried, and now a get a different backtrace. It segfaults
at 100% of instances, but it seems always in different regions:
(gdb) bt
#0 0x
On Tue, Oct 11, 2016 at 11:14:14PM +0900, Norbert Preining wrote:
> nemo (file manager of cinnamon) is happily crashing in gobject code.
> I have installed all kind of debug symbol packages, and even rebuilt
> libgtk3 and installed the (otherwise not available) debug symbols,
> and then I get the
Source: glib2.0
Severity: important
Hi all,
nemo (file manager of cinnamon) is happily crashing in gobject code.
I have installed all kind of debug symbol packages, and even rebuilt
libgtk3 and installed the (otherwise not available) debug symbols,
and then I get the following backtrace:
Core wa
6 matches
Mail list logo
