Failed to execute default file manager (Input /Output Error) [SOLVED]

yochaigal · 2015-04-26 17:06:40

I'm having an issue in XFCE where the default Terminal, Browser and File Manager launch correctly - but with this error:

Failed to execute default [file manager] [terminal emulator] [browser]
Input /Output Error

I have the requisite "Preferred Application" set as Chrome/Thunar/xfce4-terminal.

If I run

exo-open --launch FileManager

From terminal, it says:

[1] 4281 segmentation fault (core dumped) exo-open --launch FileManager

Remember, it launches the app successfully - and the apps themselves launch correctly, it's only exo-open that I have a problem with! Everything else works great on this system.

Last edited by yochaigal (2015-04-28 11:10:06)

Head_on_a_Stick · 2015-04-26 17:32:57

I/O error sounds hardware-related.

Check your cables & connectors and run SMARTCTL on your drive.

yochaigal · 2015-04-26 17:36:42

Unfortunately this is not the case - my SMART status/filesystem are all in good condition; further I'm using a brand-new SSD, further this problem existed before (new system, imaged over from previous non-SSD) on a previous drive that is also in excellent health.
TL; DR my background is in data recovery, hard drive health is not the issue.

I actually found a number of posts identical to mine - I/O error and everything. However, for them it was always a simple case of not having a preferred application set.

bleach · 2015-04-26 17:58:05

is xorg-xprop installed

is your issue anything like this?

Head_on_a_Stick · 2015-04-26 18:00:17

yochaigal wrote:

TL; DR my background is in data recovery, hard drive health is not the issue.

With all due respect, is it possible that the cable and/or connector could be damaged?

yochaigal · 2015-04-26 19:03:22

bleach wrote:

is xorg-xprop installed
is your issue anything like this?

Yes it is installed - and xdg-settings get default-web-browser shows the correct setting.

yochaigal · 2015-04-26 19:04:32

Head_on_a_Stick wrote:

yochaigal wrote:
TL; DR my background is in data recovery, hard drive health is not the issue.
With all due respect, is it possible that the cable and/or connector could be damaged?

Unlikely - I recently rebuilt this machine (imaged OS to all-new hardware, including SATA cables), and the problem existed before (with separate SATA cables, drives, motherboard), I just ignored it until now.
Thanks for your help so far, though!

progandy · 2015-04-26 19:14:23

Exactly where do you get the IO error? The IO error could be the result of the exo-open crash I think. Could you try to recompile exo-open or maybe replace it with a simple bash script for testing purposes?
Edit: To clarify, if you run exo-open from terminal, does it display the I/O error or is that error message part of some other application?
Edit: If I understand this exo mess, then exo-open delegates --launch to "/usr/lib/xfce4/exo-1/exo-helper-1". What happens if you run that directly?

Last edited by progandy (2015-04-26 19:32:53)

yochaigal · 2015-04-26 19:32:34

Imagine you're clicking a URL from within an application - say, Steam.
It will launch of Chrome, but then this error appears:

demolitions · 2015-04-27 10:39:45

I got the same problem, I observed the problem appearing with those lines in "dmesg", the same library (libpthread-2.21.so) is also present in other software errors (critical and not) since my last update (friday 24th).
I'll try downgrading glibc, see if that works around the problem.

