Javier Adrián Ortiz de la Tabla [adriandelatabla@gmail.com] wrote:

...

...

And with the new xorg-server the behavior I'm seing is that if I try to maximize/minimize a window, fluxbox freezes, but if I do top, I don't see any process eating resources, neither memory, neither cpu...

Another weird behavior, is that fluxbox keys are dead.  I configured for example:

Yes, I've experienced the same problem, but I have hal enabled. After upgrading with 'pacman -Syu', fluxbox started to freeze with no aparent reason. I can't switch between desktiops (Ctrl-Fx), can't click to activate a window, etc.

-- Javier Adrián Ortiz de la Tabla

The last six entries of my /var/log/Xorg.0.log are: config/hal: New Input Device Request failed (8). There are six of those. Hal is running here also. Ctrl-Alt-Fx works here. T.

On 3/7/10, Thaddeus Nielsen <thaddeusn@gmail.com> wrote:

Javier Vasquez [j.e.vasquez.v@gmail.com] wrote:

...

Hi,

Today's pacman -Syu installed new xorg-server package:

% pacman -Qs xorg-server local/xorg-server 1.7.5.901-1 (xorg) X.Org X servers

I have xorg.conf configured without hal support:

Section "ServerFlags" Option "AutoAddDevices" "False" Option "AllowEmptyInput" "False" EndSection

I also have fluxbox installed:

% pacman -Qs fluxbox local/fluxbox 1.1.1-1 A lightweight and highly-configurable window manager

And with the new xorg-server the behavior I'm seing is that if I try to maximize/minimize a window, fluxbox freezes, but if I do top, I don't see any process eating resources, neither memory, neither cpu...

Another weird behavior, is that fluxbox keys are dead. I configured for example:

# alt-left / alt-right Mod1 Right :NextWorkspace Mod1 Left :PrevWorkspace

And they don't work. Well, if I try them like between the 1st 2 seconds, they actually work, after 2 seconds, they don't do a thing...

I don't think this is a video card issue, since I have the same issue with a nvidia video card, and an ati video card:

Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "Quadro FX 570M"

...

Driver "radeon" VendorName "ATI Technologies Inc" BoardName "Radeon RV250 [Mobility FireGL 9000]"

Is this a bug? I don't want to use hal, but perhaps it's inevitable now as opposed as before, when we could still not depend upon it... So I'm not sure if the only way to make Xorg work now is through hal, or if this is just a temporal bug to be fixed...

Please let me know.

Thanks,

-- Javier.

I was able to "downgrade" back to xorg-server-1.7.5-1 and things seem to be working OK for now.

T.

Downgrading actually works as suggested. There's a forum already with dicsussion about this: http://bbs.archlinux.org/viewtopic.php?id=92679 And a bug already filed as a result: http://bugs.archlinux.org/task/18598 I'll have to keep an eye on it, to see how it progress, :-) Thanks, -- Javier.

On 3/9/10, Guus Snijders <gsnijders@gmail.com> wrote:

On 07-03-10 21:57, Javier Vasquez wrote:

...

Hi,

Today's pacman -Syu installed new xorg-server package:

% pacman -Qs xorg-server local/xorg-server 1.7.5.901-1 (xorg) X.Org X servers

For the record, this problem is fixed in 1.7.5.901-2. Bugreport is here: http://bugs.archlinux.org/task/18598

Just check pacman to see if it is available on your local mirror.

HTH.

mvg, Guus

And the patch was reverted on Xorg as well (it seems): http://cgit.freedesktop.org/xorg/xserver/commit/?id=2086e4920a16248aa1501142... However the issue is still under investigation. -- Javier.