October 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] when is data physically written to disk (Reiserfs)?
by Daniel Bauer 23 Oct '14

23 Oct '14

Hello I'd like to know when data that should be written is really written physically to the disk. I use OS 12.3, Reiserfs (with encrypted LV for /home, /root, /swap, on 1 drive and separate encrypted drive outside LVM) Several times after switching off without properly shutting down (after power fail) and rebooting I noticed that there were many systemd-fsck[720]: Trans replayed:... Trans replayed: mountid... even when the computer was not doing anything before the switch-off occurred. Like today: the computer was "on" during the night, but without doing anything, in the early morning the electricity was cut off and so I had to reboot and I got hundreds of "replay"-messages... I thought, data would be written to the disk physically and definitively at least in moments when the computer has nothing else to do, but how comes that after hours of being idle there still remains so much to replay? Is this normal? Should I check some settings? Thanks for explanation or hints... Daniel -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] v12.3 and html5
by Dave Smith 23 Oct '14

23 Oct '14

Hi, I am using v12.3. Recently I have been encountering more html5 videos on the internet. They do not work well in either chromium or firefox. They will not play until the video is completely loaded which for some reason takes significantly longer than flash and there is no sound. I have high speed internet and have no problems with anything else, just html5. How can I get this working? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] a decent manual pr howto on pulseaudio
by Istvan Gabor 23 Oct '14

23 Oct '14

Hello: Does anyone know about a decent manual or howto on pulseaudio? I mean something that explains the basics, its mechanism etc, not only some short instructions if want achieve this type this or similar. I checked pulseaudio wiki web page (http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/) but it is really lacking substantial information. Many of the links/pages are simply empty. I also tried to read command line syntax as the link http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/CLI/ suggests but could not find the manual on my opensuse (12.2) system. > man pulse-cli-syntax No manual entry for pulse-cli-syntax I would like to do so "complex" things such as recording and listening to a stream so that the recording volume should not be altered by changing the listening volume (in other terms the volumes for listening and for recording should be independent.) Furthermore I don't know how to use pavucontrol. How and why the the different volume settings alter each other? Why is it that when I move the slider to the left (decrease volume) there is no audible volume difference until a point, but after that point there is a dramatic volume decrease? Thanks for any help, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] ld --as-needed -lgcc_s causing linker failure when called by gcc, OK standalone
by David C. Rankin 23 Oct '14

23 Oct '14

