Done.
http://bugzilla.gnome.org/show_bug.cgi?id=582587
** Bug watch added: GNOME Bug Tracker #582587
http://bugzilla.gnome.org/show_bug.cgi?id=582587
--
Ctl-Alt-L does not lock screen immediately after startup
https://bugs.launchpad.net/bugs/354792
You received this bug notification because
Here it is.
It applies correctly to the package version '0.10.25-2ubuntu1.1', after all the
other patches in 'debian/patches/'.
** Attachment added: "Fix subtitles autoload in gst-plugins-base0.10
(0.10.25-2ubuntu1.1)"
http://launchpadlibrarian.net/36527470/protect-subtitle-elements.patch
--
I have modified the '90-Add-guarded-brightness-stepping-functions' patch in
order to get 12 levels of brightness adjustment, and changed the formulas used
to calculate the next step for decreasing/increasing brightness in order to get
constant steps.
It seems to work good on Samsung NC10.
Please
Public bug reported:
In Intrepid I was used to enable the autologin feature in gdm, then add the
'gnome-screensaver-command --lock' in Startup Applications to lock the screen
immediately after login. This way I was ready to work just inserting my user
password. Furthermore, when I started up my
** Attachment added: "screensaver_startup_timeout_customizable.patch"
http://launchpadlibrarian.net/25994427/screensaver_startup_timeout_customizable.patch
--
Add a gconf key for setting the time delay before to start 'gnome-screensaver'
at session startup
https://bugs.launchpad.net/bugs/36
Looking at the code in 'gpm-brightness.c', it seems that xrandr is
preferred over hal when both are available. I don't know why but there
is certainly a good reason if it's so.
--
Brightness control is slow and not costant with
90-Add-guarded-brightness-stepping-functions.patch
91-Using-guarded
No, it's manually set. It was set to 24 in the original patch, I changed it to
12 to get bigger steps.
IMHO this is not a good solution, because a fixed value is not good for
everyone, as you stated.
However, I just modified the original patch, I don't know if there is a more
generic way to set
It seems that hal support is not always available. For example, 'lshal' does
not report any UDI for backlight on Samsung NC10. Apart from that, it would be
a bad idea to use hal in gpm xrandr functions.
Looking at the code, there are two distinct way to set brightness, xrandr and
hal.
--
Brigh
It seems that hal support is not always available. For example 'lshal' does not
report any UDI for backlight on Samsung NC10. Apart from that, it's a bad idea
to use hal in xrandr functions.
As I said in a previous comment xrandr is preferred over hal when both are
available, and hal support get
The issue is caused by a recent change in gnome-settings-daemon that adds a 30
sec delay for starting gnome-screensaver. This is the reason for it (directly
from source code):
/*
* We'll start the screensaver after a delay so it doesn't
* compete with other processes
I've build a new 'gst-plugins-base0.10' package which includes the (adapted)
upstream patch.
It's based on version '0.10.25-2ubuntu1' (not the proposed
'0.10.25-2ubuntu1.1'), and it's available on my testing PPA:
https://launchpad.net/~voria/+archive/archive
--
Totem hangs while loading a vide
11 matches
Mail list logo
