x11-common: I fiddled with the X11 symbolic links
Trying to fullfill x11-common's postinst requests, I'm pretty certain I
messed up my X11 lib / bin / include directories and symlinks.
Where can I find a description of what the standard X11 directory setup is
(for sid), with details about the
/usr/lib/X11 /usr/bin/X11 and /usr/include/X11 symbolic links, so I can fix
my box ?
Here's the detail of what happened :
first, x11-common.postinst claimed that /usr/bin/X11 "points to wrong
location". (It was pointing to ".")
I then tried various other destinations, read the postinst script for
insight, and no luck.
At some point I typed
apt-get -f install x11-common instead of just apt-get -f install, and then
got a dialog information about the symlink issue.
from then on I managed to rework various symlinks :
/usr/bin/X11
/usr/lib/X11
/usr/include/X11
in a way that satisfied x11-common.postinst.
but now a few X programs exhibit issues. for instance xdtv :
open("/usr/lib/X11/locale/common/xlcDef.so.2", O_RDONLY) = -1 ENOENT (No
such file or directory)
write(2, "Warning: Unable to load any usab"..., 43) = 43
and I had to alter symlinks again so it could find the X11 locale
directory...
I wasnt paying enough attention in the process so I can't say for sure what
the precise steps where in that faulty update. I'm guessing it might all be
caused by my /usr being a symlink itself...
--
Samuel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X programs crash with request_code 151
[EMAIL PROTECTED] (14 April 2006 03:38, <[EMAIL PROTECTED]>) a écrit : > there have been several reports identical to yours and it appears that > another upgrade is required. Something that broke earlier has > supposedly been fixed. I haven't made this upgrade yet so can't be > sure, check the archives for yesterday and today. yes, in fact I reported this as a bug to x11-com, and it got merged with other reports on libxfixes3, where the bug is actually coming from. The other reports had different error codes (152 while mine is 151) thus I hadn't found them in my searches, and I had no clue which exact X library this error was coming from. My report was quickly replied to, and then downgrading libxfixes3 did solve the problem. (on the mirrors I use, unstable hasnt yet replaced libxfixes 1:3.0.1.2-2 with a new, fixed version ; so downgrading it is the temporary solution till that happens) >> PS : two previous attempts at reaching the mailing list still haven't >> produced any effect, 10 hours after sending the first mail. Is it me >> or are some emails being blocked by the ML system ?? what does it take >> to make it thru to this list ?? > > you are getting through. are you subscribed? no, I'm using gmane to read the list. I had first sent a post with a trashmail.net adress, and waited 10 hours before deciding it had been somehow blocked out. When trying other 'From's I did not wait that long, and the delay in gmane made me think those were still being blocked... ah well, sorry the duplicates. the ironical thing is how I end-up putting 2 of my email adresses in a public list while initially trying to protect from spam behind a trashmail alias :/ -- Samuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X programs crash with request_code 151
I just used aptitude to upgrade my debian/unstable box (the previousfull update was on 2006-03-19), and then several graphical programs are now having one same error. For some it is fatal, for some it onlyprints an error report.These errors don't happen _at all _ when I launch windowmaker insteadof kde, and I absolutely don't know if this problem is specific to mybox, or due to a bug in a package (and then which package..)Just in case it could be hardware-related, my video card is a nvidia GeForce2 with 32MB RAM, and my screen is set to 1680x1050 (16bpp), I'musing latest xorg server, with nv driver.Here are the reports from a few various programs, hoping someone mightpoint me in the right direction : -- firefox and thunderbird : crashes on launch with :The program 'Gecko' received an X Window System error.This probably reflects a bug in the program.The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 418 error_code 1 request_code 151 minor_code 23) (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.)-- gqview : crashes on launch,The program 'gqview' received an X Window System error. This probably reflects a bug in the program.The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 143 error_code 1 request_code 151 minor_code 23)etc.-- "gimp --verbose" starts OK, until I click "open" then crashes The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 19546 error_code 1 request_code 151 minor_code 23)- knode : reports errors, works normallyX Error: BadRequest (invalid request code or no such operation) 1 Major opcode: 151 Minor opcode: 23 Resource id: 0x3e4it seems all KDE apps work (printing a few of those reports along theway), as overall my kde desktop and usual kde apps appear unaffected. -- opera : reports that same error, works normally-- SamPS : two previous attempts at reaching the mailing list still haven't produced any effect, 10 hours after sending the first mail. Is it me or are some emails being blocked by the ML system ?? what does it take to make it thru to this list ??
X apps bug : 'BadRequest' / Major opcode: 151
I just used aptitude to upgrade my debian/unstable box (the previous full update was on 2006-03-19), and then several graphical programs are now having one same error. For some it is fatal, for some it only prints an error report. These errors don't happen _at all_ when I launch windowmaker instead of kde, and I absolutely don't know if this problem is specific to my box, or due to a bug in a package (and then which package..) Just in case it could be hardware-related, my video card is a nvidia GeForce2 with 32MB RAM, and my screen is set to 1680x1050 (16bpp), I'm using latest xorg server, with nv driver. Here are the reports from a few various programs, hoping someone might point me in the right direction : -- firefox and thunderbird : crashes on launch with : The program 'Gecko' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 418 error_code 1 request_code 151 minor_code 23) (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.) -- gqview : crashes on launch, The program 'gqview' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 143 error_code 1 request_code 151 minor_code 23) etc. -- "gimp --verbose" starts OK, until I click "open" then crashes The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 19546 error_code 1 request_code 151 minor_code 23) - knode : reports errors, works normally X Error: BadRequest (invalid request code or no such operation) 1 Major opcode: 151 Minor opcode: 23 Resource id: 0x3e4 it seems all KDE apps work (printing a few of those reports along the way), as overall my kde desktop and usual kde apps appear unaffected. -- opera : reports that same error, works normally P.S. : I am resending this mail, as it seems first mail never made it through. If this ends up being a duplicate post, I'm sorry. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
