August 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] leap422 - having trouble not patching firefox
by Per Jessen 09 Aug '17

09 Aug '17

We're thinking of trying out leap422 in the office, for real. Still slightly limited given a couple of show-stoppers, but I thought I would give it a go and see how far I get. However, I want to keep the current firefox (50.0-39.2) because it doesn't suffer from this issue: https://bugzilla.opensuse.org/show_bug.cgi?id=1011196 "incorrect rendering of option with css class". So I locked "MozillaFirefox". Running zypper patch gives me two problems: Resolving package dependencies... 2 Problems: Problem: patch:openSUSE-2016-1392-1.noarch conflicts with MozillaFirefox.x86_64 < 50.0.2-42.2 provided by MozillaFirefox-50.0-39.2.x86_64 Problem: MozillaFirefox-translations-common-52.2-57.12.2.x86_64 requires MozillaFirefox = 52.2, but this requirement cannot be provided Problem#1 is easily solved by option 1, don't install. Problem#2: Problem: MozillaFirefox-translations-common-52.2-57.12.2.x86_64 requires MozillaFirefox = 52.2, but this requirement cannot be provided uninstallable providers: MozillaFirefox-52.2-57.12.2.x86_6 [repo-update] Solution 1: Following actions will be done: do not install patch:openSUSE-2017-712-1.noarch remove lock to allow installation of MozillaFirefox-52.1.1-57.9.1.x86_64[repo-update] Solution 2: deinstallation of MozillaFirefox-translations-common-50.0-39.2.x86_64 Solution 3: remove lock to allow installation of MozillaFirefox-52.2-57.12.2.x86_64[repo-update] Solution 4: break MozillaFirefox-translations-common-52.2-57.12.2.x86_64 by ignoring some of its dependencies Question: Shouldn't there be a Solution#5: do not install MozillaFirefox-translations-common-52.2-57.12.2.x86_64 ? -- Per Jessen, Zürich (26.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 32

[opensuse] shutdown: "command failed"
by Daniel Bauer 09 Aug '17

09 Aug '17

Hi, When I shutdown my 42.3, at the end of all the shutdown messages the are about 20 to 30 lines telling "command failed", before the machine turns off. I have this since I upgraded from 42.1 to 42.3, but never have seen it before. I wonder if this is just as "cosmetic" thing I can ignore or if I should check something. If so: where and what? :-) Thanks for hints. Daniel -- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Buildservice - 'Submit' to Maintenance?
by David C. Rankin 09 Aug '17

09 Aug '17

All, After patching gtk2 to correct the gtkrecentchooserdefault.c error corrected in https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de…, when choosing submit, I get: Unable to submit: The target project openSUSE:Leap:42.2:Update is a maintenance release project, a submit self is not possible, please use the maintenance workflow instead. What does this mean? How do I submit the patch for consideration? -- 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 21

[opensuse] Nvidia rpm package checksum error
by Carlos E. R. 09 Aug '17

09 Aug '17

