May 2005 - openSUSE Users - openSUSE Mailing Lists

Samba column and row - page setup
by Chadley Wilson 25 May '05

25 May '05

Greetings, I am running a suse9.2 box no gui purely as a PC-Server, it has a dit matrix printer attached to it and it works just fine. The client has now requested the printer be able to print label sheets. The sheets are also continuous feed like the paper except there are labels with no gaps. There are 5 across the top IIRC and can't remember how many down, but anyway. I know that I will need to setup rows and columns in the page setup. Anyone here know how, or has read something thing that could assist me in setting up samba to do this sort of printing? Any suggestion would be greatly appreciated, Thanks (I hope I have explained this well enough) -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================

3 2

Two-weekly (!) cronjobs on SUSE 9.1
by pelibali 25 May '05

25 May '05

Hi! I setup a folder named '/etc/cron.twoweekly' and put few scripts into it. To ensure the execution of these files, I made a modification to the '/etc/crontab' file and added the following line 29 21 14,28 * * root rm -f /var/spool/cron/lastrun/cron.twoweekly The extra two-weekly jobs I configured run well, except, that in case in the above timepoint my comp was not turned on, no retry happens after x minutes as it is the case for all of the original cron.hourly/daily/... stuff happens. Any idea how could get the wished effect and get the scripts run when next time my computer is switched on? Thanks, Pelibali

7 10

kscd with digital playback w 9.3
by Joe Morris (NTM) 25 May '05

25 May '05

I know this was discussed a while back, with no resolution. Has anyone found out how to get kscd working again in 9.3? It worked with 9.2 and kde 3.4 with digital extraction. I even tried rebuilding the src.rpm but no go. It seems it is not allowed to reach a backend. -- Joe Morris New Tribes Mission Email Address: Joe_Morris(a)ntm.org Registered Linux user 231871

2 2

Re: [SLE] CUPS and SuSE 9.2 (was 9.1)
by babu walad 25 May '05

25 May '05

Johannes, I also notice that my cupsd is not running. Looks like I have problems earlier in the setup process. Babu --- Johannes Meixner <jsmeix(a)suse.de> wrote: > > Hello, > > On May 19 10:08 babu walad wrote (shortened): > > When I try to use the CUPS web interface at > > http://localhost:631/admin it asks for a login and > > password. > > See our support database. > There is a detailed explanation there. > > > > I looked under the PPD directory and it was empty. > > I cannot guess what you mean with "PPD directory" > (/etc/cups/ppd/ or /usr/share/cups/model/ or > whatever) but > http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html > should help in case of general problems. > > > Kind Regards > Johannes Meixner > -- > SUSE LINUX Products GmbH, Maxfeldstrasse 5 > Mail: jsmeix(a)suse.de > 90409 Nuernberg, Germany WWW: > http://www.suse.de/ > > -- > Check the headers for your unsubscription address > For additional commands send e-mail to > suse-linux-e-help(a)suse.com > Also check the archives at http://lists.suse.com > Please read the FAQs: suse-linux-e-faq(a)suse.com > > > __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/

1 0

Re: [SLE] Viewing DVD Movies
by Joseph Loo 24 May '05

24 May '05

