GNOME toolbar transparency and GTK themes

It seems that GNOME 2.10 toolbar transparency doesn't work with certain GTK themes. Whether or not it works does not seem to depend on the engine - some pixmap themes (e.g. Grand Canyon) don't cause problems, wheras others (Rubbersoul) inhibit toolbar transparency, leaving ugly opaque patches. Only about half of the themes that come with GNOME and gnome-themes-extras allow for complete toolbar transparency.
What's going on here? Is there any way to fix the problem?

Okay...
- Most pixmap themes don't work.
- No SVG themes seem to work.
- Industrial engine themes mostly work.
- Smooth engine themes may or may not work.
This is weird as hell.

Similar Messages

  • [SOLVED] Remove toolbar-borders in gtk-theme

    Hi, I've tried stuff with ythickness = 0 but now I'm done with it and posting here: how to remove the lines above and below the toolbar like indicated in the screenshot? Gtkrc here, it belongs to Cobra-Orange but I modified it to have transparancy and stuff. Get that Cobra theme and replace the gtkrc if you want to try for yourself.
    Last edited by VCoolio (2011-01-07 14:49:27)

    tydell wrote:I have question about something different, but also about gtk theming.
    Can you tell me how to change this one thing (that triangle in red circle)?
    That's the resize-grip. Tweaking depends on your theme engine. If it's pixmap you can gimp the .png file, else you'll need to find the right class to tweak, probably somewhere near the statusbar section. Search for "function = RESIZE_GRIP". You can disable by
    GtkStatusbar::has-resize-grip      = FALSE
    Post your gtkrc if you need more.

  • [SOLVED] Fluxbox and gtk theme

    I have a problem with fluxbox. Some programs using gtk themes (e.g. spacefm, audacious) have ugly grayish 'redmond' look. I have tried to follow this how-to:
    http://wiki.fluxbox.org/index.php?title … gtk_themes
    and also tried to switch theme with lxapperance and gtk-chtheme. No success. The gtk-chtheme shows a correct theme, so within the preview the theme is fine. However, it won't change the appearance of other windows. Some other programs like firefox or thunderbird change the theme.
    I have also tried to compile spacefm with gtk3 support and use adwaita theme. Again I got the ugly look. In other desktop managers, e.g. lxdm both spacefm and audacious look as expected.
    Last edited by kmiernik (2013-05-15 11:23:25)

    Thanks guys! It must have been something in the .config/gtk-3.0 folder. Once I removed it and created settings.ini like this one:
    [Settings]
    gtk-theme-name = Adwaita
    gtk-icon-theme-name = Tango
    gtk-fallback-icon-theme = gnome
    gtk-font-name = Sans 8
    gtk-auto-mnemonics = 1
    gtk-visible-focus = automatic
    I can have a normal appearance of gtk3 applications. Interesting thing is that this is exactly the same settings file I have tried before. Probably something else in the folder was overriding the theme.
    Last edited by kmiernik (2013-05-15 11:24:06)

  • Gnome splash screen and gtk-apps in awesome huge fonts.

    Hi all,
    I installed awesome wm the other day and for some reason all GTK-apps have huge fonts. GDM and the gnome splash screen have the same issue. I'm thinking this is a DPI issue but I wouldn't know where to start looking. Could someone point me in the right direction?
    Thanks.

    Master One wrote:
    In the meantime I swapped over to KDEMOD again, but I am still not satisfied. I prefer a mix of QT and GTK+ applications, and whatever I tried, they just do not look the same if running them in KDE or XFCE4.
    Maybe I should try running a WM instead of a DE, after some reading I am very tempted to go for Openbox.
    Can somebody running just a WM comment on the results, when mixing QT & GTK+ apps?
    I use Openbox and don't have any ugly looking apps. Granted, I think the only QT app I use is opera though

  • Tialing window managers (dwm) and gtk themes

    Is it posable to use GTK themes with tialing window managers?, i.e. to make firefox less ugly.
    Also would it be posable to combine a tialing window manager with a pannel aplication, i.e. gnome-pannel. to make a more productive desktop expiriance?
    I like tialing aplications (Blender), but sofar the tialing window managers I have tryed(wmii and dwm) dont seem terably useable. I am looking for somwthing that works more like Blender, create tiles by hovering the mouse over a border, right click, split. this prosess would be folowed in reverce to get rid of a tile. currantly running aplications can be assighned to a tile from a drop down list in the corner. aplications started from eather a terminal, or a auto hiding pannel at the top of the screen, which also displays system infomation.
    Are there any DE's like this, or should i start coding one
    Last edited by Hessiess (2008-07-22 20:34:02)

    rson451 wrote:As for the rest, I've never used Blender so I have no clue what you are talking about.
    In Blender to subdivide the main window you right click on the border between two windows and select "Split Area" from the context menu, then you move the mouse to the place you want to split and click. If you start from a horizontal border you make a vertical split, and if you start from a vertical border you make a horizontal split. To remove a division you select "Join Areas" from the same context menu, and then click the window you want to remove. Windows have a sort of menu/status bar, and it has a popup menu from which you can select any of the "programs" (3d view, text editor, preferences, &c) that are part of Blender. Window borders can be dragged for resizing, of course.
    And no, I don't know of any WM that works like this. The closest is probably StumpWM or Ratpoison—you divide and join windows in the same way, but it's keyboard controlled: "^t s" makes a horizontal split, "^t S" is vertical, and there's keystrokes for entering resize mode and removing a division as well. The keystrokes are fine for creating and deleting windows (and even better if you rebind them to use the 0, 1, 2, 3 keys like Emacs), but resizing is a pain.

  • Gnome 3.6 and Eclipse theme issue

    Hi all,
    I just upgraded to Gnome 3.6, but since then there are some issues with Eclipse buttons. Specifically, toggle buttons states for selected/not selected appear to be the same, with only the text color being slightly darker when selected. Here is a screenshot:
    This happens with both Eclipse 4.2 and 3.7, and it didn't happen on Gnome 3.4, so this should be a bug of Gnome 3.6 Adwaita theme.
    Anyone else experiencing this too?
    Thanks

    Filed a bug on Gnome's Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=687519

  • Setting the GTK theme for Chromium

    Hello,
    Apparently my Chromium installation does not correctly follow my GTK theme settings although it should according to the Chromium settings. There I defined that Chromium should use my GTK theme.
    Screenshot of the settings in Chromium and Gnome Tweak Tool: http://i.imgur.com/LK1a4fd.png
    Screenshot of how Chromium looks like: http://i.imgur.com/xL6Qi3y.png
    Look at the buttons of the context menu for example. They do not look like as if they would follow the GTK theme.
    Any ideas are appreciated.

    Toggling between classic and GTK theme does not make any difference.
    [orschiro@thinkpad ~]$ cat ~/.gtkrc-2.0
    # DO NOT EDIT! This file will be overwritten by LXAppearance.
    # Any customization should be done in ~/.gtkrc-2.0.mine instead.
    gtk-theme-name="Zukitwo"
    gtk-icon-theme-name="Faenza-Dark"
    gtk-font-name="Droid Sans 10"
    gtk-cursor-theme-name="Adwaita"
    gtk-cursor-theme-size=24
    gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
    gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
    gtk-button-images=1
    gtk-menu-images=1
    gtk-enable-event-sounds=0
    gtk-enable-input-feedback-sounds=0
    gtk-xft-antialias=1
    gtk-xft-hinting=1
    gtk-xft-hintstyle="hintfull"
    gtk-xft-rgba="rgb"
    gtk-color-scheme="tooltip_fg_color:#000000\nlink_color:#08c\nbase_color:#F7F7F7\nselected_fg_color:#f5f5f5\ntext_color:#2c2c2c\nbg_color_dark:#3f3f3f\ntext_color_dark:#FFF\nbg_color:#d4d4d4\ntooltip_bg_color:#F5F5B5\nselected_bg_color:#6699CC\nfg_color:#2c2c2c\n"
    include "/home/orschiro/.gtkrc-2.0.mine"
    [orschiro@thinkpad ~]$ cat ~/.gtkrc.mine
    cat: /home/orschiro/.gtkrc.mine: No such file or directory
    Why does it not exist? Is it not created by one of the theme choosing apps?
    [orschiro@thinkpad ~]$ ls ~/.config/gtk-2.0
    total 4
    -rw-r--r-- 1 orschiro users 292 Sep 16 19:06 gtkfilechooser.ini

  • Upgraded to Firefox 5.0. Cannot keep my refresh, stop & home buttons organised. Lost my plugin buttons (yes they ARE compatible with 5). View toolbars customise shows me them again, but the done they disappear again. Firefox 5 is buggy.

    Why have my buttons gone. No refresh, reload, stop and No plugin buttons. cannot get them back- even with view toolbars customise and dragging them back to the left because when I am 'done' they magically disappear again. Fix this bug. Help me

    Firstly, try following the instructions here:
    https://support.mozilla.com/en-US/kb/Toolbar%20keeps%20resetting
    Hopefully, after doing that, the buttons should stay where you put them.
    As far as the reload/stop buttons are concerned, they've been effectively merged into a single button. It is possible to split them though. When customising, drop a "Flexible Space" widget so that it is situated between both buttons (they always show as two separate buttons in the customisation mode).
    It's also worth noting that, if you want plugin icons to appear on a status bar, you can re-instate this behaviour with the help of the [https://addons.mozilla.org/en-US/firefox/addon/status-4-evar/ Status-4-Evar] extension.

  • Openbox Themes in gtk-theme-switch

    I've got a little problem with gtk-theme-switch, both Openbox, and gtk-theme-switch expect their respective themes to be in ~/.themes, obconf can tell the difference, and doesn't show those that won't work, gtk-theme-switch, however, shows all my Openbox themes, which it won't work with.
    I would be really grateful if someone could provide me with a solution, or of necessary, an alternate program to change GTK themes in a pure Openbox environment.

    It has two commands, switch, for old GTK1.x themes, and switch2 for GTK2 themes.
    I'll try gtk-chtheme and see if it makes any difference.
    Yep, gtk-chtheme doesn't show my Openbox themes, thanks.
    Last edited by Jaejae (2008-05-24 07:54:46)

  • Having difficulty setting up transparent GTK themes

    I've been trying to set up a minimal dark transparent GTK theme to go with my i3/tint2 setup, using compton.
    This is the theme I had in mind: http://gnome-look.org/content/show.php/?content=149606
    Unfortunately, the end result has always been a pitch black gtk theme with no transparency whatsoever :(
    The wiki, multiple forum posts, and endless RTFMing has lead me to a dead end... so I'm coming here as a last resort!

    Welcome to the Arch Linux forums!
    In such cases, it's mostly the best thing to ask the one who made those screenshots for how the transparency effect can be achieved.
    As a more general note: Given the information you have provided us, it is difficult to determine what you have already tried, hence difficult to provide any useful help.
    BaconicSynergy wrote:endless RTFMing
    Have you read the compton man page? It seems the -i option may be right for you.
    Last edited by ayekat (2015-05-04 04:53:01)

  • 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)

  • Running GNOME apps in Xfce; not detecting GTK+ theme

    I primarily use Xfce4 as my desktop environment, but with some GNOME apps such as file-roller and gedit. It appears that GNOME apps no longer detect the current GTK+ theme while using Xfce. They just use the horrible, blocky default theme. This seems to have started after an update about a month ago, and reinstalling the system didn't fix it. Has anyone else had this problem? Any help is appreciated.

    Kinux wrote:
    I had the same problem. Searching the forums, the solution for me was to :
    pacman -S gnome-themes-standard
    And then a symbolic link to gtk3 theme :
    ln -s /usr/share/themes/Adwaita/gtk-3.0 ~/.config/
    This way the new gedit or fileroller use the Adwaita theme while normal Xfce programs use the one I set in Appearance settings.
    Hope this helps you too.
    Hi，my friend, You are right! Thank you very much!!!

  • Use a gtk theme for one app and another for the whole system??

    I would like to know if is it possible to use a theme for one application and use another for the remaining of the system? I use OpenBox and I change themes with Lxappearance...
    Thanks,

    Uhh, thanks mauryck for the question and anonymous_user for the answer! I use a very slow gtk theme, and one program suffer from it, but this theme is so beautiful so I dont like to change. Never though about this solution, use a different theme only for this program!
    Sometimes the solution is so simple...

  • I have 3 computers...Window PC, PowerBook G3 (old) and MacBook Pro. I use firefox for all of them and have for quite some time. Is there a way for them all to use the same toolbar? Each of them have differnet bookmark/ settings etc.,

    I have 3 computers...Window PC, PowerBook G3 (old) and MacBook Pro. I use firefox for all of them and have for quite some time. Is there a way for them all to use the same toolbar? Each of them have differnet bookmark/ settings etc.,

    Open Media Encoder and add your Sequences:
    File > Add Premiere Pro Sequence
    Navigate to your Premiere Project and select it in the list.
    You can then select multiple Sequences from the Project (Ctrl+Click)
    and load them all at once into Media Encoder and apply
    the same encoding preset to all Sequences at the same time.

  • Shiki-colors GTK themes look like default gnome theme.

    Whenever I attempt to use the latest Shiki-colors GTK theme, setting it with LXappearance, my GTK theme instead reverts to the default gnome theme. Other themes work fine. Does anyone have an idea why this would be happening, or how to fix it?

    If I remember correctly, that theme needs the latest development version of the murrine engine from AUR (if it is the murrine version that you are trying to use).
    http://aur.archlinux.org/packages.php?ID=18624
    Last edited by testube_babies (2009-03-31 17:59:46)

Maybe you are looking for