RE: Various X errors (difficult to see)
At 01:07 PM 3/21/2008, Luca Presotto wrote: >>This error refers to the artsd daemon already running, or the system thinks this daemon is running. You should open a terminal window and do: >>ps -ax|grep -i art >>and see if the artsd daemon is running or not. If it is not, you may need to force it to start. >I'll try that later! If I do ps -ax etc... I get: 1185 ?? S 0:00.03 kdeinit: kdeinit: klauncher --new-startup (kdeinit) 1187 ?? S 0:00.28 kdeinit: kdeinit: kded --new-startup (kdeinit) 1206 ?? S 0:00.49 /usr/local/bin/artsd -F 10 -S 4096 -s 60 -m artsmessage -c drkonqi -l 3 -f 1106 v0 I+ 0:00.00 /bin/sh /usr/local/bin/startx 1131 v0 I 0:00.01 /bin/sh /usr/local/bin/startkde 1328 p0 R+ 0:00.00 grep -i art I think that 1206 is the right daemon and is correctly running. Correct? Looks like the right daemon. I wonder if your config files are trying to start it twice. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Various X errors (difficult to see)
>>This error refers to the artsd daemon already running, or the system thinks >>this daemon is running. You should open a terminal window and do: >>ps -ax|grep -i art >>and see if the artsd daemon is running or not. If it is not, you may need to >>force it to start. >I'll try that later! If I do ps -ax etc... I get: 1185 ?? S 0:00.03 kdeinit: kdeinit: klauncher --new-startup (kdeinit) 1187 ?? S 0:00.28 kdeinit: kdeinit: kded --new-startup (kdeinit) 1206 ?? S 0:00.49 /usr/local/bin/artsd -F 10 -S 4096 -s 60 -m artsmessage -c drkonqi -l 3 -f 1106 v0 I+ 0:00.00 /bin/sh /usr/local/bin/startx 1131 v0 I 0:00.01 /bin/sh /usr/local/bin/startkde 1328 p0 R+ 0:00.00 grep -i art I think that 1206 is the right daemon and is correctly running. Correct? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
R: Various X errors (difficult to see)
>>Is it something wrong in /etc/hosts?? >It could be your /etc/hosts or /etc/hosts.allow or you may need to add: > -listen_tcp >to your startx commandline. I supposed the problem was there! I'll look at -listen_tcp and at hosts.allow. I have doubts about setting hosts. X used to give me errors about not being able to connect (but still worked!). Then I tried to set up hosts correctly and now here's the new "problem". I've read "man hosts", read the handbook and googled around but it's not very clear what I should write in this file. My hostname is lucy. It's a laptot that eventually connects to the nearest available network. So it isn't part of a domain or something like that. In the end I set up the concerned hosts lines to: ::1 localhost localhost.my.domain lucy 127.0.0.1 localhost localhost.my.domain lucy Is it correct? Why should I leave localhost.my.domain ? >These messages are errors telling you the window manager cannot manage these >mimetypes. >Did you remove any ports for handling these types of archive files? No, I didn't remove anything! But I copied just 3 warnings. There were 130 of them related not only to archive files handling but almost to everything. >This error refers to the artsd daemon already running, or the system thinks >this daemon is running. You should open a terminal window and do: >ps -ax|grep -i art >and see if the artsd daemon is running or not. If it is not, you may need to >force it to start. I'll try that later! >When you say "every time you launch a program" how exactly are you trying to >launch a program? Either with the kde "launch program", either launching the file in a xterm, either when firefox opens a new popupAnd I think those are pretty much all the possible ways I explored! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Various X errors (difficult to see)
At 11:14 AM 3/21/2008, Luca Presotto wrote: >You should run startx and redirect the output to a file and check the >errors and then try to fix them. To do this try: >startx >/tmp/somexerrorlogfile 2>&1 Done that! Here-s the first error(s): DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket Warning: kbuildsycoca is unable to register with DCOP. kbuildsycoca running... DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... DCOP Cleaning up dead connections. Reusing existing ksycoca Is it something wrong in /etc/hosts?? It could be your /etc/hosts or /etc/hosts.allow or you may need to add: -listen_tcp to your startx commandline. Then I get lots of line(130!) like : kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-tbz2' kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/zip' kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-7z' kbuildsycoca: WARNING: '/usr/local/share/applications/themus-theme-applier.desktop' specifies undefined mimetype/servicetype 'application/x-gnome-theme-installed' These messages are errors telling you the window manager cannot manage these mimetypes. Did you remove any ports for handling these types of archive files? Then finally: DCOP Cleaning up dead connections. Launched ok, pid = 1283 ICE default IO error handler doing an exit(), pid = 1222, errno = 0 There are already artsd objects registered, looking if they are active... Error: Can't add object reference (probably artsd is already running). If you are sure it is not already running, remove the relevant files: /tmp/ksocket-Luca/Arts_SoundServerV2 /tmp/ksocket-Luca/Arts_SoundServer /tmp/ksocket-Luca/Arts_SimpleSoundServer /tmp/ksocket-Luca/Arts_PlayObjectFactory /tmp/ksocket-Luca/Arts_AudioManager This error refers to the artsd daemon already running, or the system thinks this daemon is running. You should open a terminal window and do: ps -ax|grep -i art and see if the artsd daemon is running or not. If it is not, you may need to force it to start. Then, every time I launch a program that open a new window I get: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x66 When you say "every time you launch a program" how exactly are you trying to launch a program? The error is complaining about passing a bad parameter, so if you are launching the program just through your window manager, you must have a bad configuration file. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Various X errors (difficult to see)
>You should run startx and redirect the output to a file and check the >errors and then try to fix them. To do this try: >startx >/tmp/somexerrorlogfile 2>&1 Done that! Here-s the first error(s): DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket Warning: kbuildsycoca is unable to register with DCOP. kbuildsycoca running... DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... DCOP Cleaning up dead connections. Reusing existing ksycoca Is it something wrong in /etc/hosts?? Then I get lots of line(130!) like : kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-tbz2' kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/zip' kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-7z' kbuildsycoca: WARNING: '/usr/local/share/applications/themus-theme-applier.desktop' specifies undefined mimetype/servicetype 'application/x-gnome-theme-installed' Then finally: DCOP Cleaning up dead connections. Launched ok, pid = 1283 ICE default IO error handler doing an exit(), pid = 1222, errno = 0 There are already artsd objects registered, looking if they are active... Error: Can't add object reference (probably artsd is already running). If you are sure it is not already running, remove the relevant files: /tmp/ksocket-Luca/Arts_SoundServerV2 /tmp/ksocket-Luca/Arts_SoundServer /tmp/ksocket-Luca/Arts_SimpleSoundServer /tmp/ksocket-Luca/Arts_PlayObjectFactory /tmp/ksocket-Luca/Arts_AudioManager Then, every time I launch a program that open a new window I get: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x66 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Various X errors (difficult to see)
At 09:18 AM 3/21/2008, Luca Presotto wrote: Hi, I have a freebsd 7.0 release with xorg 7.3 installed on a i386 with a NVIDIA GeForce Go 7300 Official nvidia drivers installed and apparently no problems. In the xorg.0.log file there aren't any errors, glx is correctly loaded etc.. My system starts without X and then I use startx to start X server and KDE3.5 (if I'm not wrong about the version). Some errors are written on the console and I'm not able to see them! To see them I have to stop X (with ctrl+ bkspc) and use scroll lock to see what's there. I found the console full of "X error: bad window parameter" (and some numbers and parameters which I can't remember) Then I find a lots of warnings about kde problems (about loading arts daemons). Except for these errors that I wouldn't be seeing if logging in directly in a graphical environment everything seems to work fine. So I have some questions: is this way of reporting errors correct? Can this be the related to the fact that when I try to use compiz-fusion it starts but it's way too slow and uses a lot of cpu? Should I worry about these errors? How can I solve them?? (They seem really too generic) Thank you! You should run startx and redirect the output to a file and check the errors and then try to fix them. To do this try: startx >/tmp/somexerrorlogfile 2>&1 -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Various X errors (difficult to see)
On Fri, 21 Mar 2008 15:18:45 +0100, "Luca Presotto" <[EMAIL PROTECTED]> wrote: > Hi, > I have a freebsd 7.0 release with xorg 7.3 installed on a i386 with a > NVIDIA GeForce Go 7300 Official nvidia drivers installed and > apparently no problems. In the xorg.0.log file there aren't any > errors, glx is correctly loaded etc.. > > My system starts without X and then I use startx to start X server and > KDE3.5 (if I'm not wrong about the version). > > Some errors are written on the console and I'm not able to see them! > To see them I have to stop X (with ctrl+ bkspc) and use scroll lock to > see what's there. You can grab most of the errors by redirecting both standard `output' and standard `error' to a file, i.e.: bash$ startx 2>&1 | tee logfile Then, after you exit X11, keep a copy of `logfile' around, and see if you can make more sense of the errors :) - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Various X errors (difficult to see)
Hi, I have a freebsd 7.0 release with xorg 7.3 installed on a i386 with a NVIDIA GeForce Go 7300 Official nvidia drivers installed and apparently no problems. In the xorg.0.log file there aren't any errors, glx is correctly loaded etc.. My system starts without X and then I use startx to start X server and KDE3.5 (if I'm not wrong about the version). Some errors are written on the console and I'm not able to see them! To see them I have to stop X (with ctrl+ bkspc) and use scroll lock to see what's there. I found the console full of "X error: bad window parameter" (and some numbers and parameters which I can't remember) Then I find a lots of warnings about kde problems (about loading arts daemons). Except for these errors that I wouldn't be seeing if logging in directly in a graphical environment everything seems to work fine. So I have some questions: is this way of reporting errors correct? Can this be the related to the fact that when I try to use compiz-fusion it starts but it's way too slow and uses a lot of cpu? Should I worry about these errors? How can I solve them?? (They seem really too generic) Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
