It's true. I got out the XFCE because the most errors in the your
graphical inteface.

    Em Segunda-feira, 16 de Janeiro de 2017 14:16, Norman 
<1512...@bugs.launchpad.net> escreveu:
 

 It's a shame that Xfce devs can't fix this bug since 2015. Time to
switch to MATE.

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1603030).
https://bugs.launchpad.net/bugs/1512120

Title:
  thunar crashes on file renaming

Status in thunar:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed

Bug description:
  When renaming files in a folder while re-sorting similarly named
  files, thunar crashes fairly often. Apport does not detect the
  crashes.

  Running thunar in valgrind produces these log entries in the moment of
  the crash:

  ==28859== Thread 1:
  ==28859== Invalid read of size 1
  ==28859==    at 0x04c2ffd3: strcmp (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==28859==    by 0x0014590c: thunar_file_compare_by_name (within 
/usr/bin/thunar)
  ==28859==    by 0x00153e3d: thunar_list_model_cmp_func (within 
/usr/bin/thunar)
  ==28859==    by 0x07e4da23: ??? (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.1)
  ==28859==    Address 0x0 is not stack'd, malloc'd or (recently) free'd
  ==28859==
  ==28859== Process terminating with default action of signal 11 (SIGSEGV)
  ==28859== Access not within mapped region at address 0x0
  ==28859==    at 0x04c2ffd3: strcmp (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==28859==    by 0x0014590c: thunar_file_compare_by_name (within 
/usr/bin/thunar)
  ==28859==    by 0x00153e3d: thunar_list_model_cmp_func (within 
/usr/bin/thunar)
  ==28859==    by 0x07e4da23: ??? (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.1)
  ==28859==    If you believe this happened as a result of a stack
  ==28859==    overflow in your program's main thread (unlikely but
  ==28859==    possible), you can try to increase the size of the
  ==28859==    main thread stack using the --main-stacksize= flag.
  ==28859==    The main thread stack size used in this run was 8388608.
  ==28859==
  ==28859== HEAP SUMMARY:
  ==28859== in use at exit: 11,169,056 bytes in 101,668 blocks
  ==28859== total heap usage: 8,917,549 allocs, 8,815,881 frees, 736,520,410 
bytes allocated
  ==28859==
  ==28859== For counts of detected and suppressed errors, rerun with: -v
  ==28859== Use --track-origins=yes to see where uninitialised values come from
  ==28859== ERROR SUMMARY: 1046 errors from 45 contexts (suppressed: 0 from 0)
  ==28859==

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: thunar 1.6.10-1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  1 18:57:09 2015
  InstallationDate: Installed on 2015-02-05 (268 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150205)
  SourcePackage: thunar
  UpgradeStatus: Upgraded to wily on 2015-05-28 (156 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120

Title:
  thunar crashes on file renaming

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to