When? Gnome 2.24

moljac024 wrote:These kinds of threads should be locked on sight.
Agreed.
moljac024 wrote:How many have been started about Gnome 2.24 ?
Well, still 12,000 short to be the same number as KDE4 threads when it came out.

Similar Messages

Conky disappers when Gnome-Desktop starts

Hi there,
I've installed conky as a systemmonitor and would like to let it start when my Gnome-Desktop starts. To achieve this, I put the "conky"-command under System -> Preferences -> Session. In principle this works, because when Gnome starts, I can see that conky is startet, too.
But when Gnome starts Metacity, conky ist shifted to the background (or whatever). With "top" I can see, that it's still running, but I can't see it anymore.
Does anyone know, how I can start conky automatically when Gnome starts up?
If you're interested or may it helps - here is my .conkyrc:
# Create own window instead of using desktop (required in nautilus)
own_window yes
own_window_type override
own_window_transparent yes
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
# Use double buffering (reduces flicker, may not work for everyone)
double_buffer yes
# fiddle with window
use_spacer yes
use_xft yes
# Update interval in seconds
update_interval 3.0
# Minimum size of text area
# minimum_size 250 5
# Draw shades?
draw_shades no
# Text stuff
draw_outline no # amplifies text if yes
draw_borders no
xftfont Arial:size=10
uppercase no # set to yes if you want all text to be in uppercase
# Stippled borders?
stippled_borders 3
# border margins
border_margin 9
# border width
border_width 10
# Default colors and also border colors, grey90 == #e5e5e5
default_color white
own_window_colour black
own_window_transparent yes
# Text alignment, other possible values are commented
#alignment top_left
alignment top_right
#alignment bottom_left
#alignment bottom_right
# Gap between borders of screen and text
gap_x 10
gap_y 10
# stuff after 'TEXT' will be formatted on screen
TEXT
$color
${color orange}SYSTEM ${hr 2}$color
$nodename $sysname $kernel on $machine
${color orange}CPU ${hr 2}$color
${freq}MHz Load: ${loadavg} Temp: ${acpitemp}
$cpubar
${cpugraph 000000 ffffff}
NAME PID CPU% MEM%
${top name 1} ${top pid 1} ${top cpu 1} ${top mem 1}
${top name 2} ${top pid 2} ${top cpu 2} ${top mem 2}
${top name 3} ${top pid 3} ${top cpu 3} ${top mem 3}
${top name 4} ${top pid 4} ${top cpu 4} ${top mem 4}
${color orange}MEMORY / DISK ${hr 2}$color
RAM: $memperc% ${membar 6}$color
Swap: $swapperc% ${swapbar 6}$color
Root: ${fs_free_perc /}% ${fs_bar 6 /}$color
home: ${fs_free_perc /home}% ${fs_bar 6 /home}$color
CDRom: ${fs_free_perc /mnt/cdrom}% ${fs_bar 6 /mnt/cdrom}
DVD: ${fs_free_perc /mnt/dvd}% ${fs_bar 6 /mnt/dvd}
${color orange}NETWORK (${addr eth0}) ${hr 2}$color
Down: $color${downspeed eth0} k/s ${alignr}Up: ${upspeed eth0} k/s
${downspeedgraph eth0 25,140 000000 ff0000} ${alignr}${upspeedgraph eth0
25,140 000000 00ff00}$color
Total: ${totaldown eth0} ${alignr}Total: ${totalup eth0}
Inbound: ${tcp_portmon 1 32767 count} Outbound: ${tcp_portmon 32768
61000 count}${alignr}Total: ${tcp_portmon 1 65535 count}
${color orange}LOGGING ${hr 2}$color
${execi 30 tail -n3 /var/log/messages.log | fold -w50}
${color orange}FORTUNE ${hr 2}$color
${execi 120 fortune -s | fold -w50}

Gnome lays its desktop above the root-window in its own borderless window. But conky is drawn directly to the root-window so the Gnome Desktop is always on top of it. The only workaround is to configure conky to run it its own window or not start the gnome-desktop executable.

XChat/Gnome: No tray icon when launched at startup

Hi Archers,
I added XChat to the Gnome startup application list. When Gnome starts, XChat is started too, but it doesn't appear in the notification area.
When I start it during a Gnome session, it does appear in it.
Did I miss something? Am I the only one to experience that issue?
Thanks for your help.

