[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: X crashes at Firefox runtime



Hello,

MENGUAL Jean-Philippe, on mer. 23 août 2017 23:40:18 +0200, wrote:
> X.log:

It'd be useful to have the full X.log

> [1917118.356]     compiled for 1.19.0, module version = 2.3.4
> [1917118.356]     Module class: X.Org Video Driver
> [1917118.356]     ABI class: X.Org Video Driver, version 23.0
> [1917118.356] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [1917118.356] (II) FBDEV: driver for framebuffer: fbdev
> [1917118.356] (II) VESA: driver for VESA chipsets: vesa
> [1917118.357] (WW) Falling back to old probe method for modesetting
> [1917118.357] (II) modeset(1): using default device
> [1917118.357] (II) Loading sub module "fbdevhw"
> [1917118.357] (II) LoadModule: "fbdevhw"
> [1917118.357] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
> [1917118.357] (II) Module fbdevhw: vendor="X.Org Foundation"
> [1917118.357]     compiled for 1.19.3, module version = 0.0.2
> [1917118.357]     ABI class: X.Org Video Driver, version 23.0
> [1917118.357] (**) FBDEV(2): claimed PCI slot 0@0:2:0
> [1917118.357] (II) FBDEV(2): using default device
> [1917118.357] (WW) Falling back to old probe method for vesa
> [1917118.357] (EE) Screen 0 deleted because of no matching config section.
> [1917118.357] (II) UnloadModule: "modesetting"
> [1917118.357] (EE)
> Fatal server error:
> [1917118.357] (EE) Cannot run in framebuffer mode. Please specify busIDs       
> for all framebuffer devices
> [1917118.357] (EE)
> [1917118.357] (EE)
> Please consult the The X.Org Foundation support
>      at [36]http://wiki.x.org
>  for help.
> [1917118.357] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
> additional information.
> [1917118.357] (EE)
> [1917118.366] (EE) Server terminated with error (1). Closing log file.
> 
> 
> Any help is welcome: what package should I investigate? how could I get more
> debugging info?

This looks like an X server issue (or a driver), since it's not supposed
to crash, ever, whatever other programs' behavior.

It'll thus be more useful to discuss with Xorg people.

Samuel


Reply to: