Hey, I'm running Gentoo Linux, with baselayout-2, which is notably faster than baselayout-1. However, it always hangs at "starting gpm." I've tried re-emerging gpm to no avail. A little less than half a second after the "starting gpm" message starts, gpm is active and I can move my mouse around the screen. However, the screen still says "starting gpm" and after a while, times out, saying that gpm failed to start. This also makes it so that, if it's in the default runlevel, that local doesn't start, and I am unable to login unless I skip gpm service from starting. If I start it later, it has the same symptom: it just sits there at starting gpm, even after the gpm process has started. Killing the initscript gives an error, but gpm is still going. It's odd.
This bug is not a blocker at all. gpm is not required for the system to operate perfectly. As a server, data storage, day-to-day use, it's not required. And by they way, I'm not able to reproduce your bug.
you forgot `emerge --info`; please post it
Well, I had considered it a blocker because it stopped local from starting, which stopped my computer from starting, but I see your point. You can't reproduce it, you say? Huh.
Created attachment 122670 [details] emerge --info It wouldn't fit in the comment box, so here's my emerge --info.
I cannot reproduce this. Please attach your /etc/conf.d/gpm
Created attachment 123185 [details] GPM configuration Here it is. By the way, I get the same behavior even after emerge -eD --with-bdeps=y world, so it's probably something on my end. But I don't know what...
I had the same problem with baselayout-1 on my laptop and it's still present in baselayout-2.
Created attachment 124102 [details, diff] Close stdin/out/err when daemonising This patch should fix it - please test and report back.
Works like a charm!
please dont close bugs when the fix isnt in the tree
Sorry! I didn't know, my bad. Thanks for the patch Roy, by the way.
Fixed now.
