Bug 13323

Summary:	Starting Firefox crashes X back to the login dialog
Product:	Mageia	Reporter:	John Hardie <acecoder>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	critical
Priority:	Normal
Version:	4
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	firefox-24.5.0-1.mga4.src.rpm	CVE:
Status comment:

Description John Hardie 2014-05-05 17:59:41 CEST

Description of problem: I just did a system update and one of the updates it contained was Firefox, so I was keen to see its new features, but when I started Firefox X crashed and I was back at the login dialog.  I don't think the bug is Firefox itself though, because starting some other applications (Qt Creator, Amarok) does the same thing. I also noticed that I was getting a new window border effect when mousing across taskbar icons, so I deactivated desktop effects but that didn't help.  I suspect one of the other updates is at fault, not Firefox.  I'm not sure where to find the appropriate log files to see exactly what's happening, but if you can tell me where to look I can give you more info.  I am using XRender-Native for desktop effects because OpenGL crashes X on my system.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Run the group of updates which contained this Firefox update.
2.Start Firefox (or Amarok, or Qt Creator)
3.


Reproducible: 

Steps to Reproduce:

Comment 1 Manuel Hiebel 2014-05-08 20:21:21 CEST

anything in xorg logs /var/log/Xorg.*

or sessions one ~/.xsession-errors* ?

Version: 1 => 4

Comment 2 John Hardie 2014-05-13 18:01:28 CEST

Thanks Manuel.  I probably should have mentioned that I'm running a virtual machine.  I've got several VM's running Linux (Mageia 3, Mageia 4, Mint 14 KDE, Ubuntu) and Windows (XP, 8.1 Pro).  These are all running on Parallels Desktop 9 for Mac on a MacBook Air running OS X 10.9.2 Mavericks.

As expected, the actual cause of the problem was something else, namely the mesa graphics library, which had been updated from 10.0.3 to 10.0.5.  I was able to narrow it down by restoring a backed up VM, and then using snapshots of the VM as I updated just a few updates at a time.  Then, going back to the VM which had the problem, I increased its video memory from 32MB to 256MB and it came good.  Surprisingly though, when I put it back to 32MB it remained ok.  In any case I was able to complete all the current updates, including kernel 3.12.18-1, and did several restarts and logins with no video crashes.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME