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

Re: X crashes at Firefox runtime




Le 24/08/2017 à 00:05, Samuel Thibault a écrit :
> 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

http://paste.debian.net/982794

>> [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.

ok. Probably interesting to determine the package first, as otherwise
they stay quite (at least Debian maintainers, upstream is somewhat
different).

regards

> Samuel
> 
> 

-- 
Logo Hypra 	JEAN-PHILIPPE MENGUAL
DIRECTEUR TECHNIQUE ET QUALITÉ
102, rue des poissonniers, 75018, Paris
Tel : +331 84 73 06 61 <tel:+33184730661> Mob : +336 76 34 93 37
<tel:+33676349337>
jpmengual@hypra.fr <mailto:jpmengual@hypra.fr>
www.hypra.fr <http://www.hypra.fr/>
Facebook Hypra <https://www.facebook.com/hyprasoftware/> Twitter Hypra
<https://twitter.com/Hypra_> Linkedin Jean-Philippe
<https://fr.linkedin.com/in/jean-philippe-mengual-800133135>



Reply to: