May 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Re: Mix NewtorkManager and traditional ethernet configuration
by Carlos E. R. 03 Jun '15

03 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-05-22 22:23, Roger Oberholtzer wrote: > > > On Friday, May 22, 2015, Carlos E. R. wrote: > > In NetworkManager you can have connections that start on system > start, "shared" for all users, that require the root password to > change. But the user can add/remove/configure his own connections. > > is that the case in 13.1? if so, I will have to check this out. I > don't recall the root password thing. I recall that you could > change everything. Yes, absolutely. The user can connect and disconnect, but for configuration it requires the root password. And it starts automatically on boot. 13.2 I haven't tested. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlVfrYIACgkQja8UbcUWM1yRCwD+L+et7gwUSRW99Bf4i7CPAbvu wTYQ4mrJf/+S2i5lWlsA/0RvaqtM6VK2XxKEgwWw44vcZJWbk03YSCuk+oeIs1Qt =FMK7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 9

[opensuse] vfat timestamp again
by Istvan Gabor 02 Jun '15

02 Jun '15

Hello: I took photos with a digital camera which saves the photos to a vfat formatted sdcard. The camera's clock is set correctly according to my local time. When I mount the vfat filesystem in openSUSE 13.2 using a card reader, the timestamps the photos are 2 hours ahead. (OpenSUSE 13.2 system time is set to UTC.) Eg. timestamp shows 18:20 instead of 16:20, the time when the photo was actually taken. I find this behavior - again - unacceptable, ridiculous, and annoying. Isn't there any option with which this stupid behavior could be changed so that the filesystem times would be interpreted as the user's local time? Is this so big expectation? I would like to archive the images, and therefore the timestamps applied at mounting will be preserved. I don't want to archive wrong timestamps, because it is important when the photos were taken. I know I can look at metainfo, but it is not real a solution. What I want is changing the timestamps applied when the filesystem is mounted. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 38

Re: [opensuse] raid use case
by Linda Walsh 02 Jun '15

02 Jun '15

Greg Freemyer wrote: > Depends... you can have a background task run and read through the > entire > disk. If anything comes up as different between the two copies, you'd > know -- at least that's what my lsi card does about once a week.... --- > > > I don't know if your also card does this, but mdraid does better than that. > > If the scan detects a media error, mdraid recreates the data from via > raid1/5/6 redundant raid members and re-writes the bad sector. The > drive itself should use the rewrite of a known bad sector to force a > sector reallocate, thus the member drive is restored from silently > degraded to "perfect" in short order. ---- Practical issue: you can't do RAID5 or RAID6 with 2 disks, which is what I thought the original poster had. Secondly when you remap sectors, it slows down the drive -- so that drive won't be within 'tolerance' for hardware RAID, so you'd need to replace the drive most likely (if you had a hot spare in the machine, it could immediately start a rebuild). Third -- RAID1 is safer than RAID6 for the same # of total disks in all cases w/same # of even spindles (need an even number for RAID1, obviously). If you only have 3 disks total, you could probably do RAID6 and it would be safer, but 1 data + 2 parity...ouch. But the 1st minimum size demonstrates the problem (and it gets worse w/more disks). With min number of spindles that will work for both: 4, RAID6 would have 2 data disks and 2 parity. while raid10 would have 2 data disks and 2 mirrors. If your failure rate is 'x', then the no-fail rate is 1-x per disk. In the raid 6, if any of the other 3 disks fail (in addition to 1st failure), the raid is toast. With a RAID10, there is only 1 disk that can cause the whole array to fail (the mirror of the one that went bad). If you get a 2nd fail on another pair, you can still rebuild. With only 1 disk "exposed" on RAID10, the % chance of the whole RAID failing is the %chance of 1 disk failing. However, w/raid6, there are 3 disks that are critical to rebuild the bad one -- their "no fail case is (1 - x)**3. I.e. say it was a 1% fail, 99% nofail. In RAID10 chances of whole RAID being safe would be 99% (the no fail rate for the 1 partner of the one that failed). In RAID 6, though it's .99**3 -- or .970. In that best case RAID6 has 3x the 'total fail' chances as the RAID10's. If you have 8 total spindles (6 data/2parity for raid6 vs. 4data+4mirror for raid10), then 1 disk goes. For RAID10, the total fail case only happens if the failed-drive's pair go's so it's still 99% chance of not failing. Vs. RAID6, .99**7 == .932) -- or a almost a 7% chance of a total fail vs. RAID10's 1% chance. The next point up is moving from 512-byte sect disks to 4k... It takes less space for a more power ECC on 4k than the one on 512: (from a Hitachi brief:) .... The second benefit is that a larger and more powerful error correction code (ECC) can be utilized, providing better integrity of user data.... > Only if you are using media scrubbing routinely can you have confidence > that the member drives go from "perfect" to failed without a silently > degraded state in the middle. --- LSI defaults them to once/week. > > When TB size drives first hit the market, a lot of raid5 rebuilds were > failing due to the silent bad sector degradation. That's when the > community started strongly urging everyone to either use media scrubbing > or raid-6. (Raid 6 has 2 redundant drives so it can rebuild a failed > member drive even in the presence of media errors on the surviving members). ---- But w/raid6 after 1 drive fails the chances of non-failure have to be multiplied by # drives left. With RAID10, it's a constant. (Combinatorics) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 83

