e2 crashes when clicking the command.mkdir-button

  • From: Joe Koenig <joe.koenig@xxxxxx>
  • To: emelfm2@xxxxxxxxxxxxx
  • Date: Tue, 18 May 2010 08:14:30 +0200

Hello,

sometimes e2 crashes when performing the "mkdir/Create new directory(ies)" 
action on the task toolbar.  Specifically: it happens as soon as I click the 
mkdir button.

This is not reproduceable at all, seems all accidental.

As a sidenote: I'm running Archlinux now.  I noticed that when installing e2 
on Ubuntu/Kubuntu (a few weeks ago) it installed lots of Gnome-dependencies 
alongside.  Archlinux didn't.  However, I only ran (K)Ubuntu for a few 
hours/days, so I can't tell whether this behaviour occured there too, as I 
used other/inferior filemangers there.

I created a custom task-toolbar-item with the command: mkdir `date +%s`
to see whether this behaviour occured there, too.  It didn't.  But, as I said: 
this isn't exactly reproduceable.



$ emelfm2 -v
emelFM2 v. 0.7.1
Licensed under the GPL
Copyright (C) 2003-2009, tooar <tooar@xxxxxxxxxxx>
Build date: Tue Dec 22 21:28:22 EST 2009
Build platform: GTK+ 2.18.5 Linux 2.6.31-ARCH/i686


$ ldd /usr/bin/emelfm2
        linux-gate.so.1 =>  (0xb778f000)
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb73af000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb731c000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb72ff000)
        libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb72f5000)
        libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb7282000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb7241000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7203000)
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb71ff000)
        librt.so.1 => /lib/librt.so.1 (0xb71f6000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb71f2000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb712a000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb7111000)
        libc.so.6 => /lib/libc.so.6 (0xb6fc5000)
        libm.so.6 => /lib/libm.so.6 (0xb6fa0000)
        libdl.so.2 => /lib/libdl.so.2 (0xb6f9c000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0xb6f8d000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb6f84000)
        libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb6f81000)
        libXi.so.6 => /usr/lib/libXi.so.6 (0xb6f74000)
        libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb6f6d000)
        libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb6f63000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0xb6e49000)
        libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xb6e46000)
        libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xb6e43000)
        libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb6e3e000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb6e24000)
        libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0xb6d8a000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb6d65000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb6ce0000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb6cb2000)
        libpng14.so.14 => /usr/lib/libpng14.so.14 (0xb6c8c000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb6c76000)
        libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xb6c17000)
        libxcb-render-util.so.0 => /usr/lib/libxcb-render-util.so.0 (0xb6c13000)
        libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0xb6c0c000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb6bf3000)
        libpcre.so.0 => /lib/libpcre.so.0 (0xb6bc0000)
        /lib/ld-linux.so.2 (0xb7790000)
        libresolv.so.2 => /lib/libresolv.so.2 (0xb6bab000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb6b85000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0xb6b81000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb6b7c000)

$ uname -a
Linux Jessi 2.6.33-ARCH #1 SMP PREEMPT Mon Apr 26 20:00:20 CEST 2010 i686 AMD 
Athlon(tm) II X2 240 Processor AuthenticAMD GNU/Linux


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: