[Expired for thunar (Ubuntu) because there has been no activity for 60
days.]
** Changed in: thunar (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372140
** Tags removed: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372140
Title:
thunar segfault, memory corruption in the gslice magazine allocator
To manage notifications about this bug go to
I don't know when, but this bug was eventually fixed. I still use my
Ubuntu 14.04 system on Canonical's ESM extension and it's been years
since I've had Caja or Thunar crash like above. I consider this bug
fixed. You can mark it closed.
--
You received this bug notification because you are a memb
** Changed in: thunar (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372140
Title:
thunar segfault, memory corruption in the gslice magazine allocator
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: thunar (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372140
Title:
thu
Thanks for the response. I understand memory corruption bugs all look
fairly generic in terms of their error messages but linking this issue
to similar bugs on launchpad is the only way I can get anyone to pay
attention.
It crashes randomly. I have not been able to find any correlation with
any be
As an aside, I have run memtest86 multiple times. My RAM is fine. No
applications except Thunar (gmain) and Caja crash like this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372140
Title:
thunar
Well if you still get the crash then it is something different. The
dangling signal crash had a specific way to cause it - it wouldn't crash
until you quit thunar - and we were able to verify it was fixed. But
memory corruption can be caused by any number of things and they all
look the same in the
Er, more specifically this bug,
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296 , which
was supposed to be fixed by the above bug fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137214
This crash looks very similar to what is fixed in,
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1316509 . But I
have that version of libgtk2 and it is not fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Here's another backtrace I made after installing more debug symbol
packages to full cover Thunar's dependencies.
** Attachment added: "thunar segfault backtrace (full debug symbols)"
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1372140/+attachment/4211926/+files/thunar_full.txt
--
Y
libgtk2.0-0:
Installed: 2.24.23-0ubuntu1.1
Candidate: 2.24.23-0ubuntu1.1
Version table:
*** 2.24.23-0ubuntu1.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.24.23-0ubuntu1 0
12 matches
Mail list logo
