Bug 5485 - GNOME 3.4.1-1.mga2 crash when startx
Summary: GNOME 3.4.1-1.mga2 crash when startx
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-04-19 08:18 CEST by Luan Pham
Modified: 2012-04-22 01:23 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Luan Pham 2012-04-19 08:18:21 CEST
Description of problem: Crash when begin startx and had go back to previous, since this was work well on Mageia-2-Beta2 


Version-Release number of selected component (if applicable):
3.4.1-1.mga2

How reproducible:
Happen every time.

Steps to Reproduce:
1.
2.
3.
Comment 1 Manuel Hiebel 2012-04-19 08:58:33 CEST
maybe a wrong update (http://pkgsubmit.mageia.org/), the gnome-shell was not rebuild (there is only gnome3.4.0 in the iso), can you update an try again ?

and maybe also *attach* your ~.xsession-errors.old

Keywords: (none) => NEEDINFO

Comment 2 Luan Pham 2012-04-19 09:46:11 CEST
When I try to upgrade from Mageia-2-beta2 to Mageia-2-beta3 it not even install anything, and it just went through user setting screen. On my i586 I upgrade from Mageia-1 to Mageia-2-beta3 thing went better.
Comment 3 Manuel Hiebel 2012-04-19 09:50:55 CEST
upgrade from the beta2 to the beta3 ? if you use the dvd this normal since 
cauldron = alpha1/alpha2/beta1/beta2 + updates = beta3

Source RPM: GNOME 3.4.1-1.mga2 => (none)
Severity: critical => major

Comment 4 Luan Pham 2012-04-20 19:13:09 CEST
After try couple thing I had learn this error: GNOME 3 fail to startx because of graphics issues rather then GNOME it self.  GNOME 3 was working great under Beta2 until upgrade to beta 3.
Comment 5 Luan Pham 2012-04-22 01:23:37 CEST
I finally solve this problem by add RADEON FIRMWARE from Nonfree depository.

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


Note You need to log in before you can comment on or make changes to this bug.