[opensuse] network manager only connects after 2nd or 3rd attempt
by Daniel Bauer 02 Jun '15

02 Jun '15

Hello, on my laptop with OS 13.2, after booting the network manager shows that it is connected to my wifi, but there is no connection to the internet, i can't even get to the router (192.168...) Then I click on disconnect and then on connect again and it usually works. Sometimes I need a third or a fourth attempt. It looks to me that if "connecting" takes a longer time, then the connection does not work, although shown as connected, and when it goes fast, it works... It does not depend on the distance to the antenna. What could be the reason for this? Where can I search and for what should I look? thanks for 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

8 19

[opensuse] grep needs to be updated to 2.21
by Linda Walsh 01 Jun '15

01 Jun '15

I was using grep to scan names of files in RPM's. Some of the names are in latin1 instead of UTF-8, and the version of grep installed with 13.2 (2.20), gives messages like this: *** file = libvtkUtilitiesPythonInitializer-pv4.2.so.1 grep: invalid UTF-8 byte sequence in input ----- *** file = libvtkPVClientServerCoreCore-pv4.2.so.1 grep: invalid UTF-8 byte sequence in input ----- the 'file' part is my script -- name of the file I am looking for, but grep aborts because of the invalid UTF-8 bytes in the "rpm -ql" output of some package or another. I D/L their current version (2.21) and verified it is fixed; output comes up now, like: *** file = libvtkUtilitiesPythonInitializer-pv4.2.so.1 /home/rpms/13.2/repo/oss/suse/x86_64/paraview-4.2.0-1.2.x86_64.rpm:/usr/lib64/paraview/libvtkUtilitiesPythonInitializer-pv4.2.so.1 /home/rpms/13.2/repo/oss/x64+noarch/paraview-4.2.0-1.2.x86_64.rpm:/usr/lib64/paraview/libvtkUtilitiesPythonInitializer-pv4.2.so.1 ----- *** file = libvtkPVClientServerCoreCore-pv4.2.so.1 /home/rpms/13.2/repo/oss/suse/x86_64/paraview-4.2.0-1.2.x86_64.rpm:/usr/lib64/paraview/libvtkPVClientServerCoreCore-pv4.2.so.1 /home/rpms/13.2/repo/oss/x64+noarch/paraview-4.2.0-1.2.x86_64.rpm:/usr/lib64/paraview/libvtkPVClientServerCoreCore-pv4.2.so.1 I have dumped the names of all the files of all the rpms in 13.2, so if something is "looking" for one of those files, I can scan the distribution for the file. The bug only appears if you use the "-P" option of grep -- which I used. The grep maintainers were able to reproduce my problem with an older version... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Laptop Fn-Keys not working on SuSE 13.1
by MarkusGMX 31 May '15