Hi, Today I ran an update in Leap 42.2. This time I decided to also update the NVidia rpm packages, and all of them reported checksum errors. I attach a photo of the error yast gave - it did not allow me to copy paste the text. Another user in the Spanish mail list reported the same problem, using zypper this time; I'll paste the error he got: +++------------------------- ... Retrieving: nvidia-gfxG03-kmp-default-340.102_k4.4.27_2-18.1.x86_64.rpm .........................[done] Warning: Digest verification failed for file 'nvidia-gfxG03-kmp-default-340.102_k4.4.27_2-18.1.x86_64.rpm' [/var/cache/zypp/packages/download.nvidia.com-leap/x86_64/nvidia-gfxG03-kmp-default-340.102_k4.4.27_2-18.1.x86_64.rpm] expected d9844df9a3ffa3c110d16c447293a633ca4e71013c52e3c14011145742f1bfa0 but got cef17e27677f0e66bd0b00d48f66d94479699fd4aebe1929d62d2425457715b9 Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. However if you made certain that the file with checksum 'cef1..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file. Unblock or discard? [cef1/...? shows all options] (discard): -------------------------++- However, the packages do pass the gpg --checksig test: Telcontar:/var/cache/zypp/packages/download.nvidia.com-leap/x86_64 # rpm --checksig nvidia-gfxG03-kmp-default-340.102_k4.4.27_2-18.1.x86_64.rpm nvidia-uvm-gfxG03-kmp-default-340.102_k4.4.27_2-18.1.x86_64.rpm nvidia-glG03-340.102-18.1.x86_64.rpm nvidia-computeG03-340.102-18.1.x86_64.rpm x11-video-nvidiaG03-340.102-18.1.x86_64.rpm nvidia-gfxG03-kmp-default-340.102_k4.4.27_2-18.1.x86_64.rpm: (sha1) dsa sha1 md5 gpg OK nvidia-uvm-gfxG03-kmp-default-340.102_k4.4.27_2-18.1.x86_64.rpm: (sha1) dsa sha1 md5 gpg OK nvidia-glG03-340.102-18.1.x86_64.rpm: (sha1) dsa sha1 md5 gpg OK nvidia-computeG03-340.102-18.1.x86_64.rpm: (sha1) dsa sha1 md5 gpg OK x11-video-nvidiaG03-340.102-18.1.x86_64.rpm: (sha1) dsa sha1 md5 gpg OK Telcontar:/var/cache/zypp/packages/download.nvidia.com-leap/x86_64 # So I decided to go ahead and install. Ideas? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

2 2

[opensuse] Security trust relationship not present
by Mikhail Ramendik 08 Aug '17

08 Aug '17

Hello, I have Leap 42.2 (want to wait a bit with the upgrade). The software update app says there is a failure - "Security trust relationship not present". This happened once before but resolved after a zypper up - now it's back. Is there a way to fix the problem permanently? -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 7

[opensuse] Windows 10 will let everyone run Linux inside Windows following Fall Creators Update - TechRepublic
by James Knott 08 Aug '17

08 Aug '17

Microsoft has certainly changed, since Bill & Steve left! Both Leap 42 and SUSE Linux Enterprise Server will be available. http://www.techrepublic.com/article/windows-10-will-let-everyone-run-linux-… -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

11 21

[opensuse] curious wlan prob on toshiba satellite s55-c5274
by Patrick Shanahan 08 Aug '17

08 Aug '17

has following wireless chip/software: 02: PCI 700.0: 0282 WLAN controller [Created at pci.378] Unique ID: eS2I.0LuFraIuP2D Parent ID: hoOk.nRJfFo0MDI2 SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:07:00.0 SysFS BusID: 0000:07:00.0 Hardware Class: network Model: "Intel Dual Band Wireless-AC 7265" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x095a "Wireless 7265" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x5010 "Dual Band Wireless-AC 7265" Revision: 0x61 Driver: "iwlwifi" Driver Modules: "iwlwifi" Device File: wlp7s0 Features: WLAN Memory Range: 0xb3300000-0xb3301fff (rw,non-prefetchable) IRQ: 52 (no events) HW Address: dc:53:60:be:2c:b5 Permanent HW Address: dc:53:60:be:2c:b5 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v00008086d0000095Asv00008086sd00005010bc02sc80i00" Driver Info #0: Driver Status: iwlwifi is active Driver Activation Cmd: "modprobe iwlwifi" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #9 (PCI bridge) I sporadically loose wireless connection to local wired boxes but not to external (outside router) or local wireless boxes. I cannot attribute a cause or condition which results in this, but I can boot to windows 10 and observe same condition. but I can use windows network repair and regain full access to all local devices. I see the same with static or dhcp assigned address, and with a belkin usb dongle. but the dongle will see local wired connections for a short period, several minutes, and then fail to access wired local addresses. it does access outside and local wireless devices. open to any and all suggestions. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 15

[opensuse] Re: [opensuse-factory] hylafax+ 5.5.8 localized Email notification chops german Umlauts
by Carlos E. R. 07 Aug '17

07 Aug '17

