Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#15459 - [rox] 2.8-1 pinboard error after GTK2 upgrade
Attached to Project:
Arch Linux
Opened by Paco (CaptainHook8) - Thursday, 09 July 2009, 15:00 GMT
Last edited by Tobias Kieslich (tobias) - Monday, 14 September 2009, 15:47 GMT
Opened by Paco (CaptainHook8) - Thursday, 09 July 2009, 15:00 GMT
Last edited by Tobias Kieslich (tobias) - Monday, 14 September 2009, 15:47 GMT
|
DetailsHi!
I have Rox 2.8-1. I got a problem when launching rox pinboard by the command "rox -p Default" : ----------------- (ROX-Filer:31336): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed The program 'ROX-Filer' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAtom (invalid Atom parameter)'. (Details: serial 234 error_code 5 request_code 20 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.) -------------------- The error is related to GTK2, I got GTK2 2.16.2-1. Previous version of GTK2 didn't give any problem with rox pinboard. Please fix it. |
This task depends upon
Closed by Tobias Kieslich (tobias)
Monday, 14 September 2009, 15:47 GMT
Reason for closing: Fixed
Additional comments about closing: 2.10 fixed that
Monday, 14 September 2009, 15:47 GMT
Reason for closing: Fixed
Additional comments about closing: 2.10 fixed that
Thank you very much for the fix.I appreciate that.
Paco