Thank you for taking the time to report this bug and helping to make
Ubuntu better. The version of Ubuntu you're reporting this issue on is
in End of Life status, and newer versions have fixed this issue. You can
learn more about this at https://wiki.ubuntu.com/Releases
** Changed in: metacity (Ub
** Changed in: metacity
Importance: Unknown => High
--
False reports of "Window not responding" error
https://bugs.launchpad.net/bugs/29584
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Yes, I agree. It would be nice to see this fixed in Dapper.
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
opening a dapper task since the fix is easy enough and that would be
nice to get a backport for dapper
** Changed in: metacity (Ubuntu Dapper)
Importance: Untriaged => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Confirmed
--
False reports of "Window no
That upload fixes the issue:
metacity (1:2.16.2-0ubuntu1) edgy; urgency=low
.
* New upstream version:
- partial audit to fix timestamp usage (partly fixes #355180)
- remove compilation warnings
- automatic detection of stable/unstable in configure script
- make windows be
** Changed in: metacity (upstream)
Status: Confirmed => Fix Released
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
fixed upstream
** Changed in: metacity (Ubuntu)
Status: Confirmed => Fix Committed
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yes, what I have heard from people who have amd64 installation, it
appears on them.
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: metacity (upstream)
Status: Unknown => Confirmed
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Do all the people having that issue use and amd64 installation? I've
commented upstream about that on
http://bugzilla.gnome.org/show_bug.cgi?id=348305. That might be a GTK
bug
** Changed in: metacity (Ubuntu)
Status: Needs Info => Confirmed
** Bug watch added: GNOME Bug Tracker #348305
I have tryed debug this with older versions of metacity too, it seems to
exist in version 2.10.3 of metacity too. I'm not even sure is this
metacity problem(?)
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
I can confirm this. Thought it only happens in my amd64 box, but not
with x86 box. Both are running Dapper with latest updates.
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
on edgy gedit asks for the password on opening, closing the gedit window
while the password dialog is opened leads a hang to the password dialog
but no "Window not responding" message
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
u
** Bug 50572 has been marked a duplicate of this bug
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug 49346 has been marked a duplicate of this bug
--
False reports of "Window not responding" error
https://launchpad.net/bugs/29584
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Bug is still present, tried in gedit and GIMP.
In pygtk at least, the problem seems to be due to a delete_event signal
being captured and held onto whilst waiting for user input. I have a
way round this for small apps, but it would be great to have it fixed at
the source
--
False reports of "Wi
16 matches
Mail list logo
