It works! Thank you, I have been dealing with this glitch for two
releases now. Brilliant.
--
smb password protected share cannot be accessed
https://bugs.launchpad.net/bugs/206439
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
de
It definitely decreases the number of steps, but still has 2 too many
for my AAO. I think setting GPM_BRIGHTNESS_DIM_LEVELS to 12 by default
is the problem. Is it possible to set it to the value of
"laptop_panel.num_levels" as reported by hal? I attached my lshal output
above and it seems to report
Is GPM_BRIGHTNESS_DIM_LEVELS set using xrandr? The patch seems to set it
to 12 by default.
+#define GPM_BRIGHTNESS_DIM_LEVELS 12
--
Brightness control is slow and not costant with
90-Add-guarded-brightness-stepping-functions.patch
91-Using-guarded-and-scaled-stepping-when-dimming.patch
ht
What about setting it to the value reported by laptop_panel.num_levels
from hal. I borrowed the code below from https://fedorahosted.org/hal-
cups-
utils/browser/systemv/hal_lpadmin?rev=63db99983c74ba8c7efaee60e9b509e986a9204f
for a possible way to incorporate the hal-get-property command. It
shoul
I guess that won't change until hardware developers start building with
linux in mind... A less eloquent solution in the mean time might be to
create a gpmbightness.conf file that users can manually set
GPM_BRIGHTNESS_DIM_LEVELS to suit their needs. This could be parsed
first and if null a default
** Attachment added: "gpm.log"
http://launchpadlibrarian.net/34181208/gpm.log
--
Acer Aspire One: OSD for brightness keys not working properly
https://bugs.launchpad.net/bugs/441825
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnom
Here you go...
b...@aao-lin:~$ hal-device /org/freedesktop/Hal/devices/computer_backlight
libhal.c 546 : No device with id /org/freedesktop/Hal/devices/computer_backlight
org.freedesktop.Hal.NoSuchDevice: No device with id
/org/freedesktop/Hal/devices/computer_backlight
I have attached the full
Should this also be applied to "Volumes" section of the netbook edition?
Currently a right click on a removable drive in this section on UNE only
gives unmount as an option.
--
Context menu for an USB pendrive shows "Unmount", "Eject" and "Safely Remove
Drive"
https://bugs.launchpad.net/bugs/453
My Acer Aspire One will return from suspend locked if suspended via the
indicator applet, but not if through lid closure. My packages are up to
date and I have restarted today.
--
Computer no longer locks on suspend or lid close
https://bugs.launchpad.net/bugs/428115
You received this bug notific
Here you go:
lid_battery = suspend
hibernate = hibernate
suspend = suspend
lid_ac = suspend
power = interactive
--
Computer no longer locks on suspend or lid close
https://bugs.launchpad.net/bugs/428115
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whic
Here is my .xsession-errors output following a lid closure:
** (nm-applet:1660): DEBUG: applet_common_device_state_changed
** (nm-applet:1660): DEBUG: old state indicates that this was not a disconnect 2
** (nm-applet:1660): DEBUG: applet_common_device_state_changed
** (nm-applet:1660): DEBUG: foo
Logging in as new user didn't fix the issue. Still no lockscreen.
--
Computer no longer locks on suspend or lid close
https://bugs.launchpad.net/bugs/428115
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Here you go. Also, I'm not using autologin...
** Attachment added: "gpm.log"
http://launchpadlibrarian.net/33170266/gpm.log
--
Does not lock screen on lid close when using gdm autologin
https://bugs.launchpad.net/bugs/428115
You received this bug notification because you are a member of Ubunt
b...@aao-lin:~$ gconftool -R /apps/gnome-screensaver
lock_enabled = false
idle_activation_enabled = true
cycle_delay = 10
status_message_enabled = true
mode = blank-only
theme = screensavers-ubuntu_theme
user_switch_enabled = true
idle_delay = 10
logout_delay = 120
power_management_delay
This fixed the issue, however I never changed this option. It must have
been a default on the alpha version I installed. This should definitely
be the default option, if it isn't already with newer versions. Thanks
for the help.
--
Does not lock screen on lid close when using gdm autologin
https:
As far as I can tell, this is the last Jaunty bug listed on the
AspireOne Community page that doesn't have a workaround. Even though
this bug doesn't limit the ability to change brightness, it is highly
visible. As Ubuntu is trying to make headway into the netbook market,
and the AAO is a very popu
16 matches
Mail list logo
