Bug 5097

Summary:	GNOME3 losses icons after updates, "Oh no! Something has gone wrong."
Product:	Mageia	Reporter:	Scott Fulford <nextwavecs>
Component:	Release (media or process)	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	guillomovitch, olav, sysadmin-bugs, wilcal.int
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	.xsession-errors file

Description Scott Fulford 2012-03-25 21:24:47 CEST

Description of problem: After fresh instalation of M2B2 x64, install nvidia proprietary drivers, gnome3 looks great. 

http://i1079.photobucket.com/albums/w505/nextwave1980/Mageia%202%20beta%202%20x64%20GNOME3/IMG_0183.jpg

After completing updates, reboot and gnome3 logs in to a screen "Oh no! Something is wrong.

http://i1079.photobucket.com/albums/w505/nextwave1980/Mageia%202%20beta%202%20x64%20GNOME3/IMG_0185.jpg

Pressing Alt+F4 closes error message and brings up the gnome3 but missing icons.

http://i1079.photobucket.com/albums/w505/nextwave1980/Mageia%202%20beta%202%20x64%20GNOME3/IMG_0180.jpg

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

How reproducible: easily repeatable


Steps to Reproduce:
1.Install OS
2.Install nvidia drivers, reboot, update, and reboot
3.problem occurs, (twice tested)

Comment 1 Scott Fulford 2012-03-25 21:29:22 CEST

Noticed this, (after manually installing gnome-tweak-tool) http://i1079.photobucket.com/albums/w505/nextwave1980/Mageia%202%20beta%202%20x64%20GNOME3/IMG_0181.jpg

Shell theme missing.

Comment 2 Scott Fulford 2012-03-25 21:40:02 CEST

Created attachment 1848 [details]
.xsession-errors file

Comment 3 Scott Fulford 2012-03-26 01:35:55 CEST

upgraded libgnomekbd to 3.4.0 and "Oh no! Something has gone wrong." error has vanished.  Still no icons, when logged in.

Comment 4 Scott Fulford 2012-03-26 02:12:43 CEST

update... restarted and still have "oh no!" message..... :(

Olav Vitters 2012-03-26 09:32:04 CEST

Attachment 1848 mime type: application/octet-stream => text/plain

Comment 5 Olav Vitters 2012-03-26 09:35:13 CEST

Could you attach ~/.xsession-errors again with the latest libgnomekbd updates (3.4.0.1)?

In case something crashed, I'd like a stack trace.

Meaning: from a terminal do something like:
gdb /usr/lib64/gnome-settings-daemon
then gdb starts; it might suggest some debug packages; install them

within gdb do:
 r, <enter>

then when something crashes:
 bt, <enter>

attach what bt gives please.

CC: (none) => olav

Guillaume Rousse 2012-03-26 13:41:00 CEST

CC: (none) => guillomovitch

William Kenney 2012-03-26 19:13:23 CEST

CC: (none) => wilcal.int

Comment 6 Scott Fulford 2012-03-28 02:27:21 CEST

I'm sorry for taking so long to get back to you. I went and ran an update and libgnomekbd (3.4.0.2) installed. Rebooted, and no error messages logs in.. icons fine.  I dont know but I think this solved it. I can reinstall a fresh copy and reproduce this to double check that its reproducible. Sorry I can't be much help.. but this has been awesome in a development sense. I leave for 2 or 3 days and come back, run updates, and everything works.  This is great work !  If there is anything you'd still like for me to submit, please don't hesitate to ask.

Comment 7 Olav Vitters 2012-03-28 10:16:14 CEST

If latest updates fixed it, then it was the same cause as another bug.

Therefore marking as duplicate. If it persists again (in coming week or so), please reopen (after a week probably new problem, so then just file a new bug).

*** This bug has been marked as a duplicate of bug 5098 ***

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