Aaaaaaand...there we go, X got OOM'd. Plus nouveau is fucking up again.
Follow

@p i had that OOM problem with the xorg intel driver. the solution was to use kms or how it's called. can't really blame nouveau for nvidias fuckery ;)

the first own install i used was suse 9.0 iirc. everything worked as well or better than today. including printing i had set up using the graphical UI.

@bonifartius Oh, this was nouveau fucking up because X got OOM'd because Seamonkey's build scripts were running 16 C++ compilers and they were eating all the memory.

@p ah, ok, i read it like nouveau was misbehaving :)

for me it was X memory leaking because of the broken intel driver. it took days but in the end X had allocated all the memory and things got wonky. was really annoying and hard to debug as it took so long to happen.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.