I updated thunar and exo today (among others, full pacman.log extract quoted)
[2012-12-04 13:25] upgraded exo (0.8.0-1 -> 0.10.0-1) [2012-12-04 13:26] upgraded lazarus (1.0.2-1 -> 1.0.4-1) [2012-12-04 13:26] upgraded lib32-fontconfig (2.10.1-1 -> 2.10.2-1) [2012-12-04 13:26] upgraded lib32-glib2 (2.34.2-1 -> 2.34.3-1) [2012-12-04 13:26] upgraded lib32-harfbuzz (0.9.6-1 -> 0.9.7-1) [2012-12-04 13:26] upgraded lib32-pango (1.32.2-1 -> 1.32.3-1) [2012-12-04 13:26] upgraded lib32-v4l-utils (0.8.8-1 -> 0.8.9-1) [2012-12-04 13:26] upgraded libmicrohttpd (0.9.23-1 -> 0.9.23-2) [2012-12-04 13:26] upgraded libssh (0.5.2-1 -> 0.5.3-1) [2012-12-04 13:26] upgraded pcre (8.31-1 -> 8.32-1) [2012-12-04 13:26] upgraded thunar (1.4.0-4 -> 1.6.0-1)
and since then every time I open a window and try to double click or right click on a folder, it crashes with a segmentation fault. journalctl gives nothing, but /var/log/messages reports
Dec 4 14:04:36 localhost kernel: [ 2519.578639] Thunar: segfault at fffffffd ip 00007f06c7217dc8 sp 00007fff93e948e0 error 4 in libc-2.16.so[7f06c71cd000+19d000] Dec 4 14:04:36 localhost systemd-coredump: Process 3536 (Thunar) dumped core.
My glibc version is 2.16.0-5 which, as far as I can see, is the latest version. I reinstalled it for good measure, but the problem remains.
Any ideas? Perhaps a thunar bug?
Addendum: I started rodent, it did the same thing.
Dec 4 14:14:41 localhost systemd-coredump: Process 3677 (rodent) dumped core.
I downgraded thunar to thunar-1.4.0-4 from my cache, both thunar and rodent work. Weird!!
Last edited by GordonGR (2012-12-11 12:31:35)
I think it's glibc related, try downgrading it or rolling back with the ARM trick @ https://wiki.archlinux.org/index.php/Do … ckages#ARM
As you may use "downgrade" script I posted about on LinkedIn @ https://www.linkedin.com/groupAnswers?v … =105851449
The "downgrade" script @ https://aur.archlinux.org/packages/downgrade/
and usage simple, just issue "downgrade packagename" and you're good to go
Hope it helps.
It doesn't happen to me on a fully up-to-date system. If it was glibc wouldn't everyone using thunar have the same problem?
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
@loafer: Nor happens to me with an up to date packages too but can't tell
I’ve had Thunar 1.6 crash on me too, but with the en_GB.UTF-8 locale, so I don’t know if it’s related.
Since I dislike the changes made to thunar, I quickly downgraded to 1.4 which works fine.