31 May '15

Hello, on my old Samsung R70 the hardware keys (brightness up and down, volume up down, laptop LCD on/off and so on) where working on 10.3 and 12.1. 13.1 seems to suppress the keys or is missing important stuff whereas GRUB still lets me decrease or increase LCD brightness with Fn-up and Fn-down. Looking at https://forums.opensuse.org/showthread.php/493519-Unable-to-set-global-shor…! I found out that /sys/devices/platform/samsung/leds is missing. I was not able to find that somewhere. So this page does not help. A manual of that laptop is here: http://downloadcenter.samsung.com/content/UM/200705/20070514091526750_Oslo_… andf here in German: http://downloadcenter.samsung.com/content/UM/200704/20070416160633062_Oslo_… The keys are also described here: "- Fn+F1 - Help --> it works! - Fn+F2 - Battery icon --> no funktion - Fn+F3 - euro-symbol --> doesn't insert the euro sign - Fn+F4 - display switch --> not tested - Fn+F5 - backlight on/off --> no funktion - Fn+F6 - mute --> it works! - Fn+F7 - Samsung MagicDoctor (Windows) --> no funktion - Fn+F8 - easy speedup manager (Windows) --> no funktion - Fn+F9 - WLAN on/off --> no funktion - Fn+F10 - touchpad on/off --> it works! - Fn+F11 - numlock --> it works! - Fn+F12 - scroll lock --> no funktion - WWW key --> nautilus or if open startpage in browser - it works! (no hanging) - backlight keys --> indicator comes up without taken effect + no reaction of keyboard - volume keys --> it works" [ https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/219116 ] Fn+F1 does not work for me. WLAN button does not work for me too which is very bad. WWW key = Home key works for me if e.g. firefox is already open. Everything else is the same for me as in the above description. What do I have to change in SuSE 13.1 to get these keys working again? Everything else is working with SuSE 13.1 on this quite old laptop. Thanks in advance. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Postgresql 9.4 upgrade openSUSE13.1
by Arup Rakshit 31 May '15

31 May '15

Hi, I have installed long back postgresql92, and I want to upgrade it to postgresql 9.4. But not seeing any package for that. Any help ? [arup@music_track (master)]$ zypper info postgresql94 Loading repository data... Reading installed packages... package 'postgresql94' not found. [arup@music_track (master)]$ -- ================ Regards, Arup Rakshit ================ Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. --Brian Kernighan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] Not able to send email from Gmail account using Kmail client
by Arup Rakshit 31 May '15

31 May '15

Hi, I am not able to send from Gmai account using Kmail client. Getting error : Failed to transport message. Your SMTP server does not support PLAIN. Choose a different authentication method. The server responded: 5.7.8 Username and Password not accepted. Learn more at 5.7.8 http://support.google.com/mail/bin/answer.py?answer=14257 hj11sm11374952pbd.33 - gsmtp Please let me know if you need any more information. Regards, Arup -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 8

[opensuse] disk speed
by jdd 31 May '15

31 May '15

I know of some CLI like hdparm, but is there on iopenSUSE an utility like the ubuntu one? http://askubuntu.com/questions/69932/is-there-an-sd-card-diagnostic-utility ubuntu one name is so generic, it's impossible to google for it :-( thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Keyboard slow after sleep
by Paul Groves 31 May '15

31 May '15

I have had an issue since 12.2 (Currently on 13.2) whereby I put my computer to sleep (usually accidentally when changing volume) and when I wake it up the keyboard is incredibly slow to respond. When it is woken up the keyboard will not recognise mutliple key presses and if I type normally it misses half the letters because its response time is so long. I can work around this by unplugging and re-connecting the keyboard's USB and then it works fine again. I can replicate the issue every time. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 7