Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd
What about Jaunty's Compiz?
On Mon, Jun 22, 2009 at 12:21 PM, Martin Pitt
wrote:
> karmic's compiz does not blacklist 965 any more either.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: Fix Released
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Released
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Fix Released
> Status in compiz in Ubuntu Karmic: Fix Released
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specified. Users can still override this with their own
> settings, larger or smaller, as desired.
>
> A side effect of this patch is that it also mitigates bug 158415 to a
> degree, which will make projector usage somewhat easier for this hardware
> because it will enable X to recognize higher resolutions available from the
> external monitor than were available on initial boot.
>
> [Test Case]
> The best method found to reproduce the bug is:
> a. Enable compiz
> b. Set your desktop to a 6x1 workspace layout
> c. Run http://launchpadlibrarian.net/25683477/repro.sh
> d. System will freeze anywhere from 1-20 min typically
> e. Power-button shutdown is required to reset the system
>
> [Regression Potential]
> In general, Virtual has been widely and extensively tested, so we do not
> expect this patch to trigger regressions.
>
> The patch is coded to only take effect on i965 systems, so the scope of any
> regression that might conceivably be triggered will be limited to just that
> hardware.
>
> [Suspects]
> Omitting obviously trivial, unrelated changes, here are what changed in
> several suspect packages in the timeframe in question:
>
> * intel driver:
> 4/01: 118_drop_legacy3d.patch: Removed Legacy3D
> 4/03: 114_fix_xv_with_non_gem.patch: Dropped since it caused regression
> 4/06: 119_drm_bo_unreference_needs_null.patch: Fixes various nullptr
> derefs
> 4/08: 120_fix_vt_switch.patch: Fix nullptr deref in video playback
>
> * xserver:
> 4/08: 177_animated_cursor_change_master.patch: fixes animated cursors
> 4/06: 174_set_bg_pixmap_of_cow_to_none.patch: Sets bg pixmap of
> composite overlay window to None
> 3/30: 172_cwgetbackingpicture_nullptr_check.patch: fix race condition
> when minimzing/maximizing firefox with flash video playing.
>
> * mesa:
> 4/03: 7.4 released
>* Added MESA_GLX_FORCE_DIRECT env var for Xlib/software driver
>* GLSL version 1.20 is returnd by the GL_SHADING_LANGUAGE_VERSION query
>* glGetActiveUniform() returned wrong size for some array types
>* Fixed some error checking in glUniform()
>* Fixed a potential glTexImage('proxy target') segfault
>* Fixed bad reference counting for 1D/2D texture arrays
>* Fixed VBO + glPush/PopClientAttrib() bug #19835
> * Assorted i965 driver bug fixes
>* Fixed a Windows compilation failure in s_triangle.c
>* Fixed a GLSL array indexing bug
>* Fixes for building on Haiku
>
> * linux:
> 4/04: 2.6.28-11.41: Revert MCHBAR patch
> 4/02: 2.6.28-11.40: Add MCHBAR patch
>
> * libdrm:
> 4/04: 02_libdrm_nouveau_update.patch: Only affects nouveau code
> 3/29: libdrm-nouveau1.symbols: Probably innocuous
>
> [Workarounds]
> Various people have found one or more of the following have helped to
> reduce the frequency
Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd --- please test new package
On Sun, Jun 7, 2009 at 1:21 AM, Tom Jaeger wrote: > This is going to happen if you "unredirect" fullscreen windows (System > -> Preferences -> CompizConfig Settings Manager -> General Options -> > General -> Unredirect Fullscreen Windows). That fixed it... although I don't understand what it did, or why it never did that before. :P Now if I could just get my window borders back... > > Thomas Foss wrote: > > When in full-screen mode in Firefox (F11), the entire screen "blinks" > > whenever the little alt-text window (or whatever it's called) pops up. > It's > > very annoying. I think it's more of a Compiz problem than a graphics > problem > > in general... but it didn't do this before. Perhaps a fresh install of > > Compiz will settle it down... > > > > --Thomas > > -- > [i965] X freezes starting on April 3rd > https://bugs.launchpad.net/bugs/359392 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in X.org xf86-video-intel: Confirmed > Status in “compiz” source package in Ubuntu: In Progress > Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released > Status in compiz in Ubuntu Jaunty: Fix Committed > Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed > Status in compiz in Ubuntu Karmic: In Progress > Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released > > Bug description: > [Problem] > Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965 > users started noticing X freeze after several hours of use, triggered by > application usage especially noticeable with (but not unique to) compiz > enabled. > > [Impact] > The freeze bug affects a subset of i965 based systems, most particularly > those using compiz. Exact numbers cannot be determined, but may be as high > as 25-50% based on rough estimates. > > The problem is severe: An unpredictable lockup of the system that requires > a power cycle to recover from. For some users it comes on within minutes, > while for others it comes after a few hours of use. > > [How Addressed in Development Version] > For now, the patch being proposed for Jaunty has been uploaded to Karmic. > > Longer term, we plan to move from EXA to UXA once the latter is stable > enough. It has been found that while UXA exhibits other kinds of freezes, > we've not yet been able to reproduce this particular freeze there. > > [Patch for Jaunty] > A low-risk workaround that has proven effective at eliminating freezes, or > at least greatly reducing their frequency, is to increase the Virtual > framebuffer size. Some users do this locally as a matter of course to gain > dual-head support, so this setting has received extremely widespread testing > already. > > The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it > is not otherwise specified. Users can still override this with their own > settings, larger or smaller, as desired. > > A side effect of this patch is that it also mitigates bug 158415 to a > degree, which will make projector usage somewhat easier for this hardware > because it will enable X to recognize higher resolutions available from the > external monitor than were available on initial boot. > > [Test Case] > The best method found to reproduce the bug is: > a. Enable compiz > b. Set your desktop to a 6x1 workspace layout > c. Run http://launchpadlibrarian.net/25683477/repro.sh > d. System will freeze anywhere from 1-20 min typically > e. Power-button shutdown is required to reset the system > > [Regression Potential] > In general, Virtual has been widely and extensively tested, so we do not > expect this patch to trigger regressions. > > The patch is coded to only take effect on i965 systems, so the scope of any > regression that might conceivably be triggered will be limited to just that > hardware. > > [Suspects] > Omitting obviously trivial, unrelated changes, here are what changed in > several suspect packages in the timeframe in question: > > * intel driver: > 4/01: 118_drop_legacy3d.patch: Removed Legacy3D > 4/03: 114_fix_xv_with_non_gem.patch: Dropped since it caused regression > 4/06: 119_drm_bo_unreference_needs_null.patch: Fixes various nullptr > derefs > 4/08: 120_fix_vt_switch.patch: Fix nullptr deref in video playback > > * xserver: > 4/08: 177_animated_cursor_change_master.patch: fixes animated cursors > 4/06: 174_set_bg_pixmap_of_cow_to_none.patch: Sets bg pixmap of > composite overlay window to None > 3/30: 172_cwgetbackingpicture_nullptr_check.patch: fix race condition > when minimzing/maximizing fi
Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd --- please test new package
When in full-screen mode in Firefox (F11), the entire screen "blinks" whenever the little alt-text window (or whatever it's called) pops up. It's very annoying. I think it's more of a Compiz problem than a graphics problem in general... but it didn't do this before. Perhaps a fresh install of Compiz will settle it down... --Thomas On Sat, Jun 6, 2009 at 5:51 PM, Thomas wrote: > Graphics are really smooth. Window borders have gone all wonky... not > glitching, just... different. And I can't seem to change them back. > http://dl.getdropbox.com/u/455435/LiveJournal//Metacity.png > http://dl.getdropbox.com/u/455435/LiveJournal/Compiz.png > (The "Metacity" screenshot is what the window borders used to look like all > the time, and still look like in Metacity.) > > I also can't seem to grab the cube with the middle mouse button anymore... > Somehow I remember being able to rotate the cube with Ctrl+Alt+Button1 or > also with the middle mouse button... but I only see one "initiate" shortcut > setting, so I don't know how to get it back to doing both. Hmm. > > Overall though I think these are small problems for which I just need to > find the right settings. I haven't seen any problems with the graphics so > far. Are there any specific tests I should do to try to provoke it? > > --Thomas > > > On Sat, Jun 6, 2009 at 5:23 PM, Thomas wrote: > >> Alright, I'll give it a shot. >> >> --Thomas >> >> >> On Sat, Jun 6, 2009 at 4:56 PM, Martin Pitt wrote: >> >>> Thomas Foss [2009-06-06 13:18 -]: >>> > Quick question... does these freezes only happen when Compiz is >>> enabled? I >>> > think I have this bug (because I've got a 965GM chipset and Compiz is >>> > disabled), but I've never had any freezes. Should I be re-enabling >>> Compiz to >>> > see if this patch fixes the problem, or will it remove the Compiz >>> blacklist >>> > automatically? >>> >>> It mostly occurs with compiz. You might also be able to reproduce it >>> with other 3D applications, though. >>> >>> Please note that the compiz package in jaunty-proposed removed the >>> blacklisting of 965, so you should test both together. >>> >>> -- >>> [i965] X freezes starting on April 3rd >>> https://bugs.launchpad.net/bugs/359392 >>> You received this bug notification because you are a direct subscriber >>> of the bug. >>> >>> Status in X.org xf86-video-intel: Confirmed >>> Status in “compiz” source package in Ubuntu: In Progress >>> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix >>> Released >>> Status in compiz in Ubuntu Jaunty: Fix Committed >>> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed >>> Status in compiz in Ubuntu Karmic: In Progress >>> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released >>> >>> Bug description: >>> [Problem] >>> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965 >>> users started noticing X freeze after several hours of use, triggered by >>> application usage especially noticeable with (but not unique to) compiz >>> enabled. >>> >>> [Impact] >>> The freeze bug affects a subset of i965 based systems, most particularly >>> those using compiz. Exact numbers cannot be determined, but may be as high >>> as 25-50% based on rough estimates. >>> >>> The problem is severe: An unpredictable lockup of the system that >>> requires a power cycle to recover from. For some users it comes on within >>> minutes, while for others it comes after a few hours of use. >>> >>> [How Addressed in Development Version] >>> For now, the patch being proposed for Jaunty has been uploaded to Karmic. >>> >>> Longer term, we plan to move from EXA to UXA once the latter is stable >>> enough. It has been found that while UXA exhibits other kinds of freezes, >>> we've not yet been able to reproduce this particular freeze there. >>> >>> [Patch for Jaunty] >>> A low-risk workaround that has proven effective at eliminating freezes, >>> or at least greatly reducing their frequency, is to increase the Virtual >>> framebuffer size. Some users do this locally as a matter of course to gain >>> dual-head support, so this setting has received extremely widespread testing >>> already. >>> >>> The patch for Jaunty causes the Virtual size to be se
Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd --- please test new package
Graphics are really smooth. Window borders have gone all wonky... not glitching, just... different. And I can't seem to change them back. http://dl.getdropbox.com/u/455435/LiveJournal//Metacity.png http://dl.getdropbox.com/u/455435/LiveJournal/Compiz.png (The "Metacity" screenshot is what the window borders used to look like all the time, and still look like in Metacity.) I also can't seem to grab the cube with the middle mouse button anymore... Somehow I remember being able to rotate the cube with Ctrl+Alt+Button1 or also with the middle mouse button... but I only see one "initiate" shortcut setting, so I don't know how to get it back to doing both. Hmm. Overall though I think these are small problems for which I just need to find the right settings. I haven't seen any problems with the graphics so far. Are there any specific tests I should do to try to provoke it? --Thomas On Sat, Jun 6, 2009 at 5:23 PM, Thomas wrote: > Alright, I'll give it a shot. > > --Thomas > > > On Sat, Jun 6, 2009 at 4:56 PM, Martin Pitt wrote: > >> Thomas Foss [2009-06-06 13:18 -]: >> > Quick question... does these freezes only happen when Compiz is enabled? >> I >> > think I have this bug (because I've got a 965GM chipset and Compiz is >> > disabled), but I've never had any freezes. Should I be re-enabling >> Compiz to >> > see if this patch fixes the problem, or will it remove the Compiz >> blacklist >> > automatically? >> >> It mostly occurs with compiz. You might also be able to reproduce it >> with other 3D applications, though. >> >> Please note that the compiz package in jaunty-proposed removed the >> blacklisting of 965, so you should test both together. >> >> -- >> [i965] X freezes starting on April 3rd >> https://bugs.launchpad.net/bugs/359392 >> You received this bug notification because you are a direct subscriber >> of the bug. >> >> Status in X.org xf86-video-intel: Confirmed >> Status in “compiz” source package in Ubuntu: In Progress >> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix >> Released >> Status in compiz in Ubuntu Jaunty: Fix Committed >> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed >> Status in compiz in Ubuntu Karmic: In Progress >> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released >> >> Bug description: >> [Problem] >> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965 >> users started noticing X freeze after several hours of use, triggered by >> application usage especially noticeable with (but not unique to) compiz >> enabled. >> >> [Impact] >> The freeze bug affects a subset of i965 based systems, most particularly >> those using compiz. Exact numbers cannot be determined, but may be as high >> as 25-50% based on rough estimates. >> >> The problem is severe: An unpredictable lockup of the system that >> requires a power cycle to recover from. For some users it comes on within >> minutes, while for others it comes after a few hours of use. >> >> [How Addressed in Development Version] >> For now, the patch being proposed for Jaunty has been uploaded to Karmic. >> >> Longer term, we plan to move from EXA to UXA once the latter is stable >> enough. It has been found that while UXA exhibits other kinds of freezes, >> we've not yet been able to reproduce this particular freeze there. >> >> [Patch for Jaunty] >> A low-risk workaround that has proven effective at eliminating freezes, or >> at least greatly reducing their frequency, is to increase the Virtual >> framebuffer size. Some users do this locally as a matter of course to gain >> dual-head support, so this setting has received extremely widespread testing >> already. >> >> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it >> is not otherwise specified. Users can still override this with their own >> settings, larger or smaller, as desired. >> >> A side effect of this patch is that it also mitigates bug 158415 to a >> degree, which will make projector usage somewhat easier for this hardware >> because it will enable X to recognize higher resolutions available from the >> external monitor than were available on initial boot. >> >> [Test Case] >> The best method found to reproduce the bug is: >> a. Enable compiz >> b. Set your desktop to a 6x1 workspace layout >> c. Run http://launchpadlibrarian.net/25683477/repro.sh >> d. System will freeze anywhere from 1-20 min typically >> e
Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd --- please test new package
Alright, I'll give it a shot. --Thomas On Sat, Jun 6, 2009 at 4:56 PM, Martin Pitt wrote: > Thomas Foss [2009-06-06 13:18 -]: > > Quick question... does these freezes only happen when Compiz is enabled? > I > > think I have this bug (because I've got a 965GM chipset and Compiz is > > disabled), but I've never had any freezes. Should I be re-enabling Compiz > to > > see if this patch fixes the problem, or will it remove the Compiz > blacklist > > automatically? > > It mostly occurs with compiz. You might also be able to reproduce it > with other 3D applications, though. > > Please note that the compiz package in jaunty-proposed removed the > blacklisting of 965, so you should test both together. > > -- > [i965] X freezes starting on April 3rd > https://bugs.launchpad.net/bugs/359392 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in X.org xf86-video-intel: Confirmed > Status in “compiz” source package in Ubuntu: In Progress > Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released > Status in compiz in Ubuntu Jaunty: Fix Committed > Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed > Status in compiz in Ubuntu Karmic: In Progress > Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released > > Bug description: > [Problem] > Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965 > users started noticing X freeze after several hours of use, triggered by > application usage especially noticeable with (but not unique to) compiz > enabled. > > [Impact] > The freeze bug affects a subset of i965 based systems, most particularly > those using compiz. Exact numbers cannot be determined, but may be as high > as 25-50% based on rough estimates. > > The problem is severe: An unpredictable lockup of the system that requires > a power cycle to recover from. For some users it comes on within minutes, > while for others it comes after a few hours of use. > > [How Addressed in Development Version] > For now, the patch being proposed for Jaunty has been uploaded to Karmic. > > Longer term, we plan to move from EXA to UXA once the latter is stable > enough. It has been found that while UXA exhibits other kinds of freezes, > we've not yet been able to reproduce this particular freeze there. > > [Patch for Jaunty] > A low-risk workaround that has proven effective at eliminating freezes, or > at least greatly reducing their frequency, is to increase the Virtual > framebuffer size. Some users do this locally as a matter of course to gain > dual-head support, so this setting has received extremely widespread testing > already. > > The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it > is not otherwise specified. Users can still override this with their own > settings, larger or smaller, as desired. > > A side effect of this patch is that it also mitigates bug 158415 to a > degree, which will make projector usage somewhat easier for this hardware > because it will enable X to recognize higher resolutions available from the > external monitor than were available on initial boot. > > [Test Case] > The best method found to reproduce the bug is: > a. Enable compiz > b. Set your desktop to a 6x1 workspace layout > c. Run http://launchpadlibrarian.net/25683477/repro.sh > d. System will freeze anywhere from 1-20 min typically > e. Power-button shutdown is required to reset the system > > [Regression Potential] > In general, Virtual has been widely and extensively tested, so we do not > expect this patch to trigger regressions. > > The patch is coded to only take effect on i965 systems, so the scope of any > regression that might conceivably be triggered will be limited to just that > hardware. > > [Suspects] > Omitting obviously trivial, unrelated changes, here are what changed in > several suspect packages in the timeframe in question: > > * intel driver: > 4/01: 118_drop_legacy3d.patch: Removed Legacy3D > 4/03: 114_fix_xv_with_non_gem.patch: Dropped since it caused regression > 4/06: 119_drm_bo_unreference_needs_null.patch: Fixes various nullptr > derefs > 4/08: 120_fix_vt_switch.patch: Fix nullptr deref in video playback > > * xserver: > 4/08: 177_animated_cursor_change_master.patch: fixes animated cursors > 4/06: 174_set_bg_pixmap_of_cow_to_none.patch: Sets bg pixmap of > composite overlay window to None > 3/30: 172_cwgetbackingpicture_nullptr_check.patch: fix race condition > when minimzing/maximizing firefox with flash video playing. > > * mesa: > 4/03: 7.4 released >* Added MESA_GLX_FORCE_DI
Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd --- please test new package
Quick question... does these freezes only happen when Compiz is enabled? I
think I have this bug (because I've got a 965GM chipset and Compiz is
disabled), but I've never had any freezes. Should I be re-enabling Compiz to
see if this patch fixes the problem, or will it remove the Compiz blacklist
automatically?
On Sat, Jun 6, 2009 at 2:55 PM, Bernhard
wrote:
> I tested with both compiz and metacity and with many audio and video
> streams simulanteously and it seems to me that this last archive green
> package has seriously improved my experience, especially in that there
> is no more audio and video stuttering. I never had freezes though, so
> I cannot say anything about that.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: In Progress
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Committed
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
> Status in compiz in Ubuntu Karmic: In Progress
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specified. Users can still override this with their own
> settings, larger or smaller, as desired.
>
> A side effect of this patch is that it also mitigates bug 158415 to a
> degree, which will make projector usage somewhat easier for this hardware
> because it will enable X to recognize higher resolutions available from the
> external monitor than were available on initial boot.
>
> [Test Case]
> The best method found to reproduce the bug is:
> a. Enable compiz
> b. Set your desktop to a 6x1 workspace layout
> c. Run http://launchpadlibrarian.net/25683477/repro.sh
> d. System will freeze anywhere from 1-20 min typically
> e. Power-button shutdown is required to reset the system
>
> [Regression Potential]
> In general, Virtual has been widely and extensively tested, so we do not
> expect this patch to trigger regressions.
>
> The patch is coded to only take effect on i965 systems, so the scope of any
> regression that might conceivably be triggered will be limited to just that
> hardware.
>
> [Suspects]
> Omitting obviously trivial, unrelated changes, here are what changed in
> several suspect packages in the timeframe in question:
>
> * intel driver:
> 4/01: 118_drop_legacy3d.patch: Removed Legacy3D
> 4/03: 114_fix_xv_with_non_gem.patch: Dropped since it caused regression
> 4/06: 119_drm_bo_unreference_needs_null.patch: Fixes various nullptr
> derefs
> 4/08: 120_fix_vt_switch.patch: Fix nullptr deref in video playback
>
> * xserver:
> 4/08: 177_animated_cursor_change_master.patch: fixes animated cursors
> 4/06: 174_set_bg_pixmap_of_cow_to_none.patch: Sets bg pixmap of
> composite overlay window to None
> 3/30: 172_cwgetbackingpicture_nullptr_check.patch: fix race condition
> when minimzing/maximizing firefox with flash video playing.
>
> * mesa:
> 4/03: 7.4 released
>* Added MESA_GLX_FORCE_DIRECT env var for Xlib/software driver
>* GLSL version 1.20 is returnd by the GL_SHADING_LANGUAGE_VERSION query
>* glGetActiveUniform() returned wrong size for some array types
>* Fixed some error checking in glUniform()
>* Fixed a potential glTexImage('proxy target') segfault
>* Fixed bad reference counting for 1D/2D texture arrays
>* Fixed VBO + glPush/PopC
Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd
On Thu, Jun 4, 2009 at 9:59 PM, reini wrote: > Am Donnerstag 04 Juni 2009 schrieb ichudov: > > On Thu, Jun 04, 2009 at 06:00:37PM -, Vincenzo Ciancia wrote: > > > In this case, putting the old driver back in the distribution > > > and starting to chose the right driver based on user's feedback > > > until the too many intel issues are solved, would be mandatory. > > > > I tend to agree with you. > > I'd like to point out that I tried the old (i.e. intrepid) driver > version (don't remember where I found it - it was somewhere in the > ubuntu wiki AFAIR). It didn't change the freezing problem at all > (made it worse if anything). > > So switching back to the old driver isn't really a very helpful > suggestion... > > --reini That's very odd... the problem definitely wasn't around in Intrepid, at least for me. -- [i965] X freezes starting on April 3rd https://bugs.launchpad.net/bugs/359392 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd
How would one reinstall the old driver? I didn't think it was an option. Heck, I'd downgrade back to Intrepid if I there was a way to do it. There should be a "downgrade" button that's as big and shiny as the Jaunty upgrade button was. (Or maybe the upgrade buttons could just have little warning labels on the side... like cigarettes do.) On Thu, Jun 4, 2009 at 8:08 PM, Vincenzo Ciancia wrote: > Il giorno gio, 04/06/2009 alle 20.00 +0200, Vincenzo Ciancia ha scritto: > > > > > > In this case, putting the old driver back in the distribution and > > starting to chose the right driver based on user's feedback until the > > too many intel issues are solved, would be mandatory. > > > > @Bryce, it's easy to put back the old driver in the distribution, and > > if > > there is not enough manpower to create the whitelist, I would chose > > the > > old one as a default. May I ask you "why not"? > > > > A piece is missing here "the whitelist" would be created based on user > feedback to enable the new driver only for those combinations where it > actually works. I said "works" without any attributes :) > > V. > > -- > [i965] X freezes starting on April 3rd > https://bugs.launchpad.net/bugs/359392 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in X.org xf86-video-intel: Confirmed > Status in “compiz” source package in Ubuntu: In Progress > Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released > Status in compiz in Ubuntu Jaunty: Fix Committed > Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed > Status in compiz in Ubuntu Karmic: In Progress > Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released > > Bug description: > [Problem] > Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965 > users started noticing X freeze after several hours of use, triggered by > application usage especially noticeable with (but not unique to) compiz > enabled. > > [Impact] > The freeze bug affects a subset of i965 based systems, most particularly > those using compiz. Exact numbers cannot be determined, but may be as high > as 25-50% based on rough estimates. > > The problem is severe: An unpredictable lockup of the system that requires > a power cycle to recover from. For some users it comes on within minutes, > while for others it comes after a few hours of use. > > [How Addressed in Development Version] > For now, the patch being proposed for Jaunty has been uploaded to Karmic. > > Longer term, we plan to move from EXA to UXA once the latter is stable > enough. It has been found that while UXA exhibits other kinds of freezes, > we've not yet been able to reproduce this particular freeze there. > > [Patch for Jaunty] > A low-risk workaround that has proven effective at eliminating freezes, or > at least greatly reducing their frequency, is to increase the Virtual > framebuffer size. Some users do this locally as a matter of course to gain > dual-head support, so this setting has received extremely widespread testing > already. > > The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it > is not otherwise specified. Users can still override this with their own > settings, larger or smaller, as desired. > > A side effect of this patch is that it also mitigates bug 158415 to a > degree, which will make projector usage somewhat easier for this hardware > because it will enable X to recognize higher resolutions available from the > external monitor than were available on initial boot. > > [Test Case] > The best method found to reproduce the bug is: > a. Enable compiz > b. Set your desktop to a 6x1 workspace layout > c. Run http://launchpadlibrarian.net/25683477/repro.sh > d. System will freeze anywhere from 1-20 min typically > e. Power-button shutdown is required to reset the system > > [Regression Potential] > In general, Virtual has been widely and extensively tested, so we do not > expect this patch to trigger regressions. > > The patch is coded to only take effect on i965 systems, so the scope of any > regression that might conceivably be triggered will be limited to just that > hardware. > > [Suspects] > Omitting obviously trivial, unrelated changes, here are what changed in > several suspect packages in the timeframe in question: > > * intel driver: > 4/01: 118_drop_legacy3d.patch: Removed Legacy3D > 4/03: 114_fix_xv_with_non_gem.patch: Dropped since it caused regression > 4/06: 119_drm_bo_unreference_needs_null.patch: Fixes various nullptr > derefs > 4/08: 120_fix_vt_switch.patch: Fix nullptr deref in video playback > > * xserver: > 4/08: 177_animated_cursor_change_master.patch: fixes animated cursors > 4/06: 174_set_bg_pixmap_of_cow_to_none.patch: Sets bg pixmap of > composite overlay window to None > 3/30: 172_cwgetbackingpicture_nullptr_check.patch: fix race condition > when minimzing/maximizing firefox with flash video playing. > > * mesa: > 4/03:
Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd
You can say that again...
On Thu, Jun 4, 2009 at 3:17 PM, ichudov wrote:
> When people say "Linux is not ready for desktop", this is what they
> mean.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: In Progress
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Committed
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
> Status in compiz in Ubuntu Karmic: In Progress
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specified. Users can still override this with their own
> settings, larger or smaller, as desired.
>
> A side effect of this patch is that it also mitigates bug 158415 to a
> degree, which will make projector usage somewhat easier for this hardware
> because it will enable X to recognize higher resolutions available from the
> external monitor than were available on initial boot.
>
> [Test Case]
> The best method found to reproduce the bug is:
> a. Enable compiz
> b. Set your desktop to a 6x1 workspace layout
> c. Run http://launchpadlibrarian.net/25683477/repro.sh
> d. System will freeze anywhere from 1-20 min typically
> e. Power-button shutdown is required to reset the system
>
> [Regression Potential]
> In general, Virtual has been widely and extensively tested, so we do not
> expect this patch to trigger regressions.
>
> The patch is coded to only take effect on i965 systems, so the scope of any
> regression that might conceivably be triggered will be limited to just that
> hardware.
>
> [Suspects]
> Omitting obviously trivial, unrelated changes, here are what changed in
> several suspect packages in the timeframe in question:
>
> * intel driver:
> 4/01: 118_drop_legacy3d.patch: Removed Legacy3D
> 4/03: 114_fix_xv_with_non_gem.patch: Dropped since it caused regression
> 4/06: 119_drm_bo_unreference_needs_null.patch: Fixes various nullptr
> derefs
> 4/08: 120_fix_vt_switch.patch: Fix nullptr deref in video playback
>
> * xserver:
> 4/08: 177_animated_cursor_change_master.patch: fixes animated cursors
> 4/06: 174_set_bg_pixmap_of_cow_to_none.patch: Sets bg pixmap of
> composite overlay window to None
> 3/30: 172_cwgetbackingpicture_nullptr_check.patch: fix race condition
> when minimzing/maximizing firefox with flash video playing.
>
> * mesa:
> 4/03: 7.4 released
>* Added MESA_GLX_FORCE_DIRECT env var for Xlib/software driver
>* GLSL version 1.20 is returnd by the GL_SHADING_LANGUAGE_VERSION query
>* glGetActiveUniform() returned wrong size for some array types
>* Fixed some error checking in glUniform()
>* Fixed a potential glTexImage('proxy target') segfault
>* Fixed bad reference counting for 1D/2D texture arrays
>* Fixed VBO + glPush/PopClientAttrib() bug #19835
> * Assorted i965 driver bug fixes
>* Fixed a Windows compilation failure in s_triangle.c
>* Fixed a GLSL array indexing bug
>* Fixes for building on Haiku
>
> * linux:
> 4/04: 2.6.28-11.41: Revert MCHBAR patch
> 4/02: 2.6.28-11.40: Add MCHBAR patch
>
> * libdrm:
> 4/04: 02_libdrm_nouveau_update.patch: Only affects nouveau code
> 3/29: libdrm-nouveau1.symbols: Probably innocuous
>
> [Workarounds]
> Various people have found one or more of the following have helped to
> reduce the f
[Bug 367830] Re: F-Spot lost the folder structure in 9.04
*** This bug is a duplicate of bug 353989 *** https://bugs.launchpad.net/bugs/353989 There's a patch over at this other bug which seems to be fixing the issue: https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/354264/comments/9 ** This bug has been marked a duplicate of bug 353989 Import saves images in home root -- F-Spot lost the folder structure in 9.04 https://bugs.launchpad.net/bugs/367830 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 359392] Re: [i965] X freezes starting on April 3rd
As was mentioned before, this bug does not exist in UXA... I wouldn't really call it a "fix", it simply never arose in that code. But there are many unrelated valid reasons why Ubuntu doesn't use UXA yet. On Thu, May 28, 2009 at 3:35 PM, Marius Gedminas wrote: > On Thu, May 28, 2009 at 11:38:38AM -, Gustavo Narea wrote: > > Jgull8502 said: > > > I have a Dell m1330 Intel Corporation Mobile GM965/GL960 Integrated > > > Graphics Controller (rev 0c). I've been holding off upgrading because > of > > > the intel bugs. I'm wondering if it's relatively safe to upgrade to > 9.04 > > > now. I don't mind doing some configuring but I'm wondering if there's a > > > condensed list of things I can try if I experience this freezing. > > > > I have the same hardware and, as I reported here recently, this bug is > solved > > with UXA: > > https://wiki.ubuntu.com/X/UxaTesting > > > > UXA works perfectly here. Just add that line to you X config, reboot > > and enjoy your Ubuntu install. > > > > UXA fixes all the bugs of the previous driver: Display corruptions and X > > freezes. Plus, it doesn't introduce _any_ bugs. > > Caveat emptor. When I tried UXA on Intel GM965 in Jaunty, I suffered > from two show-stopper bugs: (1) memory leak that would eat up all the > RAM within a day or two, causing all applications to be swapped out and > (2) X would crash on every suspend & resume, requiring me to log in > again and restart all the apps. Both bugs affected me with stock Jaunty > driver as well as xserver-xorg-video-intel 2.7.1 from the ubuntu-x-swat > PPA. > > So, I wouldn't recommend UXA as the panacea. > > Marius Gedminas > -- > It is a mess, pure and simple. Sucks to be away from Unix, huh? >-- man perlfaq3 > > -- > [i965] X freezes starting on April 3rd > https://bugs.launchpad.net/bugs/359392 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in X.org xf86-video-intel: Confirmed > Status in “compiz” source package in Ubuntu: In Progress > Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released > Status in compiz in Ubuntu Jaunty: Fix Committed > Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed > Status in compiz in Ubuntu Karmic: In Progress > Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released > > Bug description: > [Problem] > Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965 > users started noticing X freeze after several hours of use, triggered by > application usage especially noticeable with (but not unique to) compiz > enabled. > > [Impact] > The freeze bug affects a subset of i965 based systems, most particularly > those using compiz. Exact numbers cannot be determined, but may be as high > as 25-50% based on rough estimates. > > The problem is severe: An unpredictable lockup of the system that requires > a power cycle to recover from. For some users it comes on within minutes, > while for others it comes after a few hours of use. > > [How Addressed in Development Version] > For now, the patch being proposed for Jaunty has been uploaded to Karmic. > > Longer term, we plan to move from EXA to UXA once the latter is stable > enough. It has been found that while UXA exhibits other kinds of freezes, > we've not yet been able to reproduce this particular freeze there. > > [Patch for Jaunty] > A low-risk workaround that has proven effective at eliminating freezes, or > at least greatly reducing their frequency, is to increase the Virtual > framebuffer size. Some users do this locally as a matter of course to gain > dual-head support, so this setting has received extremely widespread testing > already. > > The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it > is not otherwise specified. Users can still override this with their own > settings, larger or smaller, as desired. > > A side effect of this patch is that it also mitigates bug 158415 to a > degree, which will make projector usage somewhat easier for this hardware > because it will enable X to recognize higher resolutions available from the > external monitor than were available on initial boot. > > [Test Case] > The best method found to reproduce the bug is: > a. Enable compiz > b. Set your desktop to a 6x1 workspace layout > c. Run http://launchpadlibrarian.net/25683477/repro.sh > d. System will freeze anywhere from 1-20 min typically > e. Power-button shutdown is required to reset the system > > [Regression Potential] > In general, Virtual has been widely and extensively tested, so we do not > expect this patch to trigger regressions. > > The patch is coded to only take effect on i965 systems, so the scope of any > regression that might conceivably be triggered will be limited to just that > hardware. > > [Suspects] > Omitting obviously trivial, unrelated changes, here are what changed in > several suspect packages in the timeframe in question: > > * intel driver: > 4/01: 118_drop_legacy3d.
Re: [Bug 306755] Re: SigmaTel STAC9205: Headphone Jack Not Working
Is anyone else having trouble with runaway CPU usage after upgrading ALSA? Now and then my fan will start going full-speed, and my processors are fully loaded, but I can't find a pattern to it. And it's only started recently. --Thomas On Sun, May 24, 2009 at 9:01 PM, Thomas wrote: > Bingo. That does it. > > > On Sun, May 24, 2009 at 8:37 PM, gearond wrote: > >> Not exactly sure why these settings are now necessary, or if they got >> changed by the udate script, but the mplayer problem is now fixed, >> YeHaaw. I used this - >> >> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/221488/comments/7 >> >> -- >> SigmaTel STAC9205: Headphone Jack Not Working >> https://bugs.launchpad.net/bugs/306755 >> You received this bug notification because you are a direct subscriber >> of the bug. >> >> Status in ALSA driver: New >> Status in “linux” source package in Ubuntu: Confirmed >> >> Bug description: >> The headphone jack does not work on the Gateway T-6836. When headphones >> are plugged in, the speakers are muted but no sound comes from the >> headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA >> 1.0.16. >> >> This is a Regression and should be marked as such (I don't know how). The >> original description follows: >> >> My headphone jack works perfectly fine upon turning the computer on or >> restarting it if the headphones are already in it. If I take the headphones >> out and put them back in, it stops working. If they are not in when I turn >> the computer on, and then I put them in, it doesn't work. If they are >> working and then I put the computer into hibernate, they stop working when I >> wake it up. If the volume is muted when I turn the computer on, the sound >> does not work even if I unmute it. If I log out and then back in, it does >> not fix it >> > > -- SigmaTel STAC9205: Headphone Jack Not Working https://bugs.launchpad.net/bugs/306755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 306755] Re: SigmaTel STAC9205: Headphone Jack Not Working
Bingo. That does it. On Sun, May 24, 2009 at 8:37 PM, gearond wrote: > Not exactly sure why these settings are now necessary, or if they got > changed by the udate script, but the mplayer problem is now fixed, > YeHaaw. I used this - > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/221488/comments/7 > > -- > SigmaTel STAC9205: Headphone Jack Not Working > https://bugs.launchpad.net/bugs/306755 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in ALSA driver: New > Status in “linux” source package in Ubuntu: Confirmed > > Bug description: > The headphone jack does not work on the Gateway T-6836. When headphones > are plugged in, the speakers are muted but no sound comes from the > headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA > 1.0.16. > > This is a Regression and should be marked as such (I don't know how). The > original description follows: > > My headphone jack works perfectly fine upon turning the computer on or > restarting it if the headphones are already in it. If I take the headphones > out and put them back in, it stops working. If they are not in when I turn > the computer on, and then I put them in, it doesn't work. If they are > working and then I put the computer into hibernate, they stop working when I > wake it up. If the volume is muted when I turn the computer on, the sound > does not work even if I unmute it. If I log out and then back in, it does > not fix it > -- SigmaTel STAC9205: Headphone Jack Not Working https://bugs.launchpad.net/bugs/306755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 306755] Re: SigmaTel STAC9205: Headphone Jack Not Working
I've noticed that too, but I mistakenly thought it was related to the flash problem, because I only ever use Mplayer as an embedded player in Firefox. On Sun, May 24, 2009 at 8:17 PM, gearond wrote: > Found another side effect of fixing this bug, mplayer now only plays in > some kind of "frame every 2 seconds" mode. Totally unusable. This is > playing quicktime movies. So, I guess I will continue to use windows for > some things. If I wasn't unemployed, or a better programmer, I'd offer > some help. > > -- > SigmaTel STAC9205: Headphone Jack Not Working > https://bugs.launchpad.net/bugs/306755 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in ALSA driver: New > Status in “linux” source package in Ubuntu: Confirmed > > Bug description: > The headphone jack does not work on the Gateway T-6836. When headphones > are plugged in, the speakers are muted but no sound comes from the > headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA > 1.0.16. > > This is a Regression and should be marked as such (I don't know how). The > original description follows: > > My headphone jack works perfectly fine upon turning the computer on or > restarting it if the headphones are already in it. If I take the headphones > out and put them back in, it stops working. If they are not in when I turn > the computer on, and then I put them in, it doesn't work. If they are > working and then I put the computer into hibernate, they stop working when I > wake it up. If the volume is muted when I turn the computer on, the sound > does not work even if I unmute it. If I log out and then back in, it does > not fix it > -- SigmaTel STAC9205: Headphone Jack Not Working https://bugs.launchpad.net/bugs/306755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379795] Re: Pidgin crashes when I try to delete a group
Right click on group name... click "Delete Group"... click "Remove Group" confirmation button. "Show Empty Groups" can be checked or not-- doesn't make a difference. -- Pidgin crashes when I try to delete a group https://bugs.launchpad.net/bugs/379795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 306755] Re: SigmaTel STAC9205: Headphone Jack Not Working
I'm T-6836, and it works for me with the addition of the following line in /etc/modprobe.d/alsa-base.conf: options snd-hda-intel enable_msi=0 model=eapd --Thomas On Sun, May 24, 2009 at 12:26 AM, Rob Yurkowski wrote: > I installed the snapshot (-snap instead of -di), and it works > beautifully for me--both flash and multiplexed sound. > > We can confirm that this works on the: > > T-1625 > T-6828 > > Pending confirmation from the T-6838 crowd, and that -snap works for > everyone else, I'll close the bug as 'resolved'. > > -- > SigmaTel STAC9205: Headphone Jack Not Working > https://bugs.launchpad.net/bugs/306755 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in ALSA driver: New > Status in “linux” source package in Ubuntu: Confirmed > > Bug description: > The headphone jack does not work on the Gateway T-6836. When headphones > are plugged in, the speakers are muted but no sound comes from the > headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA > 1.0.16. > > This is a Regression and should be marked as such (I don't know how). The > original description follows: > > My headphone jack works perfectly fine upon turning the computer on or > restarting it if the headphones are already in it. If I take the headphones > out and put them back in, it stops working. If they are not in when I turn > the computer on, and then I put them in, it doesn't work. If they are > working and then I put the computer into hibernate, they stop working when I > wake it up. If the volume is muted when I turn the computer on, the sound > does not work even if I unmute it. If I log out and then back in, it does > not fix it > -- SigmaTel STAC9205: Headphone Jack Not Working https://bugs.launchpad.net/bugs/306755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 306755] Re: SigmaTel STAC9205: Headphone Jack Not Working
That does it! I wonder what that technically does, though... Hooray for fixing problems that should have been fixed a long time ago! Now let's all sit back and hope that the next release candidate won't break it again. On Sat, May 23, 2009 at 5:30 AM, Rob Yurkowski wrote: > As a correction to my previous post, this -does- work on the T-6828. The > issue with mine was that it required a line to be appended to > /etc/modprobe.d/alsa-base.conf, and the computer restarted: > > options snd-hda-intel enable_msi=0 model=eapd > > O happy day! > > -- > SigmaTel STAC9205: Headphone Jack Not Working > https://bugs.launchpad.net/bugs/306755 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in ALSA driver: New > Status in “linux” source package in Ubuntu: Confirmed > > Bug description: > The headphone jack does not work on the Gateway T-6836. When headphones > are plugged in, the speakers are muted but no sound comes from the > headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA > 1.0.16. > > This is a Regression and should be marked as such (I don't know how). The > original description follows: > > My headphone jack works perfectly fine upon turning the computer on or > restarting it if the headphones are already in it. If I take the headphones > out and put them back in, it stops working. If they are not in when I turn > the computer on, and then I put them in, it doesn't work. If they are > working and then I put the computer into hibernate, they stop working when I > wake it up. If the volume is muted when I turn the computer on, the sound > does not work even if I unmute it. If I log out and then back in, it does > not fix it > -- SigmaTel STAC9205: Headphone Jack Not Working https://bugs.launchpad.net/bugs/306755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379795] Re: Pidgin crashes when I try to delete a group
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27092164/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/27092165/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/27092166/ProcStatus.txt -- Pidgin crashes when I try to delete a group https://bugs.launchpad.net/bugs/379795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379795] [NEW] Pidgin crashes when I try to delete a group
Public bug reported: Binary package hint: pidgin I am unable to delete groups. Every time I do so Pidgin instantly crashes. Any contacts within the group are removed, but the is never deleted. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/pidgin Package: pidgin 1:2.5.5-1ubuntu8 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.28-11-generic x86_64 ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Pidgin crashes when I try to delete a group https://bugs.launchpad.net/bugs/379795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 306755] Re: SigmaTel STAC9205: Headphone Jack Not Working
Oh, fixed the volume keys problem. Apparently it's a separate setting from the volume applet selection. On Fri, May 22, 2009 at 7:07 PM, Thomas wrote: > I see the headphone option now, but it's still not working. And my keyboard > volume keys seem to be changing PCM, instead of Speaker, even after changing > the preferences... > > Looks like a vast improvement at least. > > > On Fri, May 22, 2009 at 3:51 PM, Andrix wrote: > >> Hi guys! >> I've made my headphones work :). I've found the solution in this thread: >> http://ubuntuforums.org/showthread.php?p=6589810#post6589810 >> >> Download the script and run with the options "-di" >> >> sudo ./AlsaUpgrade-1.0.x-rev-1.17.sh -di >> >> Then reboot, and everything works !! >> >> Basically the script, download the last version of alsa (1.0.20) and then >> compile it. >> >> I can cofirm that this bug is solved with that version of alsa, and is >> working in: >> Gateway T-1625 >> Ubuntu 9.04 - 64 bit >> >> Cheers and I hope this work for you! :) >> >> P.S: I wondering why ubuntu not update the alsa version to 1.0.20 ? >> >> -- >> SigmaTel STAC9205: Headphone Jack Not Working >> https://bugs.launchpad.net/bugs/306755 >> You received this bug notification because you are a direct subscriber >> of the bug. >> >> Status in ALSA driver: New >> Status in “linux” source package in Ubuntu: Confirmed >> >> Bug description: >> The headphone jack does not work on the Gateway T-6836. When headphones >> are plugged in, the speakers are muted but no sound comes from the >> headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA >> 1.0.16. >> >> This is a Regression and should be marked as such (I don't know how). The >> original description follows: >> >> My headphone jack works perfectly fine upon turning the computer on or >> restarting it if the headphones are already in it. If I take the headphones >> out and put them back in, it stops working. If they are not in when I turn >> the computer on, and then I put them in, it doesn't work. If they are >> working and then I put the computer into hibernate, they stop working when I >> wake it up. If the volume is muted when I turn the computer on, the sound >> does not work even if I unmute it. If I log out and then back in, it does >> not fix it >> > > -- SigmaTel STAC9205: Headphone Jack Not Working https://bugs.launchpad.net/bugs/306755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 306755] Re: SigmaTel STAC9205: Headphone Jack Not Working
I see the headphone option now, but it's still not working. And my keyboard volume keys seem to be changing PCM, instead of Speaker, even after changing the preferences... Looks like a vast improvement at least. On Fri, May 22, 2009 at 3:51 PM, Andrix wrote: > Hi guys! > I've made my headphones work :). I've found the solution in this thread: > http://ubuntuforums.org/showthread.php?p=6589810#post6589810 > > Download the script and run with the options "-di" > > sudo ./AlsaUpgrade-1.0.x-rev-1.17.sh -di > > Then reboot, and everything works !! > > Basically the script, download the last version of alsa (1.0.20) and then > compile it. > > I can cofirm that this bug is solved with that version of alsa, and is > working in: > Gateway T-1625 > Ubuntu 9.04 - 64 bit > > Cheers and I hope this work for you! :) > > P.S: I wondering why ubuntu not update the alsa version to 1.0.20 ? > > -- > SigmaTel STAC9205: Headphone Jack Not Working > https://bugs.launchpad.net/bugs/306755 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in ALSA driver: New > Status in “linux” source package in Ubuntu: Confirmed > > Bug description: > The headphone jack does not work on the Gateway T-6836. When headphones > are plugged in, the speakers are muted but no sound comes from the > headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA > 1.0.16. > > This is a Regression and should be marked as such (I don't know how). The > original description follows: > > My headphone jack works perfectly fine upon turning the computer on or > restarting it if the headphones are already in it. If I take the headphones > out and put them back in, it stops working. If they are not in when I turn > the computer on, and then I put them in, it doesn't work. If they are > working and then I put the computer into hibernate, they stop working when I > wake it up. If the volume is muted when I turn the computer on, the sound > does not work even if I unmute it. If I log out and then back in, it does > not fix it > -- SigmaTel STAC9205: Headphone Jack Not Working https://bugs.launchpad.net/bugs/306755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306755] Re: Headphone Jack Stopped Working After Upgrading
The same thing is happening with the microphone jack, too. If I plug in a mic before I boot, it'll work (but extremely quietly...), but if I unplug it and plug it back in, it doesn't work at all. This is really frustrating. I've been reading other posts about people who are trying to get Skype working... why does Ubuntu have such trouble with sound? -- Headphone Jack Stopped Working After Upgrading https://bugs.launchpad.net/bugs/306755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306755] Re: Headphone Jack Stopped Working After Upgrading
Yup, me too. Gateway T-6836. http://www.alsa- project.org/db/?f=2512cd7649c23f5067eb6f773f2c646147f0e298 -- Headphone Jack Stopped Working After Upgrading https://bugs.launchpad.net/bugs/306755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325567] Re: no sound from headphones gateway t-6836
*** This bug is a duplicate of bug 306755 *** https://bugs.launchpad.net/bugs/306755 ** This bug has been marked a duplicate of bug 306755 Headphone Jack Stopped Working After Upgrading -- no sound from headphones gateway t-6836 https://bugs.launchpad.net/bugs/325567 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
