[ask] How to fix Bug X Error of failed request on Slackware 14.1?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[ask] How to fix Bug X Error of failed request on Slackware 14.1?
I just upgraded my slackware from 14.0 to 14.1 and many applications I've installed when was still using 14.0 are not running in 14.1, like netbeans, mysql workbench, firefox, thunderbird, xmind, wine, google earth and more..
when I run from console they have similar error message, like this:
Code:
The program 'XMind' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
(Details: serial 11 error_code 16 request_code 128 minor_code 5)
(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.)
bash-4.2$ firefox
(process:5422): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
(process:5422): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
###!!! ABORT: XINERAMAIsActive: BadLength (poly request too large or internal Xlib length error): file /tmp/mozilla-esr24/toolkit/xre/nsX11ErrorHandler.cpp, line 157
###!!! ABORT: XINERAMAIsActive: BadLength (poly request too large or internal Xlib length error): file /tmp/mozilla-esr24/toolkit/xre/nsX11ErrorHandler.cpp, line 157
Segmentation fault
bash-4.2$ /opt/netbeans-7.3.1/bin/netbeans
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 128 (XINERAMA)
Minor opcode of failed request: 5 (XINERAMAQueryScreens)
Serial number of failed request: 11
Current serial number in output stream: 11
yes, they have similar message
Code:
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
what bug is that? and how to fix it? it's really frustated me.
by the way, this is my mechine spesification:
Quote:
netbook aspire one 722
bash-4.2$ uname -a
Linux darkstar 3.10.17 #1 SMP Wed Oct 23 16:28:33 CDT 2013 x86_64 AMD C-60 APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux
With upgrading from 14.0 to 14.1 many libraries were replaced by newer versions. Most likely you will have to recompile those programs.
I am a bit curious, why do you have used external sources for programs like Firefox and Thunderbird? Slackware provides already packages for them.
Also, how did you upgrade to the newer version?
With upgrading from 14.0 to 14.1 many libraries were replaced by newer versions. Most likely you will have to recompile those programs.
I am a bit curious, why do you have used external sources for programs like Firefox and Thunderbird? Slackware provides already packages for them.
Also, how did you upgrade to the newer version?
Firefox and Thunderbird are from Slackware 14.1 packages, I didn't build them my self.
I follow this document :
Found this thread about your issue with firefox, and it seems related to catalyst driver. You can try to reinstall/upgrade this driver to see if that solve your problem.
What's your issue with mysql workbench? I did something with mine in slackware 64 14.1, I can check later.
sorry guys, after I rechecked, mysql-workbench has no similar error like other. it's different error type, here:
Code:
bash-4.2$ mysql-workbench
/usr/libexec/mysql-workbench-bin: error while loading shared libraries: libzip.so.1: cannot open shared object file: No such file or directory
Found this thread about your issue with firefox, and it seems related to catalyst driver. You can try to reinstall/upgrade this driver to see if that solve your problem.
Hope this helps.
Cheers.
--
SeB
now I'm using amd-driver-installer-catalyst-13-4-x86.x86_64, is that mean I should downgrade it?
sorry guys, after I rechecked, mysql-workbench has no similar error like other. it's different error type, here:
Code:
bash-4.2$ mysql-workbench
/usr/libexec/mysql-workbench-bin: error while loading shared libraries: libzip.so.1: cannot open shared object file: No such file or directory
You need to recompile mysql-workbench to build against libzip-0.10.1-i486-1 which is bumping their shared library to libzip.so.2
now I'm using amd-driver-installer-catalyst-13-4-x86.x86_64, is that mean I should downgrade it?
Your issue with firefox seems to be related to the proprietary amd driver. But to be sure about that, It would be a good idea to uninstall it, use a generic driver (i.e vesa) and check if firefox still crashes. If firefox works with the generic driver, retry with the amd driver, starting with the latest revision (seems to be 13.12).
Your issue with firefox seems to be related to the proprietary amd driver. But to be sure about that, It would be a good idea to uninstall it, use a generic driver (i.e vesa) and check if firefox still crashes. If firefox works with the generic driver, retry with the amd driver, starting with the latest revision (seems to be 13.12).
--
SeB
Hmm.. I've friend also said like you said, "it's cuz by amd driver anyway". How to uninstall amd driver? just running #removepkg fglrx-12.104-x86_64-1 ? is anything should be configured after removing fglrx?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.