November 2012 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Chromium browser has changed it's home location
by Raymond Wooninck 24 Nov '12

24 Nov '12

Dear openSUSE users, Since this morning, the Chromium browser will no longer be maintained on the openSUSE OBS, nor will it be provided together with the openSUSE distribution. Instead the Chromium browser will be build on Packman and be available for the already supported openSUSE versions. This new version will replace the chromium-ffmpeg package that was already delivered through Packman. In the next days, I will delete the Chromium package from it's home location network:chromium and also send a delete request to openSUSE:Factory. The reason for this change is that ffmpeg support is becoming more and more integrated with the browser itself, making it very hard to remove the ffmpeg related sourcefiles and still keeping a workable browser. In the last few weeks, I tried everything to keep Chromium part of the openSUSE distribution but unfortunately I failed. And as we all know ffmpeg is one of those packages that are not allowed to be present on the openSUSE OBS. Therefore the only logical decision was to move Chromium completely to Packman. The new package will be a full enabled Chromium with build-in support for ffmpeg. The new version 25.0.1329 is already available from Packman and should be installed automatically as that it replaces the chromium-ffmpeg package. If not, please check manually in order to get the latest version from Packman. This should be a one-time manual intervention. Regards Raymond Community Maintainer for the openSUSE Chromium package -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 16

[opensuse] chromium problem
by lynn 24 Nov '12

24 Nov '12

12.2 with YOU Hi everyone. Since I last updated I now get this message when launching chromium: 'Your profile can not be used because it is from a newer version of Chromium. Some features may be unavailable. Please specify a different profile directory or use a newer version of Chromium.' However, my profile woks fine. How should I proceed? Thanks, L x -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] RE: Help with establishing an FTP Server
by secure domain 24 Nov '12

24 Nov '12

Could someone help walk me through the creation of an FTP Server using the GUI in YAST I hope there is a 'how to' procedure as the help text is of little value and the Global Help app in opensuse is next to useless. Here is what I dont understand in the YAST FTP Server Help Page >Umask for Anonymous: >The value that the umask for file creation is set to for anonymous users. If you want to specify >octal values, remember the "0" prefix, otherwise the value will be treated as a base 10 integer. >Umask for Authenticated Users: >The value that the umask for file creation is set to for authenticated users. If you want to specify >octal values, remember the "0" prefix, otherwise the value will be treated as a base 10 integer. I have a feeling the mask is the user UI number and I should use the user FTP, however I dont know that users password or if there is any password. >FTP Directory for Anonymous Users: >Here you can specify a directory which is used for ftp anonymous users. By pressing Browse you >can select a directory from the local filesystem. >FTP Directory for Authenticated Users: >You can specify a directory which is used for ftp authenticated users. By pressing Browse you can >select a directory from the local filesystem. I do not know what directory/file permissions are needed as far a owner/user/group/others when I do not want to use the default /srv/ftp directory. >Enable/Disable Anonymous and Local Users >Anonymous Only If enabled only anonymous logins are permitted. Authenticated Users Only If >enabled only authenticated users are permitted. Both If enabled authenticated users and >anonymous users are permitted. What is the difference between passive mode and an anonymous user found in >Enable Passive Mode >If enabled the ftp server will allow passive mode for connections All other fields I understand and in this situation upload from the FTP is not required, only write access. Thanks...BTW...IF the GUI Interface can not accomplish configuring an FTP server I need to know as we need to either remove it from Yast or fix it Thank you to all...... -- Confidentiality/Limited Liability Statement This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message, you must not disseminate, copy or take any action in reliance on it. If you have received this message in error,please notify the author immediately. Any views expressed in this message are those of the individual sender and the author accepts no liability for the content of this message except where the sender specifically states them to be the views of the author. IMPORTANT NOTE - Disclaimer: Whilst the services and the information and the facilities provided by and/or through this e-mail are provided in good faith, no representations, warranties or other promises are made in relation to the accuracy, quality, reliability or suitability of the services or the information or the facilities provided by and/or through this e-mail and you accept them and make use of them at your own risk and relieve the author from all liability (in contract, tort or otherwise whatsoever) for any loss, expense or damage suffered by you as a result of such use. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

[opensuse] Chromium browser has returned to it's openSUSE uhome location
by Raymond Wooninck 24 Nov '12

24 Nov '12