Since Gnome 2.30, it is finally possible to enter a composite command as a startup application command.
However, the workaround still doesn't work. By entering this command, XChat isn't started at all.

Gnome 3.2 authentication failed when login

I update all package by pacman -Syu. My arch start gnome as login as default, but gnome cannot list user list.
and click not list？ to enter username and password.
but it saied authentication failed. I only has one root acount. it worked when gnome is 3.0. donot know why?
any one meet this?
thanks
---kenan

Wonder is right about not using the root account... BUT... I can confirm the same problem.
After updating to gnome 3.2, gdm responds with "Authentication Failure" no matter what valid account I use to login. I've looked in the /var/log/gdm/:0-greeter log and here's all I get:
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Calling StartConversation
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=Ready
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Received Ready (gdm-password)
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Calling BeginVerification
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=DefaultLanguageNameChanged
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=DefaultSessionNameChanged
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Received DefaultSessionNameChanged (gnome)
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=InfoQuery
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Received InfoQuery (gdm-password, Username:)
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Calling AnswerQuery
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=SelectedUserChanged
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Received SelectedUserChanged (myuser)
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=DefaultLanguageNameChanged
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=DefaultSessionNameChanged
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Received DefaultSessionNameChanged (gnome)
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=SecretInfoQuery
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Received SecretInfoQuery (gdm-password, Password: )
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Calling AnswerQuery
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=Problem
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Received Problem (gdm-password, Authentication failure)
JS LOG: error: Authentication failure
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=ConversationStopped
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Received ConversationStopped (gdm-password)
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: Calling Cancel
(gnome-shell:1868): GdmGreeter-DEBUG: GdmGreeterClient: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=Reset
I fixed the permissions on /var/lib/gdm/.config/dconf from 755 to 700 (since pacman complained during the update) and I tried removing and reinstalling gdm.
No luck so far... Will keep trying.

GNOME 3.4 changing remembered automount and display settings

Here's an interesting observation.
My setup is the following: notebook computer + external display.
2 user accounts A and B and I'm using GNOME 3.4 in fall-back mode.
I think it's important to know, account A was created before I bought external display and started using it as a main one. Account B was created when I already used external display.
So, I use only external display at 1920x1200 resolution:
xrandr
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
VGA-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
1920x1200 60.0*+
1920x1080 60.0
1600x1200 60.0
1680x1050 60.0
1280x1024 60.0
1280x960 60.0
1024x768 60.0
800x600 60.3
640x480 60.0
720x400 70.1
LVDS connected (normal left inverted right x axis y axis)
1280x800 60.0 +
1280x720 59.9
1152x768 59.8
1024x768 59.9
800x600 59.9
848x480 59.7
720x480 59.7
640x480 59.4
I also have a bunch of external USB drives connected to this notebook computer and they get automounted with the help of udisks2 helper:
mount |grep udis
/dev/sdb1 on /run/media/A/9d244934-d9fa-4a8e-8dd7-5c595f5518cf type ext2 (rw,nosuid,nodev,relatime,uhelper=udisks2)
So, I boot my Arch Linux, external display is connected and notebook is configured (by clicking Fn+Display key to choose to output video signal to external display only), I see GDM. So far so good, only external display is used, choosing automatically correct native resolution of 1920x1200.
I enter user account password in GDM, GNOME starts loading.
What happens for user A is that:
- notebook's display gets lit up, showing video output in its native resolution of 1280x800
- external display duplicates the video output apparently in this 1280x800 resolution (because the image is kind of zoomed and unscaled, blurred: because it's not a native resolution)
- I have to click Fn+Display key to switch available modes and choose one when only external display is used. When it's done, native resolution of 1920x1200 is chosen for external display and all is good.
However, when I resume from sleep notebook when logged in as user A, even though the external display is used in native resolution, just as it's supposed to be, I can see that notebook's screen is glowing, but not showing any video output. I need then to turn off power for it pushing Fn+Sun (an icon depicting sun with one half filled, and the other empty signifying on/off modes) .
The USB disks. When GNOME is loaded for user A I can see in Places my drives, but I have to manually click them to get them mounted. When resuming from sleep, I have to do it again. They're automatically detected, but aren't mounted.
All of that shouldn't be normally happening. Why?
Because for user B none of that is true.
External display works as expected on GNOME's start, when resuming from sleep under user B notebook's screen never isn't glowing. USB disks are automounted when user session is loaded, or OS is resumed from sleep.
Obviously, I want the same for user A. But there aren't really any settings to tweak, at least none that I know of or could find myself.
It would seem that something like session settings are different for these two user accounts, but I know really little about session management in GNOME. Might be something else.
I would appreciate it if you shared your insights or ideas as to how to make user A GNOME session to behave much like user B's in respect to displays and mounting of external USB drives.
Last edited by xCrucialDudex (2012-10-13 07:56:41)

I have the same problem as you. I can't access the system settings nor the online accounts thing. I guess we will have to wait till the next patch or something. Here is the bug report.

GTK Theme :: X-Forwarding :: gnome-settings-daemon

Just wondering if anyone else has come across an error like this. Every GTK application I run using X-Forwarding looks really bad (small fonts, old boxy gnome 2.0 theme). When I attempt to start gnome-appearance properties (also over ssh, as there is no screen connected to the server), I get the following dialog box:
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 Bonobo, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager.
I first tried to manually start gnome-settings-daemon, which runs for about 1 second before it quits. During that second all my windows take on the correct theme and fonts. The debug output is confusing and looks like it's crashing right before / after it tries to load a keyboard manager.
matt@bender ~ $ gnome-settings-daemon --no-daemon --debug
Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
Xlib: extension "RANDR" missing on display "localhost:10.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
** (gnome-settings-daemon:14301): DEBUG: Successfully connected to D-Bus
** (gnome-settings-daemon:14301): DEBUG: Starting settings manager
** (gnome-settings-daemon:14301): DEBUG: Loading settings plugins from dir: /usr/lib/gnome-settings-daemon-2.0/
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Media keys' file='/usr/lib/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin' location='media-keys'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/media-keys for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Typing Break' file='/usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin' location='typing-break'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/typing-break for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Font' file='/usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin' location='font'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/font for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Keyboard' file='/usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin' location='keyboard'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keyboard for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Clipboard' file='/usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin' location='clipboard'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/clipboard for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/background.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Background' file='/usr/lib/gnome-settings-daemon-2.0/background.gnome-settings-plugin' location='background'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/background for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Mouse' file='/usr/lib/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin' location='mouse'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/mouse for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/housekeeping.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Housekeeping' file='/usr/lib/gnome-settings-daemon-2.0/housekeeping.gnome-settings-plugin' location='housekeeping'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/housekeeping for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/screensaver.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Screensaver' file='/usr/lib/gnome-settings-daemon-2.0/screensaver.gnome-settings-plugin' location='screensaver'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/screensaver for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='X Settings' file='/usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin' location='xsettings'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xsettings for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Accessibility Keyboard' file='/usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin' location='a11y-keyboard'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/a11y-keyboard for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Dummy' file='/usr/lib/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin' location='dummy'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/dummy for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='XRandR' file='/usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin' location='xrandr'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrandr for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/sound.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Sound' file='/usr/lib/gnome-settings-daemon-2.0/sound.gnome-settings-plugin' location='sound'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/sound for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='Keybindings' file='/usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin' location='keybindings'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keybindings for changes
** (gnome-settings-daemon:14301): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsPluginInfo: name='X Resource Database' file='/usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin' location='xrdb'
** (gnome-settings-daemon:14301): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrdb for changes
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298050 initialising
** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libxrandr.so
** (gnome-settings-daemon:14301): DEBUG: Registering GsdXrandrPlugin
** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdXrandrPlugin
** (gnome-settings-daemon:14301): DEBUG: GsdXrandrPlugin initializing
** (gnome-settings-daemon:14301): DEBUG: Activating xrandr plugin
** (gnome-settings-daemon:14301): DEBUG: Starting xrandr manager
** (gnome-settings-daemon:14301): WARNING **: Unable to start xrandr manager: Failed to initialize XRandR extension
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated xrandr
** (gnome-settings-daemon:14301): DEBUG: Plugin xrandr: active
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x82980a0 initialising
** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libxsettings.so
** (gnome-settings-daemon:14301): DEBUG: Registering GnomeXSettingsPlugin
** (gnome-settings-daemon:14301): DEBUG: Creating object of type GnomeXSettingsPlugin
** (gnome-settings-daemon:14301): DEBUG: GnomeXSettingsPlugin initializing
** (gnome-settings-daemon:14301): DEBUG: Activating xsettings plugin
** (gnome-settings-daemon:14301): DEBUG: Starting xsettings manager
** (gnome-settings-daemon:14301): DEBUG: Setting GTK modules 'canberra-gtk-module:gnomebreakpad'
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated xsettings
** (gnome-settings-daemon:14301): DEBUG: Plugin xsettings: active
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298140 initialising
** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libsound.so
** (gnome-settings-daemon:14301): DEBUG: Registering GsdSoundPlugin
** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdSoundPlugin
** (gnome-settings-daemon:14301): DEBUG: GsdSoundPlugin initializing
** (gnome-settings-daemon:14301): DEBUG: Activating sound plugin
** (gnome-settings-daemon:14301): DEBUG: Starting sound manager
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated sound
** (gnome-settings-daemon:14301): DEBUG: Plugin sound: active
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298190 initialising
** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libfont.so
** (gnome-settings-daemon:14301): DEBUG: Registering GsdFontPlugin
** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdFontPlugin
** (gnome-settings-daemon:14301): DEBUG: GsdFontPlugin initializing
** (gnome-settings-daemon:14301): DEBUG: Activating font plugin
** (gnome-settings-daemon:14301): DEBUG: Starting font manager
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated font
** (gnome-settings-daemon:14301): DEBUG: Plugin font: active
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298200 initialising
** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libbackground.so
** (gnome-settings-daemon:14301): DEBUG: Registering GsdBackgroundPlugin
** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdBackgroundPlugin
** (gnome-settings-daemon:14301): DEBUG: GsdBackgroundPlugin initializing
** (gnome-settings-daemon:14301): DEBUG: Activating background plugin
** (gnome-settings-daemon:14301): DEBUG: Starting background manager
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsManager: emitting plugin-activated background
** (gnome-settings-daemon:14301): DEBUG: Plugin background: active
** (gnome-settings-daemon:14301): DEBUG: GnomeSettingsModule 0x8298250 initialising
** (gnome-settings-daemon:14301): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libkeyboard.so
** (gnome-settings-daemon:14301): DEBUG: Registering GsdKeyboardPlugin
** (gnome-settings-daemon:14301): DEBUG: Creating object of type GsdKeyboardPlugin
** (gnome-settings-daemon:14301): DEBUG: GsdKeyboardPlugin initializing
** (gnome-settings-daemon:14301): DEBUG: Activating keyboard plugin
** (gnome-settings-daemon:14301): DEBUG: Starting keyboard manager
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 145 error_code 137 request_code 134 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
[1238394881,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
Sorry for the long output, I wasn't sure if some small bit of information in there could be relevant. I'm just kinda hoping that someone else has had this problem and came up with an easy fix.
-Matt

Hi!
You might be interested in the workaround found here:
https://bugs.launchpad.net/ubuntu/+sour … bug/199245
It seems the gnome-settings-daemon crashes while trying to load the keyboard plugin, you might have more luck getting it to work if you deactivate the plugin. It worked here at least.
For this, I have put this line in my session starting script.
gconftool-2 -t bool --set /apps/gnome_settings_daemon/plugins/keyboard/active false
I am using NX, but your problem is almost exactly like mine and NX is basically X session forwarding on steroids.
I still don't know what this plugin affects on a gdm session, so I have this untested bit in my .gnomerc file.
gconftool-2 -t bool --set /apps/gnome_settings_daemon/plugins/keyboard/active true
(the plugin is reactivated)
I am not sure that the .gnomerc file is executed when gdm starts a session, so it's a guess for now (I will try to edit later with my results).
[EDIT]
The command in the .gnomerc file didn't work.
This plugin, as I thought, sets the keyboard settings, it is quite useful to have it activated.
The only workaround I found (for now) is to test if this is an NX session and if not, activate it. (I don't know if it is doable to check if it is an X11-Forwarding session.)
[/EDIT]
[EDIT2]
Oh wow, old post! In this date of February 19th 2010, I cam across this post.
I had a similar problem and had it resolved with my old self's help today. (I had a hard time searching and found this post... I feel dumb).
Always within an NX session, I had a similar problem. The gnome-settings-daemon still wouldn't start, but with the updates in GNOME, the message changed. Here is the new message:
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.
This is the other key you want to deactivate with NX.
/apps/gnome_settings_daemon/plugins/xrandr/active
The keyboard key still needs to be deactivated.
Cheers for any internet dweller who finds this!
[/EDIT2]
These two modifications will work in any session scripts, but you have to disable the plugin before the gnome-settings-daemon runs, but I think activating it after is not a problem (try activating it when gnome-settings-daemon is running, it will crash under NX).
Anyway, it could be interesting to link to that wiki page you will write here!
Good luck!
Oh, I'm putting some keywords here for search engines to pick this up as the problem seems to be common accross many remote protocols like: VNC gnome-settings-daemon, X11 over SSH gnome-settings-daemon and X over SSH gnome-settings-daemon. xrandr gnome-settings-daemon crash.
Last edited by samueldr (2010-02-19 05:22:04)

[Solved] Gnome Integration Missing In Chromium 35

Hello all,
With the newly released Chromium 35, it seems that Gnome integration is missing.
Specifically, it does not recognize gnome in the Gnome extensions site via the plugin that was available in version 34.
Anything can be done about it?
Thanks, Adam.
http://i.imgur.com/hj7RKqP.png
http://i.imgur.com/R1OQMor.png
Moderator Edit [ewaller] Converted over sized imaged to url links
* EDIT *
Issue due to Chrome 35 no longer supporting the NPAPI plugin architecture.
Last edited by adam777 (2014-05-21 12:58:32)

decryptedepsilon wrote:Also, if anyone is using Hangouts extension, do they experience gnome-shell crashes on starting Hangouts? I have them. Also happens with Cinnamon so it must be gnome-shell related. Chromium 35 added something which doesn't play well with gnome-shell yet.
I use the hangouts extension (a lot!) and google-chrome beta which is currently on version 36+ but have no crashes. Nor did I have any crashes for the months when google-chrome beta was on any of the many 35 versions. [Actually, I had a few gnome-shell crashes over a few days when gnome-shell first moved to version 3.12+ but discovered it due to the skype extension which I removed and have not see one since].

Error starting the GNOME Settings Daemon

After a full system upgrade of about 500mb, I now get this error when Gnome is started. Also, im kinda new to this...
"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:
The name org.gnome.SettingsDaemon was not provided by any .service files
GNOME will still try to restart the Settings Daemon next time you log in."
The things is, my background and other desktop stuff is still in their place. But my keyboard has gone back to its default setting and the drivers for my wireless isnt getting loaded. I also have problems playing music with Amarok.
After the full upgrade of my system I installed compiz-fusion and AWM, but they arent started when i boot. Could they be a problem?
I looked at some issues with similar error messages, where they downgraded the gnome-settings-tools, how do I do that?

Hi there!
I copied the from where pacman generates the fallback version before starting to upgrade.
[2008-05-30 18:44] :: Begin build
[2008-05-30 18:44] :: Parsing hook [base]
[2008-05-30 18:44] :: Parsing hook [udev]
[2008-05-30 18:44] :: Parsing hook [autodetect]
[2008-05-30 18:44] :: Parsing hook [pata]
[2008-05-30 18:44] :: Parsing hook [scsi]
[2008-05-30 18:44] :: Parsing hook [sata]
[2008-05-30 18:44] :: Parsing hook [usbinput]
[2008-05-30 18:44] :: Parsing hook [keymap]
[2008-05-30 18:44] :: Parsing hook [filesystems]
[2008-05-30 18:44] :: Generating module dependencies
[2008-05-30 18:44] :: Generating image '/boot/kernel26.img'...SUCCESS
[2008-05-30 18:44] ==> SUCCESS
[2008-05-30 18:44] ==> Building image "fallback"
[2008-05-30 18:44] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2008-05-30 18:44] :: Begin build
[2008-05-30 18:44] :: Parsing hook [base]
[2008-05-30 18:44] :: Parsing hook [udev]
[2008-05-30 18:44] :: Parsing hook [pata]
[2008-05-30 18:44] :: Parsing hook [scsi]
[2008-05-30 18:44] :: Parsing hook [sata]
[2008-05-30 18:44] :: Parsing hook [usbinput]
[2008-05-30 18:44] :: Parsing hook [keymap]
[2008-05-30 18:44] :: Parsing hook [filesystems]
[2008-05-30 18:44] :: Generating module dependencies
[2008-05-30 18:44] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2008-05-30 18:44] ==> SUCCESS
[2008-05-30 18:44] upgraded kernel26 (2.6.24.1-2 -> 2.6.25.4-1)
[2008-05-30 18:44] upgraded ipw3945 (1.2.2-7 -> 1.2.2-10)
[2008-05-30 18:44] upgraded libdvdnav (0.1.10-2 -> 0.1.10-3)
[2008-05-30 18:44] upgraded libebml (0.7.7-1 -> 0.7.8-1)
[2008-05-30 18:44] upgraded libgail-gnome (1.20.0-1 -> 1.20.0-2)
[2008-05-30 18:44] upgraded libnetworkmanager (0.6.5-1 -> 0.6.6-1)
[2008-05-30 18:44] upgraded libnl (1.0pre6-1 -> 1.1-1)
[2008-05-30 18:44] upgraded libsamplerate (0.1.2-4 -> 0.1.3-1)
[2008-05-30 18:44] upgraded licenses (2.3-1 -> 2.4-1)
[2008-05-30 18:44] upgraded lvm2 (2.02.33-1 -> 2.02.36-1)
[2008-05-30 18:44] upgraded man-pages (2.77-1 -> 2.79-1)
[2008-05-30 18:45] Updating font cache... done.
[2008-05-30 18:45] upgraded ttf-dejavu (2.23-1 -> 2.25-1)
[2008-05-30 18:45] upgraded mplayer (1.0rc2-2.1 -> 1.0rc2-3)
[2008-05-30 18:45] upgraded nautilus-cd-burner (2.20.0-1 -> 2.22.1-1)
[2008-05-30 18:45] upgraded networkmanager (0.6.5-3 -> 0.6.6-1)
[2008-05-30 18:45] In order to use the new nvidia module, exit Xserver and unload it manually.
[2008-05-30 18:45] upgraded nvidia (169.09-2 -> 169.12-4)
[2008-05-30 18:45] upgraded opera (9.25-2 -> 9.27-1)
[2008-05-30 18:45] upgraded orca (2.20.3-1 -> 2.22.0-1)
[2008-05-30 18:45] upgraded pcmciautils (014-3 -> 014-4)
[2008-05-30 18:45] upgraded perlxml (2.34-4 -> 2.36-1)
[2008-05-30 18:45] upgraded perl-xml-simple (2.18-1 -> 2.18-2)
[2008-05-30 18:45] upgraded printproto (1.0.3-1 -> 1.0.4-1)
[2008-05-30 18:45] upgraded pycairo (1.4.0-3 -> 1.4.12-1)
[2008-05-30 18:45] upgraded qt (4.3.3-4 -> 4.3.4-1)
[2008-05-30 18:46] upgraded seahorse (2.20.3-1 -> 2.22.1-1)
[2008-05-30 18:46] upgraded sound-juicer (2.20.1-1 -> 2.22.0-1)
[2008-05-30 18:46] upgraded tar (1.19-2 -> 1.20-2)
[2008-05-30 18:46] installed ndesk-dbus (0.6.0-1)
[2008-05-30 18:46] installed ndesk-dbus-glib (0.4.1-1)
[2008-05-30 18:46] installed mono-addins (0.3.1-2)
[2008-05-30 18:46] upgraded tomboy (0.8.1-1 -> 0.10.1-1)
[2008-05-30 18:46] upgraded totem-plparser (2.21.91-1 -> 2.22.2-1)
[2008-05-30 18:46] installed libepc (0.3.5-1)
[2008-05-30 18:46] installed python-elementtree (1.2.6-2)
[2008-05-30 18:46] installed python-gdata (1.0.11.1-1)
[2008-05-30 18:46]
[2008-05-30 18:46] ==> Totem has been built with GStreamer. By default, only plugins from
[2008-05-30 18:46] ==> gst-plugins-good and gst-plugins-base are installed.
[2008-05-30 18:46] ==>
[2008-05-30 18:46] ==> To play additional media formats, more plugins are available from
[2008-05-30 18:46] ==> gstreamer0.10-ugly-plugins, gstreamer0.10-bad-plugins
[2008-05-30 18:46] ==> and gstreamer0.10-ffmpeg packages.
[2008-05-30 18:46] ==>
[2008-05-30 18:46] ==> There's also a xine build of Totem available, install totem-xine instead
[2008-05-30 18:46] ==> of this package if you want xine to play your media files.
[2008-05-30 18:46]
[2008-05-30 18:46] upgraded totem (2.20.1-3 -> 2.22.2-1)
[2008-05-30 18:46] upgraded totem-plugin (2.20.1-3 -> 2.22.0-1)
[2008-05-30 18:46] Remove vi related symlinks ...
[2008-05-30 18:46] Create vi related symlinks...
[2008-05-30 18:46] Updating vi help tags...done.
[2008-05-30 18:46] upgraded vi (7.1.228-1 -> 7.1.267-1)
[2008-05-30 18:46] upgraded vino (2.20.1-1 -> 2.22.1-1)
[2008-05-30 18:46] upgraded vlc (0.8.6d-2 -> 0.8.6f-3)
[2008-05-30 18:46] upgraded wget (1.11-1 -> 1.11.2-1)
[2008-05-30 18:47] upgraded xfsprogs (2.9.4-2 -> 2.9.7-1)
[2008-05-30 18:47] upgraded xorg-apps (1.0.3-2 -> 1.0.3-3)
[2008-05-30 18:47] upgraded xproto (7.0.11-1 -> 7.0.12-1)
[2008-05-30 18:47] upgraded xtrans (1.0.4-1 -> 1.2-1)
[2008-05-30 18:47] upgraded zenity (2.20.1-1 -> 2.22.1-1)
Last edited by derelic (2008-05-31 16:17:58)

[SOLVED]Removing enlightenment and gnome...

Apologies if this has been posted already, I did a little search but couldn't find anything.
I installed arch a couple of weeks ago with enlightenment, to me it looked by far the most advanced environment to use. However there's hardly any support! They have a mailing list instead of a forum, is this 1994?
So I went and installed gnome, but it's not starting.
I just want to get rid of all of it now, gnome, enlightenment, all the rubbish along with it and install openbox then go from there.
I don't want my comp filled with random rubbish and I worry that it may be at the point where it's more beneficial to reinstall arch and start again but I know you good folks on the forum can help me avoid that monumental nooby stress that comes packaged with arch.
Cheers!
Last edited by jpjenkins (2014-04-03 18:58:31)

Thanks, I was concerned about the dependencies not removing, it makes sense to just -R the original installation!
I didn't make any effort at all henk, it's not the reason why I want to uninstall though. When gnome 3.12 is packaged up I'll give it a shot. For now, a simple window manager will suffice while I fine tune the engine.
Thanks guys.

Freenx crash in gnome remote session

I'm using freenx for acess my office computer at home. But, after gnome is update for 3.4 nxclient connect the session and crash when gnome is loading. In kde session work fine, but crash when gtk3 applications start run.

I just also noticed that opening .jpg files crashes NX.

Help - problems with GNOME 2.6 install

I just did a fresh install of Arch base packages, then xfree86. I then did pacman -Sy pacman, pacman -Syu, then pacman -S gnome
Then, while installing GNOME, my screen fills with about 500 lines of the following error:
error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: no such file or directory
Can anyone suggest a fix?

Xentac wrote:
I don't know if these are fatal errors exactly. The problem is that gnome-common installs a script in /etc/profile.d, that hasn't been run yet, to set up things like library paths. Log out and log back in, then try gnome. If that doesn't work then try running ldconfig and try again.
If it still doesn't work then it is indeed a problem that does need looking at. I've got ideas... but they're still just ideas.
Well, the gconf library errors started during the fresh install of GNOME, and all of the other errors I'm seeing when GNOME starts, as far as I can tell, point to gconf. But that's a guess on my part.
Yes, I've tried logging out, restarting, re-installing, ldconfig, but no luck.

Gnome apps crashing

Hi
I was browsing though the gnome themes when gnome-theme-manager suddenly crashed. Now I am not able to open the theme-manager or anything else gnome related. Every time I rightclick on the gnome panel - it crashes. The same goes for search for files, log out, nautilus and so on. I think the theme that I am stuck with is buggy. How can I change the theme manually? Which file do I edit?
Thank you.
By the way the theme is pretty ugly - so please help

That didn't help. I deleted the theme entries but the faulty theme presisted. But I did give me an idea I just deleted the theme from the .theme directory and voila. Thank you anyways

Udev and gnome-power-manager

Hi,
Recently I upgrade the udev from 141-5-i686 to 145-1-i686 in my MSI wind. Then the following problem begins:
When the system boots this characters can be seen in the screen just before udev is finished: ^@^@
I can add more characters during the whole boot process if I press Fn+F5 (the brightness hotkey).
When gnome is running, in few minutes the screen change the brightness very fast, like blinking. This problem only happens if the gnome-power-manager is enabled.
Downgrading udev fix the problem.
Does anyone know if this is something related with this particular version of udev, or can I do something to fix it?
I don't know if the following messages will help, because them can be seen with the current and with the old udev version. But they are the only ones that I think are related with hotkeys amb modules loading. So I post them just in case.
messages.log:
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd06/26/2008:svnMICRO-STARINTERNATIONALCO.,LTD
:pnU-100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU-100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvrVer.001:' is
not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d000027A6sv00001462sd00000110bc03sc80i00' is not a valid module or alias
name
Aug 29 14:57:02 peremsi load-modules.sh: 'platform:vesafb' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d00002448sv00000000sd00000000bc06sc04i01' is not a valid module or alias
name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0103:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0303:PNP030B:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0F03:PNP0F13:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'usb:v0C45p62C0d0100dcEFdsc02dp01ic0Eisc02ip00' is not a valid module or alias name
Aug 29 14:57:08 peremsi ntfs-3g[2611]: Version 2009.4.4 integrated FUSE 27
(so many times) This message is because the kernel do not map some hotkeys. Gnome do it.
atkbd.c: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e078 <keycode>' to make it known.

recently, I updated system, and now I have same problem like you had. I was not sure, what could cause this brightness fast changing. I thought about hal, dbus, udev. Never tried to downgrade udev. Now, I have udev 146. I am not sure what version I had before system upgrading.
Now, I have kernel 2.6.31, and I am not sure if udev 141 will work with this kernel...
I have MSI WIND, also...
Last edited by kunalagon (2010-01-08 11:15:54)

Gnome 2.12 Moving to Stable?

Hello all,
Is there an estimate as to when Gnome 2.12 will move from testing to stable?
Thanks.

When it is done, which means, operation libtool-slay is done.
Still having some issues with bad menus and interaction with KDE, I'm programming workarounds for the bad standard compatibility in KDE at this moment (got icon lookup in /opt/gnome/share/pixmaps working already, no more blank icons in KDE menus )

[request] gnome menus 2.14 and alacarte 0.9

gnome menus 2.14
http://ftp.gnome.org/pub/GNOME/sources/ … enus/2.14/
alacarte 0.9
http://www.realistanew.com/projects/alacarte/

pressh wrote:Well, if alacarte is not up to date in AUR, flag it out of date too so that I don't have to read the forum to find out
OK, will do when gnome-menus is updated

Locale bug in gnome

Hiya!
Hopefully someone can point me in the right direction on this one, it occurred with the recent X update.
I use a swedish keyboard layout that works fine outside of X. When gnome is started it assumes US layout even though swedish keymap is set in the preferences gnome-menu. If I switch it to something else and back again the problem is corrected. Running "setxkbmap" also fixes the problem. But this shouldn't be necessary on every session. Xorg.conf contains no reference to any locale and never has on this system. Any ideas?

pooflinger wrote:It works as expected, thanks chimeric.
Np, glad I could help .
pooflinger wrote:I added it, and now gnome uses the X setting instead. It's really a shame that gnome is still so utterly unstable. Maybe it's time to switch to something else...
I think this has nothing to do with Gnome because I think it always relies on the X settings and if "Xkblayout" is not set in your xorg.conf it Xorg defaults to "us" (which makes me wonder because you said it worked before - maybe your xorg.conf got b0rked after the upgrade?).

When? Gnome 2.24

Similar Messages

Maybe you are looking for