Arch Linux

I've attached an strace of an failure start. The application hangs on "futex(0x97ea20, FUTEX_WAIT_PRIVATE, 0, NULL"

regards
Kai

Which desktop manager are you using?

Hi,

Gnome 3.10.1 and also the latest nvidia drivers from the Arch Repo.

regards
Kai

Hi,
can you try to extract this file and to do:
make -C keepass-test run

I think it's the same problem of http://forum.manjaro.org/index.php?topic=8253.0

Hi,

tryed it 4+ times and it works for now. But is rather an workaround instead of a fix, isn't? I has found stuff that it's maybe related to the current nvidia-drivers ->

https://www.smuxi.org/issues/show/903
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728743

/edit
Same with other mono apps, like banshee or monodevelop.

regards
Kai

Keepass will no longer start up for me as well. I am running an up-to-date x64 Arch system with an Xfce4 desktop.

I recently updated to the latest linux kernel (3.12.3-1) and Nvidia driver set (v331.20-2); keepass had been working until this update.

On this thread now, thanks for linking me Timothy. I suppose I am in a similar boat. This will teach me to keep an update .kdb file ... I'm fairly certain this is due to a mono issue. If You need file comparisons to my Fedora installation. Please let me know.

The starting-up failures only seem to happen when a process in run directly from within a window manager session. E.g. tomboy consistenly will stall when I start it from the GNOME shell directly. However, when I open a terminal window and start it from there, it'll start up fine.

Might be related: Some people seeing this Mono thing also see a lot of non-mono processes zombifying with the latest Nvidia blob. Compare https://bbs.archlinux.org/viewtopic.php?pid=1359745

Is anyone also seeing quirks when running Firefox? When I start it from within the Gnome shell, the window will just vanish without trace. Running from a terminal works normally.

Don't know if it's related or not. On my machine after recent updates all mono apps are freezing. I can't even run a compiler, e.g.:

[nsf @ Test]$ dmcs -h
error CS2007: Unrecognized command-line option: `-h'

And the process never returns. Maybe a kernel incompatibility with mono runtime or something. Perhaps they've fixed it in git already. Will try installing mono-git for now.

Adding to the above, indeed as reported above strace ends with this, seems like a typical deadlock:

write(1, "error CS2007: Unrecognized comma"..., 52error CS2007: Unrecognized command-line option: `-h') = 52
write(1, "\n", 1
) = 1
sched_yield() = 0
tgkill(2227, 2228, SIGPWR) = 0
futex(0x97ea20, FUTEX_WAIT_PRIVATE, 0, NULL

Same thing on mono-git. Surprisingly enough it was able to build itself. Have no idea how.

Hm.. after -Syu it works now. And this time there were no critical packages, besides xorg. Maybe it's indeed related to some weird nvidia driver issues. But really hard to imagine how that happens.

I can't confirm this. I just upgraded everything to current state (2013-12-19) and still have these problems.

Yes, the bug appears again. All mono apps are hanging. Really sad one.

I've the same issue (with games from Steam like Rogue Legacy, FEZ and Jack the Lumber). Mono version 3.2.3, Gnome 3.10.2.1, NVidia 331.20. It appears randomly, sometimes helps to run application from terminal (but unfortunatelly not allways).

Guys, for now the only really working solution is to rollback to previous nvidia driver and linux kernel. I'm using linux-3.11.1 and nvidia-325.15, everything works smoothly. Yes, it is indeed a problem with nvidia driver. The other bug about firefox segfaults is the same problem. After rolling back both problems disappear.

@nsf As much as I appreciate your tip, I think this can not be the true and final solution for these issues. I hope this gets fixed ASAP, since it's really annoying for now.

I can no longer reproduce this issue using the just-released 331.38 driver. It appears to be fully resolved, as was indicated by an NVIDIA employee at https://devtalk.nvidia.com/default/topic/633706/l/r/2/#4066578

Fortunately, I can confirm what Thomas Hebb just posted, that the error seems to be gone on all my machines running the latest nVidia driver 331.38. For me this seems to be fixed by now and I wasn't able to reproduce the error anymore.

My issues with games on Steam are also gone after updating the NVidia driver. I'd also problem with freezing of Firefox. Now it runs well. So it was most likely connected.