Op 28-10-12 17:40, Marcus Meissner schreef:

On Sun, Oct 28, 2012 at 05:27:51PM +0100, Oddball wrote:

...

I need to log in to desktop as root, but after i enter the password and hit enter, this message pops-up:

...

Call to lnuser failed (temporary directories full?). Check your installation. Is there something i have to do, to get root into my desktop again? Perhaps your / disk is full. Check that ;)

Ciao, Marcus

Are you serious? I can login to my other users without a problem, 6GB space left.. -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 28-10-12 19:51, James Knott schreef:

Oddball wrote:

...

I can login to my other users without a problem, 6GB space left..

Is /home on a different partition than /root? If so, one can be full and the other not.

That is sane, /home is separate, but on my /root partition is 3GB freespace.. -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 28-10-12 18:29, Felix Miata schreef:

On 2012-10-28 17:27 (GMT+0100) Oddball composed:

...

I need to log in to desktop as root, but after i enter the password and hit enter, this message pops-up:

...

Call to lnuser failed (temporary directories full?). Check your installation.

...

Is there something i have to do, to get root into my desktop again?

Is there an uncommented line anywhere in kdmrc with "AllowRootLogin=true"?

There is now, but that did not change anything, helas. thnx anyways. ;-) -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 28-10-12 19:28, Carlos E. R. schreef:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2012-10-28 18:29, Felix Miata wrote:

...

On 2012-10-28 17:27 (GMT+0100) Oddball composed:

...

...

Call to lnuser failed (temporary directories full?). Check your installation. Is there an uncommented line anywhere in kdmrc with "AllowRootLogin=true"? The error message should indicate that, not the error that it does produce. And that implies what exactly? I think also it is a permission problem, but i am not sure, and i do not know where root permissions are handled...

- -- Cheers / Saludos,

Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith))

-- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 28-10-12 20:07, Felix Miata schreef:

On 2012-10-28 19:47 (GMT+0100) Oddball composed:

...

I think also it is a permission problem, but i am not sure, and i do not know where root permissions are handled...

Can you login root on a tty and get into X with startx?

Probably you cannot if the last line of /etc/permissions.local is still commented. If you uncomment to try again, first either run 'SuSEconfig permissions' or reboot.

I forgot how to get to init3...? -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Oddball wrote:

I forgot how to get to init3...?

While booting, put a 3 on the Boot options line. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 28-10-12 21:03, Felix Miata schreef:

On 2012-10-28 15:24 (GMT-0400) James Knott composed:

...

Oddball wrote:

...

...

I forgot how to get to init3...?

...

While booting, put a 3 on the Boot options line.

That is one to remember, thnx.

Considering the context of the entire thread, I have to think what he was really after was remembering how to get to a tty, not to reboot without starting X: Ctrl-Alt-Fx.

Indeed, it was this one i was after! ;-) -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 28-10-12 20:07, Felix Miata schreef:

On 2012-10-28 19:47 (GMT+0100) Oddball composed:

...

I think also it is a permission problem, but i am not sure, and i do not know where root permissions are handled...

Can you login root on a tty and get into X with startx?

Probably you cannot if the last line of /etc/permissions.local is still commented. If you uncomment to try again, first either run 'SuSEconfig permissions' or reboot.

No, i can not. I get exactly the same message.

# # suexec is only secure if the document root doesn't contain files # writeable by wwwrun. Make sure you have a safe server setup # before setting the setuid bit! See also # https://bugzilla.novell.com/show_bug.cgi?id=263789 # http://httpd.apache.org/docs/trunk/suexec.html # #/usr/sbin/suexec2 root:root 4755

# setuid bit on Xorg is only needed if no display manager, ie startx # is used. Beware of CVE-2010-2240. # #/usr/bin/Xorg root:root 4711

This is what is there in /etc/permissons.local But Marcus said:

if you login via kdm, please do not touch this file, it is not the problem.

Check /var/log/messages and other logfiles.

Ciao, Marcus

So do i touch the file ? or not? (or do you mean another one? Marcus?) /var/log/messages is much too big to go trough, and too detailed. One part caught my eye: (it has nothing to do with the root-login failure though...)

ACPI Warning: 0x00000400-0x0000041f SystemIO conflicts with Region \SMRG 1 (20120913/utaddress-251) Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI Warning: 0x00000400-0x0000041f SystemIO conflicts with Region \_SB_.PCI0.SBRG.SMRG 2 (20120913/utaddress-251) Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI: Battery Slot [BAT0] (battery present) Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: cfg80211: Calling CRDA to update world regulatory domain Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI Warning: 0x00000828-0x0000082f SystemIO conflicts with Region \PMIO 1 (20120913/utaddress-251) Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI Warning: 0x00000828-0x0000082f SystemIO conflicts with Region \_SB_.PCI0.SBRG.PMS0 2 (20120913/utaddress-251) Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI Warning: 0x000004b0-0x000004bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPBX 1 (20120913/utaddress-251) Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI Warning: 0x00000480-0x000004af SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPBX 1 (20120913/utaddress-251) Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Oct 25 16:56:22 EeePc-Rob-SFN9 kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich

