openSUSE Users September 2009

users@lists.opensuse.org

204 participants
306 discussions

by Tracer Bullet

Hi all, Reading some mails on the GIMP mail list, I ran across the procedure to install some more fonts for not only Gimp, but the system and StarOffice to use also. Well, I installed the fonts, went to the shell and issued the command xset fp+ <font directory> and then the rehash command and all fonts are there! Ok, that went well, but each time I restart the system, I have to do it all over again? Is there a way to make it permanent and read the new fonts like it does the ones the system installs or is that a no-no? end of line Tracer Shell commands: xset fp+ <new font directory> xset fp rehash -- ---KMail 1.2--- SuSE Linux v7.2--- Registered Linux User #225206 /tracerb(a)sprintmail.com/ *Magic Page Products* *Team Amiga* http://home.sprintmail.com/~tracerb

4 years, 6 months

[opensuse] Where can I get genIS_PLAINcache

by Chuck Payne

Hi, I am trying to set up a simple repo, I read on the opensuse site about a binary called genIS_PLAINcache, because I can't see to find it or the package yast2-packmanager either. Can someone help. I am setting this repo up for SLE9, I have tried to use createrepo but I keeping getting errors. -- ---------------------------------------- When a place gets crowded enough to require ID's, social collapse is not far away. It is time to go elsewhere. The best thing about space travel is that it made it possible to go elsewhere. -- Robert Heinlein -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 years, 3 months

HP Laser 1020

by Alfredo Cole

Hi: I just bought this printer, thinking it would work right out of the box. I'm running SUSE 9.3 with CUPS, and it does not seem to support this model. Anybody got this printer to work? Any pointers would help. Best regards. -- Alfredo Cole-Tuckler

10 years, 9 months

[opensuse] kernel messages - disk errors?

by Dave Howorth

We had a generator test at work over the weekend that exceeded the UPS time limits so machines shut down. They've all come back but I'm seeing a lot of messages in /var/log/messages of one of them (every few minutes). I strongly suspect they're telling me to buy a new disk but I need to find and read the friendly manual to be sure. Can anybody confirm my suspicion and/or point me at the correct manual? Thanks, Dave Here's a sample of one burst of messages: Sep 28 13:50:07 suse1 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 28 13:50:07 suse1 kernel: ata3.00: BMDMA stat 0x25 Sep 28 13:50:07 suse1 kernel: ata3.00: cmd c8/00:08:a3:c0:73/00:00:00:00:00/e3 tag 0 cdb 0x0 data 4096 in Sep 28 13:50:07 suse1 kernel: res 51/40:08:a3:c0:73/00:00:00:00:00/e3 Emask 0x9 (media error) Sep 28 13:50:07 suse1 kernel: ata3.00: configured for UDMA/100 Sep 28 13:50:07 suse1 kernel: ata3: EH complete Sep 28 13:50:11 suse1 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 28 13:50:11 suse1 kernel: ata3.00: BMDMA stat 0x25 Sep 28 13:50:11 suse1 kernel: ata3.00: cmd c8/00:08:a3:c0:73/00:00:00:00:00/e3 tag 0 cdb 0x0 data 4096 in Sep 28 13:50:11 suse1 kernel: res 51/40:08:a3:c0:73/00:00:00:00:00/e3 Emask 0x9 (media error) Sep 28 13:50:11 suse1 kernel: ata3.00: configured for UDMA/100 Sep 28 13:50:11 suse1 kernel: ata3: EH complete Sep 28 13:50:15 suse1 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 28 13:50:15 suse1 kernel: ata3.00: BMDMA stat 0x25 Sep 28 13:50:15 suse1 kernel: ata3.00: cmd c8/00:08:a3:c0:73/00:00:00:00:00/e3 tag 0 cdb 0x0 data 4096 in Sep 28 13:50:15 suse1 kernel: res 51/40:08:a3:c0:73/00:00:00:00:00/e3 Emask 0x9 (media error) Sep 28 13:50:20 suse1 avahi-daemon[3595]: Invalid query packet. Sep 28 13:50:28 suse1 kernel: ata3.00: configured for UDMA/100 Sep 28 13:50:28 suse1 kernel: ata3: EH complete Sep 28 13:50:28 suse1 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 28 13:50:28 suse1 kernel: ata3.00: BMDMA stat 0x25 Sep 28 13:50:28 suse1 kernel: ata3.00: cmd c8/00:08:a3:c0:73/00:00:00:00:00/e3 tag 0 cdb 0x0 data 4096 in Sep 28 13:50:28 suse1 kernel: res 51/40:08:a3:c0:73/00:00:00:00:00/e3 Emask 0x9 (media error) Sep 28 13:50:28 suse1 kernel: ata3.00: configured for UDMA/100 Sep 28 13:50:28 suse1 kernel: ata3: EH complete Sep 28 13:50:28 suse1 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 28 13:50:28 suse1 kernel: ata3.00: BMDMA stat 0x25 Sep 28 13:50:28 suse1 kernel: ata3.00: cmd c8/00:08:a3:c0:73/00:00:00:00:00/e3 tag 0 cdb 0x0 data 4096 in Sep 28 13:50:28 suse1 kernel: res 51/40:08:a3:c0:73/00:00:00:00:00/e3 Emask 0x9 (media error) Sep 28 13:50:28 suse1 kernel: ata3.00: configured for UDMA/100 Sep 28 13:50:28 suse1 kernel: ata3: EH complete Sep 28 13:50:28 suse1 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 28 13:50:28 suse1 kernel: ata3.00: BMDMA stat 0x25 Sep 28 13:50:28 suse1 kernel: ata3.00: cmd c8/00:08:a3:c0:73/00:00:00:00:00/e3 tag 0 cdb 0x0 data 4096 in Sep 28 13:50:28 suse1 kernel: res 51/40:08:a3:c0:73/00:00:00:00:00/e3 Emask 0x9 (media error) Sep 28 13:50:28 suse1 kernel: ata3.00: configured for UDMA/100 Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor] Sep 28 13:50:28 suse1 kernel: Descriptor sense data with sense descriptors (in hex): Sep 28 13:50:28 suse1 kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Sep 28 13:50:28 suse1 kernel: 03 73 c0 a3 Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed Sep 28 13:50:28 suse1 kernel: end_request: I/O error, dev sda, sector 57917603 Sep 28 13:50:28 suse1 kernel: ata3: EH complete Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB) Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] Write Protect is off Sep 28 13:50:28 suse1 avahi-daemon[3595]: Invalid query packet. Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB) Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] Write Protect is off Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 Sep 28 13:50:28 suse1 kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