I am not sure what I am looking for. loo@crab:~> ldd `which gmplayer` libmad.so.0 => /usr/lib64/libmad.so.0 (0x00002aaaaabc2000) libdv.so.4 => /usr/lib64/libdv.so.4 (0x00002aaaaace0000) libtheora.so.0 => /usr/lib64/libtheora.so.0 (0x00002aaaaae11000) libogg.so.0 => /usr/lib64/libogg.so.0 (0x00002aaaaaf2f000) liblzo.so.1 => /usr/lib64/liblzo.so.1 (0x00002aaaab034000) libmp3lame.so.0 => /usr/lib64/libmp3lame.so.0 (0x00002aaaab14f000) libm.so.6 => /lib64/tls/libm.so.6 (0x00002aaaab31b000) libpng.so.3 => /usr/lib64/libpng.so.3 (0x00002aaaab472000) libz.so.1 => /usr/lib64/libz.so.1 (0x00002aaaab59f000) libjpeg.so.62 => /usr/lib64/libjpeg.so.62 (0x00002aaaab6b2000) libasound.so.2 => /usr/lib64/libasound.so.2 (0x00002aaaab7d3000) libdl.so.2 => /lib64/libdl.so.2 (0x00002aaaab99c000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00002aaaaba9f000) libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00002aaaabbb4000) libcdda_interface.so.0 => /usr/lib64/libcdda_interface.so.0 (0x00002aaaabd44000) libcdda_paranoia.so.0 => /usr/lib64/libcdda_paranoia.so.0 (0x00002aaaabe52000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00002aaaabf5a000) libgif.so.4 => /usr/lib64/libgif.so.4 (0x00002aaaac071000) libsmbclient.so.0 => /usr/lib64/libsmbclient.so.0 (0x00002aaaac17a000) libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00002aaaac3e3000) libgtk-1.2.so.0 => /opt/gnome/lib64/libgtk-1.2.so.0 (0x00002aaaac522000) libgdk-1.2.so.0 => /opt/gnome/lib64/libgdk-1.2.so.0 (0x00002aaaac78c000) libgmodule-1.2.so.0 => /opt/gnome/lib64/libgmodule-1.2.so.0 (0x00002aaaac8c8000) libglib-1.2.so.0 => /opt/gnome/lib64/libglib-1.2.so.0 (0x00002aaaac9cc000) libXi.so.6 => /usr/X11R6/lib64/libXi.so.6 (0x00002aaaacaf5000) libXext.so.6 => /usr/X11R6/lib64/libXext.so.6 (0x00002aaaacbfd000) libX11.so.6 => /usr/X11R6/lib64/libX11.so.6 (0x00002aaaacd0f000) libaa.so.1 => /usr/lib64/libaa.so.1 (0x00002aaaacf1e000) libGL.so.1 => /usr/lib64/libGL.so.1 (0x00002aaaad03c000) libXxf86dga.so.1 => /usr/X11R6/lib64/libXxf86dga.so.1 (0x00002aaaad1dd000) libXv.so.1 => /usr/X11R6/lib64/libXv.so.1 (0x00002aaaad2e3000) libXxf86vm.so.1 => /usr/X11R6/lib64/libXxf86vm.so.1 (0x00002aaaad3e8000) libXinerama.so.1 => /usr/X11R6/lib64/libXinerama.so.1 (0x00002aaaad4ee000) libSDL-1.2.so.0 => /usr/lib64/libSDL-1.2.so.0 (0x00002aaaad5f0000) libdirectfb-0.9.so.21 => /usr/lib64/libdirectfb-0.9.so.21 (0x00002aaaad785000) libslang-utf8.so.1 => /usr/lib64/libslang-utf8.so.1 (0x00002aaaad8d4000) libncurses.so.5 => /lib64/libncurses.so.5 (0x00002aaaada66000) libartsc.so.0 => /opt/kde3/lib64/libartsc.so.0 (0x00002aaaadbc7000) libgmodule-2.0.so.0 => /opt/gnome/lib64/libgmodule-2.0.so.0 (0x00002aaaadccf000) libgthread-2.0.so.0 => /opt/gnome/lib64/libgthread-2.0.so.0 (0x00002aaaaddd2000) libglib-2.0.so.0 => /opt/gnome/lib64/libglib-2.0.so.0 (0x00002aaaaded6000) libesd.so.0 => /usr/lib64/libesd.so.0 (0x00002aaaae05e000) libaudiofile.so.0 => /usr/lib64/libaudiofile.so.0 (0x00002aaaae168000) liblirc_client.so.0 => /usr/lib64/liblirc_client.so.0 (0x00002aaaae28f000) libc.so.6 => /lib64/tls/libc.so.6 (0x00002aaaae394000) libresmgr.so.0.9.8 => /lib64/libresmgr.so.0.9.8 (0x00002aaaae5ba000) /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) libSM.so.6 => /usr/X11R6/lib64/libSM.so.6 (0x00002aaaae6bf000) libICE.so.6 => /usr/X11R6/lib64/libICE.so.6 (0x00002aaaae7c9000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00002aaaae8e4000) libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00002aaaaea1e000) libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00002aaaaeb36000) libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00002aaaaecb0000) libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00002aaaaedd5000) libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00002aaaaeed8000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00002aaaaefda000) libldap-2.2.so.7 => /usr/lib64/libldap-2.2.so.7 (0x00002aaaaf0ef000) liblber-2.2.so.7 => /usr/lib64/liblber-2.2.so.7 (0x00002aaaaf225000) libexpat.so.0 => /usr/lib64/libexpat.so.0 (0x00002aaaaf333000) libgpm.so.1 => /usr/lib64/libgpm.so.1 (0x00002aaaaf457000) libGLcore.so.1 => /usr/lib64/libGLcore.so.1 (0x00002aaaaf55d000) libnvidia-tls.so.1 => /usr/lib64/tls/libnvidia-tls.so.1 (0x00002aaaafd42000) libstdc++.so.5 => /usr/lib64/libstdc++.so.5 (0x00002aaaafe43000) libdirect-0.9.so.21 => /usr/lib64/libdirect-0.9.so.21 (0x00002aaab0020000) libfusion-0.9.so.21 => /usr/lib64/libfusion-0.9.so.21 (0x00002aaab0129000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00002aaab022f000) libssl.so.0.9.7 => /usr/lib64/libssl.so.0.9.7 (0x00002aaab0346000) libcrypto.so.0.9.7 => /usr/lib64/libcrypto.so.0.9.7 (0x00002aaab047b000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002aaab06af000) Cristian Rodriguez wrote: >2005/5/24, Joseph Loo <jloo(a)acm.org>: > >>That is interesting. Mine does not work at all. It seems I am missing a >>bunch of stuff on the system. It will not let me load it properly. I >>will have to try to reload the system. By the way, is libdvdcss 32 or 64 >>bit? >> >> >Dear Joseph: > >Im running Mplayer form packman in a amd64 SUSE box and no problems at all. >seems to be a dependency problem...:S > >chek your dependencies >what says : > >ldd `which gmplayer` > >(yes..backticks) > > -- Joseph Loo jloo(a)acm.org

