April 2009 - openSUSE Users - openSUSE Mailing Lists

[opensuse] ooconvert / DocumentConverter.py / ErrorCodeIOException
by Per Jessen 28 Apr '09

28 Apr '09

I'm trying to use ooconvert to convert an sxw document to a pdf, but I don't get any further than this: Traceback (most recent call last): File "/usr/share/ooo3/program/DocumentConverter.py", line 16, in <module> from com.sun.star.task import ErrorCodeIOException File "/usr/lib/ooo3/basis-link/program/uno.py", line 291, in _uno_import raise ImportError( "type "+ name + "." +x + " is unknown" ) ImportError: type com.sun.star.task.ErrorCodeIOException is unknown I'm on openSUSE 11.1, openoffice 3.0 - I can't help thinking that I'm missing some or other package, but what? /Per -- Per Jessen, Zürich (13.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 1

[opensuse] Mandy 7.2 fires right up after 3-4 years sitting on a shelf!
by David C. Rankin 28 Apr '09

28 Apr '09

Listmates, Had to share this somewhat comical but painfully fun event. Long ago I retired my mandrake 7.2 (odyssey) server and the box had gone through a number of changes since I yanked the 40G IBM Deskstar drive out of it after (??) 4 years of continual service. The network card was new, the video card was new, but despite the changes, when I put the drive back into the box - 7.2 fired right up! Remember linuxconf? Remember when you were not even presented with a list of potential modules to load, but instead had to look in /lib/modules/<kernel> just to find something that looked close like the 3c90x.ko module to get a 3c950 card running? Recall the old drakes - XFdrake, menudrake, etc.? Man what a trip down memory lane and talk about cobweb filled memories. The entire ordeal was prompted by a new lady that I hired today needing a box put together on the quick. I wasn't going to sacrifice the raid array in the box or the spare 250G drive in there that I still had not had time to parse through to make sure I wasn't throwing anything important away. Thus, the old 40G was enlisted to pull another tour of duty, and... for the first time in its 8 year life, it was spoon fed -- windows.... yuk! So we bid a fair adieu to mandy 7.2, and 12 hours later had a fully updated XP install, complete with a slew of the little utilities I can't live without (fileMenuTools, FMview, mysql gui tools, etc...) and topped off with a full MS Office, OpenOffice, Gimp, PaintShop Pro, and imagemagick install with all updates through SP3 to current installed. (What a painful process) The more you have to go back a tinker with windows, the more you appreciate the elegance of Linux and the distribution Novell has put together. The trip down memory lane with mandy 7.2 and KDE 2 also showed just how far KDE3 had come since the early days. We can only hope that KDE4 can achieve as much. (P.S. Next time I'm just buying a preloaded box at Staples, this install and configure from scratch stuff with windows is just too damn painful...) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

10 28

[opensuse] problems writing files to nfs mounted folder with default acls set
by Ken Gramm 28 Apr '09

28 Apr '09

Hi all! I was wondering if anyone else was having problems writing files to an ACL enabled NFS mount? I've got 4 boxes: - server01 is running 11.0 and is my file server - server02 is running 11.0 - workstation01 has been running 11.1 since the day it was released - workstation02 is a newly loaded 11.1 test machine All machines are fully patched. server01's /etc/exports file has the following entry: /data *(rw,no_root_squash,sync,no_subtree_check) The fstab entry for the folder is: /dev/sda3 /data ext3 acl,user_xattr 1 2 I'm also sharing the /data folder through Samba. Security on the /data folder has always been: server01:/ # getfacl data # file: data # owner: root # group: root user::rwx user:ken:rwx group::rwx mask::rwx other::r-x The other three machines have the share mounted on /data with the default NFS settings. All machines (except the new one) have been in this basic configuration since well before 10.x with the workstation running the latest release and the servers usually one release behind. I can't tell you exactly when, but within the last couple of months when I try to do anything that would write to the share from the 11.1 boxes, I get an error message like: cp: cannot create regular file test.txt: invalid argument But when I look, the directory shows that the file has been created with a 0K file size, and of course it is empty. And it doesn't matter if I am logged in as myself or as ROOT. I get the same error. The other 11.0 box doesn't seem to suffer from the same issue. I can copy files with it all day long. I can also copy files from the 11.1 boxes to the Samba share without a problem. Now, if I remove the "default" ACL entries, but keep the regular ones, I regain the ability to write to this folder using the 11.1 boxes. But I loose some control over how ACLs are applied to newly created files, and this becomes an issue for the other users that share this data. So, my question is, am I alone in this issue, or are others having the same problem? Ken