Dear openSUSE Users, Last week, I send out the message that it was no longer possible to build Chromium on the openSUSE OBS. This due to issues with ffmpeg, etc. Due to the big help of Ludwig Nussel, we resolved the issues and I can now inform you that we are building Chromium again in it's old location and that we will continue shipping Chromium with openSUSE. A new subpackage was introduced (chromium-ffmpegsumo) that builds a restricted form of the multimedia library required by Chromium. This library supports all the opensource codecs. On Packman we continue to build the chromium-ffmpeg package that contains the same multimedia library, but then with support for more proprietary codecs (equal to the ones supported by the official Chrome browser). If you install the chromium-ffmpeg package, then automatically the new chromium-ffmpegsumo package will be deinstalled. This is the correct behavior. I would like to thank Ludwig again for his help in resolving this matter. As a reminder: The Chromium browser is build in the network:chromium repository and from there updates to Factory and maintenance updates for 12.2/12.1 are shipped. I would like to apologize for the inconvienence this might cause due to swapping the repositories. Regards Raymond -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: how to set global environment variables in crontabs
by Joachim Schrod 24 Nov '12

24 Nov '12

Anton Aylward wrote: > Joachim Schrod said the following on 11/23/2012 12:33 PM: >> Anton Aylward wrote: >>> Joachim Schrod said the following on 11/23/2012 10:49 AM: >>>> I use Perl to test that the env var is set for all cron jobs and not >>>> just for shell scripts. >>> >>> If you used the 'env' command you'd see a lot more and that _might_ give >>> a clue. >> >> What clue _might_ I need? >> My posted scripts work. I tested them. >> >> Meike is right that $ENV is not sourced -- which is strange, but I >> didn't investigate. [....] >> >> I also don't want an entry like >> * * * * * env > > Ah, we're talking at cross purposes then! > I was thinking in terms of experimenting - seeing what _could_ be put in > the environment and what ended up in there that you didn't explicitly > put there, varying conditions, different shells, entries in /etc/passwd > and so forth. > > And yes, I did that I found that it does vary things. > > You seem to be jumping straight to 'production'. > > Fair enough. This wasn't as critical for me as for you; I had the time > to experiment ... It wasn't critical, I simply didn't have the time to experimet. (Just look at the hours when I'm writing these emails... :-)) For me, it was a question of a fellow openSUSE user -- which I though I could answer from my knowledge base, just a link and some few tips. The surprise caught me, when my hint didn't work. So I took a few minutes off my lunch break, tried it out, and found a way to make it work. For me, tt was always the specific problem of Meike, and not some general issue with cron or such -- not even the generic issue that surely lingers behind Meike's original question, as unspecified as it is. I know from your posts here, that you're a professional, that's why I answered your post at all. I thought already that this is a communication problem, thanks to confirm it. You seem to have thought about the general problem, my POI in this discussion was to solve the immediate problem -- you did problem management, and I was on incident management track. ;-) Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jschrod(a)acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] Re: how to set global environment variables in crontabs
by Meike Stone 24 Nov '12

24 Nov '12

> > As hinted in the last cited line: > >> the /etc/crontab is: >> ============================================== >> SHELL=/bin/bash >> ENV=/etc/profile.d/my-env.sh > > If $SHELL is /bin/bash, $ENV is not read. Then $BASH_ENV is read. Yes you are right. But I changed it to SHELL=/bin/sh and the same problem again. As you can see in my former posting, the variables are read (debug output from cron), but they are not set in the called cron (output from "set") Thanx Meike -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] Re: how to set global environment variables in crontabs
by Joachim Schrod 23 Nov '12

23 Nov '12

