crash upon saving or connecting in Site Manager dialog (xorg 1.12) (oxygen-gtk 1.2.2)

[Thomas M]

Filezilla crashes upon saving or attempting to connect to a host in the Site Manager dialog.

Started on the commandline the following message is displayed:

tom ~  $  filezilla
The program 'filezilla' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 39845 error_code 3 request_code 155 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.)

I believe that the problem occured with the latest xorg-server upgracde. I haven't noticed any crashes with any other gtk applications.

Archlinux:

KDE 4.8.1-2
xorg-server 1.12.0-1
filezilla 3.5.3-1

[d47]

I'll add onto this, since I was about to report the same thing.

Getting the same error with Archlinux and KDE. I went ahead and compiled from the Filezilla repo to verify.

[10:06:10 ~]$ ~/Apps/bin/filezilla 
The program 'filezilla' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 34109 error_code 3 request_code 151 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.)

I have a weird setup where I have two screens running with two graphics chips. The first one runs with the open source intel driver and the second one with the nouveau driver. This crash only happens on the intel screen since the update to Xorg 1.12. It still works fine on the nouveau screen.

[Thomas M]

This crash only happens on the intel screen since the update to Xorg 1.12. It still works fine on the nouveau screen.

for me the crash is happening on a single nvidia display with binary blob driver version 295.20

[feliphe]

same error.
ArchLinux.
Kde.
Ati free driver.
And system up to date..

[developer.kg]

Same for me.
Fedora rawhide
KDE 4.8.1
xorg 1.12.0
nVidia 295.20

[hawk0090]

Same Error
Fedora 16
KDE 4.8.1
xorg 1.11.4
system up to date
:(

[Robert Phair]

I had precisely the same problem referred to above. Reinstalling the package had no effect. After removing the .filezilla directory, it now works normally.

Fedora 16, system up to date, KDE 4.8.1

[d47]

Doesn't work for me. Even tried on a new user. Recreating the config files has no effect.

Arch Linux
KDE 4.8.1

[Arthur Țițeică]

After all it seems that oxygen-gtk is at fault.

​https://bugs.kde.org/show_bug.cgi?id=295875

There's no crash with another GTK theme.

[d47]

I'll confirm that's what it was. I upgraded to their re-released version of oxygen-gtk (can be found here in 1.2.2-1: ​http://download.kde.org/stable/oxygen-gtk2/) and the bug is no longer present.

I flagged that package out of date for Arch, so this should be fixed soon for the Arch users.

[Thomas M]

Thanks everyone for getting to the bottom of this. Changing the theme as described above fixed the issue for me as well. I hope it's ok to close the bug since it doesn't appear filezilla is at fault here at all.

Waiting for oxygen-gkt to come through:

​http://www.archlinux.org/packages/extra/x86_64/oxygen-gtk2/

[d47]

If you don't want to wait, here's the pkgbuild I used to get their re-released version running:

​http://pastebin.com/Bd7pdM7r

[sadjy]

Replying to sadjy:

thanks for this Bug report [​http://www.clashgame.com/clash/which-is-the-best-millennium-adaptation
]

there's a non-exhaustive list of bugs corrected in this forum ​http://www.goodsmmo.com that's good