1 1

[opensuse] Recent experience with Ubuntu 9.04, Gnome on openSUSE 11.1, and KDE 4.2.
by Fred A. Miller 28 Apr '09

28 Apr '09

I spent quite a bit of time comparing Ubuntu 9.04, Gnome on openSUSE 11.1, and KDE 4.2 11.1. I wasn't successful in getting Gnome to work with the Intel 3945 wifi, no matter what I did nor how I did it in Ubuntu. It did work in Gnome on openSUSE 11.1, however. ALL installs were clean....formatted partitions. The lack of configurability in Gnome is VERY apparent when one has been using KDE 3.5 AND newer for a long time. Gnome is VASTLY inferior to KDE 4.2, even though it's not a finished product yet. Yes, there are some things that are better....like a LOT of screen savers and they just work, which is not true of KDE 4.2. Now, as to the differences between Ubuntu/Kubuntu and openSUSE. A friend and writer recently said something to the effect that in Linux, Ubuntu is like an old VW and openSUSE 11.1 is like a Cadillac. I agree. The only problem is, that the "Cadillac" needs to be as easy to install and setup as the "VW" is. THEN, openSUSE will really have something to market! Fred -- The problem with socialism is that you eventually run out of other people's money. - Margaret Thatcher -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

7 7

[opensuse] This is supposed to work on openSUSE as well....Amarok 2 help.
by Fred A. Miller 28 Apr '09

28 Apr '09

>From a friend in the Philippines. Fred 15 April 2009 Ubuntu 9.04 / Amarok 2 Sound Problem I launched Amarok 2 to play a song just moments ago and to my horror, there was no sound. Grrrr.... Here's the solution: 1. Install phonon-backend-xine. 2. Remove phonon-backend-gstreamer. -- Gun-toting Americans are clearly more self-sufficient than the sissy Europeans. This is great news for everyone except Barney Frank, who's always secretly wondered what it would be like to be taken by a Somali pirate. --Ann Coulter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Bugs? in SuSE11 or fundamental linux flaws? file bug(s)
by Linda Walsh 27 Apr '09

27 Apr '09