[  587.042204] traps: xfce4-terminal[1022] general protection ip:7f6500100150 sp:7ffe14c978d8 error:0 in libpthread-2.21.so[7f65000ee000+18000]
[  592.113288] traps: xfce4-terminal[1026] general protection ip:7fbf1c97a150 sp:7ffe2f916188 error:0 in libpthread-2.21.so[7fbf1c968000+18000]
[  620.913826] traps: xfce4-notifyd[494] general protection ip:7fa4859a2150 sp:7fff84dd7708 error:0 in libpthread-2.21.so[7fa485990000+18000]
[  974.008983] traps: xfce4-terminal[1384] general protection ip:7f519df84150 sp:7ffe3573e4f8 error:0 in libpthread-2.21.so[7f519df72000+18000]
[  974.850083] traps: xfce4-terminal[1387] general protection ip:7f6ed57f8150 sp:7ffec58369c8 error:0 in libpthread-2.21.so[7f6ed57e6000+18000]
[  975.521687] traps: xfce4-terminal[1390] general protection ip:7f5e91d00150 sp:7ffd70179d18 error:0 in libpthread-2.21.so[7f5e91cee000+18000]
[  979.179030] traps: exo-open[1393] general protection ip:7fbdd2a24150 sp:7ffe9e0c5608 error:0 in libpthread-2.21.so[7fbdd2a12000+18000]
[  984.286944] traps: exo-helper-1[1395] general protection ip:7fd5d8473150 sp:7ffd53706a08 error:0 in libpthread-2.21.so[7fd5d8461000+18000]
[ 1012.318773] traps: xfce4-terminal[1502] general protection ip:7ffb62b1b150 sp:7fffd5c986f8 error:0 in libpthread-2.21.so[7ffb62b09000+18000]
[ 1101.456187] traps: xfce4-terminal[1521] general protection ip:7f3285cf2150 sp:7fff3c6df158 error:0 in libpthread-2.21.so[7f3285ce0000+18000]
[ 1102.120447] traps: xfce4-terminal[1525] general protection ip:7fdd50c3a150 sp:7ffe96656ce8 error:0 in libpthread-2.21.so[7fdd50c28000+18000]
[ 1103.246180] traps: xfce4-terminal[1529] general protection ip:7f93f2b49150 sp:7ffc539d34e8 error:0 in libpthread-2.21.so[7f93f2b37000+18000]
[ 1103.976302] traps: xfce4-terminal[1532] general protection ip:7f6a55204150 sp:7ffd13eb77f8 error:0 in libpthread-2.21.so[7f6a551f2000+18000]
[ 1118.718286] traps: xfce4-terminal[1953] general protection ip:7efc94fb9150 sp:7ffd6f5fbed8 error:0 in libpthread-2.21.so[7efc94fa7000+18000]
[ 1160.851856] traps: xfce4-terminal[1992] general protection ip:7f39aaddb150 sp:7ffdb4478aa8 error:0 in libpthread-2.21.so[7f39aadc9000+18000]
[ 1165.279367] traps: xfce4-terminal[2004] general protection ip:7f3a50756150 sp:7ffd743c07b8 error:0 in libpthread-2.21.so[7f3a50744000+18000]
[ 1173.696850] traps: xfce4-terminal[2008] general protection ip:7f0930b98150 sp:7ffc5cd54e78 error:0 in libpthread-2.21.so[7f0930b86000+18000]
[ 1177.567234] traps: xfce4-terminal[2011] general protection ip:7f5ea2222150 sp:7ffd81d4e898 error:0 in libpthread-2.21.so[7f5ea2210000+18000]

demolitions · 2015-04-27 13:37:21

demolitions wrote:

I got the same problem, I observed the problem appearing with those lines in "dmesg", the same library (libpthread-2.21.so) is also present in other software errors (critical and not) since my last update (friday 24th).
I'll try downgrading glibc, see if that works around the problem.