Anton Aylward wrote: > Joachim Schrod said the following on 11/23/2012 10:49 AM: >> I use Perl to test that the env var is set for all cron jobs and not >> just for shell scripts. > > If you used the 'env' command you'd see a lot more and that _might_ give > a clue. What clue _might_ I need? My posted scripts work. I tested them. Meike is right that $ENV is not sourced -- which is strange, but I didn't investigate. After she told that in her email, I wrote the scripts and tested it. (Before, I only relayed info from documentation.) My test result: $BASH_ENV is sourced when SHELL is set to /bin/bash; so she can use that. IMNSHO: One doesn't need any additional clue, output by the command env, here. I'm not interested in other env vars. I'm just interested in the one that is set in the to-be-sourced /tmp/setenv.sh. I also don't need to test that $ENV or $BASH_ENV are set, I use env vars in crontab all the time and that Just Works(tm), no need to check that again. I also don't want an entry like * * * * * env which would send email every minute. Instead I want it in a file where I can use F in less. In addition, IMO, just one line added there is better than a whole bunch of lines; one sees differences to previous invocations faster. Humans are excellent pattern matchers line-by-line, but not so block-by-block. I.e., I think my Perl script is also better than "env >>/tmp/foo.out". Maybe adding a timestamp to that one line would be helpful, and even for that the Perl script is better again, just add localtime() to the print statement. Just my 0.02 EUR, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jschrod(a)acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Why can't i login to Desktop as root?
by Oddball 23 Nov '12

23 Nov '12

Op 17-11-12 17:30, Felix Miata schreef: > 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. (<corrected) > > 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 I studied it for a while, but i seem rather dumb. I tried some of the commands to get everything listed in a file, but there seems to be no file, or i do not know where to look for it, or if and how to specify where it should be stored, in case that would be necessary. If there is a default place where it is stored, i just have to know where that is of course. I now have a large log of all that happens, on a tty. Is this output anywhere else? Or a way to get the output which is there, to a place to be able to scroll it? Please forgive me my stupidity, but the only thing i would like to accomplish, is to get the complete output of the tty, to a file, to be able to study it. I see that it registers everything that happens, should happen, or does not happen, so it might be interesting to relate some issues. I also noticed that there is a root desktop on tty3 atm, which is accessible and usable at the same time as the one in tty7, switched of course. I do not know how it gets there, unless a rootdesktop, when opened, always loads in the next available tty. I did not shut down, only sleep, because i wanted to capture the output in tty2. I looked at /var/log but there is nothing there, just wtmp, but i do not know how to open it to show normal text (ASCII) -- Have a nice day, Oddball. OS: Linux 3.7.0-rc5-2-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.3 "release 520" -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

15 103

[opensuse] Bigger .odt files from LibreOffice
by Carlos E. R. 23 Nov '12

23 Nov '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I have just noticed that if I save again an .odt file dated 2012-07-31, sized at 16279 bytes it now gets a size of 27096 bytes. The exact same documents, just open and save as. I observed this in two documents at least. I have unziped both files (two version of same), and the only noticeable difference is the ./Thumbnails/thumbnail.png file. new: 14842 old: 4065 Both are: thumbnail.png: PNG image data, 181 x 256, 8-bit/color RGB, non-interlaced So I assume that somewhere the compression of png files has changed; I do not know if in source code or in some config file. Can somebody else verify this? I can not open a Bugzilla as I'm using 11.4 evergreen, but I think that this can be replicated on newer versions. - -- 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/ iF4EAREIAAYFAlCvdr0ACgkQja8UbcUWM1z/AAD/SebAdAwl01/MtKIk6AQbdEhQ +SHc5MBfkTJiEKGOr2IA/2VQVOYm3R1tDDaOsap437NqfuN6lGI0zniWgGbYbwKC =wODx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] Re: [open OFF LIST suse] Re: how to set global environment variables in crontabs
by Meike Stone 23 Nov '12

23 Nov '12

2012/11/23 Anton Aylward <Anton.Aylward(a)rogers.com>: > Meike Stone said the following on 11/23/2012 10:59 AM: >> 2012/11/23 Anton Aylward <opensuse(a)antonaylward.com>: >>> Joachim Schrod said the following on 11/23/2012 10:49 AM: >>>> I use Perl to test that the env var is set for all cron jobs and not >>>> just for shell scripts. >>> >>> If you used the 'env' command you'd see a lot more and that _might_ give >>> a clue. >>> >> >> I tried 'env' and 'set' in the crontab, but the variables are not set ... > > > That's not what I meant > I'm talking about the 'env' command not the ENV directive in cron > > try 'man 1 env' to see what the env COMMAND does. > > If you're not setting the environment then it reports it. > That was what I intended > > And entry like: > * * * * * env Yes, thats what I mean this too. And I don't want execute any command (via env). I used 'env' to show me the Environment. (from manualpage: "If no COMMAND, print the resulting environment.") I used 'set' and 'env' in my testcron to print out the environment ... Meike -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0