Re: [Bug 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This seems to be resolved. I've upgraded to 9.04 on both my laptops and I haven't had backlight issues since. On 4/21/2009 2:15 PM, Leann Ogasawara wrote: > @Ryan, is this fix still the cause of a regression for you? Does the > regression still remain in the upcoming Jaunty 9.04 release - > http://cdimage.ubuntu.com/daily-live/current/ . Please let us know. > Thanks. > > ** Changed in: linux (Ubuntu) > Status: Fix Committed => Fix Released > > ** Changed in: linux (Ubuntu) > Assignee: Ben Collins (ben-collins) => (unassigned) > > -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
I registered a bug on this when I couldn't find this one... bug # 199976 I know this has all been rehashed, but I think trying to add location / TZ data for each location entry is not going to work because the system doesn't select a location entry with the proper timezone in the first place. I think an acceptable way to handle this time zone issue is to scrap the current location options and create a new location database with one entry per state / region / et al that fits into a timezone... currently there are many many many entries for the same time zones. Right now there are lots of time zone choices that don't seem to have any logic as to why they were selected. Coming from a US Perspective, I believe there are very few instances where timezones do not follow state borders. We should really have a tz entry for each state (maybe state capitals unless the state has two time zones) or reduce the number of entries overall in tzdata. Menominee, Wisconsin has a tz entry and I'm not sure why... we could remove all Mid-west USA entries except Chicago (which is CST) and I think people would figure it out. It would also be helpful to display the timezone (even just the abbreviation) for each location ... so that I know that Rainy River or Chicago are both in the same Time Zone. I'll explain my issue (below) with locations as they exist today: Rainy River is on the border of Minnesota (USA) / Ontario (Canada) which is a very sparsely populated area with the two main industries being Farming (Sugar Beets) and Tourism (Fishing.) I only know about the Rainy River because I lived up there for a few years and fished the River but most of the state's residents do not know that as a location in our time zone. and here specifically is my issue with the proximity based approach currently being applied... the system currently picks locations closer to the target city even though they're across time zones. When picking a location for the city of Hibbing, Minnesota, USA -- the time zone defaults to America/Atikokan ... which is Eastern Standard Time (-5 GMT,) but all of Minnesota is Central Standard Time (-6 GMT.) This is also a problem for Grand Marais, Minnesota -- which gets lumped in with the America/Thunder_Bay ... which is actually Canada, not USA. Grand Marais, Minnesota (not Michigan) is set to EST and it should be CST. Minneapolis, Minnesota defaults to America/Rainy_River and it is further East than Hibbing. So there is an issue somewhere with how cities are associated with time zones. It seems like the NE "arrowhead" of Minnesota is all set to Eastern Standard Time instead of Central Standard Time. -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
According to Wikipedia there are 245 political entities in the world... http://en.wikipedia.org/wiki/List_of_countries ... and only 193 with general international recognition So we've got 24 time zones... A little history: In 1878, Sir Sandford Fleming (1827–1915) developed the system of worldwide time zones that we still use today. He proposed that the world be divided into 24 time zones, each spaced 15º (fifteen degrees) of longitude apart (like 24 sections of an orange). He came to this idea because Earth completes a rotation every 24 hours and there are 360º of longitude, so each hour Earth rotates 1/24th of a circle or 15º. So if this is the logic... why not just define each 24 hr time period... based on it's longitude... Then define "political" exemptions which to the best of my research cover large geographical terroritories but are clearly defined by geo- political boundaries... China is ONE timezone. A few US States don't do timezones.. .Alaska (USA) should span a few timezones, but has been consolidated to 1. And here's the current info on daylight savings time: http://webexhibits.org/daylightsaving/g.html Taking a look at this "large" problem and breaking it down to the most general concrete information and then defining exemptions .. has me looking at it this way... 1. define "true" time zones as represented by the only data we know to be consistant... Longitude. -- The location of the user is always technically based on Longitude and Latitude... so this way we should be able to determine the "true" timezone. 2. define continental and sub-continental exemptions -- define large exceptions... exemptions that span countries... -- maybe this never happens 3. define country-wide timezones -- basically which countries wrap themselves into a single timezone. --- China 4. define regional exemptions -- a regional exemption must fit inside of a country --- aka alaska, usa --- Navajo tribal nation spans 3 states and participates in daylight savings time even though part of the nation lies in Arizona which does not participate. --- Russia, 11 time-zones permanent daylight savings time (so 1hr ahead of actual time zone) --- other exemptions are the half and quarter-time modifications 5. unique / specific cirumstances... In South Asia, if you follow a straight line west along the 27º latitude you will move back and forth across time zones: from Pakistan UTC +5 hours, India +5:30, Nepal +5:45, India (Sikkim) +5:30, China +8, Bhutan +6, India (Arunachal Pradesh) +5:30, Myanmar +6:30. ... you could define the able based on the rules #2 and #3... and define regional areas between two longitudinal points... within a specified country. I think the key to the breakdown based on a descending order of priority (+): Default Time Zone based on Longitude Continent Country of Origin Region of County City / Other / Specific And the big news... has anybody seen this government ftp site with all of the timezone data defined? ftp://elsie.nci.nih.gov/pub/ -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
Yeah, In my solution I didn't mean that you'd need to document each city's timezone -- only if there was something unique about it... you should be able to just map countries and potentially states / regions of countries... *IF* you needed anything at all. Ryan -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 186441] Re: [Hardy] Recursive directory deletion doesnt work for external mounted drives
I can confirm this on Ubuntu Hardy 8.04 64-bit Updated as of today. Delete or Delete All gives the error: "Error Removing File: File Exists" Prompting you to Skip, Skip All or Cancel... with all three options just closing the delete dialog while leaving all files selected for deletion. -- [Hardy] Recursive directory deletion doesnt work for external mounted drives https://bugs.launchpad.net/bugs/186441 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 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This was working fine for me on my ThinkPad X61T laptop until the latest Kernel this worked fine. With the latest kernel (24-11) my laptop display now properly displays after resuming from suspend, but now I cannot control the brightness through the Gnome applet or the function keys on my keyboard. The keys (via OSD) and slider work and show that the brightness is being changed, but it doesn't actually change the brightness of the screen. -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 88828] Re: mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /)
*** This bug is a duplicate of bug 107668 *** https://bugs.launchpad.net/bugs/107668 I've had the same issue now -- how can an older bug be the duplicate of a newer bug? -- mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /) https://bugs.launchpad.net/bugs/88828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu (via bug 107668). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 186441] Re: [Hardy] Recursive directory deletion doesnt work for external mounted drives
I can confirm this on Ubuntu Hardy 8.04 64-bit Updated as of today. Delete or Delete All gives the error: "Error Removing File: File Exists" Prompting you to Skip, Skip All or Cancel... with all three options just closing the delete dialog while leaving all files selected for deletion. -- [Hardy] Recursive directory deletion doesnt work for external mounted drives https://bugs.launchpad.net/bugs/186441 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 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This was working fine for me on my ThinkPad X61T laptop until the latest Kernel this worked fine. With the latest kernel (24-11) my laptop display now properly displays after resuming from suspend, but now I cannot control the brightness through the Gnome applet or the function keys on my keyboard. The keys (via OSD) and slider work and show that the brightness is being changed, but it doesn't actually change the brightness of the screen. -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
I registered a bug on this when I couldn't find this one... bug # 199976 I know this has all been rehashed, but I think trying to add location / TZ data for each location entry is not going to work because the system doesn't select a location entry with the proper timezone in the first place. I think an acceptable way to handle this time zone issue is to scrap the current location options and create a new location database with one entry per state / region / et al that fits into a timezone... currently there are many many many entries for the same time zones. Right now there are lots of time zone choices that don't seem to have any logic as to why they were selected. Coming from a US Perspective, I believe there are very few instances where timezones do not follow state borders. We should really have a tz entry for each state (maybe state capitals unless the state has two time zones) or reduce the number of entries overall in tzdata. Menominee, Wisconsin has a tz entry and I'm not sure why... we could remove all Mid-west USA entries except Chicago (which is CST) and I think people would figure it out. It would also be helpful to display the timezone (even just the abbreviation) for each location ... so that I know that Rainy River or Chicago are both in the same Time Zone. I'll explain my issue (below) with locations as they exist today: Rainy River is on the border of Minnesota (USA) / Ontario (Canada) which is a very sparsely populated area with the two main industries being Farming (Sugar Beets) and Tourism (Fishing.) I only know about the Rainy River because I lived up there for a few years and fished the River but most of the state's residents do not know that as a location in our time zone. and here specifically is my issue with the proximity based approach currently being applied... the system currently picks locations closer to the target city even though they're across time zones. When picking a location for the city of Hibbing, Minnesota, USA -- the time zone defaults to America/Atikokan ... which is Eastern Standard Time (-5 GMT,) but all of Minnesota is Central Standard Time (-6 GMT.) This is also a problem for Grand Marais, Minnesota -- which gets lumped in with the America/Thunder_Bay ... which is actually Canada, not USA. Grand Marais, Minnesota (not Michigan) is set to EST and it should be CST. Minneapolis, Minnesota defaults to America/Rainy_River and it is further East than Hibbing. So there is an issue somewhere with how cities are associated with time zones. It seems like the NE "arrowhead" of Minnesota is all set to Eastern Standard Time instead of Central Standard Time. -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
According to Wikipedia there are 245 political entities in the world... http://en.wikipedia.org/wiki/List_of_countries ... and only 193 with general international recognition So we've got 24 time zones... A little history: In 1878, Sir Sandford Fleming (1827–1915) developed the system of worldwide time zones that we still use today. He proposed that the world be divided into 24 time zones, each spaced 15º (fifteen degrees) of longitude apart (like 24 sections of an orange). He came to this idea because Earth completes a rotation every 24 hours and there are 360º of longitude, so each hour Earth rotates 1/24th of a circle or 15º. So if this is the logic... why not just define each 24 hr time period... based on it's longitude... Then define "political" exemptions which to the best of my research cover large geographical terroritories but are clearly defined by geo- political boundaries... China is ONE timezone. A few US States don't do timezones.. .Alaska (USA) should span a few timezones, but has been consolidated to 1. And here's the current info on daylight savings time: http://webexhibits.org/daylightsaving/g.html Taking a look at this "large" problem and breaking it down to the most general concrete information and then defining exemptions .. has me looking at it this way... 1. define "true" time zones as represented by the only data we know to be consistant... Longitude. -- The location of the user is always technically based on Longitude and Latitude... so this way we should be able to determine the "true" timezone. 2. define continental and sub-continental exemptions -- define large exceptions... exemptions that span countries... -- maybe this never happens 3. define country-wide timezones -- basically which countries wrap themselves into a single timezone. --- China 4. define regional exemptions -- a regional exemption must fit inside of a country --- aka alaska, usa --- Navajo tribal nation spans 3 states and participates in daylight savings time even though part of the nation lies in Arizona which does not participate. --- Russia, 11 time-zones permanent daylight savings time (so 1hr ahead of actual time zone) --- other exemptions are the half and quarter-time modifications 5. unique / specific cirumstances... In South Asia, if you follow a straight line west along the 27º latitude you will move back and forth across time zones: from Pakistan UTC +5 hours, India +5:30, Nepal +5:45, India (Sikkim) +5:30, China +8, Bhutan +6, India (Arunachal Pradesh) +5:30, Myanmar +6:30. ... you could define the able based on the rules #2 and #3... and define regional areas between two longitudinal points... within a specified country. I think the key to the breakdown based on a descending order of priority (+): Default Time Zone based on Longitude Continent Country of Origin Region of County City / Other / Specific And the big news... has anybody seen this government ftp site with all of the timezone data defined? ftp://elsie.nci.nih.gov/pub/ -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 88828] Re: mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /)
*** This bug is a duplicate of bug 107668 *** https://bugs.launchpad.net/bugs/107668 I've had the same issue now -- how can an older bug be the duplicate of a newer bug? -- mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /) https://bugs.launchpad.net/bugs/88828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu (via bug 107668). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
Yeah, In my solution I didn't mean that you'd need to document each city's timezone -- only if there was something unique about it... you should be able to just map countries and potentially states / regions of countries... *IF* you needed anything at all. Ryan -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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
Re: [Bug 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This seems to be resolved. I've upgraded to 9.04 on both my laptops and I haven't had backlight issues since. On 4/21/2009 2:15 PM, Leann Ogasawara wrote: > @Ryan, is this fix still the cause of a regression for you? Does the > regression still remain in the upcoming Jaunty 9.04 release - > http://cdimage.ubuntu.com/daily-live/current/ . Please let us know. > Thanks. > > ** Changed in: linux (Ubuntu) > Status: Fix Committed => Fix Released > > ** Changed in: linux (Ubuntu) > Assignee: Ben Collins (ben-collins) => (unassigned) > > -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
I registered a bug on this when I couldn't find this one... bug # 199976 I know this has all been rehashed, but I think trying to add location / TZ data for each location entry is not going to work because the system doesn't select a location entry with the proper timezone in the first place. I think an acceptable way to handle this time zone issue is to scrap the current location options and create a new location database with one entry per state / region / et al that fits into a timezone... currently there are many many many entries for the same time zones. Right now there are lots of time zone choices that don't seem to have any logic as to why they were selected. Coming from a US Perspective, I believe there are very few instances where timezones do not follow state borders. We should really have a tz entry for each state (maybe state capitals unless the state has two time zones) or reduce the number of entries overall in tzdata. Menominee, Wisconsin has a tz entry and I'm not sure why... we could remove all Mid-west USA entries except Chicago (which is CST) and I think people would figure it out. It would also be helpful to display the timezone (even just the abbreviation) for each location ... so that I know that Rainy River or Chicago are both in the same Time Zone. I'll explain my issue (below) with locations as they exist today: Rainy River is on the border of Minnesota (USA) / Ontario (Canada) which is a very sparsely populated area with the two main industries being Farming (Sugar Beets) and Tourism (Fishing.) I only know about the Rainy River because I lived up there for a few years and fished the River but most of the state's residents do not know that as a location in our time zone. and here specifically is my issue with the proximity based approach currently being applied... the system currently picks locations closer to the target city even though they're across time zones. When picking a location for the city of Hibbing, Minnesota, USA -- the time zone defaults to America/Atikokan ... which is Eastern Standard Time (-5 GMT,) but all of Minnesota is Central Standard Time (-6 GMT.) This is also a problem for Grand Marais, Minnesota -- which gets lumped in with the America/Thunder_Bay ... which is actually Canada, not USA. Grand Marais, Minnesota (not Michigan) is set to EST and it should be CST. Minneapolis, Minnesota defaults to America/Rainy_River and it is further East than Hibbing. So there is an issue somewhere with how cities are associated with time zones. It seems like the NE "arrowhead" of Minnesota is all set to Eastern Standard Time instead of Central Standard Time. -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
According to Wikipedia there are 245 political entities in the world... http://en.wikipedia.org/wiki/List_of_countries ... and only 193 with general international recognition So we've got 24 time zones... A little history: In 1878, Sir Sandford Fleming (1827–1915) developed the system of worldwide time zones that we still use today. He proposed that the world be divided into 24 time zones, each spaced 15º (fifteen degrees) of longitude apart (like 24 sections of an orange). He came to this idea because Earth completes a rotation every 24 hours and there are 360º of longitude, so each hour Earth rotates 1/24th of a circle or 15º. So if this is the logic... why not just define each 24 hr time period... based on it's longitude... Then define "political" exemptions which to the best of my research cover large geographical terroritories but are clearly defined by geo- political boundaries... China is ONE timezone. A few US States don't do timezones.. .Alaska (USA) should span a few timezones, but has been consolidated to 1. And here's the current info on daylight savings time: http://webexhibits.org/daylightsaving/g.html Taking a look at this "large" problem and breaking it down to the most general concrete information and then defining exemptions .. has me looking at it this way... 1. define "true" time zones as represented by the only data we know to be consistant... Longitude. -- The location of the user is always technically based on Longitude and Latitude... so this way we should be able to determine the "true" timezone. 2. define continental and sub-continental exemptions -- define large exceptions... exemptions that span countries... -- maybe this never happens 3. define country-wide timezones -- basically which countries wrap themselves into a single timezone. --- China 4. define regional exemptions -- a regional exemption must fit inside of a country --- aka alaska, usa --- Navajo tribal nation spans 3 states and participates in daylight savings time even though part of the nation lies in Arizona which does not participate. --- Russia, 11 time-zones permanent daylight savings time (so 1hr ahead of actual time zone) --- other exemptions are the half and quarter-time modifications 5. unique / specific cirumstances... In South Asia, if you follow a straight line west along the 27º latitude you will move back and forth across time zones: from Pakistan UTC +5 hours, India +5:30, Nepal +5:45, India (Sikkim) +5:30, China +8, Bhutan +6, India (Arunachal Pradesh) +5:30, Myanmar +6:30. ... you could define the able based on the rules #2 and #3... and define regional areas between two longitudinal points... within a specified country. I think the key to the breakdown based on a descending order of priority (+): Default Time Zone based on Longitude Continent Country of Origin Region of County City / Other / Specific And the big news... has anybody seen this government ftp site with all of the timezone data defined? ftp://elsie.nci.nih.gov/pub/ -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
Yeah, In my solution I didn't mean that you'd need to document each city's timezone -- only if there was something unique about it... you should be able to just map countries and potentially states / regions of countries... *IF* you needed anything at all. Ryan -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 88828] Re: mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /)
*** This bug is a duplicate of bug 107668 *** https://bugs.launchpad.net/bugs/107668 I've had the same issue now -- how can an older bug be the duplicate of a newer bug? -- mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /) https://bugs.launchpad.net/bugs/88828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu (via bug 107668). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This seems to be resolved. I've upgraded to 9.04 on both my laptops and I haven't had backlight issues since. On 4/21/2009 2:15 PM, Leann Ogasawara wrote: > @Ryan, is this fix still the cause of a regression for you? Does the > regression still remain in the upcoming Jaunty 9.04 release - > http://cdimage.ubuntu.com/daily-live/current/ . Please let us know. > Thanks. > > ** Changed in: linux (Ubuntu) > Status: Fix Committed => Fix Released > > ** Changed in: linux (Ubuntu) > Assignee: Ben Collins (ben-collins) => (unassigned) > > -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 186441] Re: [Hardy] Recursive directory deletion doesnt work for external mounted drives
I can confirm this on Ubuntu Hardy 8.04 64-bit Updated as of today. Delete or Delete All gives the error: "Error Removing File: File Exists" Prompting you to Skip, Skip All or Cancel... with all three options just closing the delete dialog while leaving all files selected for deletion. -- [Hardy] Recursive directory deletion doesnt work for external mounted drives https://bugs.launchpad.net/bugs/186441 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 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This was working fine for me on my ThinkPad X61T laptop until the latest Kernel this worked fine. With the latest kernel (24-11) my laptop display now properly displays after resuming from suspend, but now I cannot control the brightness through the Gnome applet or the function keys on my keyboard. The keys (via OSD) and slider work and show that the brightness is being changed, but it doesn't actually change the brightness of the screen. -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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
Re: [Bug 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This seems to be resolved. I've upgraded to 9.04 on both my laptops and I haven't had backlight issues since. On 4/21/2009 2:15 PM, Leann Ogasawara wrote: > @Ryan, is this fix still the cause of a regression for you? Does the > regression still remain in the upcoming Jaunty 9.04 release - > http://cdimage.ubuntu.com/daily-live/current/ . Please let us know. > Thanks. > > ** Changed in: linux (Ubuntu) > Status: Fix Committed => Fix Released > > ** Changed in: linux (Ubuntu) > Assignee: Ben Collins (ben-collins) => (unassigned) > > -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 88828] Re: mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /)
*** This bug is a duplicate of bug 107668 *** https://bugs.launchpad.net/bugs/107668 I've had the same issue now -- how can an older bug be the duplicate of a newer bug? -- mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /) https://bugs.launchpad.net/bugs/88828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu (via bug 107668). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
Yeah, In my solution I didn't mean that you'd need to document each city's timezone -- only if there was something unique about it... you should be able to just map countries and potentially states / regions of countries... *IF* you needed anything at all. Ryan -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 186441] Re: [Hardy] Recursive directory deletion doesnt work for external mounted drives
I can confirm this on Ubuntu Hardy 8.04 64-bit Updated as of today. Delete or Delete All gives the error: "Error Removing File: File Exists" Prompting you to Skip, Skip All or Cancel... with all three options just closing the delete dialog while leaving all files selected for deletion. -- [Hardy] Recursive directory deletion doesnt work for external mounted drives https://bugs.launchpad.net/bugs/186441 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 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This was working fine for me on my ThinkPad X61T laptop until the latest Kernel this worked fine. With the latest kernel (24-11) my laptop display now properly displays after resuming from suspend, but now I cannot control the brightness through the Gnome applet or the function keys on my keyboard. The keys (via OSD) and slider work and show that the brightness is being changed, but it doesn't actually change the brightness of the screen. -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
I registered a bug on this when I couldn't find this one... bug # 199976 I know this has all been rehashed, but I think trying to add location / TZ data for each location entry is not going to work because the system doesn't select a location entry with the proper timezone in the first place. I think an acceptable way to handle this time zone issue is to scrap the current location options and create a new location database with one entry per state / region / et al that fits into a timezone... currently there are many many many entries for the same time zones. Right now there are lots of time zone choices that don't seem to have any logic as to why they were selected. Coming from a US Perspective, I believe there are very few instances where timezones do not follow state borders. We should really have a tz entry for each state (maybe state capitals unless the state has two time zones) or reduce the number of entries overall in tzdata. Menominee, Wisconsin has a tz entry and I'm not sure why... we could remove all Mid-west USA entries except Chicago (which is CST) and I think people would figure it out. It would also be helpful to display the timezone (even just the abbreviation) for each location ... so that I know that Rainy River or Chicago are both in the same Time Zone. I'll explain my issue (below) with locations as they exist today: Rainy River is on the border of Minnesota (USA) / Ontario (Canada) which is a very sparsely populated area with the two main industries being Farming (Sugar Beets) and Tourism (Fishing.) I only know about the Rainy River because I lived up there for a few years and fished the River but most of the state's residents do not know that as a location in our time zone. and here specifically is my issue with the proximity based approach currently being applied... the system currently picks locations closer to the target city even though they're across time zones. When picking a location for the city of Hibbing, Minnesota, USA -- the time zone defaults to America/Atikokan ... which is Eastern Standard Time (-5 GMT,) but all of Minnesota is Central Standard Time (-6 GMT.) This is also a problem for Grand Marais, Minnesota -- which gets lumped in with the America/Thunder_Bay ... which is actually Canada, not USA. Grand Marais, Minnesota (not Michigan) is set to EST and it should be CST. Minneapolis, Minnesota defaults to America/Rainy_River and it is further East than Hibbing. So there is an issue somewhere with how cities are associated with time zones. It seems like the NE "arrowhead" of Minnesota is all set to Eastern Standard Time instead of Central Standard Time. -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
According to Wikipedia there are 245 political entities in the world... http://en.wikipedia.org/wiki/List_of_countries ... and only 193 with general international recognition So we've got 24 time zones... A little history: In 1878, Sir Sandford Fleming (1827–1915) developed the system of worldwide time zones that we still use today. He proposed that the world be divided into 24 time zones, each spaced 15º (fifteen degrees) of longitude apart (like 24 sections of an orange). He came to this idea because Earth completes a rotation every 24 hours and there are 360º of longitude, so each hour Earth rotates 1/24th of a circle or 15º. So if this is the logic... why not just define each 24 hr time period... based on it's longitude... Then define "political" exemptions which to the best of my research cover large geographical terroritories but are clearly defined by geo- political boundaries... China is ONE timezone. A few US States don't do timezones.. .Alaska (USA) should span a few timezones, but has been consolidated to 1. And here's the current info on daylight savings time: http://webexhibits.org/daylightsaving/g.html Taking a look at this "large" problem and breaking it down to the most general concrete information and then defining exemptions .. has me looking at it this way... 1. define "true" time zones as represented by the only data we know to be consistant... Longitude. -- The location of the user is always technically based on Longitude and Latitude... so this way we should be able to determine the "true" timezone. 2. define continental and sub-continental exemptions -- define large exceptions... exemptions that span countries... -- maybe this never happens 3. define country-wide timezones -- basically which countries wrap themselves into a single timezone. --- China 4. define regional exemptions -- a regional exemption must fit inside of a country --- aka alaska, usa --- Navajo tribal nation spans 3 states and participates in daylight savings time even though part of the nation lies in Arizona which does not participate. --- Russia, 11 time-zones permanent daylight savings time (so 1hr ahead of actual time zone) --- other exemptions are the half and quarter-time modifications 5. unique / specific cirumstances... In South Asia, if you follow a straight line west along the 27º latitude you will move back and forth across time zones: from Pakistan UTC +5 hours, India +5:30, Nepal +5:45, India (Sikkim) +5:30, China +8, Bhutan +6, India (Arunachal Pradesh) +5:30, Myanmar +6:30. ... you could define the able based on the rules #2 and #3... and define regional areas between two longitudinal points... within a specified country. I think the key to the breakdown based on a descending order of priority (+): Default Time Zone based on Longitude Continent Country of Origin Region of County City / Other / Specific And the big news... has anybody seen this government ftp site with all of the timezone data defined? ftp://elsie.nci.nih.gov/pub/ -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
Yeah, In my solution I didn't mean that you'd need to document each city's timezone -- only if there was something unique about it... you should be able to just map countries and potentially states / regions of countries... *IF* you needed anything at all. Ryan -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 186441] Re: [Hardy] Recursive directory deletion doesnt work for external mounted drives
I can confirm this on Ubuntu Hardy 8.04 64-bit Updated as of today. Delete or Delete All gives the error: "Error Removing File: File Exists" Prompting you to Skip, Skip All or Cancel... with all three options just closing the delete dialog while leaving all files selected for deletion. -- [Hardy] Recursive directory deletion doesnt work for external mounted drives https://bugs.launchpad.net/bugs/186441 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 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This was working fine for me on my ThinkPad X61T laptop until the latest Kernel this worked fine. With the latest kernel (24-11) my laptop display now properly displays after resuming from suspend, but now I cannot control the brightness through the Gnome applet or the function keys on my keyboard. The keys (via OSD) and slider work and show that the brightness is being changed, but it doesn't actually change the brightness of the screen. -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
I registered a bug on this when I couldn't find this one... bug # 199976 I know this has all been rehashed, but I think trying to add location / TZ data for each location entry is not going to work because the system doesn't select a location entry with the proper timezone in the first place. I think an acceptable way to handle this time zone issue is to scrap the current location options and create a new location database with one entry per state / region / et al that fits into a timezone... currently there are many many many entries for the same time zones. Right now there are lots of time zone choices that don't seem to have any logic as to why they were selected. Coming from a US Perspective, I believe there are very few instances where timezones do not follow state borders. We should really have a tz entry for each state (maybe state capitals unless the state has two time zones) or reduce the number of entries overall in tzdata. Menominee, Wisconsin has a tz entry and I'm not sure why... we could remove all Mid-west USA entries except Chicago (which is CST) and I think people would figure it out. It would also be helpful to display the timezone (even just the abbreviation) for each location ... so that I know that Rainy River or Chicago are both in the same Time Zone. I'll explain my issue (below) with locations as they exist today: Rainy River is on the border of Minnesota (USA) / Ontario (Canada) which is a very sparsely populated area with the two main industries being Farming (Sugar Beets) and Tourism (Fishing.) I only know about the Rainy River because I lived up there for a few years and fished the River but most of the state's residents do not know that as a location in our time zone. and here specifically is my issue with the proximity based approach currently being applied... the system currently picks locations closer to the target city even though they're across time zones. When picking a location for the city of Hibbing, Minnesota, USA -- the time zone defaults to America/Atikokan ... which is Eastern Standard Time (-5 GMT,) but all of Minnesota is Central Standard Time (-6 GMT.) This is also a problem for Grand Marais, Minnesota -- which gets lumped in with the America/Thunder_Bay ... which is actually Canada, not USA. Grand Marais, Minnesota (not Michigan) is set to EST and it should be CST. Minneapolis, Minnesota defaults to America/Rainy_River and it is further East than Hibbing. So there is an issue somewhere with how cities are associated with time zones. It seems like the NE "arrowhead" of Minnesota is all set to Eastern Standard Time instead of Central Standard Time. -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
According to Wikipedia there are 245 political entities in the world... http://en.wikipedia.org/wiki/List_of_countries ... and only 193 with general international recognition So we've got 24 time zones... A little history: In 1878, Sir Sandford Fleming (1827–1915) developed the system of worldwide time zones that we still use today. He proposed that the world be divided into 24 time zones, each spaced 15º (fifteen degrees) of longitude apart (like 24 sections of an orange). He came to this idea because Earth completes a rotation every 24 hours and there are 360º of longitude, so each hour Earth rotates 1/24th of a circle or 15º. So if this is the logic... why not just define each 24 hr time period... based on it's longitude... Then define "political" exemptions which to the best of my research cover large geographical terroritories but are clearly defined by geo- political boundaries... China is ONE timezone. A few US States don't do timezones.. .Alaska (USA) should span a few timezones, but has been consolidated to 1. And here's the current info on daylight savings time: http://webexhibits.org/daylightsaving/g.html Taking a look at this "large" problem and breaking it down to the most general concrete information and then defining exemptions .. has me looking at it this way... 1. define "true" time zones as represented by the only data we know to be consistant... Longitude. -- The location of the user is always technically based on Longitude and Latitude... so this way we should be able to determine the "true" timezone. 2. define continental and sub-continental exemptions -- define large exceptions... exemptions that span countries... -- maybe this never happens 3. define country-wide timezones -- basically which countries wrap themselves into a single timezone. --- China 4. define regional exemptions -- a regional exemption must fit inside of a country --- aka alaska, usa --- Navajo tribal nation spans 3 states and participates in daylight savings time even though part of the nation lies in Arizona which does not participate. --- Russia, 11 time-zones permanent daylight savings time (so 1hr ahead of actual time zone) --- other exemptions are the half and quarter-time modifications 5. unique / specific cirumstances... In South Asia, if you follow a straight line west along the 27º latitude you will move back and forth across time zones: from Pakistan UTC +5 hours, India +5:30, Nepal +5:45, India (Sikkim) +5:30, China +8, Bhutan +6, India (Arunachal Pradesh) +5:30, Myanmar +6:30. ... you could define the able based on the rules #2 and #3... and define regional areas between two longitudinal points... within a specified country. I think the key to the breakdown based on a descending order of priority (+): Default Time Zone based on Longitude Continent Country of Origin Region of County City / Other / Specific And the big news... has anybody seen this government ftp site with all of the timezone data defined? ftp://elsie.nci.nih.gov/pub/ -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 88828] Re: mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /)
*** This bug is a duplicate of bug 107668 *** https://bugs.launchpad.net/bugs/107668 I've had the same issue now -- how can an older bug be the duplicate of a newer bug? -- mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /) https://bugs.launchpad.net/bugs/88828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu (via bug 107668). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This seems to be resolved. I've upgraded to 9.04 on both my laptops and I haven't had backlight issues since. On 4/21/2009 2:15 PM, Leann Ogasawara wrote: > @Ryan, is this fix still the cause of a regression for you? Does the > regression still remain in the upcoming Jaunty 9.04 release - > http://cdimage.ubuntu.com/daily-live/current/ . Please let us know. > Thanks. > > ** Changed in: linux (Ubuntu) > Status: Fix Committed => Fix Released > > ** Changed in: linux (Ubuntu) > Assignee: Ben Collins (ben-collins) => (unassigned) > > -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
Yeah, In my solution I didn't mean that you'd need to document each city's timezone -- only if there was something unique about it... you should be able to just map countries and potentially states / regions of countries... *IF* you needed anything at all. Ryan -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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
Re: [Bug 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This seems to be resolved. I've upgraded to 9.04 on both my laptops and I haven't had backlight issues since. On 4/21/2009 2:15 PM, Leann Ogasawara wrote: > @Ryan, is this fix still the cause of a regression for you? Does the > regression still remain in the upcoming Jaunty 9.04 release - > http://cdimage.ubuntu.com/daily-live/current/ . Please let us know. > Thanks. > > ** Changed in: linux (Ubuntu) > Status: Fix Committed => Fix Released > > ** Changed in: linux (Ubuntu) > Assignee: Ben Collins (ben-collins) => (unassigned) > > -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 186441] Re: [Hardy] Recursive directory deletion doesnt work for external mounted drives
I can confirm this on Ubuntu Hardy 8.04 64-bit Updated as of today. Delete or Delete All gives the error: "Error Removing File: File Exists" Prompting you to Skip, Skip All or Cancel... with all three options just closing the delete dialog while leaving all files selected for deletion. -- [Hardy] Recursive directory deletion doesnt work for external mounted drives https://bugs.launchpad.net/bugs/186441 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 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
This was working fine for me on my ThinkPad X61T laptop until the latest Kernel this worked fine. With the latest kernel (24-11) my laptop display now properly displays after resuming from suspend, but now I cannot control the brightness through the Gnome applet or the function keys on my keyboard. The keys (via OSD) and slider work and show that the brightness is being changed, but it doesn't actually change the brightness of the screen. -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
I registered a bug on this when I couldn't find this one... bug # 199976 I know this has all been rehashed, but I think trying to add location / TZ data for each location entry is not going to work because the system doesn't select a location entry with the proper timezone in the first place. I think an acceptable way to handle this time zone issue is to scrap the current location options and create a new location database with one entry per state / region / et al that fits into a timezone... currently there are many many many entries for the same time zones. Right now there are lots of time zone choices that don't seem to have any logic as to why they were selected. Coming from a US Perspective, I believe there are very few instances where timezones do not follow state borders. We should really have a tz entry for each state (maybe state capitals unless the state has two time zones) or reduce the number of entries overall in tzdata. Menominee, Wisconsin has a tz entry and I'm not sure why... we could remove all Mid-west USA entries except Chicago (which is CST) and I think people would figure it out. It would also be helpful to display the timezone (even just the abbreviation) for each location ... so that I know that Rainy River or Chicago are both in the same Time Zone. I'll explain my issue (below) with locations as they exist today: Rainy River is on the border of Minnesota (USA) / Ontario (Canada) which is a very sparsely populated area with the two main industries being Farming (Sugar Beets) and Tourism (Fishing.) I only know about the Rainy River because I lived up there for a few years and fished the River but most of the state's residents do not know that as a location in our time zone. and here specifically is my issue with the proximity based approach currently being applied... the system currently picks locations closer to the target city even though they're across time zones. When picking a location for the city of Hibbing, Minnesota, USA -- the time zone defaults to America/Atikokan ... which is Eastern Standard Time (-5 GMT,) but all of Minnesota is Central Standard Time (-6 GMT.) This is also a problem for Grand Marais, Minnesota -- which gets lumped in with the America/Thunder_Bay ... which is actually Canada, not USA. Grand Marais, Minnesota (not Michigan) is set to EST and it should be CST. Minneapolis, Minnesota defaults to America/Rainy_River and it is further East than Hibbing. So there is an issue somewhere with how cities are associated with time zones. It seems like the NE "arrowhead" of Minnesota is all set to Eastern Standard Time instead of Central Standard Time. -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
According to Wikipedia there are 245 political entities in the world... http://en.wikipedia.org/wiki/List_of_countries ... and only 193 with general international recognition So we've got 24 time zones... A little history: In 1878, Sir Sandford Fleming (1827–1915) developed the system of worldwide time zones that we still use today. He proposed that the world be divided into 24 time zones, each spaced 15º (fifteen degrees) of longitude apart (like 24 sections of an orange). He came to this idea because Earth completes a rotation every 24 hours and there are 360º of longitude, so each hour Earth rotates 1/24th of a circle or 15º. So if this is the logic... why not just define each 24 hr time period... based on it's longitude... Then define "political" exemptions which to the best of my research cover large geographical terroritories but are clearly defined by geo- political boundaries... China is ONE timezone. A few US States don't do timezones.. .Alaska (USA) should span a few timezones, but has been consolidated to 1. And here's the current info on daylight savings time: http://webexhibits.org/daylightsaving/g.html Taking a look at this "large" problem and breaking it down to the most general concrete information and then defining exemptions .. has me looking at it this way... 1. define "true" time zones as represented by the only data we know to be consistant... Longitude. -- The location of the user is always technically based on Longitude and Latitude... so this way we should be able to determine the "true" timezone. 2. define continental and sub-continental exemptions -- define large exceptions... exemptions that span countries... -- maybe this never happens 3. define country-wide timezones -- basically which countries wrap themselves into a single timezone. --- China 4. define regional exemptions -- a regional exemption must fit inside of a country --- aka alaska, usa --- Navajo tribal nation spans 3 states and participates in daylight savings time even though part of the nation lies in Arizona which does not participate. --- Russia, 11 time-zones permanent daylight savings time (so 1hr ahead of actual time zone) --- other exemptions are the half and quarter-time modifications 5. unique / specific cirumstances... In South Asia, if you follow a straight line west along the 27º latitude you will move back and forth across time zones: from Pakistan UTC +5 hours, India +5:30, Nepal +5:45, India (Sikkim) +5:30, China +8, Bhutan +6, India (Arunachal Pradesh) +5:30, Myanmar +6:30. ... you could define the able based on the rules #2 and #3... and define regional areas between two longitudinal points... within a specified country. I think the key to the breakdown based on a descending order of priority (+): Default Time Zone based on Longitude Continent Country of Origin Region of County City / Other / Specific And the big news... has anybody seen this government ftp site with all of the timezone data defined? ftp://elsie.nci.nih.gov/pub/ -- Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing) https://bugs.launchpad.net/bugs/185190 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 88828] Re: mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /)
*** This bug is a duplicate of bug 107668 *** https://bugs.launchpad.net/bugs/107668 I've had the same issue now -- how can an older bug be the duplicate of a newer bug? -- mount_point cannot contain the following characters: newline, G_DIR_SEPARATOR (usually /) https://bugs.launchpad.net/bugs/88828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu (via bug 107668). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
