The gnome-settings daemon was updated today on my Fedora 11 machine and it's now performing all kinds of interesting activities. It's using my CPU a ton. And it's generating lots of network traffic. This appears to be a massive bug of some sort. Anyone know any more details? I haven't found anything yet.
If you haven't updated it, DON'T!
2.26.1-10 appears to be the culprit.
Setting up CentOS 5.5 on my laptop. After installing the synaptics driver, I am able to get a functioning X session without any problems (I'm using startx for testing). There are however two problems: 0/ mouse cursor is slow as snails and 1/ GNOME is fouled up.
- I've tried enabling SHMConfig in my xorg.conf file, and have also tried the HAL thing here. Either way synclient tells me to jump in a lack. I should be able to set suitable adjustments in xorg.conf, but running synclient -l to see what it's currently using would be much faster than hours of trial end error. As Google totally fails to provide anything helpful and I see nothing handy in documentation beyond the 1-line edit to xorg.conf I've already done, how in the universe do I actually enable SHMConfig to synclient's satisfaction? EDIT: scrolling doesn't work either, so access to synclient is even more important; on the upside I have manually tuned the mouse speed by T&E.
- GNOME was installed through the "GNOME Desktop Environment" and "GNOME Software Development" groups (yum groupinstall GNOME*) after net' installing CentOS. It has been startx'd through gnome-session. On startup I get a string of Windows: one is a dialog saying that there was an error starting the GNOME Settings Daemon with a last error message of "Failed to execute dbus-launch to autolaunch D-Bus session". The other two are dialog windows gripe about mail notification. Several icons are missing but gnome otherwise works fine, as long as I do nothing that requires SETTINGS. Searching the web and documentation hasn't helped here either, so how the flub do I fix that?
I expect to be using blackbox or something lighter most of the time, but as GNOME is the default.... it better be working!
After I login my desktop preferences are not loaded. If I try to change them (Control cneter-> apparence) I get a message that says: Unable to start the settings manager 'gnome-settings-daemon'.Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with DBus, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager.The first lines of .xsession-errors show:
/etc/X11/xim: Checking whether an input method should be started.
HOSTNAME: Undefined variable.
XDG_DATA_DIRS: Undefined variable.
[code]....
I just installed Ubuntu 10.10 on a brand new HP EliteBook 8540w with an Nvidia card. To get the machine to work at all I have to use the proprietary nvidia driver. The downside is that when I use this driver gnome-settings-daemon seems to crash when I start the machine which results in a ugly theme. To fix this I have to run the following command:
Code:
sudo gnome-settings-daemon
After this the theme is re-applied. If I try to run gnome-settings-daemon as my regular user I get the following messages:
Code:
** (gnome-settings-daemon:2187): WARNING **: Failed to acquire org.gnome.SettingsDaemon
** (gnome-settings-daemon:2187): WARNING **: Could not acquire name
[Code]...
about every second time when I start up my Ubuntu 10.4, my hard drive starts to work heavily. While it's doing so I see in the system monitor that the gnome-settings-daemon has the status 'uninterruptible'. After about 3 minutes the hard drive calms down and the status of gnome-settings-daemon switches to 'sleeping'. so from that I guess the heavy working of the hard drive is somehow related to that process. Sometimes gnome-settings-daemon seems to crash completely so that my theme is gone.
So is there a solution to that? because it's annoying that it slows down the system for about 3 minutes after start up. On the net I've found some old threads from 2004 and 2006 which describe crashing of gnome-settings-daemon. But there didn't seem to be a solution.
I'm having trouble with gnome-settings-daemon in gnome 3. I can start it with sudo and get my pretty theme, but under my normal user it segfaults.
blah@heymon ~/.config/gtk-3.0 $ gnome-settings-daemon
(gnome-settings-daemon:309: Gtk-WARNING **: Could not load named theme "Adwaita": File doesn't exist: /usr/share/themes/Adwaita/gtk-3.0/-gtk-gradient (linear,
[code]....
I recently upgraded to Ubuntu 10.10 and I am experiencing an ultra high memory usage of the gnome-settings-daemon of 2GB after suspend! Killing and restarting the daemon solves the issue. Anybody else with this behavior?
View 6 Replies View RelatedGetting this error seemingly randomly at login:
There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work correctly.
The last error message was:
Launch helper exited with unknown return code 1
GNOME will still try to restart the Settings Daemon next time you log in.
I thought I might be logging in to fast, but it happened again when I had waited several minutes.
i installed Ubuntu rel 9.10 download as a first time user. all was fine until the update manager bugged me enough to update. i allowed it to download and install the updates for rel 10.04. after the update i started having intermittent GRUB errors at boot. i worked on this problem and without warning Ubuntu returned to rel 9.10. the Linux kernel is still at level 2.6.31-21. rather than do another update manager update i am considering a download of rel 10.04 and install from that. i would then have a backup for rel 10.04. my concerns are my user data i do not have a user partition. also how would the install partition my hard drive. i allowed the install to partition my 9.10 system. my current FDISK output not sure why devices show sda i thought they woud be hda hard drive??
[Code].....
After doing the upgrade per this thread my gnome panel gets bugged when the workspace switcher applet is attached to it. Also the Cairo Dock bugs out with the workspace switcher applet attached to it. I can change desktops with key commands fine. It would just be nice if this could be fixed. I am sticking with gnome 2.32 because of my affinity with Evolution which performs better in 2.32.
View 3 Replies View Relatedi think IM-settings is dead. i cannot get ibus or scim work.IM-Settings-Daemon[6769]: CRITICAL **: Giving up to bring the process up because Main Input Method process for ibus rapidly died many times. See .imsettings.log for more details.i have re-installed butProblem has been solved...re-install or update gtk2/glib2 and remove imsettings scim ibus im-chooser etc, everything.re-install imsettings ibus and im-chooser...thats it! i found sometimes the binary is not as good as source....
View 4 Replies View RelatedHave had a clean perfectly working copy of 2.6.31.6-166 for months and after two updates to 2.6.31.12-174.2.3 and 2.6.31.12-174.2.19, neither of the newer kernel versions will allow machine to boot properly. Start-up hangs at the preload daemon with a flickering screen. To use machine, must use grub chooser and choose the original base kernel.
Running on Tyan h2000m board, opteron 2356, Nvidia 9800 GTX+ and 12GB of dram with SELinux security enabled.
While working fine in KDE, multimedia settings don't work in Gnome. When I go to System/Preferences/Sound it pops up dialogue box after a while: Quote: Waiting for sound system to respond Cancel
View 14 Replies View Relatednoticed that Fedora 12 made some odd design decisions for default GNOME settings, and I couldn't locate the System->Preferences->Windows menu item to change them back. The design options I'm talking about:
* No icons in menus (System menu for instance has no icons, though there are icons under the Preferences and Administration sub-menus... the root System menu though has none)
* Icons on toolbars are configured so the label text appears to the right of the buttons, so this makes File Explorer in Nautilus look funny to me. I like the text appearing beneath the icons like it has always been up until now.
why the Windows configuration has been removed from Fedora 12? The control-center package provides the bins for all the preferences items except for gnome-window-settings; so is it upstream that did this? Anyway, I had to dig around in the gconf-editor to find where the window settings are kept so I could change them "manually", since the Windows tool is gone now. For anyone else who wants to know, it's under /desktop/gnome/interface in the gconf-editor (namely, keys toolbar_style, buttons_have_icons, and menus_have_icons are the ones I changed).
I see the gnome 3 was release,It need to burn a CD‚But I want to update Gnome 3 from Gnome 2.32 in my system.
View 2 Replies View RelatedI have a problem with my Fedora system. Whilst I was messing around with my graphics drivers I managed to totally screw up the system, now my desktop won't start, leaving me with just the command prompt. In order to fix it I will need to get my wireless adapter connected to my home network, this is proving tricky. I understand that NetworkManager is responsible for bringing up the network but unfortunately without starting GNOME I don't have the settings available to me (through the nm-cli) or a way to configure it.
Is there a way to bring up whatever service holds the network settings without GNOME? In the meantime I am looking into alternative ways of configuring NM, perhaps through the DBUS interface? Even so, I suspect that I will still need a settings ervice at the end of it..
Not sure if others have noticed this. When I go into sound settings, click the output tab, select the sound device I want to edit and change the bass levels etc, close the window and go back in all the settings are reset to default and no changes are saved.
If I leave the window open and make the changes they are reflected in VLC for example, but if I close the window it again resets to defaults and my Bass is back at Maximum....
Is this a BUG I should report or is there something I can download to get this configured elsewhere or to fix this issue? I seem to recall something similar in Fedora 14 that was fixed, but I cant remember how I did it now
Since doing the update which included kernel "2.6.32.16-141 fc12-i686 PAE" I can no longer boot into my usual 1280x960 desktop. I can set it using NVidia settings but even though this offers to modify xorg.conf it fails to do so. I have tried running as root and it doesn't then give an error message but when I look at xorg. conf there is no section.showing any specific screen size. It worked ok before the update. In case it is relevant the video card is a Quadro FX1400 with KDE. Also the whole program seems rather unstable since the update.
View 10 Replies View RelatedI fired up my PC this morning and not unusually got an update message. I updated all that I was instructed to, as per normal - and at the end of the update was told that I'd need to restart to effect changes. I was in the middle of something else at the time so I left it but I turned the PC off an hour or so later and left it.
On starting up again I cannot get my previous resolution (1600 x 1200) and Second Life resolutely refuses to run giving a "Window creation error". Trying to change the display settings from the System> Administration menu just stops: It asks for the root PW and then nothing happens
Clearly something's gone a bit pear shaped here. I'm using Fedora 12 wth a PAE kernel and on an AMD 5200 chip with an nvidia 7900GS card. Things worked fine until this update so I strongly suspect that to be the cause but what can I do to fix it? Is there any way to "roll back" the update somehow or is there a fix?
Is it possible to delete a panel and move the remaining one in the Fallback Gnome 2-style mode? When I tried it everything seemed locked down.
View 1 Replies View RelatedI'm running an up-to-date installation of Lucid, and have come upon a little problem. It seems that applications are having trouble communicating with gnome-keyring-daemon.
When I connect to wireless networks -- even ones that are in the network manager -- it always asks me for a password.
Gwibber is crashing because it can't connect to the gnome keyring daemon.
And when I open the Passwords and Encryption Keys utility (on the Accessories menu), I get the error: "Couldn't communicate with key ring daemon."
I have verified that the daemon is starting up when I log in, that all of the appropriate keyring-related login items (certificate and key storage, secret service, & SSH key agent) are in place, and that the keyring works in other accounts on my machine. I have tried deleting my extant keyrings, but that has produced any success. And when I kill and restart the keyring daemon once I'm already logged in, the problem seems to abate.
I don't know if it matters, but for OS X compatibility purposes, I'm running as a UID under 1000.
I have written a daemon server. I would like to add the ability for the daemon to update itself. That is, it should be able to download the latest version of the code (when it receives a signal from a client) and then restart itself. I am stuck on getting the daemon to restart itself. The problem is killing the old daemon without killing the process that is starting the new daemon. In my latest attempt, the daemon that is updating itself runs a program in a subshell (using system) that starts a restarter daemon that runs the original daemon (again using system) with the restart command option. With the restart option, the new version of the daemon sends a terminate signal to the old version. Obviously, when I run the original daemon manually with the restart option, it restarts reliably. I figured that issuing the same restart command from a daemon would adequately isolate the process doing the restarting from the program being restarted. Using ps, I can see that the daemon does actually restart. However, the client locks. In fact, a few times, the OS locked and I had to reset.
View 7 Replies View RelatedSince I've upgraded to Ubuntu 10.04 my gnome-keyring-daemon isn't working on login. It is running - ps ax shows:
4927 ? SLl 0:00 /usr/bin/gnome-keyring-daemon --daemonize
but it doesn't seem to be accessible. Seahorse says: "Couldn't communicate with key ring daemon", and I never get asked to unlock my keyring on login (thus saved wireless keys are not available, for example). If I kill the gnome-keyring-daemon process and run it again from the command line, everything works. There are not messages in /var/log/messages from the keyring daemon, so i don't know what it is doing wrong.
I have Ubuntu 10.04 configured to login with Kerberos (as in [url]). Everything works fine, except gnome-keyring-daemon:
-If I login with a local user, gnome-keyring-daemon works right. Besides, the keyring is automatically unlocked with the login password.
-If I login with a Kerberos user:
- The session startup is considerably slower.
- /var/log/auth.log says something like:
Code:
- If I execute a program that needs the gnome-keyring (like Evolution), is desperately slow, and it says:
Code:
Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- If I kill all gnome-keyring-daemon (killall gnome-keyring-daemon), start a new one (gnome-keyring-daemon), and restart the application that uses the gnome-keyring, it works fine, but it ask me for the password to unlock the keyring (I think that this is the normal behaviour if gnome-keyring-daemon did not start before).
I have seen the configurations in /etc/pam.d and everything looks fine (with pam_gnome_keyring.so). Indeed, I think that if something was wrong here, the local user would not have the keyring unlocked automatically.
How to permanently disable the gnome-keyring-daemon.
I've seen posts where there was a work around to store passwords in clear text. That's not a real solution. I've seen posts where killing the process and removing ~/.gnome2/keyrings is a temporary solution until next time you log in or reboot machine. Removing the package, will force removal of the whole kitchen sink. That's too intrusive.
There must be a way to stop this thing from starting up, ever.
I tried commenting out the entries in the /etc/pam.d/* files that refer to "pam_gnome_keyring.so", and have also unchecked the 3 keyring related entries under System --> Preferences --> Startup Applications, which are affiliated with these 3 files:
But I still get this one process once I log into the console window:
There must be one more file somewhere that says, "hey when someone logs in and starts up gdm, start the gnome keyring daemon".
I have an error when I try to update or remove transmission-daemon package.
Here are some logs:
root@ubuntu:~# apt-get --reinstall install transmission-daemon
Reading package lists... Done
Building dependency tree
Reading state information... Done
[Code]...
how to update my GNOME desktop panel? In fact somehow I managed to lose my notification Applet (system tray) because of which I am unable find volume control, network status etc... I hope updating the GNOME can help to resolve my problem on notification area applet. If I can get back the notification area I will be really greatful
View 1 Replies View RelatedI've been using Fedora 15 since its release (it was a fresh install) and have run the built-in updater three times; the third time being just earlier. In running it, about 113 updates were found, and afterwards, I rebooted. Unfortunately, GNOME 3 somehow broke as a result of that update (I didn't do anything else system-wise in the meantime), though I'm not sure what could have caused it.
After logging in, I see nothing except my desktop wallpaper. The top bar doesn't exist, and there are no workable elements... a wallpaper and nothing but. Thinking it might have been a user issue, I created a new user under Xfce and then logged into it, and I had the same thing. Default wallpaper but nothing else.
I am actually in the process of reviewing Fedora 15 (and GNOME 3) and was nearly done writing what I needed to before this happened, so I'd love to figure out a way to fix it rather than reinstall the entire OS since I have things set up to my liking and would hate to have everything undone.
If it helps, I did a yum groupremove of "GNOME Desktop Environment" and then a groupinstall of it again, but that didn't help it either. It did ironically remove both KDE and Xfce I had installed, however.
Last night I upgraded from 10.04 to 10.10 and now my system is bugged. If I accidentally enter the wrong credentials at login, the computer freezes - consistently. This happens at login on startup and when unlocking the screen after it goes to sleep. Additionally, my fingerprint reader which is built in and worked perfectly before the upgrade is causing the computer to freeze after a scan to login or unlock the computer. I haven't noticed any advantages to this newer "lighter" version of ubuntu so I'm not at all opposed to a complete downgrade back to 10.04.Unless someone has a straight solution to this problem - which I doubt, just let me know how I can downgrade my kernel back to a stable version that actually functions to basic standards..
P.S. I know that the upgrade deleted/turned off some "uneeded" or absolete repositories, so I went thru and reinstalled all those involved with the fingerprint scanner, and still the same results, even after a restart so..
I'm running F13 on a HP laptop. I've been about 10 days with no internet connection. Yesterday I got internet again, and I did a package update.
After that, I rebooted and both top and bottom bars were gone from my Gnome desktop. I couldn't retrieve them anymore.
What can I do to get them back?