11 years, 2 months

[opensuse] protocol not supported bluetooth

by Martin Mielke

Hi all, Version 4.3.00 (KDE 4.3.0) "release 155" running fine. When I execute kbluetooth I get the following error message after clicking on the systray icon: "protocol not supported bluetooth" ...when I click on "OK", Konqueror launches but nothing happens. However, I can discover devices with "hcitool scan" or even using "kbluemon"... and that's it. I've been reading some threads and it seemed to be a bug on previous KDE versions... which is odd because it was working like a charm under SuSE 10.3 Am I missing something here? -- # /etc/init.d/bluetooth status Checking service bluetooth (enabled) : hcid (activated) running hid2hci (activated) opd unused rfcomm (activated) pand unused dund unused # rpm -qa | grep blue bluez-utils-3.32-8.7 bluez-firmware-1.2-99.1 bluez-audio-3.32-8.7 kdebluetooth-1.0_beta8-109.1 bluez-libs-3.32-3.2 -- TIA, Martin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

11 years, 2 months

[opensuse] What is wrong with my NX server?

by Joop Beris

Hello listmates, I have recently installed NX server, after switching to openSUSE 11.1. However, I can't seem to log in. It used to work beautifully on openSUSE 10.3. What I did is the following: - First of all, to install the NX server, I added the following repository: http://download.opensuse.org/repositories/X11:/RemoteDesktop/openSUSE_11.1/ >From that This resulted in the following packages being installed: - FreeNX - NX - freenx-client - libnxcl1 - After that, I ran nxsetup, which completed without errors. On the client, I installed version 3.3.0-6 of the NX Client for Linux from NoMachine. I chose this client because in the past, I have had bad experiences with the FreenNX client. The NoMachine client has always worked well for me. - Trying with the QtNX client, the client simply seems to freeze, without doing anything after starting the connection. - Up launching the NX client and entering the connection details, I start the connection. This takes a while, after which the client responds with: "Session startup failed". In the detail window, it says a lot more: NX> 105 /usr/bin/nxserver: line 1371: 13828 Terminated sleep $AGENT_STARTUP_TIMEOUT NX> 596 Session startup failed. NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/<user>/.nx/F-C-<hostname>-1000-8689F93F7362B387803D3B292867F08C/session". You might also want to try: ssh -X myserver; /usr/bin/nxnode --agent to test the basic functionality. Session log follows: Can't open /var/lib/nxserver/db/running/sessionId{8689F93F7362B387803D3B292867F08C}: No such file or directory. mv: cannot stat `/var/lib/nxserver/db/running/sessionId{8689F93F7362B387803D3B292867F08C}'NX> 1006 Session status: closed : No such file or directory NX> 280 Exiting on signal: 15 FOllowing the troubleshooting advice above, I have set SESSION_LOG_CLEAN=0 in /etc/nxserver/node.conf I also tried the command "ssh -X myserver; /usr/bin/nxnode --agent" to test the basic connection from the client. This gives me the following error on the console: NX> 1000 NXNODE - Version 2.1.0-72 OS (GPL, using backend: 3.2.0) NX> 716 Starting NX Agent ... Error: Aborting session with 'Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again'. Session: Aborting session at 'Thu Jun 4 11:07:26 2009'. Session: Session aborted at 'Thu Jun 4 11:07:26 2009'. NX> 716 NX Agent exited with status: 1 NX> 1001 Bye. I find this odd, since to me this seems to be a problem with X authorization, not something to do with NX. I have confirmed that while X (KDE) is running, no one is logged into the machine at this point. I have also investigated /home/<user>/.nx/F-C-<hostname>-1000-8689F93F7362B387803D3B292867F08C/session, to see if there is some more information there. There, it lists the following: NXAGENT - Version 3.2.0 Copyright (C) 2001, 2007 NoMachine. See http://www.nomachine.com/ for more information. Info: Agent running with pid '15613'. Session: Starting session at 'Thu Jun 4 11:14:43 2009'. Info: Proxy running in server mode with pid '15613'. Info: Waiting for connection from '127.0.0.1' on port '5000'. Info: Aborting the procedure due to signal '15'. Error: Aborting session with 'Unable to open display 'nx/nx,options=/home/<user>/.nx/C-<hostname>-1000-8689F93F7362B387803D3B292867F08C/options:1000''. Session: Aborting session at 'Thu Jun 4 11:14:43 2009'. Session: Session aborted at 'Thu Jun 4 11:14:43 2009'. I enabled logging in /etc/nxserver/node.conf, and the same information is logged there. I am a bit stumped as to what to try now. Does anyone have any suggestions, please? I'll be grateful for any help or tips which help me solve this. Kind regards, Joop -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

11 years, 3 months

[opensuse] Re: [opensuse-factory] 10.3 Review

by Richard Creighton

Sid Boyce wrote: > http://www.mandrake.tips.4.free.fr/opensuse10.3.review.html > Mentions of "for the uninitiated" sounds about right. To sidestep any > problems with the DVD, I've installed from Factory. Looks like the DVD > should have been delayed until it was compared with Factory for > stability. > I think the reviewer attempted to be fair (he points to the URL to > show where he is coming from). Perhaps some pertinent pointers for 11.0. > Regards > Sid. http://www.mandrake.tips.4.free.fr/opensuse10.3.review.html should be MUST READING for management at Novell and at openSuSE.org. It is eminently fair and for the most part, accurate. I think any inaccuracies could be attributable to unfamiliarity rather than bias. If this reviewer hadn't been what I would call a 'Power-user', and had instead been someone converting from Windows, not only would they probably not have had a successful install, but would have an article that Microsoft would probably have printed in full page ads throughout the world. As it is, it should wake up Senior Management in SuSE. regards Richard -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

11 years, 3 months

[opensuse] Drivers for Intel graphic card GMA 4500MHD

by Stan Goodman

A thorough search of the Intel downloads pages failed to find a download source for drivers for the card GMA 4500MHD (or any other GMA cards). After several hours, I did find a remark that such drivers should be obtained from the download sources of ones own distribution. I have also made a Google search without finding anything, and searched the usual download repositories through YaST, also without success. Where, if at all, might the needed driver be found? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

11 years, 4 months

[opensuse] Latest NVidia driver update 185.18.31 crashes X on Quadro NVS 140M

by Jan Ritzerfeld

Hey! The latest update of the nvidia-gfxG02 driver from the NVIDIA Repository crashes X on my ThinkPad R61 with a Quadro M series graphics card. This is a known issue and was fixed in 185.18.36: http://www.nvidia.com/object/linux_display_ia32_185.18.36.html Jan -- The trouble with the rat race is that even if you win, you're still a rat. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

11 years, 4 months

[opensuse] Flash Player Plugin in Firefox still doesnt work - Mac OS X 10.x and Ubuntu always works.

by LActive＠GMX.Net

Hi all, The last 2 years or so there has been no real solution to the Firefox and Adobe Flash Player installation fiasco on a x86_64 system. I have tried all variants of installation found with search machines in the internet. I recently installed a few Mac OSX 10.x (PPC & Int.) and Ubuntu systems. None of them had the problems with Adobe's Flash Player. Why does openSUSE still have the problem? I also have no problems with Konqueror and Flash Player on openSUSE. I use it now for all flash requirements, even if a newer version can not be installed as it suggests. Firefox works with flash player in OSX and Ubuntu. A normal user (which we try to attract to migrate to openSUSE), that gets to a website with Firefox and is asked to install the plug-in, will have to select it. It starts to install and then says "Installaton failed". They do a manual installation from the link that is given to do it in the firefox plug-in finder service. I select rpm and it installs dierctly with the software installer. The software installer then reports that flash plugin could not be installed. The rpm failure message is "already installed". Copying all the sugestions' /usr/lib/browser-plugins/libflashplayer.so does nothing to help. Maunual installations of the *.tar.gz does not work either. There used to be a page on openSUSE at http://opensuse-community.org/Multimedia and http://opensuse-community.org/Restricted_Formats. No joy either. If you follow the hint to un-install all gstreamer packages, you come into a dependency hell. No normal user survives that! I got it to work for a short week until openSUSE destroyed it with an online update. How in the name of Hl can we attract normal users that will need flash player on almost all websites they use? It is a disaster! No normal user can solve the problem without CLI. Please supply a genuine fix, or sort out openSUSE's way of handling the problem in the future please, ... please, ...please! :-( Al -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

11 years, 4 months

Jump to page:

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users September 2009