LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices



Reply
 
Search this Thread
Old 01-03-2011, 05:51 PM   #1
Tijn
LQ Newbie
 
Registered: Aug 2006
Distribution: Various versions of Redhat, CentOS, Fedora, Debian, Mint
Posts: 13

Rep: Reputation: 0
Fedora 14 - no gnome-panel visible when gnome started


1-2 weeks ago I've installed Fedora 14 on 2 machines. One (64bit) is OK with respect to gnome-panel, but on the second one (32bit) I have a strange problem.
KDE is OK, but when I start Gnome, I see no gnome panel.
Code:
ps -ea | grep gnome-panel
displays that it is running.
When I kill it, it does re-spawn.
But no gnome panel bar is visible (neither the top menu, nor the bottom taskbar). Alt+F2 pops up the "Run application dialogue"

Both machines are updated by "yum update".
Gnome panel package version is gnome-panel-2.32.0.2-2.fc14.i686.

On the affected machine, I have moved my /home data from simple subdir on / partition to a dedicated partition (/home is a logical volume on to of RAID1):
Code:
mount | grep home
/dev/mapper/vg_md2-lv_home on /home type ext3 (rw)
gvfs-fuse-daemon on /home/martin/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=username)
Similar setup I have on the "working" 64bit machine (though at the moment the RAID1 is degraded to just one physical disk there... but that should not be the issue)

At the time of moving the /home, there was just one user account. Later, after moving /home, I've created 2 more and all of them have the same problem with gnome.

Could this be a selinux + ~/.gvfs issue?
selinux context for .gvfs is same as at the machine which has no issues:
Code:
ls -aZ ~ | grep .gvfs
dr-x------. username username system_u:object_r:fusefs_t:s0    .gvfs
Any other suggestions?
 
Old 01-04-2011, 12:47 AM   #2
smoker
Senior Member
 
Registered: Oct 2004
Distribution: Fedora Core 4, 12, 13, 14, 15, 17
Posts: 2,279

Rep: Reputation: 248Reputation: 248Reputation: 248
Whenever I've had that issue, I log out then back in and it usually appears. It is more graphics related than SELinux I think. The panel doesn't appear until everything on it is ready for use, so there may be an issue with networking or bluetooth startup that is slowing the panels appearance.
 
Old 01-05-2011, 01:39 AM   #3
networking.dept
Member
 
Registered: Dec 2010
Location: Ahmedabad
Distribution: Red Hat Enterprise Linux and Fedora
Posts: 44

Rep: Reputation: 8
@Tijn, What happens when you kill and start gnome panel again ?

Execute by following way and let me know its working or not.

#killall gnome-panel
#gnome-panel &
 
Old 01-05-2011, 08:31 AM   #4
Tijn
LQ Newbie
 
Registered: Aug 2006
Distribution: Various versions of Redhat, CentOS, Fedora, Debian, Mint
Posts: 13

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by networking.dept View Post
@Tijn, What happens when you kill and start gnome panel again ?

Execute by following way and let me know its working or not.

#killall gnome-panel
#gnome-panel &
I have tried this, mate - but it did not help.

Eventually I have identified (yestarday's late-nite investigation...) that it the origin of the problem is a bogus display auto-detection. For some reason (BIOS bug?) FC14 detects 2 monitors - LVDS1 + VGA1 (if using VGA-connected display) or LVDS1 + DVI1 (if using DVI-connected display)
This can be identified using following command:
Code:
$ xrandr -q
Like on a laptop with attached extra monitor - autoconfig sometimes did dual-screen configuration, with one of the monitors non-existing. The "missing" monitor was unfortunately Primary, LVDS1, so all what was visible was the secondary screen; the gnome-panel was on the primary, invisible one.
But the machine is not any laptop - but a desktop, with a single connected monitor ! (just being installed as a HTPC...)
The motherboard type is MSI 945GT Speedster-A4R, socket-based MicroATX board for use with mobile Intel CPUs (core/Yonnah and core2/Merom).
It worked well earlier with Fedora 9 - no such issues during more then 4 years.

I have figured this out when I had strange video resolution setup issues with xbmc, and later also gdm became confused - so the issues converged to one point.
In any case - KDE somehow managed it better then Gnome. Actually, I have diagnosed it by executing (in the crippled gnome session) Alt+F2 -> gnome-display-properties.

The final solution was to add the following line at the end of the gdm configuration file /etc/gdm/Init/Default
Code:
/usr/bin/xrandr --output LVDS1 --off

Last edited by Tijn; 01-05-2011 at 10:10 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Configuring the gnome panel to show only gnome apps? Mr. Asdf Linux - Software 1 09-29-2007 07:24 AM
update removes gnome-panel & gnome-core adamruss Debian 9 09-24-2007 12:11 AM
Gnome panel keeps crashing when starting gnome-session elluva Linux - Software 3 01-24-2006 05:26 PM
Gnome-panel, nautilus and gnome settings daemon Fail on Startup hitman_et Linux - General 0 04-01-2005 10:06 PM
Which Gnome and Xsession files shall I edit to get GNOME started satimis Debian 3 01-04-2004 05:44 AM


All times are GMT -5. The time now is 01:56 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration