Fedora :: Gnome 3 Freezes After F15 Upgrade
Jun 1, 2011I just upgraded from F14 to F15. My gnome3 freezes everytime I open an application. I am new to linux.
View 7 RepliesI just upgraded from F14 to F15. My gnome3 freezes everytime I open an application. I am new to linux.
View 7 RepliesFirefox 4 becomes completely unresponsive for about 5 seconds. It seems to be happening mostly but not exclusively when switching tabs. At first I thought the problem was flash related but I was wrong, it happens regardless of the pages contents. Also, the problem seems to be more frequent as more tabs are open.It's interesting that it happens only on my computer at work (Intel Q33) but not at home (NVidia GTX 570). Both computers run Fedora 15 with Gnome 3 (HW accelerated). I also tried starting in fallback mode but the problem remained.
View 9 Replies View RelatedI've read some past issues with this and was wondering if anyone else has issues with F12 / F13.
When I logout of gnome or kde on a fresh install of Fedora 13 the panels disapear but I never receive the log on window. I cannot switch to command either the screen is locked completely.
I havn't run updates or anything, the install is nearly out of box except for the installation of kde.. The issue existed before I installed kde, I was hoping it didn't have this issue lol. fat chance of that..
Anyone aware of any fix's? Or what the issue is?
who is having issues with lockups check their /var/log/messages for this
May 28 11:41:21 shayne dbus: [system] Activating via systemd: service
name='org.bluez' unit='dbus-org.bluez.service'
May 28 11:41:21 shayne dbus: [system] Activation via systemd failed for unit
'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such
file or directory. See system logs and 'systemctl status' for details.
May 28 11:41:21 shayne dbus: [system] Activating via systemd: service
name='org.bluez' unit='dbus-org.bluez.service'
[Code]...
Just installed Fedora 12 stable release without checking office/productivity, server, or developer "package options". Running Gnome.Used yum to get Amarok on here, and it freezes almost immediately every time I try to open it. The splash shows, a program shows up on the window-manager panel labeled "KDED Glob..." and the system freezes. Mouse, keyboard, all unresponsive. I had FC12 Beta on this exact system and Amarok worked fine. Noting that KDED Glob is probably part of KDE, and that I did not install KDE, I thought maybe Amarok depends on a KDE component that the repo did not pick up as a dependency. Tried to install as much of the mainstream KDE components as I could, with no change.
View 4 Replies View RelatedI had a computer running a NVIDA Quadro NVS 450 with 4 screens on Fedora 14 and it worked fine. I make a new install with Fedora 15 and I am now not able any more running more as one screen with Fedora 15. I am running now on run level 3 and when I configure the file /etc/X11/xorg.conf for one screen, Gnome starts correctly. When I change to two screens, and runs "startx", Gnome 3 starts and displays only the background picture without any manager. The file /var/log/Xorg.0.log shows no errors.
View 3 Replies View RelatedI just upgraded from F11 to F12. Everything seems to be nice except mouse. The mouse buttons (both left and right, except middle one) are accidently frozen for some times. It could happen when opening a new tab in Firefox, launching a program, opening a new windows. I cannot click anywhere but can use mouse wheel. I have to log off/ log in and it becomes normal. It does not happen so frequently (around 3-4 hours) but it is really annoying.
View 2 Replies View Relatedafter the upgrade to Constantine I have a strange behaviour with plasma. The whole desktop freezes when a plasma widget pops up - like opening the menu or plugging in a disk and the mount options are shown. The X server still runs fine (Mouse and Keyboard are still working). Afterwards everything works fine again, I can even use the widget. I also tried a fresh install, and with the noveau driver the problem wasn't there, only after I installed the nvidia driver the problem reappeared again. Desktop effects are diabled. When I try killing plasma-desktop and restarting it from the command line, the desktop also freezes for a short time again, and I get teh following output:
[Code]...
I couldn't find anything helpful in Xorg.0.log or dmesg/syslog. I used nvidia-settings to configure xorg. I have a nvidia 6600 GT. If you need more infos just ask.
I am running FC12 64bit on my desktop and the problem is that after I enter my credentials at graphicall login screen (Gnome) the computer hungs i cannot moove the mouse, CTRL+ALT+DEL won't work the Caps and Scroll lock on my keboard are blinking. Nothing responds. I am absolutelly cluless. Untill yesterday i was using FC12 i686 and never had this problem, but i got 4GB ram so in order to get those fully i installed the 64bit version. On clean install of the 64bit ver everything went fine, but i updated the system and followed theese instroctions [LINK]http://www.howtoforge.com/the-perfect-desktop-fedora-12-i686-gnome[/LINK] and that's all
View 13 Replies View RelatedI am running FC12 64bit on my desktop and the problem is that after I enter my credentials at graphicall login screen (Gnome) the computer hungs i cannot moove the mouse, CTRL+ALT+DEL won't work the Caps and Scroll lock on my keboard are blinking. Nothing responds. I am absolutelly cluless. Untill yesterday i was using FC12 i686 and never had this problem, but i got 4GB ram so in order to get those fully i installed the 64bit version. On clean install of the 64bit ver everything went fine, but i updated the system and followed theese instroctions [URL] and that's all.
Before i atempt to login i can ssh to the machine.
About a week ago I used preupgrade to make the transition F14 -> F15 on a x86_64 workstation.
The system has been fully updated ever since, but I'm still not able to login either with KDE or Gnome. With KDE, the login process freezes before completion, whereas with Gnome I get the "wallpaper" behaviour reported here: [URL]
Funny though, I can login in the KDE failsafe session.
I could find no other thread reporting this problem and am at a loss on how to start diagnosing the problem. If anyone out there has any suggestion, I'd welcome it...
what's the difference between a "regular" KDE session and the failsafe one? They both look & feel the same to me...
I have upgraded my Laptop from Fedora12 to Fedora 13 via DVD image (x64 version). After the upgrade, I tried to update via YUM every package that still needed upgrade (especially nvidia drivers), and I got
[Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-13-x86_64
So, I tried to delete and reimport the rpmfusion repos, but when I go to this page:
[URL]
and try to install the RPMs, it only allows me to open them with Archive Manager!
So I looked into GNOME menus and... damn, apparently I can't find Package manager anymore!
Where did it go? and more importantly, why can't I install RPMs anymore? Can anyone enlight me on what went wrong?
Being the fool that I am, I forgot the good old terminal. I have still to nail down in my brain that going by terminal always works better than GUI. Using RPM -Uvh I managed to re-import all repos whose GPG key wasn't signed, and so I finally can upgrade my packages.
Package Manager is missing from GNOME. I have a couple of packages that I installed outside from repositories (they are SongBird and PersonalBrain), and I want to upgrade one (SongBird) and delete the other (PersonalBrain) but since I am in no way an expert when it comes to use the Terminal, I don't know how to uninstall them both (and then reinstall an upgraded version of SongBird).
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.
View 1 Replies View RelatedI upgraded my Fedora 11 installation to Fedora 13. The upgrade was successful, but some of the gnome commands are giving strange error.
[saurav@xion] ~ $ gnome-appearance-properties
gnome-appearance-properties: symbol lookup error: /usr/lib64/libpangoft2-1.0.so.0: undefined symbol: g_utf8_skip
[saurav@xion] ~ $ gnome-keyboard-properties
gnome-keyboard-properties: symbol lookup error: /usr/lib64/libORBit-2.so.0: undefined symbol: g_ascii_table
All path etc., are set correct.
I upgraded Fedora 10 to Fedora 11 via preupgrade. And now system succesfully boot, but Gnome doesn't starts (i think). There is only black screen and I can only write there.
View 14 Replies View RelatedAfter the Upgrade of my Fedora Insatallation (FC 10 => 12) I have some problems with Gnome and the Login via console. The system actually boots fine and all kind of services like Postfix, IMAP, Samba, SSHD, Apache, etc. are avialable normally.
If I try however to work directly on the server I only see the completed Fedora progress icon and not as hoped for, the Login to Gnome. Also the attempt to change to a plain console with ALT-CTRL-F1 fails.
Since actually everything seems to work quite fine, I am somewhat helpless, according to should I look for, to get Gnome and the Console Login working again.
Today I've tried upgrade from F14 to F15 using preupgrade,after reboot,gnome3 can response nothing,but kde and fvwm is ok. how can i do to rescue gnome?
T7200,4G,nvidia go 7400, 2.6.38.6-27.fc15.x86_64
We are having a cluster with couple of disk servers, compute nodes and a head node. Disk server is nfs mounted on all the compute and head nodes.
The problem is that if any of the disk servers hangs, it freezes rest of the cluster too which is dangerous. Ideally, cluster should not care about the hanged server and run without any problem except files from that server is not visible.
Is there any way I could avoid the problem of freezing cluster because of one hanged server?
Against all advice in Centos docs, I built and installed several gnome packages in order to upgrade to the latest Gnumeric. Among them were: fontconfig, pango, gtk+, cairo, glib. goffice, pixman, tiff, and atk. Afterwards, I got missing fonts with some apps, but the biggest problem is interference with my Vmware Workstation GUIs. Yesterday I removed all the libraries I installed hoping to recover. Now things are better, but when I open a terminal on the desktop it opens jammed in the upper-left corner with the top grab bar out of reach of the mouse. Before I remove the ~/.gnome* directories, how to restore things?
View 1 Replies View RelatedOlder machine here that I upgraded to 10.04 after a clean install of 9.10 some months ago. When booting into GNOME, the desktop image flashes on the screen and the second the bars on top and bottom try to appear the system boots out of the desktop and returns to the log on screen. I assume this is a crash of Xserver, but just guessing. Per another page I ran: lspci | grep VGAand returned:
01:00.0 VGA compatible controller: VIA Technologies, Inc. KM400/KN400/P4M800 [S3 UniChrome] (rev 01)
I know - old machine Typing this from failsafe mode, would be great to hear from someone as to what I can do to get this working in normal mode again.
I have updated Opensuse 11.3 to 11.4. I have also updated to the latest NVIDIA drivers. Now, when Gnome desktop starts it freezes: it draws all the shortcuts on the desktop but I cannot use my wired mouse to click anything as if the desktop has freezed. The cursor shows that something is loading. I cannot also use Ctl + F2 to start xterm... But I can use Ctl + Alt + F12, so the keyboard is working.
View 5 Replies View RelatedAll open-source fanatics out there like me hate industry and large companies for being on such a high horse all the time. Well, some of us have stooped to their level (towards ubuntu noobs).
View 1 Replies View Relatedafter I installed gnome-do and set it to start at start-up, my computer has started freezing right after gnome-do initiates.what happens is I turn on my laptop and log in, and then when the desktop initiates, gnome-do starts and then immediately the prompt window for the login keyring pops up and then my dekstop environment freezes. I can move my cursor around, but when I click nothing happens and the keyboard is unresponsive. the only option is to hard reboot, but the same thing happens all over again. the curious thing though, is that the notification for connecting to a network is perfectly functional and the system monitor continues to record.
View 2 Replies View RelatedI've both tried installing GNOME 3 on Ubuntu 11.04 (via ppa) and Fedora Core 15, but I can't use GNOME shell up to 10 minutes continuously. It freezes every time. Sometimes I see "Panic occurred". My chipset is Intel 915.
View 1 Replies View RelatedWhen my wife tries to login to her computer, Gnome usually freezes. Nothing in Gnome responds to the mouse or keyboard and all I can do is go to a console and restart gdm. I can always log into Gnome under my username. I am not sure how to troubleshoot this problem. Presumably it is something in the startup apps or a config file. The quick and dirty method would be to create another user and move her data but this would be a lot of work and the problem might come back.
I have a suspicion that it is related to gnome-keyring. This is because (against my advice) she insisted on an automatic login without entering a password. This was a waste of time as gnome-keyring promptly complained and demanded a password. Many times I changed her settings to ask for a login password but it does not always change the behaviour. When it tries to log in automatically without a password Gnome locks up around the time that gnome-keyring asks for its password. The default language for her is Portuguese and mine is English if that makes any difference.
I`m running openSUSE 11.2, with GNOME 2.28 - made a fresh install.
Everything went smooth and nice, and I did not made any changes to my system, when I saw that GNOME System Monitor freezes when clicking on the "System" tab.
My gnome-panel freezes frequently. Temporary solution: I have added gnome-terminal to my startup programs, and enter "killall gnome-panel" command whenever the panel freezes. However, this is inconvenient especially when the panel freezes every now and then.
Quite interestingly, all icons, menus, and applets freeze including run dialog [Alt-F2], except logout, battery, volume, etc. in the system (applets indicator) tray [time & calendar icon also freezes in system-tray]. I have tried killing all processes related to evolution, but to no avail. someone also suggested removing applets... well, it is not mentioned which applet to remove..
At random times (approx. once a day), my whole ubuntu/gnome interface freezes. mouseover-animiations (for example on the icons in the taskbar) keep working, but clicking doesn't do anything anymore. On the keyboard, tab and arrows keeps working, but most other keys don't do anything. The only option seems to be to reboot. After that reboot everything is fine again (for a while)
Once the freeze happens, it freezes both the standard ubuntu panels but also the program I have open at that moment. It doesn't seem to be connected to a specific program I run.
Is there some log, or anything else that I can use to figure out where these freezes are coming from?
I have configured my system to suspend whenever I close the lid, by using the Power Management applet provided by my desktop manager (see my later comment). However, sometimes, when I reopen the lid, I see that the laptop is switched on but it won't resume, while the CPU heats up. I must shutdown forcefully. What could be causing this?
I have found this thread [URL] .... in regard to OpenSUSE. Is it relevant for Debian as well?
System info:
- Debian GNU/Linux: 8.1
- Linux Kernel 3.16.0-4-amd64
- MATE desktop 1.8.1
- GNOME Shell 3.14.4
Clarified that the suspend is a user-level setting.
I am on Ubuntu 10.04, and I think I have had this problem since I installed it.
When I type my password into gnome-screensaver and click "Unlock," all the buttons become disabled and the cursor turns into the "busy" look. I have to go into one of the virtual terminals and do "killall gnome-screensaver." This happens maybe 75% of the time when the screen locks.
Also, this last week or two there is a new problem where the gnome-screensaver covers only part of the screen and I can still see and use most of the desktop.