1 0

usb-stick not mounted automatically 9.3
by FX Fraipont 24 May '05

24 May '05

I've just installed 9.3 on my wife's laptop. With 9.2, when she inserted her usb-stick, it was mounted automatically and a konqueror window opebed and showed the contents. With 9.3, it does not work any more. mount /dev/sda1 (or sdb1 sometimes) -t vfat /media/usbkey works, but she can't write as user to the usbkey, and this procedure is not practical anyway. How can I revert to the 9.2 type functionality? Thanks Fx

1 0

Packet Loss.
by Marko 24 May '05

24 May '05

Hi all, Im having problems with my linux router. I'm on isdn and i made a little router to connect me to the net so i can boot to linux or windows without loosing my connection. Through windows my connection is great but from linux im getting major packet loss(see below). Please someone help. Tnx PINGING MY PC FROM THE ROUTER: PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.222 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.170 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=0.157 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=0.163 ms 64 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=0.156 ms 64 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=0.161 ms 64 bytes from 192.168.1.2: icmp_seq=13 ttl=64 time=0.165 ms 64 bytes from 192.168.1.2: icmp_seq=14 ttl=64 time=0.160 ms 64 bytes from 192.168.1.2: icmp_seq=15 ttl=64 time=0.168 ms 64 bytes from 192.168.1.2: icmp_seq=19 ttl=64 time=0.139 ms 64 bytes from 192.168.1.2: icmp_seq=20 ttl=64 time=0.178 ms 64 bytes from 192.168.1.2: icmp_seq=21 ttl=64 time=0.174 ms --- 192.168.1.2 ping statistics --- 21 packets transmitted, 12 received, 42% packet loss, time 19997ms rtt min/avg/max/mdev = 0.139/0.167/0.222/0.024 ms ------------------------------------------------------------------------ PINGING GOOGLE FROM THE LINUX ROUTER: PING www.l.google.com (66.249.87.99) 56(84) bytes of data. 64 bytes from 66.249.87.99: icmp_seq=1 ttl=247 time=205 ms 64 bytes from 66.249.87.99: icmp_seq=2 ttl=247 time=204 ms 64 bytes from 66.249.87.99: icmp_seq=3 ttl=247 time=205 ms 64 bytes from 66.249.87.99: icmp_seq=4 ttl=247 time=205 ms 64 bytes from 66.249.87.99: icmp_seq=5 ttl=247 time=204 ms 64 bytes from 66.249.87.99: icmp_seq=6 ttl=247 time=205 ms 64 bytes from 66.249.87.99: icmp_seq=7 ttl=247 time=205 ms 64 bytes from 66.249.87.99: icmp_seq=8 ttl=247 time=205 ms 64 bytes from 66.249.87.99: icmp_seq=9 ttl=247 time=205 ms 64 bytes from 66.249.87.99: icmp_seq=10 ttl=247 time=205 ms 64 bytes from 66.249.87.99: icmp_seq=11 ttl=247 time=204 ms --- www.l.google.com ping statistics --- 11 packets transmitted, 11 received, 0% packet loss, time 10008ms rtt min/avg/max/mdev = 204.866/205.171/205.682/0.626 ms

2 1

RE: [SLE] linux clock drift
by James D. Parra 24 May '05

24 May '05

>Is every 30 minutes not overdone? This was in response to the original poster. His machine would drift 52 minutes in an hour. For me, I need to maintain accuracy in the milliseconds. Especially, since I don't want to monitor when the clocks might start drifting apart, this was a quick solution, not necessarily the best solution. I am still searching for a fix for this problem. When I find it, I'll post the answer. ~James

1 0

RE: [SLE] linux clock drift
by James D. Parra 24 May '05

24 May '05

>Rather than restarting xntp, would it be better simply to run ntpdate since >xntp is a daemon. You'll need to stop the daemon to have ntpdate set the time; # ntpdate time.server 24 May 10:39:31 ntpdate[16214]: the NTP socket is in use, exiting # rcxntpd stop Shutting network time protocol daemon (NTPD) done # ntpdate time.server 24 May 10:39:39 ntpdate[16225]: adjust time server 192.168.20.72 offset 0.005761 sec Restart the daemon. ~James

1 0

OpenOffice_org1-1.1.3-4.2 released TWICE (?)
by pelibali 24 May '05

24 May '05

Hi, I couldn't find a logical explanation, maybe someone could help me to understand the situation: Last month the youpdated version '1.1.3-4.2' of OpenOffice_org1 was released and few days ago '1.1.3-4.3' appeared on the mirrors. Until this point everything seems be fine, but while comparing the .spec files of the above source rpms, interestingly only a single line, containing the version numbers differs in them. Is there an explanation to release the same YOU update actually twice with different version numbers or do I miss something? Thanks, Pelibali

1 0