On 2017-08-07 19:33, Axel Braun wrote: > Am Freitag, 4. August 2017, 19:43:20 CEST schrieb Carlos E. R.: Remember to post back to the list, not in private. >> The hyafax script is using those settings? Not UTF-8? Then that may be >> the problem. >> >> What is using /tmp/examine_me.eml? iso-8859-1 or UTF-8? The mail should >> be sent using the same thing. > > ...for the elements transmitted, iso-8859-1 and UTF-8 should give the same > result No, impossible. The first one is one byte only per char, the second is variable multibyte. You can match a small subset of the second with the first. If Hylafax produces the text in utf-8, and the mail says it is iso, you get that error you see. >> Another idea. If your command using "mail" was correct, you could edit >> the hylafax script to use mail instead. >> >> echo "--$MIMEBOUNDARY--" >> ) 2>$ERRORSTO | $SENDMAIL -f$FROMADDR -oi -t >> >> Replace the sendmail call with a "mail" call, which will need changing >> options. For instance: > > I tried various options including hardcoding > /usr/bin/mailx -r $FROMADDR > but none worked Well, it need work, replacing one with the other is not direct. You have to examine the /tmp/examine_me.eml file, see if it is suitable for "mail" command, perhaps change it by changing the code that generates it... Maybe you only need it generating the proper "Content-Type" header, or recode the text to match, as Bernhard says. > On the malformatted email, the postfix log output looks OK Postfix doesn't alter or translate the mail. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

1 0

[opensuse] WinTV HVR 1110 No Picture (sort of)
by Paul Groves 07 Aug '17

07 Aug '17

Hi, I have a Win TV HVR 1110 PCI Hybrid Analogue/Digital Tuner and I am having some trouble. I spent some time wondering why I could not get any picture and video. I had to install the linux-firmware-nonfree package. This has fixed it and I can now hear the audio from the stereo phono input but no picture (using VLC player). So I then put a VHS tape in the VCR (connected to S-video). It played audio but no picture. Same problem via composite. So I installed TV Time (as recommended by a quick internet search) and I can play the s-video and composite ports with a picture but it is very very grainy. This is not the case when I connect the VCR to the TV. The picture is perfect. So I then tuned into freeview using VLC only to find no picture but sound working fine. I tried and all the channels are shown under Media > Programme. All channels on all of our local muxes play audio but no picture. Just a black screen. So, why does TV time show a picture but VLC does not? Is there a setting I have to change? Why is the picture in TV Time so grainy? I tried setting to PAL and NTSC but it made no difference. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] Removing kernels via zypper or /sbin/purge-kernels
by Daniel Pecka 07 Aug '17

07 Aug '17

