[Bug 441396] Re: Totem hangs while loading a video with .srt (or .txt in MicroDVD format) sub from nautilus
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 -- Totem hangs while loading a video with .srt (or .txt in MicroDVD format) sub from nautilus https://bugs.launchpad.net/bugs/441396 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 441396] Re: Totem hangs while loading a video with .srt (or .txt in MicroDVD format) sub from nautilus
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 video with .srt (or .txt in MicroDVD format) sub from nautilus https://bugs.launchpad.net/bugs/441396 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 354792] Re: Ctl-Alt-L does not lock screen immediately after startup
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 you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 354792] Re: Ctl-Alt-L does not lock screen immediately after startup
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 while the session is starting */ I've attached a patch that adds a new option to gconf for setting a custom delay timeout value. It defaults to 30 seconds. Setting it to 0 will results in gnome-screensaver immediately started, and screen lockable. ** Attachment added: "gnome_screensaver_startup_timeout_customizable.patch" http://launchpadlibrarian.net/26012592/gnome_screensaver_startup_timeout_customizable.patch -- Ctl-Alt-L does not lock screen immediately after startup https://bugs.launchpad.net/bugs/354792 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver 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 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 gets dropped. -- 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 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. -- 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
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 a value. -- 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
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-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 367271] Re: Add a gconf key for setting the time delay before to start 'gnome-screensaver' at session startup
** 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/367271 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 367271] [NEW] Add a gconf key for setting the time delay before to start 'gnome-screensaver' at session startup
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 notebook with battery and get away
from it, brightness was automatically adjusted by gnome-power-manager.
In Jaunty, 'gnome-screensaver' is not immediately started at session startup,
instead it's delayed by 30 seconds and there is no way to customize this delay.
This makes impossibile to lock the screen.
I've attached a patch that adds a new gconf key
('/apps/gnome_settings_daemon/screensaver/start_screensaver_timeout') and makes
possible to customize the delay. It defaults to 30 seconds.
Setting it to 0 causes the 'gnome-screensaver' to be immediately started as it
happens in Intrepid, so the problem is fixed.
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
Add a gconf key for setting the time delay before to start 'gnome-screensaver'
at session startup
https://bugs.launchpad.net/bugs/367271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon 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
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 try it. Or else you can get a precompiled package (i386, lpia) from my PPA: https://launchpad.net/~voria/+archive/ppa ** Attachment added: "90-Add-guarded-brightness-stepping-functions.patch" http://launchpadlibrarian.net/25993877/90-Add-guarded-brightness-stepping-functions.patch -- 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