All, (ld linker gurus especially), I am befuddled by the behavior of gcc/ld in compiling/linking a couple of c/assembly files that I need help figuring out. The files are just a couple of the example files which I'm building as a 32-bit elf file on x86_64. For some reason when ld is called by gcc, the build fails. Calling ld standalone works fine. I need to understand what default behavior of the gcc/collect2/ld call is causing the problem and how I can fix it. I also have one other question at the end concerning why '-dynamic-linker /lib/ld-linux.so.2' is expressly required if it is the default, but that is separate from this first issue. For the first issue, the assembly/c files are all contained in: [a whopping 3.7k total] http://www.3111skyline.com/dl/bugs/openSuSE/131/pcasm.tar.bz2 I built the assembly files without issue using: $ nasm -felf -D ELF_TYPE -o asm_io.o asm_io.asm $ nasm -felf -o first.o first.asm Compiling the c file to object and performing an independent link produces a working executable (there is a 32/64 bit issue left, but irrelevant to this discussion): $ gcc -c -m32 -o main.o main.c $ ld -dynamic-linker /lib/ld-linux.so.2 \ -o first first.o asm_io.o main.o \ -m elf_i386 -lc Attempting to compile/link with gcc is where the problem arises. If I replace the compile of main.c to object with a request that gcc perform the compile/link, the build fails: $ gcc -v -m32 -o first main.c first.o asm_io.o -Wl,-melf_i386 <snip> x86_64-suse-linux/bin/ld: cannot find -lgcc_s collect2: error: ld returned 1 exit status Now, the part I'm stumped with is why is the link failing? The full compiler output is at: [newlines provided for readability] http://www.3111skyline.com/dl/bugs/openSuSE/131/pcasm/asm_io_main_build-alc… Looking at the final collect2 output, you see: COLLECT_GCC_OPTIONS='-v' '-m32' '-o' 'first' '-mtune=generic' '-march=i586' /usr/lib64/gcc/x86_64-suse-linux/4.8/collect2 --build-id --eh-frame-hdr -m elf_i386 -dynamic-linker /lib/ld-linux.so.2 -o first <snip> showing the '-dynamic-linker /lib/ld-linux.so.2' option is selected. So why does the link fail? Looking further, I see what appears like the likely suspects, but I am not familiar enough with the --as-needed --no-as-needed options to know if this is in fact the cause: <snip> -melf_i386 -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed <snip> The manual says: --as-needed --no-as-needed This option affects ELF DT_NEEDED tags for dynamic libraries mentioned on the command line after the --as-needed option. Normally the linker will add a DT_NEEDED tag for each dynamic library mentioned on the command line, regardless of whether the library is actually needed or not. --as-needed causes a DT_NEEDED tag to only be emitted for a library that at that point in the link satisfies a non-weak undefined symbol reference from a regular object file or, if the library is not found in the DT_NEEDED lists of other libraries, a non-weak undefined symbol reference from another dynamic library. Object files or libraries appearing on the command line after the library in question do not affect whether the library is seen as needed. This is similar to the rules for extraction of object files from archives. --no-as-needed restores the default behaviour. (https://sourceware.org/binutils/docs/ld/Options.html#Options) This seems to indicate for -lgcc_s that a DT_NEEDED tag will only be emitted if -lgcc_s satisfies: (1.) a non-weak undefined symbol reference from a regular object file or (2.) a non-weak undefined symbol reference from another dynamic library Since, libgcc_s is not needed, what is causing either of the criteria (1.) or (2.) to be satisfied? Is it some default? More importantly, how to tell the linker not to look for it? Is there some additional option I can pass or rearrange the order of the gcc command that would help? Lastly, if '-dynamic-linker /lib/ld-linux.so.2' is the default, then why must it be expressly included with the standalone ld call in order to produce a working executable? If it is omitted, the executable is produced, but inoperable due to /usr/lib/libc.so.1 being used instead of /lib/ld-linux.so.2 in the executable -- which I'm having difficulty understanding. Specifically, if linked with: $ ld -dynamic-linker /lib/ld-linux.so.2 \ -o first first.o asm_io.o main.o \ -m elf_i386 -lc the executable works and contains the following explicit reference to /lib/ld-linux.so.2: $ hexdump -C -s 272 -n 32 first 00000110 01 00 00 00 2f 6c 69 62 2f 6c 64 2d 6c 69 6e 75 |..../lib/ld-linu| 00000120 78 2e 73 6f 2e 32 00 00 03 00 00 00 05 00 00 00 |x.so.2..........| However if linked using the following: $ ld -o first first.o asm_io.o main.o -m elf_i386 -lc /usr/lib/libc.so.1 takes its place and the executable fails: $ hexdump -C -s 272 -n 32 first.sav 00000110 01 00 00 00 2f 75 73 72 2f 6c 69 62 2f 6c 69 62 |..../usr/lib/lib| 00000120 63 2e 73 6f 2e 31 00 00 03 00 00 00 05 00 00 00 |c.so.1..........| The files are identical in all other respects: $ l first* -rwxr-xr-x 1 david david 8030 Oct 21 03:15 first -rwxr-xr-x 1 david david 8030 Oct 20 21:31 first.sav But one runs, one doesn't: $ ./first Enter a number: 10 Enter another number: 14 Register Dump # 1 EAX = 00000018 EBX = 00000018 ECX = F7796132 EDX = F778B650 ESI = FFF7240C EDI = 08048290 EBP = FFF723FC ESP = FFF723DC EIP = 080482C7 FLAGS = 0216 AF PF Memory Dump # 2 Address = 0804A044 0804A040 72 3A 20 00 59 6F 75 20 65 6E 74 65 72 65 64 20 "r: ?You entered " 0804A050 00 20 61 6E 64 20 00 2C 20 74 68 65 20 73 75 6D "? and ?, the sum" You entered 10 and 14, the sum of these is 24 $ ./first.sav bash: ./first.sav: No such file or directory Why does expressly including '-dynamic-linker /lib/ld-linux.so.2' make that difference if it is the default? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] 13.1 yasm package updated 1.2.0 -> 1.3.0
by David C. Rankin 23 Oct '14

