[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2019-04-23 Thread Paul White
Last comment from reporter was over 9 years ago and he/she did not respond to comments #4, #5 or #6. Bug report would have expired but set to "In Progress" without any explanation so closing now as "Invalid". ** Changed in: totem (Ubuntu) Status: In Progress => Invalid ** Changed in:

[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2011-12-14 Thread Chris Wilson
** Also affects: totem Importance: Undecided Status: New ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2011-12-14 Thread Chris Wilson
** No longer affects: hundredpapercuts -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/475707 Title: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is

[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2011-03-26 Thread Captai222
** Changed in: totem (Ubuntu) Status: Incomplete = In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/475707 Title: Totem crashes when exiting fullscreen mode and

[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2011-02-24 Thread Omer Akram
We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future. ** Changed in: totem (Ubuntu)

[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2011-01-31 Thread Omer Akram
thanks for the bug report and sorry for not getting back to you earlier. Could you please confirm if the issue is still there for you with Ubuntu-10.04 or 10.10 ? ** Changed in: totem (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned) -- You received this bug notification

[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2009-11-05 Thread Nixed
** Tags added: totem -- Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on https://bugs.launchpad.net/bugs/475707 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs

[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2009-11-05 Thread Sebastien Bacher
** Package changed: totem (Ubuntu) = compiz (Ubuntu) ** Package changed: compiz (Ubuntu) = totem (Ubuntu) ** Package changed: totem (Ubuntu) = compiz (Ubuntu) -- Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on https://bugs.launchpad.net/bugs/475707 You

[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2009-11-05 Thread Travis Watkins
If totem is crashing this is a totem problem... ** Package changed: compiz (Ubuntu) = totem (Ubuntu) -- Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on https://bugs.launchpad.net/bugs/475707 You received this bug notification because you are a member of

[Bug 475707] Re: Totem crashes when exiting fullscreen mode and Compiz's Wobbly Windows is turned on

2009-11-05 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down