Opened 11 years ago
Closed 11 years ago
Last modified 9 years ago
#7968 closed Bug report (invalid)
crash upon saving or connecting in Site Manager dialog (xorg 1.12) (oxygen-gtk 1.2.2)
|Reported by:||Thomas M||Owned by:|
|Keywords:||xorg oxygen gtk kde oxygen-gtk||Cc:||arthur@…, mitch@…|
|Component version:||Operating system type:||Linux|
|Operating system version:||archlinux|
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.
Change History (16)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
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
comment:3 by , 11 years ago
Ati free driver.
And system up to date..
comment:4 by , 11 years ago
Same for me.
comment:5 by , 11 years ago
system up to date
comment:6 by , 11 years ago
comment:7 by , 11 years ago
comment:8 by , 11 years ago
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
comment:9 by , 11 years ago
Doesn't work for me. Even tried on a new user. Recreating the config files has no effect.
comment:10 by , 11 years ago
|Keywords:||oxygen gtk kde added|
After all it seems that oxygen-gtk is at fault.
There's no crash with another GTK theme.
comment:11 by , 11 years ago
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.
comment:12 by , 11 years ago
|Status:||new → closed|
|Summary:||crash upon saving or connecting in Site Manager dialog (xorg 1.12) → crash upon saving or connecting in Site Manager dialog (xorg 1.12) (oxygen-gtk 1.2.2)|
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:
comment:13 by , 11 years ago
If you don't want to wait, here's the pkgbuild I used to get their re-released version running:
comment:14 by , 11 years ago
|Keywords:||forex trading robots robot software automated online stock added; crash xorg oxygen gtk kde oxygen-gtk removed|
comment:15 by , 11 years ago
|Keywords:||xorg oxygen gtk kde oxygen-gtk added; forex trading robots robot software automated online stock removed|
comment:17 by , 10 years ago
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
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.
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.