The stop & go hack worked for me for the time being.
media-libs/gegl-0.2.0 built as well afterwards.

I have this exact problem (or at least one looking just like it) on one box:

event devices are present (and responsive - I can check input over an ssh connection) but X still won't add devices though. No /etc/X11/xorg.conf to disturb the server. No /run directory, actually this thread is the first ...

I don't get it. Whatever happened to the choice factor? Even for mainline kernel development, we get to choose between CFQ and no-op, even if the latter is really not a viable alternative. There's ton's of stuff in the kernels marked "Experimental" with rolls of red tape around it.

What's wrong ...

Ok, this is completely bogus, but here is what a possible "solution" appears to be. The Ubuntu thread tipped me off to this.

evince apparently screws up the margins in the config file under ~/.gnome2/evince/print-settings .

I can get documents to print using US-Letter format, but this is hardly ...

Looks like this may be a more common phenomenon...

Debian http://forums.debian.net/viewtopic.php?f=10&t=7893
Solaris: http://opensolaris.org/jive/thread.jspa?threadID=50406&tstart=0 (4th post from the top).
Fedora: http://www.fedoraforum.org/forum/showthread.php?t=166417
Ubuntu: https://bugs ...

Hi all,

using evince to print a .pdf-form seems broken somehow. I am using CUPS 1.4.6 with a Brother MFC-7820N connected through the network.

Even if A4 paper is selected (and print preview is properly displayed as being A4) it appears that the actual print output is somehow "shifted" upwards ...

:P Ah, that figures... I suspected as much, but didn't dare to ask...

But, as Gnome-2.32.x is slowly creeping into the tree even though it is package.mask ed, maybe this could also find itself in the main tree?!

BTW: I've read somewhere that I should put GSETTINGS_BACKEND=gconf but no one ever ...

I've CUPS 1.4.4 installed and had a Document printed from OpenOffice 3.2.1 on my Brother MFC-7820N using the Brother supplied .ppd and an ipp-queue.

The printer is connected over a network.

However, The printout is plain wrong. But the sneaky part: It's not all wrong. Only all the capital "D"s are ...

Maybe gdm initializes ck correctly? It is the preferred way (in the GNOME mindset) to run GNOME after all...

Well, quite obviously InputDevice and InputClass are not
equivalent, so the construct from your previous post can't work.
Which previous post? Do you mean the one in which I'm saying the exact same thing that you've now "obviously" pointed out? :roll: To quote: There is a difference between ...

As I noted few times already, 'Option "XkbRules" "xorg"' is both
invalid and redundant for evdev driver. Yes, well... If I run into trouble with my keyboard , I will keep that in mind. As for now, my trouble concerns the mouse setup, for which I am not only using the MX900 that came with the ...

Ho-hum... still no luck. I tried specifically limiting the Buttons, but all in vain. Xorg insist on not just using the info provided in xorg.conf, but also the fallback-stuff in the xorg.conf.d. As if there was no precedence whatsoever or if there is a precedence it's either misleadingly referred to ...

Ah, I see now what you meant...

Trouble is, my Logitech USB Receiver is supposed to (and does) work both as a mouse and a keyboard. I guess it should be possible to develop an input class that specifically adresses this, but so far I haven't found it.

I'll keep doctoring and will mark this solved ...

There is a difference between Section "InputDevice" and Section "InputClass". They are not equivalent, as per the man page...

The section names are:
(...)
InputDevice Input device description
InputClass Input class description
(...)
The following obsolete section names are still recognised for ...

Ok, I've looked into the man page and copied some of the stuff from /etc/X11/xorg.conf.d/05-keyboard.conf and /etc/X11/xorg.conf.d/10-evdev.conf over to xorg.conf ... It now looks like this:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "german keyboard ...

Hi Neddy, thanks for helping.

My xorg.conf is a dried old remnant. :) I deliberately have eliminated hal from my make.conf, as it is being merged into udev. It is still installed - and running currently - until it can be safely assumed that everything that used it was turned to udev. Call it ...

Evdev is getting on my nerves. It's working perfectly with my keyboard (a Logitech diNovo Bluetooth) even though I haven't yet managed to get bt to work automagically after booting, but it giving me heartburn with the mouse. I have the cordless MX900 that came with the keyboard (3 axes, 8 buttons ...

rtomek wrote:Yeah, and I hear they also had an update in the last 2 1/2 years, which this thread hasn't had

...and which I totally missed...

So which music manager can be set up to sort music by parsing filenames with a regexp? (I have real long filenames, like "Rammstein - Sehnsucht - 03 - Tier.mp3", that is "Artist - Album - track - Title"...) It should be easy.
I think someone further up already mentioned quodlibet. It claims to ...

Ho-hum... I'm currently back to using Gnome. Less candy, but MUCH more responsive now that hal is out of the way...

Even with ecomorph, e17 was pretty, but suboptimal from a usability pov (I'm on a fairly dated machine here).

P.S.: And yes, e_modules-drawer always failing to compile is a PITA too ...

Just busy ditching hal from my system because of the switch to xorg-server 1.8... he can feel it already... his mind is going...

but elementary with the dbus USE-flag depends on hal, even when e_dbus is compiled without it. Meh... Any chance this'll be fixable?

If it wasn't installed, something is definitely wrong, as you have the acpi-USE-flag set, as apparent from your emerge --info.

You have a hybrid laptop graphics card, haven't you? The VGA-arbiter line in Xorg.0.log suggests it, also you have two graphics adapters listed in your lspci.

As this is a ...

Maybe this is off-the-wall but the xorg.logs pointed me to a couple of questions:

1.) What version of acpid do you have installed?
2.) Is it running after booting completes?
3.) Is it designated to start in the boot runlevel?

Try /etc/init.d/acpid status for the answer to 2.) Your second-to-last ...

I think one is supposed to use evdev under xorg-1.8.

I can't currently install it, because of a conflict with nvidia-drivers... Plus, evdev never worked for me (or - more probably - I'm too dense to set it up correctly)...