[  587.042204] traps: xfce4-terminal[1022] general protection ip:7f6500100150 sp:7ffe14c978d8 error:0 in libpthread-2.21.so[7f65000ee000+18000]
[  592.113288] traps: xfce4-terminal[1026] general protection ip:7fbf1c97a150 sp:7ffe2f916188 error:0 in libpthread-2.21.so[7fbf1c968000+18000]
[  620.913826] traps: xfce4-notifyd[494] general protection ip:7fa4859a2150 sp:7fff84dd7708 error:0 in libpthread-2.21.so[7fa485990000+18000]
[  974.008983] traps: xfce4-terminal[1384] general protection ip:7f519df84150 sp:7ffe3573e4f8 error:0 in libpthread-2.21.so[7f519df72000+18000]
[  974.850083] traps: xfce4-terminal[1387] general protection ip:7f6ed57f8150 sp:7ffec58369c8 error:0 in libpthread-2.21.so[7f6ed57e6000+18000]
[  975.521687] traps: xfce4-terminal[1390] general protection ip:7f5e91d00150 sp:7ffd70179d18 error:0 in libpthread-2.21.so[7f5e91cee000+18000]
[  979.179030] traps: exo-open[1393] general protection ip:7fbdd2a24150 sp:7ffe9e0c5608 error:0 in libpthread-2.21.so[7fbdd2a12000+18000]
[  984.286944] traps: exo-helper-1[1395] general protection ip:7fd5d8473150 sp:7ffd53706a08 error:0 in libpthread-2.21.so[7fd5d8461000+18000]
[ 1012.318773] traps: xfce4-terminal[1502] general protection ip:7ffb62b1b150 sp:7fffd5c986f8 error:0 in libpthread-2.21.so[7ffb62b09000+18000]
[ 1101.456187] traps: xfce4-terminal[1521] general protection ip:7f3285cf2150 sp:7fff3c6df158 error:0 in libpthread-2.21.so[7f3285ce0000+18000]
[ 1102.120447] traps: xfce4-terminal[1525] general protection ip:7fdd50c3a150 sp:7ffe96656ce8 error:0 in libpthread-2.21.so[7fdd50c28000+18000]
[ 1103.246180] traps: xfce4-terminal[1529] general protection ip:7f93f2b49150 sp:7ffc539d34e8 error:0 in libpthread-2.21.so[7f93f2b37000+18000]
[ 1103.976302] traps: xfce4-terminal[1532] general protection ip:7f6a55204150 sp:7ffd13eb77f8 error:0 in libpthread-2.21.so[7f6a551f2000+18000]
[ 1118.718286] traps: xfce4-terminal[1953] general protection ip:7efc94fb9150 sp:7ffd6f5fbed8 error:0 in libpthread-2.21.so[7efc94fa7000+18000]
[ 1160.851856] traps: xfce4-terminal[1992] general protection ip:7f39aaddb150 sp:7ffdb4478aa8 error:0 in libpthread-2.21.so[7f39aadc9000+18000]
[ 1165.279367] traps: xfce4-terminal[2004] general protection ip:7f3a50756150 sp:7ffd743c07b8 error:0 in libpthread-2.21.so[7f3a50744000+18000]
[ 1173.696850] traps: xfce4-terminal[2008] general protection ip:7f0930b98150 sp:7ffc5cd54e78 error:0 in libpthread-2.21.so[7f0930b86000+18000]
[ 1177.567234] traps: xfce4-terminal[2011] general protection ip:7f5ea2222150 sp:7ffd81d4e898 error:0 in libpthread-2.21.so[7f5ea2210000+18000]

Tried downgrading glibc from 2.21-3 to 2.21-2 as this is the package which contains libpthread.so, and on my other arch workstations I don't have the issue, but to no avail, same error box pops up when using exo-open, and my IDEs are not starting.
I'll try comparing installed packages versions on both workstations.

progandy · 2015-04-27 13:41:24

Can you try downgrading the exo package?

demolitions · 2015-04-27 14:17:16

Downgrading exo from 0.10.4-3 to 0.10.4-1 stopped the popup, but not the error in dmesg, nor the segfaults.
0.10.3-2 asks for libxfce4util.so.6, I believe that was before the switch to xfce 4.12

demolitions · 2015-04-27 14:18:40

demolitions wrote:

Downgrading exo from 0.10.4-3 to 0.10.4-1 stopped the popup, but not the error in dmesg, nor the segfaults.
0.10.3-2 asks for libxfce4util.so.6, I believe that was before the switch to xfce 4.12

I forgot to add, launching /usr/lib/xfce4/exo-1/exo-helper-1 directly results with the same segfault, and the same popup if exo is > 0.10.4-1

dice · 2015-04-27 14:28:10

Might be related similar/same to this thread?
Both of you are reporting I/O issues and both are using xfce.

demolitions · 2015-04-27 14:55:53