Hello folks, I've found problem with /sbin/purge-kernels working kinda unreliably in my situation, I have following kernels: # rpm -qa kernel-\* | sort kernel-default-4.11.8-1.1.g42bd7a0.x86_64 kernel-default-4.12.3-4.1.g76ea0ca.x86_64 kernel-default-4.12.4-1.1.g2a27bf2.x86_64 kernel-default-devel-4.11.8-1.1.g42bd7a0.x86_64 kernel-default-devel-4.12.3-4.1.g76ea0ca.x86_64 kernel-default-devel-4.12.4-1.1.g2a27bf2.x86_64 kernel-devel-4.11.8-1.1.g42bd7a0.noarch kernel-devel-4.12.3-4.1.g76ea0ca.noarch kernel-devel-4.12.3-5.1.g93ed5e8.noarch kernel-devel-4.12.4-1.1.g2a27bf2.noarch kernel-firmware-20170622-35.1.noarch kernel-macros-4.12.4-1.1.g2a27bf2.noarch kernel-source-4.12.3-4.1.g76ea0ca.noarch kernel-source-4.12.3-5.1.g93ed5e8.noarch kernel-source-4.12.4-1.1.g2a27bf2.noarch kernel-source-vanilla-4.13.rc3.102.g26c5ceb-1.1.ga6978f6.noarch kernel-source-vanilla-4.13.rc3.304.gef9ca02-1.1.gc7384e8.noarch kernel-syms-4.11.8-1.1.g42bd7a0.x86_64 kernel-syms-4.12.3-4.1.g76ea0ca.x86_64 kernel-syms-4.12.4-1.1.g2a27bf2.x86_64 kernel-vanilla-4.13.rc3.102.g26c5ceb-1.1.ga6978f6.x86_64 kernel-vanilla-4.13.rc3.304.gef9ca02-1.1.gc7384e8.x86_64 kernel-vanilla-devel-4.13.rc3.102.g26c5ceb-1.1.ga6978f6.x86_64 kernel-vanilla-devel-4.13.rc3.304.gef9ca02-1.1.gc7384e8.x86_64 # ls -l /boot/vmlinuz-4* -rw-r--r-- 1 root root 7237424 Jun 29 19:31 /boot/vmlinuz-4.11.8-1.g42bd7a0-default -rw-r--r-- 1 root root 7872304 Jul 25 13:16 /boot/vmlinuz-4.12.3-4.g76ea0ca-default -rw-r--r-- 1 root root 7872304 Jul 28 13:48 /boot/vmlinuz-4.12.4-1.g2a27bf2-default -rw-r--r-- 1 root root 6831408 Aug 3 10:29 /boot/vmlinuz-4.13.0-rc3-102-g26c5ceb-1.ga6978f6-vanilla -rw-r--r-- 1 root root 6831408 Aug 6 10:42 /boot/vmlinuz-4.13.0-rc3-304-gef9ca02-1.gc7384e8-vanilla but /sbin/purge-kernels thinks there's nothing to do .. I wanted to keep for safe following kernels via zypp.conf # grep ^multiversion\\\.kernels /etc/zypp/zypp.conf multiversion.kernels = latest,latest-1,running,4.11.8-1.g42bd7a0-default,4.11.8-1.g42bd7a0,4.13.rc3.102.g26c5ceb-1.1.ga6978f6,4.13.0-rc3-102-g26c5ceb-1.ga6978f6-vanilla any/all attempts to remove 4.12.x kernel (from kernel/stable) results in following: # rpm -qa kernel\* | perl -ne 'print if m@(4\.12\.4-1\.1\.g2a27bf2|4\.12\.3-4\.1\.g76ea0ca)@' | xargs zypper rm Loading repository data... Reading installed packages... Resolving package dependencies... Problem: kernel-devel-4.11.8-1.1.g42bd7a0.noarch requires kernel-macros, but this requirement cannot be provided deleted providers: kernel-macros-4.12.4-1.1.g2a27bf2.noarch Solution 1: Following actions will be done: remove lock to allow removal of kernel-devel-4.11.8-1.1.g42bd7a0.noarch remove lock to allow removal of kernel-default-devel-4.11.8-1.1.g42bd7a0.x86_64 remove lock to allow removal of kernel-syms-4.11.8-1.1.g42bd7a0.x86_64 Solution 2: keep kernel-macros-4.12.4-1.1.g2a27bf2.noarch Solution 3: break kernel-devel-4.11.8-1.1.g42bd7a0.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c): 2 Resolving dependencies... Resolving package dependencies... The following 14 packages are going to be REMOVED: kernel-default-4.12.3-4.1.g76ea0ca kernel-default-4.12.4-1.1.g2a27bf2 kernel-default-devel-4.12.3-4.1.g76ea0ca kernel-default-devel-4.12.4-1.1.g2a27bf2 kernel-devel-4.12.3-4.1.g76ea0ca kernel-devel-4.12.4-1.1.g2a27bf2 kernel-source-4.12.3-4.1.g76ea0ca kernel-source-4.12.4-1.1.g2a27bf2 kernel-syms-4.12.3-4.1.g76ea0ca kernel-syms-4.12.4-1.1.g2a27bf2 virtualbox virtualbox-host-kmp-default virtualbox-host-source virtualbox-qt 14 packages to remove. After the operation, 2.1 GiB will be freed. Continue? [y/n/...? shows all options] (y): n Is there some supported resolution for this ? - should I report bug against /sbin/purge-kernels ? - I have to keep at least one package with kernel-defaults because several other packages wants it so that's why I have there at least locked 4.11.8 that works (compared to 4.12.x in my hw). - I'm currently happy with kernel-vanilla so I want to stick with that regards, d -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1