Plugin in background

Hi.
I am building a Plugin for adobe reader and would like it to run cuntinusly in the background from when adobe reader start.
I can really find help in the documentation...
Is there an example of something?
Thanks.
Noam

If you can give specific problems with an example provided with the SDK (not found in the web) we may be able to help. There may be a few problems, but if almost none of them work for you I'd suspect a problem of setup or expectation.
Please define "does not work" for
gMyProcPtr = ASCallbackCreateProto (AVPageViewClickProc, &MyClickProc);
If it is a compile time error, please give the declaration of gMyProcPtr, the declaration line of MyClickProc,  the compiler version you are using, and the exact error messages.
If it is a run time error, what happens?

Similar Messages

  • Auto-run plugins in background tabs

    Plugins are not running automatically in background tabs. They only run if and only if I change to the tab in question. For instance, here:
    http://plug.dj/edtentertainment/
    Every time a song ends if I want the next one to load, I have to open the tab... Or even in Facebook, it only plays the new-message sound when I open the tab.
    How to enable autorun?

    Select the Advanced tab in the Preferences window and uncheck the box marked
    Stop plug-ins to save power

  • After downloading the "new version" of Java 6 times, my plugin-check page states that it has disabled my "outdated version" and asks for me to upgrade. What do?

    Background:
    I have had this problem for several months, now. This problem began when an update came for Java on the Firefox Plugin-check. I promptly installed the new Java update. But the Firefox update wouldn't register that I downloaded it, even after I refreshed the page. So, I got rid of the old Java, and downloaded the new Java again. When the page continued to display the same message it had before, I downloaded it a few more times. Finally, Firefox stopped saying that I was out of date. Then a few weeks later maybe, I check Firefox Plugin, and on the page it says that I am outdated in Java. So I downloaded Java again. But Java was still in the list, with red and said that it needed to be updated. I restarted the computer. Then, I restarted Mozilla Firefox with no add-ons. When Java still appeared that it needed to be updated, I gave up and didn't do a thing more about it.
    Problem:
    Today I decided to check my plugins. Java was not in update the list, and at the top a banner stated, "Missing JAVA? For your safety, Firefox has disabled your outdated version of Java. Please upgrade to the latest version." I clicked "upgrade to the latest version" and was led to the Java page. I clicked the download button. My cache stated that this was the (6) download of that same Java plugin (see background). I chose to re-download it anyways. But Firefox still insists that I have not downloaded it.
    Question:
    Do I need to go to the control panel of Java and change something? Do I need to fix some setting on Firefox? Should I disable Java altogether, delete all Java-related files on my computer, and start all over with Java? What should I do?

    Try using http://ninite.com/java/ninite.exe to install Java. Please note that even though you download it you have to double click it to get it to run and install.

  • What are the terminal commands to list all plugins, extensions, etc?

    I remember a while ago reading a thread on diagnosing kernel panics and such, where someone listed a number of commands (I think there were four separate terminal commands) which produced lists of plugins, daemons, background enhancers, extensions etc which could sap resources or drive up temperature without necessarily showing up in activity monitor or anything like that.
    Anyone know what these commands are? I'm having some serious overheating problems at the moment when doing nothing but for instance watching a youtube video with no other processes running so I'd like to get these dumps and see if there's anything installed which could be causing trouble.

    Check this out : http://helpx.adobe.com/story/help/keyboard-shortcuts.html

  • Eclipse RCP Application, Plugins and Classloader

    Hi there,
    I'm currently evaluatin KODO within an eclipse RCP application.
    Anything went fine until I started to modularize my classes into
    different plugins.
    Background:
    ===========
    The application consists of a "main" plugin, a "basic persistence layer"
    plugin and an "additional persitent classes" plugin.
    "basic" contains anything for kodo connections and persistence managers
    and some general persitent classes
    "additional" introduces some applicationspecific persitent classes.
    the persistent classes of any plugin are registered using
    "kodo.PersistentClasses".
    I use "kodo.ClassResolver" to point to a class
    "MultiPluginClassResolver" which inherits from
    "MultiLoaderClassResolver" and has the classloader of each plugin
    registered.
    main depends on "basic" and "additional".
    Problem:
    ========
    Whenever I instaniate a PersistenceManager from within plugin "basic"
    kodo throws a ClassNotFoundException as shown below.
    de.bioassay.pla.assay.Assay is a class from plugin "additional"
    What am I missing?
    297 WARN [main] kodo.Runtime - java.lang.ClassNotFoundException:
    de.bioassay.pla.assay.Assay
    java.lang.ClassNotFoundException: de.bioassay.pla.assay.Assay
         at serp.util.MultiClassLoader.findClass(MultiClassLoader.java:230)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:242)
         at
    kodo.runtime.PersistenceManagerFactoryImpl.loadPersistentClasses(PersistenceManagerFactoryImpl.java:208)
         at
    kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:151)
         at
    kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:104)
         at
    kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:97)
    regards
    Markus

    Hi again.
    could solve the problem on my own:
    the "additional" plugin didn't have the jdo libraries within the
    runtime classpath. The solution was to export the jdo libraries from
    within the "base" plugin.
    regards
    Markus
    M. Stier schrieb:
    Problem:
    ========
    Whenever I instaniate a PersistenceManager from within plugin "basic"
    kodo throws a ClassNotFoundException as shown below.
    de.bioassay.pla.assay.Assay is a class from plugin "additional"
    What am I missing?

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

  • Workspace problems, please help

    When I start Indesign, the only window pane I see is the application bar, but it only takes up half the screen. When I toggle through the workspace presets, nothing changes or appears. If I choose to show a specific window pane such as "layers", it appears in the center of the screen but is stacked with a bunch of other random window panes (but in a way unlike you would normally see when you drag a window into another, they are lieterally inside one another). I can however, drag them out and rearrange them, but when I relaunch ID, the same problem appears. I've tried trashing the prefs to no avail. Any ideas?

    have you tried the Reset <workspace name> command?
    if that works to rearrange the panels properly, and it doesn't stick, then you probably have a conflict with some other software. Any third party plugins? Background utilities?

  • Error Code 5 Corrupt Files

    What is wrong with this program. Major issues the past two days.

    You need to give a lot more information if you want us to help you. Start with the Version of ID (including the patch number) and your OS, and what you are doing when you see the error, and the exact error text.
    have you done any basic troubleshooting yet, like turning off plugins or background utilities that might be conflicting, undoing any changes made to your system just before the trouble began, or using a new user account on your computer as a test?

  • Conky - Certain monitors seem stuck

    I have the XFCE genmon plugin on my panel and am piping Conky's output to it. The MEM and TEMP values change, but CPU and NET don't I've tried opening and closing programs, changing the CPU part to show all my CPU cores, the values are still stuck. I've tried both running it through the genmon plugin and in the terminal and I get the same result.
    The command to start Conky:
    conky -c /home/christian/.conkyrc-genmon
    The .conkyrc file in question:
    # ~/.conkyrc-genmon
    # conky configuration for genmon plugin
    # settings
    background no
    out_to_console yes
    out_to_x no
    total_run_times 1
    uppercase no
    use_spacer none
    cpu_avg_samples 2
    net_avg_samples 2
    # output to console
    TEXT
    CPU ${cpu cpu0}% \
    MEM ${memperc}% \
    TEMP ${acpitemp}°C \
    NET \
    ${if_existing /proc/net/route wlp4s0}\
    down ${downspeed wlp4s0} up ${upspeed wlp4s0}\
    ${else}${if_existing /proc/net/route enp5s0f0}\
    down ${downspeed enp5s0f0} up ${upspeed enp5s0f0}\
    ${else}\
    unavailable\
    ${endif}${endif}
    So is this a bug in Conky, or am I missing something in my .conkyrc?
    <edit>
    If it helps, the genmon plugin is set to run Conky every second. Having Conky run every hour (3600 seconds) and changing the total_run_times to 3600 doesn't help either.
    It appears that this is not a bug in Conky but a deficiency in the genmon applet. So is there any alternative to genmon or should I hack some other way to put Conky on top of the XFCE panel?
    </edit>
    Last edited by cardinal-biggles (2013-08-27 20:55:22)

    To start, your minimum_width line is missing the underscore but that could be a typo?  The only thing that's ever cut off the width of conky for me is maximum_width so maybe you need it larger than 1200.

  • [Gnome3.2] Battery indicator gone missing

    Since trying out gnome 3.2 from the gnome-unstable repository I noticed that on my notebook the battery/power icon on top has gone missing and I can't find
    any way to talk it into showing up again. It's pretty much vanilla, I have no extensions running.
    Does anyone have any Idea why this happens and maybe how I can get it back?
    Last edited by Little (2011-09-30 00:52:36)

    Alright, the whole output.
    Another thing I noticed, during the gdm login screen the battery indicator shows correctly.
    ** (gnome-settings-daemon:1654): DEBUG: Starting settings manager
    ** (gnome-settings-daemon:1654): DEBUG: Loading settings plugins from dir: /usr/lib/gnome-settings-daemon-3.0/
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/wacom.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Wacom' file='/usr/lib/gnome-settings-daemon-3.0/wacom.gnome-settings-plugin' location='wacom'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/media-keys.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Medientasten' file='/usr/lib/gnome-settings-daemon-3.0/media-keys.gnome-settings-plugin' location='media-keys'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/smartcard.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Smartcard' file='/usr/lib/gnome-settings-daemon-3.0/smartcard.gnome-settings-plugin' location='smartcard'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/sound.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Sound' file='/usr/lib/gnome-settings-daemon-3.0/sound.gnome-settings-plugin' location='sound'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/a11y-keyboard.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Barrierefreie Tastatur' file='/usr/lib/gnome-settings-daemon-3.0/a11y-keyboard.gnome-settings-plugin' location='a11y-keyboard'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/clipboard.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Zwischenablage' file='/usr/lib/gnome-settings-daemon-3.0/clipboard.gnome-settings-plugin' location='clipboard'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/orientation.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Orientation' file='/usr/lib/gnome-settings-daemon-3.0/orientation.gnome-settings-plugin' location='orientation'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/xsettings.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='X-Einstellungen' file='/usr/lib/gnome-settings-daemon-3.0/xsettings.gnome-settings-plugin' location='xsettings'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/color.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Farbe' file='/usr/lib/gnome-settings-daemon-3.0/color.gnome-settings-plugin' location='color'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/print-notifications.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Drucker-Benachrichtigungen' file='/usr/lib/gnome-settings-daemon-3.0/print-notifications.gnome-settings-plugin' location='print-notifications'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/xrandr.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='XRandR' file='/usr/lib/gnome-settings-daemon-3.0/xrandr.gnome-settings-plugin' location='xrandr'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/cursor.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Cursor' file='/usr/lib/gnome-settings-daemon-3.0/cursor.gnome-settings-plugin' location='cursor'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/power.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Energie' file='/usr/lib/gnome-settings-daemon-3.0/power.gnome-settings-plugin' location='power'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/housekeeping.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Housekeeping' file='/usr/lib/gnome-settings-daemon-3.0/housekeeping.gnome-settings-plugin' location='housekeeping'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/keybindings.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Tastenkürzel' file='/usr/lib/gnome-settings-daemon-3.0/keybindings.gnome-settings-plugin' location='keybindings'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/a11y-settings.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Barrierefreiheits-Einstellungen' file='/usr/lib/gnome-settings-daemon-3.0/a11y-settings.gnome-settings-plugin' location='a11y-settings'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/keyboard.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Keyboard' file='/usr/lib/gnome-settings-daemon-3.0/keyboard.gnome-settings-plugin' location='keyboard'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/background.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Hintergrund' file='/usr/lib/gnome-settings-daemon-3.0/background.gnome-settings-plugin' location='background'
    ** (gnome-settings-daemon:1654): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-3.0/mouse.gnome-settings-plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsPluginInfo: name='Mouse' file='/usr/lib/gnome-settings-daemon-3.0/mouse.gnome-settings-plugin' location='mouse'
    ** (gnome-settings-daemon:1654): DEBUG: Plugin power: inactive
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ab5f68 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libcolor.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdColorPlugin
    (gnome-settings-daemon:1654): color-plugin-DEBUG: GsdColorPlugin initializing
    (gnome-settings-daemon:1654): color-plugin-DEBUG: Activating color plugin
    (gnome-settings-daemon:1654): color-plugin-DEBUG: Starting color manager
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated color
    ** (gnome-settings-daemon:1654): DEBUG: Plugin color: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0xb4c01a50 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/liborientation.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdOrientationPlugin
    (gnome-settings-daemon:1654): orientation-plugin-DEBUG: GsdOrientationPlugin initializing
    (gnome-settings-daemon:1654): orientation-plugin-DEBUG: Activating orientation plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated orientation
    ** (gnome-settings-daemon:1654): DEBUG: Plugin orientation: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0xb4c01ac8 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libxrandr.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdXrandrPlugin
    (gnome-settings-daemon:1654): xrandr-plugin-DEBUG: GsdXrandrPlugin initializing
    (gnome-settings-daemon:1654): xrandr-plugin-DEBUG: Activating xrandr plugin
    (gnome-settings-daemon:1654): xrandr-plugin-DEBUG: Starting xrandr manager
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated xrandr
    ** (gnome-settings-daemon:1654): DEBUG: Plugin xrandr: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0xb4c01cc8 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GnomeXSettingsPlugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeXSettingsPlugin initializing
    ** (gnome-settings-daemon:1654): DEBUG: Activating xsettings plugin
    ** (gnome-settings-daemon:1654): DEBUG: Starting xsettings manager
    ** (gnome-settings-daemon:1654): DEBUG: GsdXSettingsGtk initializing
    ** (gnome-settings-daemon:1654): DEBUG: Setting GTK modules ''
    ** (gnome-settings-daemon:1654): DEBUG: xft_settings_set_xresources: orig res 'Xft.dpi: 96
    Xft.antialias: 1
    Xft.hinting: 1
    Xft.hintstyle: hintslight
    Xft.rgba: rgb
    ** (gnome-settings-daemon:1654): DEBUG: xft_settings_set_xresources: new res 'Xft.dpi: 96
    Xft.antialias: 1
    Xft.hinting: 1
    Xft.hintstyle: hintslight
    Xft.rgba: rgb
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated xsettings
    ** (gnome-settings-daemon:1654): DEBUG: Plugin xsettings: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace6c8 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libsound.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdSoundPlugin
    (gnome-settings-daemon:1654): sound-plugin-DEBUG: GsdSoundPlugin initializing
    (gnome-settings-daemon:1654): sound-plugin-DEBUG: Activating sound plugin
    (gnome-settings-daemon:1654): sound-plugin-DEBUG: Starting sound manager
    (gnome-settings-daemon:1654): sound-plugin-DEBUG: Registering directory monitor for /home/little/.local/share/sounds
    (gnome-settings-daemon:1654): sound-plugin-DEBUG: Registering directory monitor for /usr/share/
    (gnome-settings-daemon:1654): sound-plugin-DEBUG: Registering directory monitor for /usr/local/share/
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated sound
    ** (gnome-settings-daemon:1654): DEBUG: Plugin sound: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace650 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libkeyboard.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdKeyboardPlugin
    (gnome-settings-daemon:1654): keyboard-plugin-DEBUG: GsdKeyboardPlugin initializing
    (gnome-settings-daemon:1654): keyboard-plugin-DEBUG: Activating keyboard plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated keyboard
    ** (gnome-settings-daemon:1654): DEBUG: Plugin keyboard: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace628 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libwacom.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdWacomPlugin
    (gnome-settings-daemon:1654): wacom-plugin-DEBUG: GsdWacomPlugin initializing
    (gnome-settings-daemon:1654): wacom-plugin-DEBUG: Activating wacom plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated wacom
    ** (gnome-settings-daemon:1654): DEBUG: Plugin wacom: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace600 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libmouse.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdMousePlugin
    (gnome-settings-daemon:1654): mouse-plugin-DEBUG: GsdMousePlugin initializing
    (gnome-settings-daemon:1654): mouse-plugin-DEBUG: Activating mouse plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated mouse
    ** (gnome-settings-daemon:1654): DEBUG: Plugin mouse: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8acc3b8 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/liba11y-settings.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdA11ySettingsPlugin
    (gnome-settings-daemon:1654): ally-settings-plugin-DEBUG: GsdA11ySettingsPlugin initializing
    (gnome-settings-daemon:1654): ally-settings-plugin-DEBUG: Activating a11y-settings plugin
    (gnome-settings-daemon:1654): ally-settings-plugin-DEBUG: Starting a11y_settings manager
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated a11y-settings
    ** (gnome-settings-daemon:1654): DEBUG: Plugin a11y-settings: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace6f0 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/liba11y-keyboard.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdA11yKeyboardPlugin
    ** (gnome-settings-daemon:1654): DEBUG: GsdA11yKeyboardPlugin initializing
    ** (gnome-settings-daemon:1654): DEBUG: Activating a11y_keyboard plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated a11y-keyboard
    ** (gnome-settings-daemon:1654): DEBUG: Plugin a11y-keyboard: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace718 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libsmartcard.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdSmartcardPlugin
    (gnome-settings-daemon:1654): smartcard-plugin-DEBUG: GsdSmartcardPlugin initializing
    (gnome-settings-daemon:1654): smartcard-plugin-DEBUG: initializing smartcard manager
    (gnome-settings-daemon:1654): smartcard-plugin-DEBUG: GsdSmartcardPlugin Not activating smartcard plugin, because user didn't use smartcard to log in
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated smartcard
    ** (gnome-settings-daemon:1654): DEBUG: Plugin smartcard: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace740 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libkeybindings.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdKeybindingsPlugin
    (gnome-settings-daemon:1654): keybindings-plugin-DEBUG: GsdKeybindingsPlugin initializing
    (gnome-settings-daemon:1654): keybindings-plugin-DEBUG: Activating keybindings plugin
    (gnome-settings-daemon:1654): keybindings-plugin-DEBUG: Starting keybindings manager
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated keybindings
    ** (gnome-settings-daemon:1654): DEBUG: Plugin keybindings: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace768 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libbackground.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdBackgroundPlugin
    ** (gnome-settings-daemon:1654): DEBUG: GsdBackgroundPlugin initializing
    ** (gnome-settings-daemon:1654): DEBUG: Activating background plugin
    ** (gnome-settings-daemon:1654): DEBUG: Starting background manager
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated background
    ** (gnome-settings-daemon:1654): DEBUG: Plugin background: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace8a0 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdMediaKeysPlugin
    (gnome-settings-daemon:1654): media-keys-plugin-DEBUG: GsdMediaKeysPlugin initializing
    (gnome-settings-daemon:1654): media-keys-plugin-DEBUG: Activating media_keys plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated media-keys
    ** (gnome-settings-daemon:1654): DEBUG: Plugin media-keys: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace918 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libcursor.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdCursorPlugin
    (gnome-settings-daemon:1654): cursor-plugin-DEBUG: GsdCursorPlugin initializing
    (gnome-settings-daemon:1654): cursor-plugin-DEBUG: Activating cursor plugin
    (gnome-settings-daemon:1654): cursor-plugin-DEBUG: Starting cursor manager
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated cursor
    ** (gnome-settings-daemon:1654): DEBUG: Plugin cursor: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace800 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libprint-notifications.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdPrintNotificationsPlugin
    (gnome-settings-daemon:1654): print-notifications-plugin-DEBUG: Activating print-notifications plugin
    (gnome-settings-daemon:1654): print-notifications-plugin-DEBUG: Starting print-notifications manager
    (gnome-settings-daemon:1654): print-notifications-plugin-DEBUG: Connection to CUPS server 'localhost' failed.
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated print-notifications
    ** (gnome-settings-daemon:1654): DEBUG: Plugin print-notifications: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8acc2f0 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libclipboard.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdClipboardPlugin
    (gnome-settings-daemon:1654): clipboard-plugin-DEBUG: GsdClipboardPlugin initializing
    (gnome-settings-daemon:1654): clipboard-plugin-DEBUG: Activating clipboard plugin
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated clipboard
    ** (gnome-settings-daemon:1654): DEBUG: Plugin clipboard: active
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsModule 0x8ace9b8 initialising
    ** (gnome-settings-daemon:1654): DEBUG: Loading /usr/lib/gnome-settings-daemon-3.0/libhousekeeping.so
    ** (gnome-settings-daemon:1654): DEBUG: Creating object of type GsdHousekeepingPlugin
    (gnome-settings-daemon:1654): housekeeping-plugin-DEBUG: GsdHousekeepingPlugin initializing
    (gnome-settings-daemon:1654): housekeeping-plugin-DEBUG: Activating housekeeping plugin
    (gnome-settings-daemon:1654): housekeeping-plugin-DEBUG: Starting housekeeping manager
    (gnome-settings-daemon:1654): housekeeping-plugin-DEBUG: housekeeping: will tidy up in 2 minutes
    ** (gnome-settings-daemon:1654): DEBUG: GnomeSettingsManager: emitting plugin-activated housekeeping
    ** (gnome-settings-daemon:1654): DEBUG: Plugin housekeeping: active
    ** (gnome-settings-daemon:1654): DEBUG: Updating client: index=0 name='ConsoleKit Session /org/freedesktop/ConsoleKit/Session2'
    ** (gnome-settings-daemon:1654): DEBUG: Updating client: index=3 name='GNOME Shell'
    ** (gnome-settings-daemon:1654): DEBUG: Updating client: index=6 name='XSMP Session on gnome-session as 10aeb7e509fa8e773c131723457678688800000013710026'
    ** (gnome-settings-daemon:1654): DEBUG: Updating client: index=7 name='GNOME Shell Volume Control'
    ** (gnome-settings-daemon:1654): DEBUG: Updating client: index=9 name='gnome-session'
    ** (gnome-settings-daemon:1654): DEBUG: Updating client: index=10 name='GNOME Shell'
    ** (gnome-settings-daemon:1654): DEBUG: Updating client: index=11 name='GNOME Volume Control Media Keys'
    ** (gnome-settings-daemon:1654): DEBUG: Updating sink: index=0 name='alsa_output.pci-0000_00_1b.0.analog-stereo' description='Internes Audio Analog Stereo' map='front-left,front-right'
    ** (gnome-settings-daemon:1654): DEBUG: ConsoleKit session ID: /org/freedesktop/ConsoleKit/Session2
    (gnome-settings-daemon:1654): color-plugin-DEBUG: connected to colord
    (gnome-settings-daemon:1654): color-plugin-DEBUG: /home/little/.color/icc does not exist, so skipping
    ** (gnome-settings-daemon:1654): DEBUG: Updating source: index=0 name='alsa_output.pci-0000_00_1b.0.analog-stereo.monitor' description='Monitor of Internes Audio Analog Stereo'
    ** (gnome-settings-daemon:1654): DEBUG: Updating source: index=1 name='alsa_input.pci-0000_00_1b.0.analog-stereo' description='Internes Audio Analog Stereo'
    ** (gnome-settings-daemon:1654): DEBUG: Registered client at path /org/gnome/SessionManager/Client9
    (gnome-settings-daemon:1654): color-plugin-DEBUG: Done switch to new account, reload devices
    ** (gnome-settings-daemon:1654): DEBUG: Udpating card alsa_card.pci-0000_00_1b.0 (index: 0 driver: module-alsa-card.c):
    ** (gnome-settings-daemon:1654): DEBUG: Profile 'output:analog-stereo': 0 sources 1 sinks
    ** (gnome-settings-daemon:1654): DEBUG: Profile 'output:analog-stereo+input:analog-stereo': 1 sources 1 sinks (Current)
    ** (gnome-settings-daemon:1654): DEBUG: Profile 'input:analog-stereo': 1 sources 0 sinks
    ** (gnome-settings-daemon:1654): DEBUG: Profile 'off': 0 sources 0 sinks
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'alsa.card' = '0'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'alsa.card_name' = 'HDA Intel'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'alsa.long_card_name' = 'HDA Intel at 0xf6fdc000 irq 48'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'alsa.driver_name' = 'snd_hda_intel'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.bus_path' = 'pci-0000:00:1b.0'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'sysfs.path' = '/devices/pci0000:00/0000:00:1b.0/sound/card0'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.bus' = 'pci'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.vendor.id' = '8086'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.vendor.name' = 'Intel Corporation'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.product.id' = '293e'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.product.name' = '82801I (ICH9 Family) HD Audio Controller'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.form_factor' = 'internal'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.string' = '0'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.description' = 'Internes Audio'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'module-udev-detect.discovered' = '1'
    ** (gnome-settings-daemon:1654): DEBUG: Property: 'device.icon_name' = 'audio-card-pci'
    (gnome-settings-daemon:1654): orientation-plugin-DEBUG: Did not find an accelerometer
    (gnome-settings-daemon:1654): keyboard-plugin-DEBUG: Starting keyboard manager
    (gnome-settings-daemon:1654): mouse-plugin-DEBUG: Setting accel -1/-1, threshold -1 for device 'AlpsPS/2 ALPS DualPoint TouchPad'
    (gnome-settings-daemon:1654): mouse-plugin-DEBUG: Setting accel 5/2, threshold 1 for device 'DualPoint Stick'
    (gnome-settings-daemon:1654): mouse-plugin-DEBUG: Setting accel 5/2, threshold 1 for device 'Virtual core XTEST pointer'
    ** (gnome-settings-daemon:1654): DEBUG: Starting a11y_keyboard manager
    (gnome-settings-daemon:1654): media-keys-plugin-DEBUG: Starting media_keys manager
    (gnome-settings-daemon:1654): media-keys-plugin-DEBUG: Unable to parse hard-coded key 'XF86AudioRepeat' (1)
    (gnome-settings-daemon:1654): media-keys-plugin-DEBUG: Unable to parse hard-coded key 'XF86AudioRandomPlay' (1)
    (gnome-settings-daemon:1654): media-keys-plugin-DEBUG: Unable to parse hard-coded key 'XF86Hibernate' (1)
    (gnome-settings-daemon:1654): media-keys-plugin-DEBUG: adding key filter for screen: 0
    (gnome-settings-daemon:1654): cursor-plugin-DEBUG: Did not find a touchscreen, will not hide the cursor
    ** (gnome-settings-daemon:1654): DEBUG: Updating client: index=10 name='GNOME Shell'
    ** (gnome-settings-daemon:1654): DEBUG: Updating sink: index=0 name='alsa_output.pci-0000_00_1b.0.analog-stereo' description='Internes Audio Analog Stereo' map='front-left,front-right'
    ** (gnome-settings-daemon:1654): DEBUG: Updating source: index=0 name='alsa_output.pci-0000_00_1b.0.analog-stereo.monitor' description='Monitor of Internes Audio Analog Stereo'

  • Colour background for quicktime plugin and favicons

    Hi, a trivial query. I have seen some sites where the background colour for the quicktime plugin player is black not white. On my proto site http://www.goldenumber.co.uk/beermatts_trumpet_pages/ if you click on the midi files the player has a white background which I would prefer to be black. Do I need to edit the midi file itself? Any suggestions gratefully received.
    Secondly, when I access the midi files or the pdfs I lose my favicon image in the address bar. Is there a way around this?
    Regards, Matt.

    I still see a white background when I click on a MIDI file link.
    Unless you place the MIDI file in a web page (such as with EMBED SRC), you cannot control how the MIDI player plugin will display in the browser. Look at the zianet.com page linked above for an example. The directory web page is black (with text and graphics) and plays 'Hold on to the Night' in the background because it is embedded in the HTML.
    If you want to control the appearance, you need to create a new HTML page for each MIDI file.
    Example:
    Create a new file called '
    The_Fields_of_Athenry.html' and use the following example HTML...
    <html><head>
    <title>The Fields of Athenry</title></head>
    <body bgcolor="black">
    <EMBED SRC="http://www.goldenumber.co.uk/beermatts_trumpet_pages/midis/The_Fields_of_Athenry.mid " AUTOSTART="true" HIDDEN="false" Width="145" Height="24">
    </body>
    </html>
    Link to this HTML file instead of the MIDI file.

  • Xfapplet plugin has a white background

    Hello, all
    I use the Xfce panel in Openbox. Recently, I was fed up with the standard Xfce menu, so I tried some alternatives. So far, the only one I can get to work is mintMenu. It worked fine with the MATE panel. But, I prefer the Xfce panel, so I installed xfce4-xfapplet-plugin-mate from the AUR, and put the mintMenu in the Xfce panel.
    It works just fine with one really annoying problem: I have a translucent black panel, and the menu icon has a white background.
    I have tried different images of different types, so I know it isn't a problem with my image. Also, when I add text, the text has the white background. In MATE, the translucency works fine.
    When I right-click on the applet, and, under Xfapplet, select 'Properties', nothing comes up. However, in the panel preferences, when I select the applet, and click on the 'Properties' button, a frame pops up in which I can select which app I want. But, nothing about the background color. I can't find any setting in the MATE control center, Xfce control center, gconf, or dconf relating to Xfapplet.
    Any help would be greatly appreciated.

    Can you send me your sample code on how to get a background color for SwingRadioButton. I just wrote small fx program. you can modify and give it to me.
    * Main.fx
    * Created on Feb 25, 2009, 8:41:46 PM
    package swingradiobuttonsample;
    import javafx.ext.swing.SwingRadioButton;
    import javafx.scene.Group;
    import javafx.scene.paint.Color;
    import javafx.scene.Scene;
    import javafx.scene.text.Font;
    import javafx.scene.text.Text;
    import javafx.stage.Stage;
    Stage {
        title: "Application title"
        width: 550
        height: 400
        scene: Scene {
            fill: Color.BLACK
            content: Group {
                content: [
                    Text {
                        font: Font {
                            size: 16
                        x: 10,
                        y: 30
                        content: "Application content"
                    SwingRadioButton {
                        translateX: 50
                        translateY: 50
                        text: "Radio Button 1"
    }

  • Just updated to 8 & now I can't open any web pages & firefox is still running in the background after browser was closed. I uninstalled and reinstalled as well as disabled add-ons and plugins nothing has changed, can I downgrade back to on older version?

    Just updated to 8 & now I can not open any web pages as well as firefox will not close out, it still running in the background after browser was closed. I uninstalled and reinstalled as well as disabled add-ons and plugins nothing has changed, can I downgrade back to on older version?

    See "Hang at exit":
    *http://kb.mozillazine.org/Firefox_hangs
    See "Firefox hangs when you quit it":
    *https://support.mozilla.com/kb/Firefox+hangs
    A possible cause is security software (firewall) that blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.
    Remove all rules for Firefox from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.
    See:
    *https://support.mozilla.com/kb/Server+not+found
    *https://support.mozilla.com/kb/Firewalls

  • Running plugin continuously in the background

    Hello, I'm just starting out trying to make a plugin for Illustrator CC and have been a bit stuck the past few days, so I have a few questions.  The plugin I'm trying to make would have it where when you mouse over a path, an annotation pops up to display the length of the path, reguardless of what tool you have selected. 
    The major question I have is if it is possible to make a plugin that runs in the background without having to select it as a tool?
    I've been going over the SDK and guides and have tried altering the annotator sample project along with trying to make it from scratch, but I haven't gotten the results I want.  I got Annotator to display the length of paths, but I can't remove it's tool properties or make it run like it's always selected.  When I've been tryng to build from scratch, I don't see how to track the cursor since it seems to need the AIToolSuite.  I've also tried to use AINotifierSuite with kAIArtSelectionChangedNotifier, but haven't gotten it to work correctly and it wouldn't work just by mousing over paths if I had.
    Anyway, I was wondering if you guys would be able to point me in the right direction on making this because it seems like it shouldn't be nearly as difficult as it has been for me.
    Details:
    OSX 10.9.1
    XCode 5.0.2
    Illustrator CC 17.0.0

    You have to read carefully the sdk documentation (programmers guide). Illustrator plugin system is described.
    What is a plugin, types of plugins, how it works, how it is loaed, ...... You will learn many, many things.
    A plugin could be loaded during Illustrator startup and only unloaded at Illustrator shutdown. This plugin could do his "magic" during all that session. And It does not have to be a tool. 
    Notifiers:
    Plugin must register for the notifiers in which it is interested. The Notifier Suite is used to register and remove notification requests. (See AINotifierSuite).
    Here it is a sample how it sould be implemented in your plugin.
    myPlugin.h:
    //Methods to be implemented.
    ASErr StartupPlugin(SPInterfaceMessage* message);
    ASErr AddNotifiers(SPInterfaceMessage* message);
    ASErr Notify(AINotifierMessage* message);
    myPlugin.cpp:
    1- During startup, you have to register to notifications. (AddNotifiers).
    ASErr
    myPlugin::StartupPlugin(SPInterfaceMessage *message)
          ASErr error = Plugin::StartupPlugin( message );
          if (error) { return error; }
          error = AddNotifiers(message);
          if (error) { return error; }
         return error;
         // If StartupPlugin returns an error instead of kNoErr, Illustrator
         // will try to load this plug-in again later.
    2- subscribe to notifiers.  kAICSXSPlugPlugSetupCompleteNotifier in this sample.
    ASErr
    myPlugin::AddNotifiers(SPInterfaceMessage* message)
              ASErr error = kNoErr;
         error = sAINotifier->AddNotifier(message->d.self, "myPlugin" kAICSXSPlugPlugSetupCompleteNotifier,
                                 kAICSXSPlugPlugSetupCompleteNotifier, &fCSXSPlugPlugSetupCompleteNotifier);
                  if (error) { return error; }
         return error;
    3- handler (when the notification has been raised).
    ASErr
    myPlugin::Notify(AINotifierMessage* message)
              ASErr error = kNoErr;
                   if ( message->notifier == fCSXSPlugPlugSetupCompleteNotifier )
                //Do the magic here..........    
         return error;
    I hope this will help.
    Thomas.

  • How can I disable the plugin-container.exe that, runs in the background?

    Every time I click on a url, the browser freezes up momentarily and then loads the page and this is constant and I have the feeling is because of plugin-container.exe running in the background. Please advice. Thanks!!
    [email protected]

    That process is from firefox, firefox now loads the plugins in another proccess.
    Try to start firefox in safe mode to check if that process runs again.

Maybe you are looking for

  • "Convert Text to Table" Size limit issue?

    Alphabetize a List I've been using this well known work around for years. Select your list and in the Menu bar click Format>Table>Convert Text to Table Select one of the column's cells (1st click selects entire table, 2nd click selects individual cel

  • Simple question about data selection in a query

    Hi everybody, I've got the requirement to change an existing query with the query designer. It be possible to display data (i.e. sales) just for the last 3 month (actual month minus 3). What is the best approach? A colleague advised me to do with a v

  • Wireless Losing Signal in Tiger and Leopard,

    OK, So, my MBP started dropping my signal in the house two days ago, spent 2 hrs on phone with apple care only to be told to go to apple store and see genius..Genius said wireless card bad, and replaced within 2 hours, said it was good to go! Get hom

  • How to make image box edge rounded

    hi i have repeated region has image boxes i want to make the image box edge rounded thanks in advance .

  • Clock n95

    Hi Please could someone advise me to get a new analogue clock do I have to install a full new theme ? - I am looking for a good analogue clock with 2 10 20 25 etc minute markers MTIA Steve