Fedora :: Gnome Desktop Does Not Start After Shutdown On 14?
Aug 31, 2011
After power off the Gnome desktop environment does not start on my machine. It never gets past the splash screen with Fedora logo.The OS boots, and I can ssh and even run graphical applications, such as Thunderbird, remotely. No errors are reported in /var/log/Xorg.0.log. There are errors reported in .xsession-errors (attached) but I do not now how to recover from them
Our office moved yesterday. I shut down the computer cleanly and physically moved it to the new location. On startup, the wallpaper shows on both monitors, and the login screen. But, when I log in, I get failed to load session "gnome"
I am using Fedora Core 15. The only hardware that changed is I swapped out my cordless usb mouse for a corded one because I left the dongle at home. How I can I troubleshoot the problem and get my computer up and running again?
I would like to setup fedora for fullscreen, touchscreen, noexit application. So whenever you'll boot or restart the application will automatically starts. I thing there are these step required:
1. autologin 2. start fvwm after login instead of default DM - gnome 3. run application
how to autologin in fedora but it still shows that fedora gui login screen for 10 seconds and then it logs in. My problem that I dont know how to start fvwm and configure it to empty desktop (no toolbars no nothing) instead of gnome.
When # shutdown +5 is run all the terminals (including pseudo terminals) are sent broadcast messages saying system is about to go down. Is it possible for user to receive this in the form of OSD or system tray notification so that he will be informed even if he is not running any terminal emulator or running it but minimized it and working with something else?
I've recently updated to Ubuntu 10.10. At first I had no problems, but after the third time I logged in, my desktop background appeared (and nothing else) but quickly flashed to a black screen with some error messages (too fast for me to see) and I got sent to the login screen. After trying some more times I got the same problem with some small differences(sometimes my desktop icons showed up, other times it took a couple of minutes before I got kicked out).
I tried running startx from the terminal but got one of these two error messages: Server already running or could not find any listening ports. If I run "sudo startx -- :1" to switch the port I login fine, but as the root user. Gnome works perfectly here and when I login in gnome-failsafe. This leads to believe it has something to do with my user configuration. I've restarted xorg server, installed gnome-main-menu and made sure if got the current gnome package.
I am new to Linux and wow, it did not take me long to run into a huge snag. I am running Suse Linux Enterprise 10 on a laptop and by some strange reason the computer froze from overheating and I was forced to shutdown improperly. Once I restarted it booted right to the command prompt when it usually instead boots to the default user. I managed to get gnome running using the "startx gnome" command. But when gnome loads, none of my normal extentions load like my wireless driver, the sound driver, etc. how to restore gnome to automatically load the default user on start up or fix any other damage I might have done? lol
I ve been using 64 bit ubuntu maverick since its initial release and today i tun on my laptop and the gnome desktop does not work or it could be the x server i dont know all i know is when i turn my computer on all goes well till the point where you see your wallpaper and the desktop menus well i can only see a wallpaper and my mouse cursor nothing else works and I cant click on aything and ive also tried some keyboard shortcuts they too do not work help me guys please how do i know whats wrong??
I use ubuntu 10.04 in VirtualBox (upgrated from 09.10), host os is Win7.
3-4 days ago update of ubuntu required restart of Ubuntu (linux kernel was updated).
After 3 days (i.e. yesterday) I restarted the system. I found that flashlib in Chrome became to work unstable, some artefact appeared, and only scrolling down-up in browser allowed to update view of screen. I run update manager. It showed ~88Mb of updates for last 3 days.
After download of updates, apply changes was failed! I faced this first time (!). I remember message like "can not synchronize file /usr/share/..." or something like that.
I restarted ubuntu again. Now I could not login. System hangs after login. No Gnome menu appears etc.
I tried to fix issue using dpkg. I found that some lib (ure) related to OpenOffice was not assigned (version XXX required, but bersion XXXY found). dpkg offered to solve this by some combination. I did so. Then I run dpkg update, and no errors appeared.
Also I updated VirtualBox to version 3.2.4, updated VirualBox Additions via console terminal in ubuntu.
But still I can't fix problem with gdm/gnome.
dpkg-reconfigure gnome-*** did not help for me.
I tried to check logs, but I have not found something "interesting".
I looked around for threads addressing this issue and some have come close to answering it, but I have yet to see a definitive yes or no. Anyway - Here's my issue:
Background: I can SSH into my home computer (Ubuntu 9.04 running Gnome) from work (Win XP Pro) using RealVNC via Putty tunnels. This has been working flawlessly for me for awhile now. I was messing around in the terminal window and accidentally rebooted the linux box (home computer) while I was at work. No big deal I thought. So I re-start the Putty connection, and it is back up in no time. Then I try to start the VNC connection, and no go, connection refused. I remember seeing that in order for the VNC connection to work, I had to be logged into the Gnome desktop already on the Ubuntu box.
Question: Is it possible to log in and start up a Gnome desktop session from the terminal command line in Putty so I can get the VNC connection back?
I've just installed F15 KDE Edition, and as the title tells, I need to keep pressing F2 and/or Enter to make the system go through the boot up process, otherwise it freezes as long as i keep it without my interference !! and then it takes relatively long time to start the GUI, and when I switch to the console (using ALT + CTRL + F3 for example) and try to write the login or the password, there seem to be some 'bouncing' effect, that if I'm to write the login 'root', I get something like 'rrooott' ... however, this doesn't happen in the GUI .....
I have a multiboot system, with Windows7 and Linux Mint (based on ubuntu 10.4) installed along side. While Windows7 doesn't have any problem with my hardware, Linux mint has also some issues that cause the performance of media players to degrade (sound and video tearing) and cause repeated freezes to some applications (a game actually, 'wesnoth') until I press a key or move the mouse.
I have AMD Athlon 7750 dual core 2.7 GHz system, with 3GB DDR2 800 Ram, and embedded ATI Radeon HD 3200 with about 512 shared memory.
one more thing, when I booted off the live image to run the install program, I booted into the video failsafe mode (not sure of the exact name, but I think you got it, no mode setting) and passed the option 'noapic', so I suppose this options are still passed whenever I boot mysystem, as I get the text version of the progress bar during startup, rather then the graphical fedora logo ( i.e no mode setting) ..
I have a server with Fedora 13 installed and vnc-ltsp-config set up for remote desktop access. Seems to be working fine for everything I need, and with KDM instead of GDM, I'm even able to log in as root to Gnome.Which leads me to the problem. Logging in as root and I get the shutdown menu options in the Gnome "start menu". Log in as anyone else, no shutdown options. Logging in to the console as any user and I get the shutdown options.I want to enable the shutdown options for all users remotely. How can I go about doing this?
And I know someone will say "that's a bad idea". Don't worry, this is a small server at my mom's house I set up for her to run some web proxy filtering with Dan's Guardian and Privoxy. Since I'm typically logging in remotely from home using VNC of some flavor, I'd rather be able to reboot or shutdown through the menu (just more "natural" to me). I know I can shut down through the command line, but that's just too much work.
I'm running Fedora 15 with Gnome 3. I installed Gnome-Do using 'yum install gnome-do'. I opened it from the Terminal by typing 'gnome-do' but I keep getting an error message that says
Could not load desktop item: libgnome-desktop-2.so.17
Gnome-Do opens but it doesn't display any application I search for and when I try opening the Gnome-Do preferences, it quits.
I installed gnome-desktop-2.32.0-8.fc16.i686.rpm from here: [url] and then installed Gnome-Do. Everything works fine now.
I just installed Fedora 15 with the gnome desktop which looks like the android system for mobile phones, I installed wine which put the icons on my desktop but whenever I install a windows app it doesn't put an icon on my desktop for that particular application. How would I add an icon for those window apps so I can lunch them from the desktop, I don't know if you call that the desktop or just the program luncher either way how do I put an icon there so I can run those windows apps from there?
I noticed that in Fedora 15 Beta when you choose a minimal install then add ONLY the defaults of the "GNOME Desktop" package, you will get this error: gnome-desktop3-3.0.1-2.fc15.x86_64 has a required package:
system-backgrounds-gnome
When I look for gnome-desktop3-3.0.1-2.fc15.x86_64 it is not on any installation menu list. I prefer gnome, but installed KDE and that worked. Any ideas of getting gnome to work?
i want make an ad hoc host in Gnome 3. I set everything in Network Connections, but I don't know how to start it. In Gnome2 it was enough to click on icon of NetworkManager and i saw it there. But now, I'm lost.
The upgrade from 11->12 went very smoothly for me on multiple servers except for one seemingly small item that had me tearing my hair out for a few hours. Three of my machines are MythTV frontends, which rarely do anything else. As such, I have them fairly stripped down package-wise and run MythTV on GNOME with xorg-x11-xinit-session to kick it off via an .xsession script. This scheme has worked flawlessly for years across many versions of Fedora until last week when MythTV mysteriously would not start and the computer would just get stuck in an automatic login loop. I discovered that I could start MythTV after I logged into the GNOME desktop and through some testing and log inspection came to realize that it was PulseAudio that was not starting automatically. I also discovered that I could just SSH in while it was in this loop and issue 'pulseaudio -D' and the next automatic login attempt would start MythTV properly.
As a quick hack, I just tossed 'pulseaudio -D;sleep 3' into my .xsession script and it seems to be working for now. I am interested to know how it used to start up without logging into the desktop before the upgrade. Could this possibly be related to udev or dbus? I have practically no knowledge of those, but do see config files for both in the pulseaudio package.
gnome-mplayer --fullscreen file.avi opens file in the window, manually I can switch it to fullscreen but I need to start in fullscreen from command linemplayer -f file.avi opens in fullscreen from the beginning but if to play a list it shows desktop between files how to fix the problem with gnome-mplayer?
When I boot my Fedora 15 installation it shows me the blue screen with progress indicator, however I do not reach the login screen.Instead I see the textual shell where the last item is:Started Display Manager.It looks like my monitors are not detected anymore. I have been working with them though (this appeared after a restart). I am not sure how I determined it but I read in some log that no display was detected. Nothing changed to the hardware set up however.I see some suggestions to run system-config-display as root.However this command can not be found nor can it be found when I run yum install system-config-display.
Does anyone know a secure method for starting a service after a user logs in to the desktop environment? There are a couple of issues that I'm trying to work around / troubleshoot and this would assist with doing that.
I'm running Fedora 11, not sure if that matters for this question.
is there a way to bind shortcut, that would open the browser (this one exists in gnome) if it was not opened. But once the browser is running it just shows/restores opened window?
I upgraded Sunday evening from FC14 to FC15 using the yum preupgrade method. Services such as httpd, vsftpd, sshd, named and even the VNC server are all running. I can connect via VNC client and get a downgraded gnome desktop, but from the console, I cannot start X or gnome desktop.I have searched many threads over the last day+ and found many references to problems with nVidia drivers - and I have a nVidia adapter. but I am not sure what is next to do and need a lead.
I am having some problems installing Fedora 15 64-bit. I use the install DVD. I have an AMD Phenom and a NVidia 8600GTS. When I install using the normal method, my screen freezes somewhere in the settings screen for choosing the computer name. If I use the basic video driver for installing I have no problem. However after everything is installed, and Fedora starts, Gnome says that it failed to start and some features are not available.
I found some information at [URL] that I tried. However after installing kmod-nvidia and rebooting I no longer see any graphical display. A lot of text is on the screen without any error, but no x-windows appears. What can I do to install Fedora correctly and have a good working system? Is the 32-bit version easier to get it working? How can you recover from a system that does not start? What I could do to recover from it.
Recently I installed vncserver (tigervnc) on my desktop. Ever since my computer refuses to shutdown normally. At shutdown the following message pops up: Quote: System policy prevents stopping the system when other users are logged in Then I have to enter the root password to shutdown. If I stop vncserver before, the computer shuts down normally.
I created a separate /home partition to share between F10 and F11. And, of course, the gnome settings conflict. I really don't need to go back to F10 and when I install F12 over it I will omit including the separate /home directory during the install set up and that will force F12 to create the /home Dir on the same file system. So, to clear up gnome settings for now, is the only way mean deleting the .gconf, .gnome* directories? This was recommended in another post back a few years ago.