Ran into a a couple of related bugs recently and want to get some feedback on whether they are SuSE specific, or if they are fundamental design flaws in linux, or what. Short description: * had/have working SuSE11.0 sys with 1 visible SAS-based disk that the OS had labeled "sda". I could tell it was labeled 'sda' by looking in the grub menu where it instructed linux to boot from sda3, and also by typing "fdisk -l". * Drives were mounted with Labels, as is my custom /=Root, /var=Var, etc. (months pass) * Needed big scratch space, so hotpluged a 1TB SATA into the controller Drive came up as 'sdb', I formatted & used it -- even added a working entry in /etc/fstab to hold the common non-default mount options (logbufs, noatime) Life was fine until a few weeks later I rebooted. System wouldn't boot. No valid root partition found at "sda3", please specify a valid root partition. Well I hadn't changed anything in terms of moving the root partition and no boot options would work (failsafe, nothing). Then I wondered if I had been <sarcasm>"blessed"</sarcasm> by some magical randomizing device-name manager due to the new disk I plugged in. I unplugged the new drive and it still didn't boot, but got further. Now it failed "fsck". At least that dumped me into single-abuser root mode where I found that 'fsck' was trying to call the "dummy script" _fsck.xfs_ (which does nothing other than test that the device it is asked to check, 'exists'. (but that was failing!) It seems fsck doesn't understand "noauto" (it used to!) -- and now tries to force a check and disk-modification (that would happen if it was the old fsck operating on an ext-type file system and it found correctable errors). But "noauto" used to mean (doesn't it still?) _manual_ mount only! Why would fsck try to force-check a disk that was labeled 'noauto' because it might not even be present? After commenting out the fstab line, altogether, the system booted. Fsck no longer was passing a non-existent device to "fsck.xfs" that simply checked for 'existance' -- so it no longer returned an error and the system was allowed to boot up normally rather than forcing me into 'single-abuser' mode to "fix" the problem of my "manually mounted disk" not being "fsck-able" on boot. Grrrr. AAARRRRGGGG...&& GRRRRRR.... Stupid machine... this is the blessing of "automation" that is being forced on me to make my life 'easier' -- which rarely does make it easier and isn't even implemented right on multiple levels!!! Grrrr.... ;^)....this is so "dorky" >>> Please NOTE<<<: so no one gets defensive here, I'm not mad or angry, or upset (it's just a machine), but at worst, "frustrated", but really mostly amused at the machine's clumsy attempts to "help me", only to make things worse and less reliable than before! So 2 bugs: 1) Why are my drives being switch around randomly? It's a feature, right? I DO use labels in my fstab -- but SUSE doesn't use labels for 'format -l', smartd, hdparm-settings-by-device, NOR, **most importantly**, does it use the software generated labels in the boot files (lilo or grub) -- and those are the real sticklers. I've long complained about the stupidity of forcing all devices to be 'floating' and dynamic (or defaulting to floating and dynamic) and this illustrates why. Question is, is this a SuSE only bug, or is this the whole concept of dynamic device management (it bites me on network setups as well, though there seem to be ways to work around it there and force a specific device to stay 'eth0', or 'eth1'... but that doesn't happen by default either and is only a problem if you have multiple ethernet cards and want to make sure your routing and firewall settings protect and route to the correct device. But I really need to make sure that hot-plugging a hard-disk in doesn't change the boot-disk because grub/lilo (among other utils that prefer or use hardware-device names and not software-names). And 2nd, more minor bug... why is fstab forcing an fsck on a drive not marked for mounting (i.e. marked 'noauto')? This is a regression. I can file a routine bug for the 2nd, but the 1st problem I don't even know where I'd start to file the bug against what -- because the whole system of dynamic software-naming of devices, while 'well intentioned' and desirable for dynamic software volumes, isn't really desirable for fixed-boot drives that important pieces (booting et al.) of the current software doesn't support being 'dynamic' in any way. So where would, or could, or should the 2nd problem be addressed? And if someone tells me I should submit a patch for all affected pieces of software, may the great 'foo bird' come to you and doodoo on you! (just don't wipe it off if it does...) :-) Linda Walsh (trying to maintain sense of humor about all this ya know, to avoid the reduction-to-quivering/gibbering-mass reaction)... :-) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

7 10

[opensuse] remove 'Floppy Drive' from Nautilus Places
by Shawn Protsman 27 Apr '09

27 Apr '09

I jut did a fresh install of 11.1 and now have a 'Floppy Drive' item in Nautilus Places (left-side panel). How do I remove this? I have no floppy drive. Here is my fstab: > cat /etc/fstab /dev/sda1 swap swap defaults 0 0 /dev/sda2 / ext3 acl,user_xattr 1 1 /dev/sda3 /home ext3 acl,user_xattr 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Curiosity really can kill -- or at least slow you down quite a bit...
by David C. Rankin 27 Apr '09

27 Apr '09

Listmates, A caution to the curious. Never.. Ever... use a for loop and cat to attempt to look at *all* the values for a process in /proc. Bad things happen on 11.0 (probably all versions). I wanted to look at the values for a bash shell running in konsole as process 24214 so I did: for i in $(find /proc/24214 -type f); do echo -e "$i\t$(cat $i)"; done The system slowed to a crawl... I ended up having to just shut the box down to resolve the issue. ps ax or ps -elf were not helpful in locating the errant process (I'm sure the info was there, but not something I recognized). kde started behaving like windows on a bad day with execution lagging a good 15 secs. behind input. (you know, 'click input' wait...wait.. button presses) It was really a perplexing situation. No amount of ctrl+c, break, ctrl+x or the like would kill the monster I had unleashed. My questions is "what happened?" What caused the meltdown that resulted from my use of cat? I want to know so I don't do it again. (obviously I won't run this same for loop again) But, what did I cat in /proc/24214 that let the demons out of the bag? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Re: Nagios check_ntp_peer aborts
by Joachim Schrod 27 Apr '09

27 Apr '09

Peter Bloomfield wrote: >> Can somebody on an OpenSUSE 11.1 system please execute >> /usr/lib/nagios/plugins/check_ntp_peer >> and tell me if it aborts with a stack backtrace, >> owing to a buffer overflow? >> >> Just want to check that it's not just my system before I open a >> bug. (No bug with check_ntp_peer in summary exists, so nobody seems >> to have had the issue yet.) >> > > Just executed it, and the result was abort with a stack backtrace. Thanks, and also thanks to Pete Connolly, who confirmed it, too. I'll open a bug report. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Nagios check_ntp_peer aborts
by Joachim Schrod 27 Apr '09

27 Apr '09

Hi, Can somebody on an OpenSUSE 11.1 system please execute /usr/lib/nagios/plugins/check_ntp_peer and tell me if it aborts with a stack backtrace, owing to a buffer overflow? Just want to check that it's not just my system before I open a bug. (No bug with check_ntp_peer in summary exists, so nobody seems to have had the issue yet.) TIA, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2