[Bug 453072] Re: Context menu for an USB pendrive shows Unmount, Eject and Safely Remove Drive
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/453072 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 441825] Re: Acer Aspire One: OSD for brightness keys not working properly
** 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 gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 441825] Re: Acer Aspire One: OSD for brightness keys not working properly
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 hal-device output for analysis. ** Attachment added: hal-device.txt http://launchpadlibrarian.net/34181191/hal-device.txt -- 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 gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428115] Re: Does not lock screen on lid close when using gdm autologin
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 Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428115] Re: Does not lock screen on lid close when using gdm autologin
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 = 30 embedded_keyboard_enabled = false logout_enabled = false embedded_keyboard_command = lock_dialog_theme = default logout_command = themes = [] lock_delay = 0 b...@aao-lin:~$ gconftool -R /apps/gnome-power-manager/lock hibernate = true suspend = true gnome_keyring_hibernate = true blank_screen = false use_screensaver_settings = true gnome_keyring_suspend = false Your prediction was correct. Why would this work when suspended via the indicator applet and not lid closure? -- 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 Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428115] Re: Does not lock screen on lid close when using gdm autologin
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://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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428115] Re: Computer no longer locks on suspend or lid close
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_client_state_changed_cb ** (nm-applet:1660): DEBUG: going for offline with icon: notification-network-wireless-disconnected ** (nm-applet:1660): DEBUG: going for offline with icon: notification-network-wireless-disconnected ** (nm-applet:1660): DEBUG: applet_common_device_state_changed ** (nm-applet:1660): DEBUG: old state indicates that this was not a disconnect 1 ** (nm-applet:1660): DEBUG: applet_common_device_state_changed ** (nm-applet:1660): DEBUG: old state indicates that this was not a disconnect 1 ** (nm-applet:1660): DEBUG: foo_client_state_changed_cb ** (nm-applet:1660): DEBUG: going for offline with icon: notification-network-disconnected ** (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: applet_common_device_state_changed ** (nm-applet:1660): DEBUG: applet_common_device_state_changed ** (nm-applet:1660): DEBUG: applet_common_device_state_changed ** (nm-applet:1660): DEBUG: applet_common_device_state_changed ** (nm-applet:1660): DEBUG: foo_client_state_changed_cb ** (nm-applet:1660): DEBUG: going for offline with icon: notification-network-disconnected ** (nm-applet:1660): DEBUG: applet_common_device_state_changed ** (nm-applet:1660): DEBUG: applet_common_device_state_changed ** (nm-applet:1660): DEBUG: foo_client_state_changed_cb Here is the dpkg output: gnome-power-manager 2.28.0-0ubuntu1 -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428115] Re: Computer no longer locks on suspend or lid close
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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428115] Re: Computer no longer locks on suspend or lid close
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, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428115] Re: Computer no longer locks on suspend or lid close
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 notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 206439] Re: smb password protected share cannot be accessed
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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 345318] Re: Brightness control is slow and not costant with 90-Add-guarded-brightness-stepping-functions.patch 91-Using-guarded-and-scaled-stepping-when-dimming.patch
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 value of 12 could be set. -- Brightness control is slow and not costant with 90-Add-guarded-brightness-stepping-functions.patch 91-Using-guarded-and-scaled-stepping-when-dimming.patch https://bugs.launchpad.net/bugs/345318 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 345318] Re: Brightness control is slow and not costant with 90-Add-guarded-brightness-stepping-functions.patch 91-Using-guarded-and-scaled-stepping-when-dimming.patch
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 the correct number of brightness levels. Is this true for everyone else? Thanks for tackling this! -- Brightness control is slow and not costant with 90-Add-guarded-brightness-stepping-functions.patch 91-Using-guarded-and-scaled-stepping-when-dimming.patch https://bugs.launchpad.net/bugs/345318 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 345318] Re: Brightness control is slow and not costant with 90-Add-guarded-brightness-stepping-functions.patch 91-Using-guarded-and-scaled-stepping-when-dimming.patch
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 https://bugs.launchpad.net/bugs/345318 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 345318] Re: Brightness control is slow and not costant with 90-Add-guarded-brightness-stepping-functions.patch 91-Using-guarded-and-scaled-stepping-when-dimming.patch
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 should be possible to then set the output to GPM_BRIGHTNESS_DIM_LEVELS. I hope this makes sense, like I said before my coding skills are about 15 years rusty. def get_hal_property(udi, key): 34 # Read out the value of a given key for a given HAL UDI 35 devnull = file (/dev/null, r+) 36 try: 37 p = subprocess.Popen ([hal-get-property, --udi, udi, 38 --key, key], 39stdin=devnull, 40stdout=subprocess.PIPE, 41stderr=devnull) 42 (stdout, stderr) = p.communicate () 43 return stdout.strip () 44 except: 45 return -- Brightness control is slow and not costant with 90-Add-guarded-brightness-stepping-functions.patch 91-Using-guarded-and-scaled-stepping-when-dimming.patch https://bugs.launchpad.net/bugs/345318 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 345318] Re: Brightness control is slow and not costant with 90-Add-guarded-brightness-stepping-functions.patch 91-Using-guarded-and-scaled-stepping-when-dimming.patch
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 popular model, I think it would be nice to fix this last little nuisance before the 23rd. I am happy to test any code, but unfortunately my coding skills are too rusty to tackle this on my own. Thank you to everyone who has helped so far. -- Brightness control is slow and not costant with 90-Add-guarded-brightness-stepping-functions.patch 91-Using-guarded-and-scaled-stepping-when-dimming.patch https://bugs.launchpad.net/bugs/345318 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