23 Oct '14

All, Just FYI, I built an update yasm package for 13.1 in buildservice: https://build.opensuse.org/project/repositories/home:drankinatty:branches:o… One of these days I'll figure out how to point to it correctly from the myriad of links on the buildservice page... You guys working on factory can pull the package for the current release, validate it and include it if all is well. I didn't find a current build for 1.3.0 when I looked. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] System D: Debian Fork
by Anton Aylward 23 Oct '14

23 Oct '14

OBTW: Since I subscribe to this list there is no point in cc'ing me. On 10/22/2014 02:52 PM, Banga Gong wrote: > > > When did this vote occur? Development under Linux has never been about a democracy but about those who take an initiative and develop something. Either it gets used and accepted by the community or not. The only 'fascist' element that I've seen is that on occasions Linus is outspoken. There's a saying about "vote with your feet". If there's a vote going on its to accept systemd simply because the vast numbers of users are not , repeat NOT deserting systemd based implementations. > This has been foisted on the OpenSUSE community without ANY prior > discussion. Ah. BIG LIE time again. > Many who you say "agree" with you simply have no opinion because > they donb't know ANY of the issues conerning systemd. I think you mean "they don't care". For them its a "difference that makes no difference". Well, perhaps it makes debugging easier, state machines are ridiculously easy to debug, as any hardware engineer will tell you. They are much more deterministic. That they don't know the issues may well be the case because they don't care, all they care is that their system works. Maybe it works faster now, but that's a side effect and not a design criteria. > Typical leftist -- always trying to inflate the numbersof people who > agree with you by counting people who do not, > and otherwise trying to inflate the appearance of > populareity for your pet causes. Are you calling me a leftist? Strange. Most people, who deal with me, my managers and peers, call me a conservative. I fail to see what politics has to do with coding system administration. And even if you want to discuss that, this forum is not the place for it. Still, people project what they want to believe. You probably believe that 'leftists' is an insult. As such it says more about you than it does about me. > > Try this for once: HONESTY > > You'll be amzing at how many enemies it do NOT make. ROTHFLMAO! You confuse a few concepts here. You believe that you are honest when you are making personally intimidating, insulting and tactless remarks? Even if that were so, its certainly no way to to lead people to accept what you say and come to agree with your views. It seems you can't discuss the technical merits of a piece of code without resorting to personal insults. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] desktop dying after few seconds of switching on
by Peter 23 Oct '14

23 Oct '14

Bit of a general PC repair question here, but it's one on which I was hoping to install openSUSE, and I can't even get past the first hurdle. An ex-friend-turned-trou-de-cul (French people are never your friends, only future enemies) donated me a P4 desktop which supposedly worked fine but upon switching on, it only lasts a few seconds before going off. So although I can access the BIOS, I cannot even get to make any configuration changes in time before it turns off. Of course I've done a first check for loose or wrong connections. My hunch is either the motherboard or PSU is at fault, but these are things I cannot test as I have no suitable alternatives available. I'm going to embark on a systematic process of elimination with some of the other parts, but does anybody want to throw a suggestion into the hat as to what is usually at fault in this situation? I'm not going to examine every part to provide detailed specs just yet, suffice to mention that it has integrated Intel 965 graphics, so it can't be that old 'unseated video card' chestnut. Cheers, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

11 22

Re: [opensuse] System D: Debian Fork
by Ken Schneider - openSUSE 22 Oct '14

22 Oct '14

