Gentoo Forums

SlashBeast wrote:The bugzilla that I've linked does have fix for this issue.

....i said that 4 days ago at the drop of a hat....great job! how much time did you guys waste because of your contagious "i'm better than you" attitude?

nvidia-drivers are coded to not compile against an incompatible xorg-server so the end user is not likely to ever experience it

That is more of a joke than anything else, as how are you suppose to know some version of xorg in the future is incompatible until it happens? The most the devs ...

worked for me....

ct85711,

nvidia-drivers are coded to not compile against an incompatible xorg-server so the end user is not likely to ever experience it, so in a way I agree with you, but I'd bet the kernel/driver interface is more stable overall, too lazy to research further so i'll digress though.

i never use package.provided. maybe im doing it wrong? try the edit.

oh i overlooked that dpeendency. add media-libs/asio-sdk to package.provided

/etc/portage/package.provided EDIT: heres the link, just wget that in your distfiles, cuz we may fail elsewhere with the above.
http://www.steinberg.net/sdk_downloads/asiosdk2.3.zip

age of card matters for which drivers to use, but i cannot remember a major break in years assuming you're relatively up to date. maybe i'm wrong. it's always sort of cat and mouse though because of linus' rage for nvidia, but nvidia's driver people still keep up. minor breakage is frequent, major ...

it just needs asio.h from the non-free package, I assume you have it anyways? This is where it looks for it in ebuild.

there is no real hard requirement. the ABI of xorg-server is what changes relatively frequently. if you have a problem, its probably config related or a one off.

you want it to be used and from what you posted above it looked like it was not being used. try to use this overlay to install it. portage is more predictable than your own config.
https://github.com/internethering/hering-overlay

looks like a recompile with -fPIC error to me

I was so sick of 3.5s with bad sectors by that point I, never had the pleasure. now I think at 252 kB/s, I would end up breaking it by tossing it across the room.

first thing to check when gcc simple test fails is your compiler options

try just this to test: i'm wondering if maybe the wrapper is choking on the feature modifier.

Hi,

I have the same problem but my screen turns white.
The conflict seems to be with the compositor of XFCE. When I disable display compositing it starts without problems.
I think there was a bug about this but I couldn't find it. I'm sorry.

here's the fix for your issue. maybe their's too ...

jaglover, someone probably needs to bug report xorg-server people, it's a different problem.
https://bugs.debian.org/cgi-bin/bugrepo ... bug=900717
https://bbs.archlinux.org/viewtopic.php?id=237587

since one is using intel and one is using nvidia. it is probably input related

try to remove keyboard and mouse from INPUT_DEVICES, you probably do not need them. that is the common denominator from what i see too. evdev+synaptics or evdev alone or libinput alone

Xorg.0.log and emerge --info would help. I have no issues.

xlocale.h has been renamed/removed upstream, check and see if it's orphaned. if so, delete it.

I would, not promising it'll fix your issue, but it does in general work better than consolekit and it's maintained by a gentoo user.

khayyam,

openrc+consolekit+shutdown issues started cropping up last year sometime, I don't know the cause or even all the ways the kits intertwine with shutdown, but most distros have swapped consolekit for elogind in the past year, so it was more of a blanket statement that users will generally ...

ebuilds are hashed with blake2 in the tree. blake2 hashing was added directly to python in 3.6. So if portage is only built with python3.6 target, you probably don't need pyblake anymore.

My laptop, running kernel 4.17, shows similar behaviour. Look at openrc's log (/var/log/rc.log by default, if you enable logging). Mine has entries for shutdown that look OK.

Speaking from profound ignorance, I wonder if the issue lies in consolekit not switching to tty0 or something. I consider ...

sorry neddy and hu, didn't see the thread split until after.

Steven,

as far as networking and virtualbox goes, If i remember correctly, you want to goto network options of your VM and change "attached to" to bridged instead of NAT. this will allow more direct access without doing anything else. dhcp should just work at this point.

it would seem that the whitelist is now active .

if all goes as "planned", the list will wither and die.

but hopefully not before the war between council?+comrel and the foundation . :lol:

and more shitstorms about censorship

fwiw, its been 9 months since I was muted in #gentoo with no end in ...