Page 1 of 1
Folder closed when press any key
Posted: 6. Jun 2010, 12:10
by lihua
open a folder on desktop, close it and then open any file folder on desktop, press any key, the window close. Third time will be okay. the fourth time, quit again if any key is pressed...
Does anybody have same problem?
My box:
AMD 3800+ dual cores
NF550 chipset
x550 video card
Salix 13.1 fully installed
System language:zh_CN
SCIM enabled.
Re: Folder closed when press any key
Posted: 6. Jun 2010, 12:35
by gapan
No, nothing like that, but your instructions are not that clear anyway, so I might not be following the right steps.
Re: Folder closed when press any key
Posted: 6. Jun 2010, 15:41
by damNageHack
Sounds wired to me too.... Maybe broken keyboard.
Re: Folder closed when press any key
Posted: 15. Sep 2010, 07:00
by zAchAry
@lihua
Can you be more specific/detailed? Write down exactly what you did step by step.
edit: Thunar is crashing when I'm dragging a Task-Bar (from the Xfce Panel) button to a Thunar File-Manager window
Re: Folder closed when press any key
Posted: 15. Sep 2010, 07:16
by gapan
zAchAry wrote:Thunar is crashing when I'm dragging a Task-Bar (from the Xfce Panel) button to a Thunar File-Manager window
Right! It does!
Re: Folder closed when press any key
Posted: 15. Sep 2010, 07:45
by zAchAry
gapan wrote:Right! It does!
omg omg omg, gapan was just using an emoticon with an uncertain expression
Re: Folder closed when press any key
Posted: 15. Sep 2010, 09:33
by ray
Putting aside the fact it does, why would anyone want to drag a taskbar onto a file manager?
Makes no sense to me.
Cheers,
ray
Re: Folder closed when press any key
Posted: 15. Sep 2010, 10:20
by laprjns
Here's the error that get's thrown:
Code: Select all
The program 'thunar' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
(Details: serial 1977 error_code 5 request_code 24 minor_code 0)
(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.)