re: X problems
On Mon, 26 Aug 2002 [EMAIL PROTECTED] wrote: oki doki. you havethe following error, which repeats for a few applications: /opt/kde/bin/artsd: error while loading shared libraries: libaudiofile.so.0: cannot open shared object file: No such file or directory as you can see - you are missing the 'audiofile' library. this is a low-level library, used by most of the KDE applications. you need to find how you managed to miss installing it - and find which package it belongs to. since i'm not familiar with slackware - soemone else might be able to tell how to find which package this library belongs to. well, i get an error when starting kde on another slack 8.1 box saying i dont havea sound card configured or something like that, i just click ok and everything works smoothly i guess thats the same error and i doubt i didnt install that package because both systems are installed from the same cd and i chose the same kde packages for them so i either installed it or the package isnt necessary for running kde this library _must be installed_ if you want thoose underlying applications to work - when an application is dynamically linked with several libraries, and one of those libraries are not found - the application does not run. this still possibly does not have anything to do with your problem - but it is nontheless a problem that you should fix. waving with your hands and muttering holly matramonies - won't make your problems go away ;) kindly do seek a fix to this problem by finding which package was not installed - this has nothing to do with a lack of soundcard, and thus it is NOT the same problem. why do you think its the same - just because it has the word 'audio' in the error message? can't you see that the error message is different? you also ought to remember that trying to identify a problem, while other problems clutter your view - makes it much harder to identify the problem. so fix this one, and if it does not solve your major problem - then you'll at least have a clearer view of what is going on. and if you're lucky - this _is_ what causes your problem. good luck, -- guy For world domination - press 1, or dial 0, and please hold, for the creator. -- nob o. dy = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: X problems
On Sun, 25 Aug 2002 [EMAIL PROTECTED] wrote: when i 'startx' i get a black screen and sometimes (when running startx again) i get to see the desktop for a variable amount of time (0.5 seconds to 3 secs aprox.) which program did you try to configure X with? there are several such programs - one of them might work. not sure which comes with mandrake - you should have mandrake's own X config utility (drakex?), or Xconfigurator (is it redhat specific?) or xf86setup, or also - you get lots of messages when you run X, on the console from which you ran 'startx'. can you copy them _all_ into a file, and send them over? specifically the last few might tell exactly what the problem is - or they might not ;) -- guy For world domination - press 1, or dial 0, and please hold, for the creator. -- nob o. dy = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: X problems
On Sun, 25 Aug 2002, guy keren wrote: On Sun, 25 Aug 2002 [EMAIL PROTECTED] wrote: when i 'startx' i get a black screen and sometimes (when running startx again) i get to see the desktop for a variable amount of time (0.5 seconds to 3 secs aprox.) which program did you try to configure X with? there are several such programs - one of them might work. not sure which comes with mandrake - you should have mandrake's own X config utility (drakex?), or Xconfigurator (is it redhat specific?) or xf86setup, or XF86Setup came with XFree 3. xf86cfg comes wth XFree 4 . I recall XF86Setup as somewhat useful, although lacking almost any form of auto detection. xf86cfg tries to use the autodetection capabilities of xfree. Actually, it even worked for me once. But most of the times it simply failed, and crashed. also - you get lots of messages when you run X, on the console from which you ran 'startx'. can you copy them _all_ into a file, and send them over? specifically the last few might tell exactly what the problem is - or they might not ;) Agree here. Have a look and see if it makes sense. A 'Missing core pointer' is a misconfigured mouse. And 'Missing font fixed' means that something is problematic with the fonts configuration (normally it means that all the fonts are missing, not only the one called 'fixed') Have a look at the messages slightly above the last message to see some more details about the problem. -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: X problems
which program did you try to configure X with? there are several such programs - one of them might work. not sure which comes with mandrake - you should have mandrake's own X config utility (drakex?), or Xconfigurator (is it redhat specific?) or xf86setup, or i used like 3 different tools, a manual one, an automated one and another one with a graphical interface, and btw, i use slack also - you get lots of messages when you run X, on the console from which you ran 'startx'. can you copy them _all_ into a file, and send them over? specifically the last few might tell exactly what the problem is - or they might not ;) i'll copy it to a file and send it over asap To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: X problems
i attached the file to this mail just btw, now when i ran it i only saw the kde screen for half a sec when switching between VCs XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.18 i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Sun Aug 25 13:23:25 2002 (==) Using config file: /etc/X11/XF86Config Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Xlib: extension GLX missing on display :0.0. _KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root DCOPServer up and running. Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. /opt/kde/bin/artsd: error while loading shared libraries: libaudiofile.so.0: cannot open shared object file: No such file or directory Mutex destroy failure: Device or resource busy Could not dlopen library knotify.la: libaudiofile.so.0: cannot open shared object file: No such file or directory knotify: error while loading shared libraries: libaudiofile.so.0: cannot open shared object file: No such file or directory Xlib: extension GLX missing on display :0.0. Mutex destroy failure: Device or resource busy _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root Could not dlopen library knotify.la: libaudiofile.so.0: cannot open shared object file: No such file or directory knotify: error while loading shared libraries: libaudiofile.so.0: cannot open shared object file: No such file or directory Xlib: extension GLX missing on display :0.0. Could not dlopen library knotify.la: libaudiofile.so.0: cannot open shared object file: No such file or directory knotify: error while loading shared libraries: libaudiofile.so.0: cannot open shared object file: No such file or directory Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/DigitalClock) Negative sizes (2,-4) are not possible QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QLabel) Negative sizes (61,-4) are not possible QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/DigitalClock) Negative sizes (2,-4) are not possible QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QLabel) Negative sizes (61,-4) are not possible Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. Xlib: extension GLX missing on display :0.0. QObject::connect: No such signal KDockArea::docked() QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'view widget') QObject::connect: No such signal KDockArea::docked() QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'view widget') Mutex destroy failure: Device or resource busy Mutex destroy failure: Device or resource busy ICE default IO error handler doing an exit(), pid = 203, errno = 0 ICE default IO error handler doing an exit(), pid = 194, errno = 0 ICE default IO error handler doing an exit(), pid = 199, errno = 0 ICE default IO error handler doing an exit(), pid = 185, errno = 2 ICE default IO error handler doing an exit(), pid = 182, errno = 0 ICE default IO error handler doing an exit(), pid = 201, errno = 0 ICE default IO error handler doing an exit(), pid = 189, errno = 0 xinit: connection to X server lost.
Re: X problems
On Sun, 25 Aug 2002, Aviv wrote: i attached the file to this mail just btw, now when i ran it i only saw the kde screen for half a sec when switching between VCs oki doki. you have the following error, which repeats for a few applications: /opt/kde/bin/artsd: error while loading shared libraries: libaudiofile.so.0: cannot open shared object file: No such file or directory as you can see - you are missing the 'audiofile' library. this is a low-level library, used by most of the KDE applications. you need to find how you managed to miss installing it - and find which package it belongs to. since i'm not familiar with slackware - soemone else might be able to tell how to find which package this library belongs to. -- guy For world domination - press 1, or dial 0, and please hold, for the creator. -- nob o. dy = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
re: X problems
On Monday 26 August 2002 01:57, guy keren wrote: On Sun, 25 Aug 2002, Aviv wrote: i attached the file to this mail just btw, now when i ran it i only saw the kde screen for half a sec when switching between VCs oki doki. you have the following error, which repeats for a few applications: /opt/kde/bin/artsd: error while loading shared libraries: libaudiofile.so.0: cannot open shared object file: No such file or directory as you can see - you are missing the 'audiofile' library. this is a low-level library, used by most of the KDE applications. you need to find how you managed to miss installing it - and find which package it belongs to. since i'm not familiar with slackware - soemone else might be able to tell how to find which package this library belongs to. well, i get an error when starting kde on another slack 8.1 box saying i dont have a sound card configured or something like that, i just click ok and everything works smoothly i guess thats the same error and i doubt i didnt install that package because both systems are installed from the same cd and i chose the same kde packages for them so i either installed it or the package isnt necessary for running kde = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: X problems
On Mon 2002-03-18, Shai Bentin wrote: Hi list, Lately I've been having X freeze problems. what happens is during work, suddenly the mouse events are not captured, soon after that the keyboard events are gone, and although I know that the machine still functions there is nothing I can do. I can think of 2 options: (1) telnet to it from another machine (2) uses the SysRq key With the second option you can recover from many kinds of trouble, for example ALT-SysRq-r will probably give you the keyboard back. Or ALT-SysRq-i will kill all your processes except init, etc. see linux/Documentation/sysrq.txt for the details. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: X problems
On 18 Mar 2002, Shai Bentin wrote: One more thing, is there any way to break X into regular command line mode, when starting the system in runlevel 5? First thing to try: Ctrl-Alt-F1 (to switch to a text-mode console, login, and try to handle things) Typically it won't work when the X server is badly stuck Ctrl-Alt-Backspace (Kill the X server) Typically won't work under the same circumstances If you're in a network: connect from a different computer (you have an sshd listening, right?) magic sysrq: I quote another message: With the second option you can recover from many kinds of trouble, for example ALT-SysRq-r will probably give you the keyboard back. Or ALT-SysRq-i will kill all your processes except init, etc. see linux/Documentation/sysrq.txt for the details. ALT-SysRq-h should give you a Help: a short list of available commands. Beware, as those commands allow you to kill processes, and reboot your system even without a sync of the disks, not to mention a proper shutdown. -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
