Bug 9100 - On a fresh installation gnome-panel gets a load error and has to be removed
Summary: On a fresh installation gnome-panel gets a load error and has to be removed
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-18 10:52 CET by Kristoffer Grundström
Modified: 2013-09-09 19:50 CEST (History)
0 users

See Also:
Source RPM: gnome-panel
CVE:
Status comment:

Attachments
Here's what it looks like (620.36 KB, image/png)
2013-02-18 10:53 CET, Kristoffer Grundström 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Kristoffer Grundström 2013-02-18 10:52:08 CET 
Description of problem: I just installed Mageia 2 on my x86_64 Desktop using the 3.4.24-desktop-3.mga2 kernel and as I logged into Gnome, the panel had an error about notification area & I was asked to either leave it or remove it. Now it looks like in the attachment.

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

How reproducible: I've been able to reproduce this twice.

Steps to Reproduce:
1. Download the boot-nonfree.iso for x86_64
2. Burn it to a USB-stick.
3. Start installation.
4. Choose both Gnome and KDE.
5. Boot into Gnome Classical.
6. Notification area seems to crash & asks you if you want to remove or keep it.
Comment 1 Kristoffer Grundström 2013-02-18 10:53:06 CET 
Created attachment 3526 [details]
Here's what it looks like
Comment 2 Kristoffer Grundström 2013-02-18 11:03:31 CET 
Using no Testing-medias & no 32-bit medias as well.

As I reinstalled notification-daemon and gnome-panel the problem is fixed so you should take a closer look at it.

I'm also forceing Fallback-mode for Gnome.
Comment 3 Manuel Hiebel 2013-02-21 14:45:27 CET 
can't reproduce

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 4 Manuel Hiebel 2013-09-09 19:50:39 CEST 
so closing

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.