[solved/cannot be solved]Xorg-server and gnome-power-manager

I was wondering if there is hope that someone will put patches to main tree of Xorg-server which are here: http://blogs.gnome.org/hughsie/2009/08/ … of-bodges/
It should remove this weird blanking effect and time gap before screen is backlighted again. I didn't tested it, because it requires rebuild of xorg-server and I don't want to use git version, but guys there says that it's working.
Last edited by megawebmaster (2010-02-08 22:24:26)

OK, thanks for advice, I'll try building xorg-server with ABS.
I've got another problem with automatic turn off screen - media players don't prevent turning screen off while they are playing film. Is there any possibility to fix it? Only way I've found is to turn off automatic screen backlight off after couple of minutes, but it's not how tigers want this to work

Similar Messages

  • Udev and gnome-power-manager

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

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

  • [Solved]Xorg-server and nvidia binary driver don't work

    See topic. When updating to xf86-input-evdev-2.8.2-2  xf86-input-joystick-1.6.2-3  xf86-input-keyboard-1.8.0-2  xf86-input-mouse-1.9.0-2 and xorg-server-1.15.0-1 X won't start and 'systemctl status kdm.service' states that the X server has died. According to Phoronix this should not happen.
    Harvey
    Last edited by Harey (2014-01-14 11:06:53)

    The ABI check is there for a purpose:
    [ 38.018] Loading extension NV-GLX
    [ 38.027] (EE)
    [ 38.027] (EE) Backtrace:
    [ 38.029] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x5834c8]
    [ 38.029] (EE) 1: /usr/bin/X (0x400000+0x1871a9) [0x5871a9]
    [ 38.029] (EE) 2: /usr/lib/libpthread.so.0 (0x7ff70edbf000+0xf870) [0x7ff70edce870]
    [ 38.029] (EE) 3: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7ff708c51000+0x4e427f) [0x7ff70913527f]
    [ 38.029] (EE) 4: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7ff708c51000+0x4eb501) [0x7ff70913c501]
    [ 38.029] (EE) 5: /usr/bin/X (AddScreen+0x71) [0x435c81]
    [ 38.029] (EE) 6: /usr/bin/X (InitOutput+0x3df) [0x4769df]
    [ 38.029] (EE) 7: /usr/bin/X (0x400000+0x3961b) [0x43961b]
    [ 38.029] (EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff70dc35b05]
    [ 38.029] (EE) 9: /usr/bin/X (0x400000+0x24dae) [0x424dae]
    [ 38.029] (EE)
    [ 38.029] (EE) Segmentation fault at address 0x18
    [ 38.029] (EE)
    Fatal server error:
    [ 38.029] (EE) Caught signal 11 (Segmentation fault). Server aborting
    Seems we have to wait for nvidia to include xorg-server 1.15 into their driver
    Harvey

  • Gnome-power-manager 2.26 does not suspend on idle

    I got a problem with gnome-power-manager 2.26 (several Versions 2.26.0 2.26.1 2.26.2 (original PKGBUILD)). I can suspend from the applet menu. It does hibernate on critical bat level, but i does not suspend on idle, regardless what timeout values I set in screensaver and gnome-power-manager. Display sleep seems to work though. First I thought, this might be only an issue on my particular notebook, as I could not find anything on google about this, but it is the same behavior on my freshly installed desktop system.
    gnome-power-manager --verbose outputs nothing about going to standby.
    I built gnome-power-manager and gnome-screensaver from 2.24 and they do work porperly, except the notebook will not hibernating on crit bat level.
    Hardware:
    Notebook: HP Pavilion dv3550eg (centrino2 - Nvidia 9300M GS)
    Desktop: GB AMD 790XT, Phenom 720, Nvidia GTX 260
    Software:
    Arch64
    Might this be an Policy issue? Nevertheless if anyone out there has has this problem, let me know and i am goning to file a bug report.

    uwinkelvos wrote:I filed a bugrepoert about this: http://bugs.archlinux.org/task/15038
    anyone willing and able to have a look at the sources is welcome... i just do not have the skills and tools to get to the right conclusion.
    is a well know upstream problem. you should have been fill/comment on bugzilla bugtracker because is not archlinux fault.
    http://bugzilla.gnome.org/buglist.cgi?q … r-manager+
    http://blogs.gnome.org/hughsie/2009/05/ … tableness/

  • Xfce4 and gnome-network-manager [solved]

    I just made a clean install of archlinux. installed xorg and Xfce4, xfce-goodies, gnome-panel, gnome-desktop and gnome-network-manager. also I enabled GNOME services in startup and sessions. how do I start that network manager now? is nowhere in the settings, nor there is icon to add to the taskbar (i got xfapplets installed too)
    Last edited by anarxi (2009-01-14 00:22:42)

    quoted from a previous thread
    I solved it by uncommenting my <locale><charset> in /etc/locale.gen.
    First you have to enable the locales you want being supported by your system. To enable or disable them, the file /etc/locale.gen is used. It contains every locale you can enable, and you have just to uncomment lines you want to do so.
    As we want to setup an english UTF-8 conform system, we want to enable en_US.UTF-8. But for compatibility to programs that don't support UTF-8 yet, it's recommended to support any other locale, prefixed with en_US as well. Having this in mind, we enable this set of locales:
    en_US.UTF8 UTF-8
    en_US ISO-8859-1
    After you've enabled the necessary locales, you have to run locale-gen as root to update them:
    # sudo locale-gen
    Generating locales...
    en_US.UTF-8... done
    en_US.ISO-8859-1... done
    Generation complete.

  • [Solved] xorg server & keyboard conf error messages after upgrade

    I ran my daily upgrade (today was big, from FF to the kernel to xorg) and I was not able to login on GDM afterwards.
    It's weird. The X server will start, and so will the GDM login screen. But entering the password will result in a GDM crash (I later found out that KDM and SLIM have the same issue; KDM not starting and SLIM refusing the keyboard input). So after starting an alternate console and trying to start x (startx), I have this error message:
    "Th e XKEYBOARDMAP keymap compiler (xbcomp) reports:
    Error: Cannot close "/tmp/server-0.xkm" properly (not enough space?)
              Output file "/tmp/server-0.xkm" removed
    Errors from xkbcomp are not fatal to the X server
    XKB: Failed to compile keymap
    Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
    Fatal server error:
    Failed to activate core devices "
    I have been fiddling with the keyboard config on xorg.conf but I'm not sure I'm getting anywhere. Also, I downgraded the xorg-server and xkeyboard config packages just to be sure.
    Any clue?
    Thanks!
    Last edited by southerncross (2012-07-24 15:46:38)

    Well... seems I didn't have any answer on this. I fiddled a bit more but I have to say that I really came to wits' end at this stage. A couple of observations though:
    * I don't really understand this notion of a keyboard issue. My keyboard and its layout work properly but I will not be able to login regardless of login through GDM, KDM or Slim. Yet it's worth noting that in the case of GDM and SLIM the X server starts; I see the graphical interface, I click, etc. but when I type the trouble starts.
    * I tried to check my xsessions-errors file. The file is really big under a frame buffer, and it wasn't clear to me, but I found strange that the log was reporting all sorts of attempts to start KDE. I don't exactly know what's going on.
    If anybody has any clue, let me know... It's becoming very frustrating.
    Thanks!

  • ['Solved'] xorg-server 1.9.0-1 split into several xorg servers

    So what's up with the [Testing]'s xorg-server 1.9(.0-1) being split into xorg-server/-common/-devel/-xdmx/-xephyr/-xnest/-xvfb?
    Last edited by algorythm (2010-08-24 16:24:35)

    nvidia doesn't get built, just repackaged, so it doesn't require any xorg-server-* stuff to build. The -devel package is required to build drivers from source. The xorg-server and xorg-server-common packages are the usual packages that will become installed on all desktop systems.

  • SOLVE strange problem with suspend and resume with gnome-power-manager

    I have pm-utils and gnome installed.
    Suspending and hibernation works well from the command line ($ pm-hibernate and $ pm-suspend).  Resuming works without any problems.
    Suspending from gnome "Shutdown dialog" works perfectly as well.
    However, if suspending is initiated by gnome-power-manager something strange happens:  After pressing the power button resuming switches to hibernation and my laptop turns off.  Resuming from disk works fine again.
    Now, suspending works fine again if I change and save any config file in /etc/pm/.
    Here comes the strange thing:  It doesn't really matter what I change as long as I save it.
    However, as soon as I reboot resuming fails again the way I described above.
    Anyone have a clue what's going on?
    I get no error messages and I've tried all sorts of boot entries.
    Last edited by mehldutt (2007-12-26 19:42:31)

    After some try and error my guess is that "HAL" is responsible for this problem:
    I deinstalled ACPID and 'pm-utils' and switched to 'uswsusp'.
    I made the appropriate changes to the appropriate hal-scrips
    usr/lib/hal/scripts/hal-system-power-suspend:
    #!/bin/sh
    /sbin/s2ram --force
    usr/lib/hal/scripts/hal-system-power-hibernate:
    #!/bin/sh
    /sbin/s2disk
    After these changes I still have the same problem:  immidiatly after resuming form suspend (via power-button) my laptop hibernates (s2disk).
    However, if I delete all entries in "usr/lib/hal/scripts/hal-system-power-hibernate" resuming from suspend works fine again, but hibernate doesn't of course.  So, some script must be calling "usr/lib/hal/scripts/hal-system-power-hibernate" emmediatly after resuming from suspend.
    A couple of weeks ago everything worked fine.  My guess is that one of the recent hal-updates is causing this.
    How can I figure what script is calling "usr/lib/hal/scripts/hal-system-power-hibernate" after resuming from suspend?

  • [SOLVED] GNOME Power Manager Icon

    Hello,
    With the recent influx of GNOME 2.22 packages, gnome-power-manager has begun to behave strangely on my system.
    In gnome-power-preferences, I have specified that the notification area icon should only be displayed when my laptop battery is charging or discharging. Since I upgraded my GNOME packages, the icon has always appeared in my notication area upon login -- even if I am running on AC power. In that situation, the tooltip for the icon reads as follows:
    Computer is running on AC power
    Laptop batteries discharging (100%)
    Battery discharge time is currently unknown
    If I unplug the power cord from my computer,  the icon (strangely) disappears. If I then proceed to plug the cord back in, the icon will appear briefly (I assume to indicate that what little power was drained from the battery is being replenished) and then disappear once more.
    This problem is occurring on a Dell Inspiron 6400 (E1505). I feel that I might need to report this issue as a bug, but I'd first like to know if anyone else has noticed this oddity since the upgrade.
    Thanks!
    Edit:
    It seems as if gnome-power-manager thinks that I have two laptop batteries (though I have only one). Clicking on the notification icon lists two batteries: one with the usual "on AC power" icon and the other with the "discharging" (standard battery) icon.
    I do not think that there are any problems with ACPI: running acpi yields the following:
    Battery 1: charged, 100%
    I'm not quite sure where gnome-power-manager procures its information about the batteries)....
    Last edited by ssjlegendx (2008-04-20 18:34:53)

    I just updated to HAL 0.5.11rc2-2, and it seems that my problem has been solved!
    I didn't see the related bug report before starting this thread.... Thanks, JGC!
    Last edited by ssjlegendx (2008-08-02 20:44:41)

  • [SOLVED] gnome-power-manager issues since update?

    Since maybe an update (I'm not sure), gnome-power-manager isn't launched anymore. No battery applet, suspend and hibernation buttons.
    acpid, pm-utils are on.
    By launching it in terminal, it gives:
    ~$ gnome-power-manager
    (gnome-power-manager:3238): libupower-glib-WARNING **: Couldn't enumerate devices: Launch helper exited with unknown return code 127
    TI:17:42:09 TH:0x10cf090 FI:gpm-engine.c FN:gpm_engine_coldplug_idle_cb,834
    - failed to get device list: Launch helper exited with unknown return code 127
    Traceback:
    gnome-power-manager() [0x419a64]
    gnome-power-manager() [0x41904e]
    /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f3) [0x7f72b683abf3]
    /usr/lib/libglib-2.0.so.0(+0x423d0) [0x7f72b683b3d0]
    /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x182) [0x7f72b683ba42]
    gnome-power-manager() [0x40f11b]
    /lib/libc.so.6(__libc_start_main+0xfd) [0x7f72b6239c3d]
    gnome-power-manager() [0x407a49]
    So would libupower-glib bug?
    Last edited by feNNec (2011-01-16 19:03:59)

    yes there is:
    $ ./upowerd start
    ./upowerd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory
    libusb-1.0.8-1 is installed
    What's this daemon for?

  • [SOLVED] gnome-power-manager ignores dpms_method_ac

    There's no way (it seems ) to make gnome-power-manager 2.26.3-1 to work fine...
    i'd like to put my monitor in standby after a while instead of simply blank and so i set dpms_method_ac  in gconf accordingly... but with no success...
    i don't know where to find a solution...
    my laptop is a HP pavillion dv5 1210el and thisi is my actual xorg.conf:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder63) Wed May 27 03:15:36 PDT 2009
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Synaptics Touchpad" "SendCoreEvents"
    InputDevice "USB Mouse" "CorePointer"
    EndSection
    Section "InputDevice"
    Option "Device" "/dev/input/mice"
    Option "Protocol" "Auto"
    Option "ZAxisMapping" "4 5"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Emulate3Buttons" "true"
    EndSection
    Section "InputDevice"
    Identifier "Synaptics Touchpad"
    Driver "synaptics"
    Option "SendCoreEvents" "true"
    Option "Device" "/dev/psaux"
    Option "Protocol" "auto-dev"
    Option "SHMconfig" "on"
    Option "LeftEdge" "1700" # x coord left
    Option "RightEdge" "5300" # x coord right
    Option "TopEdge" "1700" # y coord top
    Option "BottomEdge" "4200" # y coord bottom
    Option "FingerLow" "25" # pressure below this level triggers release
    Option "FingerHigh" "30" # pressure above this level triggers touch
    Option "MaxTapTime" "180" # max time in ms for detecting tap
    Option "VertEdgeScroll" "true" # enable vertical scroll zone
    Option "HorizEdgeScroll" "true" # enable horizontal scroll zone
    Option "CornerCoasting" "true" # enable continuous scroll with finger in corner
    Option "CoastingSpeed" "0.30" # corner coasting speed
    Option "VertScrollDelta" "100" # edge-to-edge scroll distance of the vertical scroll
    Option "HorizScrollDelta" "100" # edge-to-edge scroll distance of the horizontal scroll
    Option "AccelFactor" "0.0020" # acceleration factor for normal pointer movements
    Option "VertTwoFingerScroll" "true" # vertical scroll anywhere with two fingers
    Option "HorizTwoFingerScroll" "true" # horizontal scroll anywhere with two fingers
    Option "EmulateTwoFingerMinZ" "120" # this may vary between different machines
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbModel" "hpdv5"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    Option "RenderAccel" "true"
    Option "DamageEvents" "True"
    Option "NoLogo" "true"
    Option "AddARGBGLXVisuals" "True"
    Option "DisableGLXRootClipping" "True"
    Option "OnDemandVBlankInterrupts" "True"
    Option "RegistryDwords""PowerMizerEnable=0x1; PerfLevelSrc=0x2233; PowerMizerDefault=0x3"
    Option "BackingStore" "True"
    Option "TripleBuffer" "True"
    Option "DPMS" "true"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Module"
    Load "glx"
    Load "synaptics"
    EndSection
    thanx!
    Last edited by euLinux (2009-07-29 07:02:14)

    hi miau!
    i changed my xorg.conf to match your suggestions... Option "DPMS" "true" moved in Monitor section and blanking and dpms settings in ServerLayout:
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Synaptics Touchpad" "SendCoreEvents"
    InputDevice "USB Mouse" "CorePointer"
    Option "BlankTime" "0"
    Option "StandbyTime" "10"
    Option "SuspendTime" "15"
    Option "OffTime" "20"
    EndSection
    i guess you suggested me to do this way, isn't it?
    unfortunately it still doesn't work!
    it seems that after login gnome-power-manager resets all the settings about dpms in xorg.conf... every section i put them in...
    this is part of the output of xset q just after login:
    Screen Saver:
    prefer blanking: yes allow exposures: yes
    timeout: 0 cycle: 600
    Colors:
    default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215
    Font Path:
    /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1,built-ins
    DPMS (Energy Star):
    Standby: 0 Suspend: 0 Off: 0
    DPMS is Enabled
    Monitor is On
    any other idea?
    thanx

  • [Solved] Systemd - Overrides settings of Gnome-Power-Manager?

    Hello!
    I've always used the following to lines to tell Gnome-Power-Manager not to suspend my laptop, when the lid is closed:
    org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank'
    org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
    I remember a huge (and regular...) discussion around Gnome 3, because the developers resisted to re-implemented a button for this in the UI of Gnome3. Well, the two lines above done their job all the time. Since the last update of Systemd this seems to be ignored:
    Oct 09 01:19:58 cupcake systemd-logind[273]: Lid closed.
    Oct 09 01:19:58 cupcake systemd-logind[273]: Suspending...
    Oct 09 01:19:58 cupcake systemd[1]: Starting Sleep.
    Oct 09 01:19:58 cupcake systemd[1]: Reached target Sleep.
    Oct 09 01:19:58 cupcake systemd[1]: Starting Suspend...
    Is anyone other affected? Looks like a real problem for me. If I close the lid I want to close my lid, nothing more an especially not suspend
    /var/log/pacman.log
    [2012-10-08 21:59] upgraded systemd (193-1 -> 194-1)
    [2012-10-08 21:59] upgraded systemd-sysvcompat (193-1 -> 194-1)
    Last edited by hoschi (2012-10-08 23:53:06)

    pablox wrote:
    hoschi wrote:
    Nope. Found it five minutes ago. My shame! Thank you
    https://wiki.archlinux.org/index.php/Sy … th_systemd
    This is driving me crazy. I've read the article, but I still don't understand what I'm supposed to do. I have tried changing values from logind.conf *IgnoreInhibited to yes to no, but the laptop still suspend when the lid is closed .
    All you need to do is set HandleLidSwitch=ignore in logind.conf, this will make systemd ignore the lid switch completely, and leave gnome to handle it. Its pretty self explanatory... You can also set the other similar options to ignore, like HandlePowerKey, HandleSuspendKey, HandleHibernateKey if you want only gnome to handle them.
    Last edited by bwat47 (2012-10-10 22:02:54)

  • Can't uninstall Premier Pro.  I keep getting messages to quit the Adobe QT32 Server and the dynamiclink manager.  I have no idea how to do these tasks?

    Can't uninstall Premier Pro.  I keep getting messages to quit the Adobe QT32 Server and the dynamiclink manager.  I have no idea how to do these tasks?

    You can kill these 2 task by opening the Windows Task manager (CTRL+ALT+SUPPR)
    Then find the processes named :
    Adobe QT32 Server
    Adobe Dynamic Link Manager
    Kill theses 2 tasks (right click then END OF TASK)
    If you got many of theses tasks, kill each.
    Then uninstall Premiere. It should be OK
    good luck
    noar

  • Gnome-Power-Manager don't save history and statistics

    I notice that g-p-m doesn't save history and statistics during a session:
    when I reboot the pc I loose every information and the graphs start by 0.
    I checked every configuration on gconf-editor, but nothing helped me.
    There is the section /apps/gnome-power-manager/info/ but there isn't a schema for any configuration, I don't know what test I could make.
    And I don't find the folder ~/.gnome2/gnome-power-manager on my Arch installations.
    I found this bug with Ubuntu:
    https://bugs.launchpad.net/ubuntu/+sour … bug/302570
    So I run lshal | grep battery to have information about my asus eeepc battery.
    This is the result:
    [root@e3pc luca]# lshal | grep battery
    udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'
      battery.charge_level.current = 20871  (0x5187)  (int)
      battery.charge_level.design = 51034  (0xc75a)  (int)
      battery.charge_level.last_full = 50638  (0xc5ce)  (int)
      battery.charge_level.percentage = 41  (0x29)  (int)
      battery.charge_level.rate = 16993  (0x4261)  (int)
      battery.is_rechargeable = true  (bool)
      battery.model = '901'  (string)
      battery.present = true  (bool)
      battery.rechargeable.is_charging = true  (bool)
      battery.rechargeable.is_discharging = false  (bool)
      battery.remaining_time = 6306  (0x18a2)  (int)
      battery.reporting.current = 2691  (0xa83)  (int)
      battery.reporting.design = 6580  (0x19b4)  (int)
      battery.reporting.last_full = 6529  (0x1981)  (int)
      battery.reporting.rate = 2191  (0x88f)  (int)
      battery.reporting.technology = 'Li-ion'  (string)
      battery.reporting.unit = 'mAh'  (string)
      battery.serial = ''  (string)
      battery.technology = 'lithium-ion'  (string)
      battery.type = 'primary'  (string)
      battery.vendor = 'ASUS'  (string)
      battery.voltage.current = 7756  (0x1e4c)  (int)
      battery.voltage.design = 8400  (0x20d0)  (int)
      battery.voltage.unit = 'mV'  (string)
      info.capabilities = {'battery'} (string list)
      info.category = 'battery'  (string)
      info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'  (string)
    Eeepc hasn't the serial. Ok...
    But on my hp 6735s there is the serial of the battery while I run "lshal | grep battery".
    And it has the same problem.
    The version of g-p-m is 2.26.2-1 on both of them.
    I had many difficulties to find documentation about this gnome daemon!!
    Somebody found a solution?
    Thank you all!

    up

  • Gnome-power-manager and screen brightness

    gnome-power-manager appears to be screwing with my ability to adjust the screen brightness. Now there are only two brightness settings that work - the ones defined in gnome-power-manager settings.  Using the keyboard shortcuts "works" in that I can increase the brightness one level but then the change gets overridden.  Decreasing the brightness sets it at the minimum level then I can get it back without entering gpm settings.  This definitely work before the last update and I think for a while after.
    Is there anyway I can get it to listen to manual adjustments?
    Edit:  I think this was due to the latest hal update.
    > lshal | grep bright
    laptop_panel.brightness_in_hardware = false (bool)
    Edit 2:
    Found http://ubuntuforums.org/archive/index.php/t-290994.html
    Adding "video" to MOD_BLACKLIST in /etc/rc.conf fixed this.  This is just a kernel module right? Nothing else will be screwed...?
    Last edited by Allan (2007-10-31 11:30:37)

    I have Sony Vaio VGN-FZ38M with Nvidia 8400M GT. I used package 'nvclock' (it is in repo) to control lcd brightness, here site with more info: NVClock.  Some time ago I also configured Fn keys to work with it (on Ubuntu), but on Arch I didn't  manged but I didn't try hard (in general i don't need, my laptop is stationary all the time). Solution I've found somwehere in Ubuntu forums.
    edit: typo in address
    edit2:
    here's the solution from Ubuntu: http://newyork.ubuntuforums.org/showthr … ?t=1004568
    Last edited by folletto (2009-06-14 20:58:56)

Maybe you are looking for