Not my case, I have the issue even on KDE:
Launching Eclipse or Netbeans yields a segmentation fault, and locates the error in the same library (libpthread.so).
It's not Java-related, 'cause other Java applications run fine, and I haven't modified my workstation in some time.
SMART says all is well, launching "Thunar" directly works fine, no errors.
exo-open gives this segfault in libpthread, ad it does so AFTER having launched Thunar or xfce4-terminal,
Thunar-volman does not work (no removable devices in the left pane)
xfce4-appfinder also puts the same error message in dmesg, but works fine.
Firefox does the same (error in dmesg, but works)
kcalc does the same.
I could go on testing every application on my machine, I get the feeling that's not an xfce issue.

One thing I could add, I got this problem after updating friday afternoon, and I update fairly regularly, at least weekly.
Since I believed this to be a problem included in some mess I made Friday with some of my applications, I tried reinstalling fresh on another workstation, the results are the same.

Since my workstations are identical, maybe it could be something hardware related? Not "faulty" hardware, but perhaps some "not that compatible" changes in some system libs?

WorMzy · 2015-04-27 15:11:46

Do you have an Intel CPU? Are you updating the microcode at boot time?

https://www.archlinux.org/news/changes- … deupdates/
https://wiki.archlinux.org/index.php/Microcode

bpye · 2015-04-27 15:37:12

WorMzy wrote:

Do you have an Intel CPU? Are you updating the microcode at boot time?
https://www.archlinux.org/news/changes- … deupdates/
https://wiki.archlinux.org/index.php/Microcode

Enabling microcode updates fixed this for me, I feel this should be in the installation guides?

Alad · 2015-04-27 15:41:29

Before people go around adding microcode to every single wiki article, we should perhaps first investigate when exactly this issue started appearing? Was there not a mention of nvidia proprietary drivers?

edit: Microcode was added to General recommendations which every Arch user is expected to read.

Last edited by Alad (2015-04-27 16:10:21)

demolitions · 2015-04-27 16:23:46

Adding microcode updates to syslinux fixed this issue, thanks very much.

Only one thing I don't understand: The news about the microcode updates is dated 2014-10-22, why it started affecting my machine only last friday?

As far as I can remember, I had no kernel nor drivers updates on that batch.

WorMzy · 2015-04-27 18:16:01

I'm not sure. There seems to have been a spate of people getting bitten by microcode bugs over the past few days. Perhaps something changed in the latest build of glibc (dated 22nd April) which is making things more susceptible to these sorts of problems.

I don't know whether this should be reported as a bug though -- people really should be loading the ucode.img if they're using an Intel CPU.

demolitions · 2015-04-28 07:38:43

I don't think this sholuld be reported as a bug, but perhaps it should be pointed out better that we should load ucode.img, now that's not automatic anymore, maybe directly in the beginner's guide.
Or maybe it should be pointed out better that the general recommendation page changes are important, I read that page something like 3 years ago, and I haven't looked at it since.

yochaigal · 2015-04-28 11:09:52

I already had microcode loading at boot (using grub). I use an Intel CPU, and I an nvidia GPU with proprietary drivers.
However, I re-installed the microcode updates and re-updated GRUB - and the I/O errors went away!
Marking thread as solved.

Last edited by yochaigal (2015-04-28 11:10:34)

Arch Linux

#1 2015-04-26 17:06:40

Failed to execute default file manager (Input /Output Error) [SOLVED]

#2 2015-04-26 17:32:57

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#3 2015-04-26 17:36:42

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#4 2015-04-26 17:58:05

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#5 2015-04-26 18:00:17

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#6 2015-04-26 19:03:22

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#7 2015-04-26 19:04:32

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#8 2015-04-26 19:14:23

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#9 2015-04-26 19:32:34

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#10 2015-04-27 10:39:45

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#11 2015-04-27 13:37:21

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#12 2015-04-27 13:41:24

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#13 2015-04-27 14:17:16

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#14 2015-04-27 14:18:40

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#15 2015-04-27 14:28:10

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#16 2015-04-27 14:55:53

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#17 2015-04-27 15:11:46

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#18 2015-04-27 15:37:12

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#19 2015-04-27 15:41:29

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#20 2015-04-27 16:23:46

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#21 2015-04-27 18:16:01

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#22 2015-04-28 07:38:43

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

#23 2015-04-28 11:09:52

Re: Failed to execute default file manager (Input /Output Error) [SOLVED]

Board footer