Launchpad has imported 15 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=295875.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-03-12T22:20:00+00:00 fstafforini wrote: Running wingide 4.1.3 with oxygen-gtk2theme selected will crash every time certain dialogs are closed (for instance start/continue or project properties). This happens since 1.2.2 and onwards, also with today's git version. It does not happen in oxygen-gtk2 1.2.0. No other theme causes this, the program works fine under all other gtk themes. This happens with wingide professional 4.1.3. So far I haven't found any other dialog in another app where this happens (but I don't use many gtk2 apps). Console output: The program wing.py received an X Window System error. This probably reflects a bug in the program. The error was BadWindow (invalid Window parameter). (Details: serial 31563 error_code 3 request_code 152 minor_code 3) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/0 ------------------------------------------------------------------------ On 2012-03-12T22:51:30+00:00 fstafforini wrote: This happens under x86-64 architecture. Could not reproduce bug using 32 bit libs and apps on the same system. Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/1 ------------------------------------------------------------------------ On 2012-03-13T05:52:31+00:00 Ruslan wrote: Please use git-bisect to find the guilty commit. Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/2 ------------------------------------------------------------------------ On 2012-03-14T08:47:36+00:00 Hugo Pereira Da Costa wrote: *** Bug 295966 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/3 ------------------------------------------------------------------------ On 2012-03-14T08:52:17+00:00 Hugo Pereira Da Costa wrote: @Ruslan, others I suspect fe399f97bd478a33241a5a4213498072292ce841 To be the guilty guy. (basically reverting compositing on a window that has been already destroyed). Can someone that experience the bug 1/ get oxygen gtk from source git clone git://anongit.kde.org/oxygen-gtk 2/ checkout before the commit before git checkout fe399f97bd478a33241a5a4213498072292ce841^ (don't forget the "^") 3/ compile and see if the bug is still there 4/ checkout the revision: git checkout fe399f97bd478a33241a5a4213498072292ce841 5/ compile and see if the bug is here. Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/4 ------------------------------------------------------------------------ On 2012-03-14T09:06:18+00:00 Hugo Pereira Da Costa wrote: @Ruslan Note: if this indeed is the bug, the fix (that does not break gtk-chtheme) would be either - find a way to check the validity of the window before reverting compositing (might be difficult) - not reverting compositing in destructor (disconnect) - revert everything manually in theme exit (for lxappearance or gth-chtheme) I sure can work on that but need confirmation first. Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/5 ------------------------------------------------------------------------ On 2012-03-14T10:21:51+00:00 Ruslan wrote: (In reply to comment #5) If you mean that the problem is our gdk_window_set_composited(window,_initiallyComposited), then it's strange that we get BadWindow after GDK_IS_WINDOW returns true. Also, I'd rather see which request fails using --sync option to GTK program and breaking on gdk_x_error(). Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/6 ------------------------------------------------------------------------ On 2012-03-14T10:23:47+00:00 Hugo Pereira Da Costa wrote: @ruslan, might be an underlying gtk issue GdkWindow still exists, but underlying X window is gone (unmapped or smthing like that) then crash when gdk_window_set_composite (or whatever the name) try access the X window to change the "composite" flag ... something like that. (iirc, I've seen this happen for other calls) Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/7 ------------------------------------------------------------------------ On 2012-03-14T11:03:13+00:00 Ruslan wrote: (In reply to comment #7) It seems you might be right. There's a gdk_window_is_destroyed() function, so maybe we should check it before setting composite state. Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/8 ------------------------------------------------------------------------ On 2012-03-14T11:05:24+00:00 Ruslan wrote: Git commit d6c4de90902a005fc14e55c1789bec276dbfcdf0 by Ruslan Kabatsayev. Committed on 14/03/2012 at 12:04. Pushed by kabatsayev into branch '1.2'. Check if GdkWindow is destroyed before restoring composited state M +1 -1 src/animations/oxygeninnershadowdata.cpp http://commits.kde.org/oxygen- gtk/d6c4de90902a005fc14e55c1789bec276dbfcdf0 Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/9 ------------------------------------------------------------------------ On 2012-03-14T11:06:49+00:00 Hugo Pereira Da Costa wrote: @ruslan sounds good. Although I'd like to have confirmation for comment #4 Anyone ? Thanks for the commit anyway ! (can't hurt) Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/10 ------------------------------------------------------------------------ On 2012-03-14T11:27:21+00:00 Hugo Pereira Da Costa wrote: @Ruslan, good news, without your commit (forward ported to gtk3), gtk3-demo was crashing at exit (likely with the same issue), and is not anymore. Most likely your fix works ! Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/11 ------------------------------------------------------------------------ On 2012-03-14T11:36:38+00:00 Ruslan wrote: OK, I mark this fixed. If it appears to not be, please reopen. Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/12 ------------------------------------------------------------------------ On 2012-03-17T13:23:03+00:00 fstafforini wrote: I confirm the original issue is fixed. Thanks! Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/13 ------------------------------------------------------------------------ On 2012-03-17T21:51:15+00:00 Ruslan wrote: *** Bug 296082 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/gtk2-engines- oxygen/+bug/992133/comments/14 ** Changed in: gtk2-engines-oxygen Status: Unknown => Fix Released ** Changed in: gtk2-engines-oxygen Importance: Unknown => Medium -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/992133 Title: Filezilla crashes when connecting to remote site To manage notifications about this bug go to: https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/992133/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