There is one, but it was for Ubuntu, or what was the Linux version for eee pc 901? But it is as old as the machine, would that be a problem? -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 29-10-12 23:59, Felix Miata schreef:

...

So do i touch the file ? or not?

It depends whether or not you care whether you can get into X as root via startx.

I have to, to get rid of an application where i cannot only use root terminal, so i try. -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2012-10-28 01:44 (GMT+0100) Oddball composed:

...

...

It depends whether or not you care whether you can get into X as root via startx.

...

I have to, to get rid of an application where i cannot only use root terminal, so i try.

It was not a good idea, same message, but all kinda things happened, and ctrl+alt+F7 did not take me back to my regular desktop after that...

so still unable to login to root desktop..

If KDM is already running, startx alone won't work. Either shut KDM down first, or do 'startx -- :1'. It may be a good idea to start fresh by rebooting with 3 on the Grub cmdline. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 30-10-12 08:48, Freek de Kruijf schreef:

Op maandag 29 oktober 2012 01:44:09 schreef Oddball:

...

so still unable to login to root desktop..

Did you try to enter "root" as the username and the root password in the login screen that you get right after booting? It is not recommended, but if this is what you are after, it works for me in 12.2 and 12.3 and earlier versions.

Nope, just the same message. And Yast broke and is not able to return to default theme, so am stuck with the most ugly dinosaur login screen ever... lol. (as if yast wants to say, don't try to improve, or i'll make it worse... :-D Do you know where Yast looks for the KDM themes, because it definitely is not the default: /usr/share/kde4/apps/kdm -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 30-10-12 10:18, Freek de Kruijf schreef:

You still work with the default version of KDE, 4.8, in 12.2. You might consider to use KDE 4.9 by adding http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.2 as an extra repository and update your system with zypper or YaST. Maybe this restores a working system. Otherwise you should consider to do a fresh install of openSUSE and copy your working data from a backup to that system and do piecewise what you want to change, so when things go wrong you undo the piece that went wrong and try something else.

Sane advice. -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 30-10-12 14:49, Patrick Shanahan schreef:

* Oddball [10-30-12 05:50]:

...

Op 30-10-12 10:18, Freek de Kruijf schreef:

...

You still work with the default version of KDE, 4.8, in 12.2. You might consider to use KDE 4.9 by adding http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.2 as an extra repository and update your system with zypper or YaST. Maybe this restores a working system. Otherwise you should consider to do a fresh install of openSUSE and copy your working data from a backup to that system and do piecewise what you want to change, so when things go wrong you undo the piece that went wrong and try something else. Sane advice. But you seem to still, somehow, have remnants of KDE3 on your system that you *cannot* get from a new system install, Not Possible!(tm).

And you will continue to find unexplanable problems while you work with a corrupted system. All (at least most) of your findings of inaccurate paths and erroneous documentation stem from a corrupted system. In spite of a few individuals heroic efforts to sustain KDE3, it is a "dead horse".

Seems time for a pristine 12.2 install.

I did, i formatted /121, and installed clean. Than created new user and removed my /home from121, -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.2 "release 511" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2012-10-30 10:22 (GMT-0400) Patrick Shanahan composed:

No, not if you still have references to KDE3 as they "do not exist" in 12.2, or you have added them since.

That's what I thought too until last month or so: # cat /etc/SuSE-release openSUSE 12.2 (i586) VERSION = 12.2 CODENAME = Mantis # zypper lr # | Alias | Name | Enabled | Refresh --+--------------------------+--------------------------+---------+-------- 1 | KDE49 | KDE49 | Yes | No 2 | Non-OSS | Non-OSS | Yes | Yes 3 | NonFreeUpdate | NonFreeUpdate | Yes | No 4 | OSS | OSS | Yes | Yes 5 | Packman | Packman | Yes | No 6 | Update-non-oss | Update-Non-Oss | Yes | Yes 7 | Updates | Updates | Yes | Yes 8 | homebjoernvPanningUpdate | homebjoernvPanningUpdate | Yes | No # zypper se -s kde | grep kdebase3 | kdebase3 ...| OSS | kdebase3-SuSE ...| OSS | kdebase3-SuSE-branding-basedonopensuse...| Updates | kdebase3-SuSE-branding-basedonopensuse...| OSS | kdebase3-SuSE-branding-openSUSE ...| OSS | kdebase3-SuSE-lang ...| OSS | kdebase3-apps ...| OSS | kdebase3-devel ...| OSS | kdebase3-extra ...| OSS | kdebase3-kdm ...| OSS | kdebase3-ksysguardd ...| OSS | kdebase3-nsplugin ...| OSS | kdebase3-runtime ...| OSS | kdebase3-samba ...| OSS | kdebase3-session ...| OSS | kdebase3-workspace ...| OSS -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Oddball wrote:

Op 30-10-12 08:48, Freek de Kruijf schreef:

...

Op maandag 29 oktober 2012 01:44:09 schreef Oddball:

...

so still unable to login to root desktop..

There's a /etc/securetty that specifies what terms root can login on. Are you sure the "terminal" you are logging in on in the graphical UI is in there? (I don't know what it would be, but just a guess that maybe something changed a devname and that file wasn't updated?) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2012-10-31 08:57 (GMT+0100) Oddball composed:

I can not go to a desktop that is root.

1-add http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.2/KDE... to /etc/zypp/repos.d/ 2-zypper ref 3-zypper lr 4-zypper dup -r 5-zypper in -f [kdm-branding-openSUSE,kdm-branding-upstream] # (pick one only) 6-confirm that /etc/sysconfig/displaymanager contains no uncommented prohibition of *ROOT_LOGIN* 7-ensure uncommented AllowRootLogin=true is in /usr/share/kde4/config/kdm/kdmrc 8-restart KDM 9-if not success, reboot and try root login again 10-report results here -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-10-31 08:57, Oddball wrote:

Op 30-10-12 22:02, Linda Walsh schreef:

...

There's a /etc/securetty that specifies what terms root can login on. Are you sure the "terminal" you are logging in on in the graphical UI is in there? (I don't know what it would be, but just a guess that maybe something changed a devname and that file wasn't updated?)

The terminals in my users desktop can go root without problem. I can not go to a desktop that is root. I do not understand your question.

Just have a look at the file. But it does not apply to graphical terminals, AFAIK. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlCQ/CgACgkQja8UbcUWM1xwdQD/fI5TDHuLxtoiIg7GRaZBQgUb xdyIeJ4/vbQAPiOI5E0A/iUD77ueokFzmeXko+nv8Cb0f1UhnuUXGgmXjfI9JPps =OChK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 29-10-12 01:14, Oddball schreef:

Op 29-10-12 23:59, Felix Miata schreef:

Something about the commandline and 3 boot. Lost the original mail...

There seems to be no cli option anymore in grub2, And:

Bestand: /etc/sysconfig/displaymanager Mogelijke waarden: yes,no Standaardwaarde: yes Configuratie-script: kdm3 Omschrijving:

Allow local access of the user root to your display manager. Note that root can never login if DISPLAYMANAGER_SHUTDOWN is "auto" and System/Security/Permissions/PERMISSION_SECURITY is "paranoid". This settings currently works only with KDM.

I could change 'auto', but i could not find the other option..... yet. -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 30-10-12 02:06, Felix Miata schreef:

On 2012-10-30 02:18 (GMT+0100) Oddball composed:

...

There seems to be no cli option anymore in grub2,

It exists. It's just not so obvious how to find it as in Grub Legacy. This is only a minor reason out of many reasons why 100% of my 100+ openSUSE installations, among which more than a dozen 12.2 and Factory, have only Grub Legacy installed. When something works for me as well as openSUSE's Grub Legacy GFXboot, I stick with it, regardless what's new and "improved". Good chance it can do as well for you.

Probably you are right. I missed out on the testing of 12 from the start. So i am not aware of the downside of all 'improvements' yet. I use to be openMINDED. And as always want to fix what is broken... But now, as always of late, there are too many changes at once, and too few people to solve the problems that brings. I forgot about the time it took to solve the most annoying, time that i no longer have, due to responsibilities. The system is not consistent, yast is not in tune. Yast says KDM3 script runs, (which might not be the same as KDM3 runs) but it breaks if one wants to change a theme, and can not reverse to the default, though it says it does. Plymouth themes from the opensuse repos install, but in reality, they do not run. No root desktop. I said it earlier, and i say it again: Too many changes at once, make it very difficult to find out what exactly causes what. Which means that despite of the fact that 122 is released, it was not ready by longshot. Which means that many users get disappointed again, and choose Ubunti, because that 'seems' to have what it takes. (not to me, but i regret not to have some things Ubunti has.) Consistent means: That if a path is appointed/assigned, it should be the path that works, and certainly if the main configuration tool says so. If not, it all becomes implausible. Credibility gets lost this way, not for loyal fans, but for new members. They try, every once in a while, and wait untill it is ready, if ever. I have to make up my mind about which path to choose: Good 'old' Grub and GFX, or hack myself into grub2 and plymouth. But still i will have no root desktop. And still i will have no login screen that i like. The only thing i have always hated, is to turn back... But it certainly does not harm to use something that works. -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op 28-10-12 19:56, Felix Miata schreef:

On 2012-10-28 19:28 (GMT+0100) Carlos E. R. composed:

...

On 2012-10-28 18:29, Felix Miata wrote:

...

...

...

...

Call to lnuser failed (temporary directories full?). Check your installation.

...

...

Is there an uncommented line anywhere in kdmrc with "AllowRootLogin=true"?

...

The error message should indicate that, not the error that it does produce.

Keyword: "should". With a problem like caused this thread, there could be an as yet unidentified bug with more than one effect.

Are there more complains about this behavior yet? -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2012-11-17 14:22 (GMT+0100) Oddball composed:

Is there an easy command to get the output of a tty to an editor?

OT for this list. Redirection: e.g. you have output from ls on the screen and want it in an editor. Just hit the up key, then add > somefilename to what history just put on cmdline. For some outputs you may need a more elaborate redirect, such as &>, to capture stderr as well. http://www.tldp.org/LDP/abs/html/io-redirection.html -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org