SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You mean comment 77 by Ali Akcaagac 2015-03-07 14:23:19 CET:
Quote:
But what happens ? Here an attempt to explain.
Everyone ran Thunar 1.6.3 before. Then Thunar 1.6.4 came up and everyone simply upgraded it. People continued using Thunar 1.6.4 as is. No further changes made to settings.
The crash shows up once people copy stuff from A to B.
But!
There was this new option introduced in Thunar 1.6.4 in preferences saying
"Show file size in binary format"
This is by default set to "off" (unselected)... But internally when code executes the condition is how ?
This causes the crashes. The initial condition is unknown.
Once I selected this setting then I won't get any crashes anymore. After that you can unselect this setting again to set it's state to "off" and even then all crashes are gone.
I tried this in the preferences of Thunar and ticking that "Show file size in binary format"-box made my crashing to stop, at least during the couple of copy-paste actions I did with my TestFolder...
Hmmm... All this talk about "uninitialised" options in XFCE, reminds me that some option settings effectively work in one state (say, ON or OFF) while they show up differently on the configuration panels by default. To synchronise their "visible" and "operational" states, I typically toggle them once or twice on the configuration panels.
I have never understood how this "Out-Of-Sync-By-Default" behaviour came about, but it is all beginning to make sense to me now.
Use 1.6.30 (the latest release). However, I think there's more to it - some people are using later 1.6.x releases and still seeing crashes, although it's not clear how often they're seeing them. I think there are at least two different bugs at play here - see my later comment on the bug report for details.
Well, check out the bug report. The cause is pretty much understood now, and it's not dbus after all (perhaps it's just that dbus-1.8.x is faster and avoids the races). I've got a build of Thunar out with an earlier patch that probably fixes the behavior *most* of the time, but once an official patch makes it into git, I'll rebuild with it.
Well, check out the bug report. The cause is pretty much understood now, and it's not dbus after all (perhaps it's just that dbus-1.8.x is faster and avoids the races). I've got a build of Thunar out with an earlier patch that probably fixes the behavior *most* of the time, but once an official patch makes it into git, I'll rebuild with it.
Thanks for the information, I removed the dbus slackbuild from the build scripts.
Can you share your patch?
-- 16-03-2015 --
-> Removed dbus package (not )
-> Added 3 patches to fix Thunar copy paste behaviour (thanks to rworkman)
-> Upgraded libxfce4ui from version 4.12.0 to 4.12.1
-> Upgraded xfce4-session from version 4.12.0 to 4.12.1
-> Upgraded xfwm4 from version 4.12.0 to 4.12.2
# dmesg
[ 247.368352] xfce4-mixer[1357]: segfault at 28 ip 00007fdd05b3653d sp 00007fff1a1d29c0 error 4 in libgtk-x11-2.0.so.0.2400.20[7fdd05a8b000+428000]
[ 263.289344] xfce4-mixer[1363]: segfault at 28 ip 00007f1f7800653d sp 00007fffb3e02b10 error 4 in libgtk-x11-2.0.so.0.2400.20[7f1f77f5b000+428000]
[ 279.633621] xfce4-mixer[1369]: segfault at 28 ip 00007f780b96153d sp 00007fff7572aea0 error 4 in libgtk-x11-2.0.so.0.2400.20[7f780b8b6000+428000]
[ 346.883753] xfce4-mixer[1376]: segfault at 28 ip 00007f2e6f90153d sp 00007fffa1adb280 error 4 in libgtk-x11-2.0.so.0.2400.20[7f2e6f856000+428000]
and nothing about segfault
This is on Slackware64-14.1 with mpla's slackbuilds.
P.S. I see this bug, but there are no solution. I revert back xfce4-mixer-4.8...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.