On 10/22/2014 02:59 PM, Banga Gong wrote: > Ken Schneider - openSUSE wrote: >> On 10/22/2014 03:40 AM, Sam M. wrote: >>> I came across this article below, and it looks like the System D >>> implementation on Debian has caused a great deal of havoc and alienation >>> amongst devs and admins, so a fork is potentially in the works. I was >>> wondering if a similar interest is also present in the openSUSE >>> community? >>> Is openSUSE going to become one huge monolith where practically every >>> package is dependent on each other, and, the user is forced into a >>> corner? >>> For instance, that atrocious Baloo virus that runs by default on a >>> new KDE >>> install will start indexing before you allowed it to, and can't be >>> removed >>> because it's dependent on so many things. Part of it can be removed >>> (last I >>> checked), but not the entire thing. If things are going to become one >>> big >>> monolith, which obviously is contrary to the Unix philosophy, why not >>> just >>> run Windows? >>> >>> It seems like more people than not don't like System D, and Lennart >>> Poettering's attitude has been described as rude, egocentric and >>> childish >>> which doesn't help the case. PulseAudio was also developed by Pottering, >>> and I don't like it at all as it's just one more broken piece of >>> software >>> on top of the already overly complex Linux sound stack. I've had >>> problems >>> with it, and it has provided me zero benefit. Anyway, I think the >>> System D >>> debate here should continue >> >> Not a problem. There is a "Soapbox" forum for these types of >> discussions available, take it there. >> > > Wrong . > > Ontopic discussionS are offtopic on the offtopic list. > > This is on topic. > > At first, you marginalized objectors by saying that we should have the > discussion later... No, I said no such thing. Re-read the thread. > now you're complaining that objections weren't talked about sooner. > and saying that because we didn't discuss it sooner, we should shut the > fuck up. Again, I said no such thing. I asked that this soapbox discussion be taken to an appropriate forum: http://forums.opensuse.org/forumdisplay.php/687-Soapbox > > How about, instead, you stop being a censorious bastard? > Again, I am not censoring anything. And people have been asked by the list admin not to use derogatory language or name calling on this list. If you have a specific problem please let us know which version of openSUSE you are using and what the problem is so that we can try and help you get your system running. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 4

[opensuse] A better way to do mouse keys.
by Anton Aylward 22 Oct '14

22 Oct '14

I have a Logitech MX510 USB mouse. It has a number of extra buttons as well as the scroll wheel, which also acts as the 'center' button. By default it works just fine with Linux. However not all the extra button do things. And some don't do what I want. I realise I can use xbindkeys, but that's another matter. My question is this: In front of and behind the scroll wheel there are buttons that have double chevrons. Pressing them scrolls the page. GOOD. I like that. But it only scrolls 4 lines at a time. How can I make these buttons scroll more than 4 lines? How/where is the 4 lines (I think its 4, it may be 3 or 5) defined? Can I change it without recompiling? There are also a couple of thumb buttons and a button that looks like this. http://png-2.findicons.com/files/icons/1890/my_toolbar/32/copy.png Currently they don't do anything. Except by using xbindkeys is there any way I can set them to do things? I'm aware of the too in systemsettings for KDE4 but it only seems to work with keyboard keys. Is there something one can do with udev for example? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 8

Re: [opensuse] System D: Debian Fork
by Sam M. 22 Oct '14

22 Oct '14

By the way, Debian devs look to be signing off on some constitutional document on their email list to avoid a fork, so a fork looks to be a measure of last resort. On Wed, Oct 22, 2014 at 2:12 AM, Sam M. <backgroundprocess(a)gmail.com> wrote: >>Debian forks multiple times a year, while opensuse forks are very rare. >>Look here: > > http://futurist.se/gldt/wp-content/uploads/12.10/gldt1210.svg > > I see your point, but System D is such a mammoth change to how things > are done that it may be one of those cancers that warrants a fork. > Rare would mean only drastic measures cause a fork, and I'm sure many > would agree that they hate System D yet love openSUSE. And they may be > willing to take drastic measures to do what they think is the right > way to do things. The more I read and learn about about System D, the > more I learn how it's its own little monolithic operating system. > > On Wed, Oct 22, 2014 at 1:36 AM, Florian Gleixner <flo(a)redflo.de> wrote: >> >> Debian forks multiple times a year, while opensuse forks are very rare. >> Look here: >> >> http://futurist.se/gldt/wp-content/uploads/12.10/gldt1210.svg >> >> >> >> >> -- >> Florian Gleixner >> SV des Bibliotheksverbund Bayern, Verbundzentrale >> im Leibniz-Rechenzentrum >> Boltzmannstr. 1 >> 85748 Garching >> >> Tel.: 089-35831-8824 >> Fax.: 089-35831-8624 >> e-mail: gleixner(a)bib-bvb.de >> e-mail: gleixner(a)lrz.de >> -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0