October 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] package naming question
by Istvan Gabor 17 Oct '17

17 Oct '17

Hello: In rpm package names which part of the name is that can be used as package name in rpm command? What is the rule? Here are a few examples from my installed rpms list: Mesa-libGL1-9.2.5-61.13.1.x86_64 kdemultimedia3-sound-3.5.10.1-11.1.4.x86_64 cpp48-4.8.1_20130909-3.2.1.x86_64 pulseaudio-module-zeroconf-4.0.git.270.g9490a-20.1.x86_64 For example I'd like to run rpm -e <package-name>. How do I know what is the package name? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Info: Conflict between SSSD and the latest version from network:/samba:/STABLE in openSUSE Leap 42.2
by Johannes Weberhofer 17 Oct '17

17 Oct '17

Just for your info: In case you are using SSSD and the latest stable version from the samba development project on Leap 42.2, you will no longer be able to start SSSD because it core-dumps. Reason is, that SSSD can not cope with the latest libldb1-1.2.2 version that comes with samba 4.7. Rolling back samba makes the system working again. Took me some hours to find... -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] SQL Database sizes query
by Paul Groves 16 Oct '17

16 Oct '17

Hi all, A little stuck here. I have a list of database names in an array (databases) in a bash script. I want to get the size of these databases. I know that this query will return the size of all databases on the server. SELECT table_schema AS "Database name", SUM(data_length + index_length) / 1024 AS "Size (kb)" FROM information_schema.TABLES GROUP BY table_schema How can I change this query to get the size of only the databases in the array? thanks Paul -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] root in extended partition (42.3)
by listreader 16 Oct '17

16 Oct '17

Leap 423 upgraded from 422. Old drive has been in use probably since 10x. Bios. Generic code is in the MBR. I have 423 / in an extended partition. Grub2 is in 423 /. All was good. I used Yast2-bootloader module to change an option (boot loader password, if it matters). I then exited normally (OK) and yast rewrote/reinstalled the bootloader. Next boot failed at a blinking cursor. I booted with Parted Magic and found that Yast had set the extended partition itself as the boot partition, rather than / which was 2 or 3 partitions deep into the extended. I fixed that and rebooted normally. I went into Yast2-bootloader and Boot Loader Location was still correctly set there as Boot from Root Partition, even though that is not what it apparently wrote to the bootloader. So, my question is, is this expected behaviour? I don't remember this happening in previous releases. Thanks. Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] ICMP Path MTU message
by Dave Howorth 15 Oct '17

15 Oct '17

I just read a blog about packet fragmentation: https://blog.cloudflare.com/ip-fragmentation-is-broken/ And then I ran the test they link to at: http://icmpcheck.popcount.org/ The first test timed out, saying: "The request timed out. Looks like the ICMP Path MTU message was not delivered to you." The second test passed, saying: "All good! IP fragments were successfully delivered to your host." To investigate the failure of the first test, I started tcpdump and reran the test. The test gave the same result (good, I suppose) and tcpdump said: acer-suse:~ # tcpdump -ni any icmp or icmp6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 17:14:00.320873 IP 139.162.188.91 > 192.168.1.72: ICMP 139.162.188.91 unreachable - need to frag (mtu 905), length 136 17:14:00.332740 IP 139.162.188.91 > 192.168.1.72: ICMP 139.162.188.91 unreachable - need to frag (mtu 905), length 136 17:14:00.344596 IP 139.162.188.91 > 192.168.1.72: ICMP 139.162.188.91 unreachable - need to frag (mtu 905), length 136 ^C 3 packets captured 3 packets received by filter 0 packets dropped by kernel I'm no tcpdump expert but it looks to me that it is saying that it did receive three ICMP Path MTU messages. Is that correct and is anybody able to explain what's going on? (hopefully will save me hours of RT-wrong-FM :) TIA, Dave PS I spent all this morning investigating why I'd lost network connection until I discovered an intermediate network switch that my wife had accidently turned off :( Perhaps I should have bought managed switches! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] bug warning from kernel in dmesg. Worth reporting?
by stakanov 15 Oct '17

15 Oct '17

I have occasional crashes when changing with alt-ctl-tty the sessions. Up to now I have no real clue why. The spontaneous crashes using kmails are gone it seems after the latest bugfix. But I do get a bug warning from kernel. If somebody can understand about what it complains, I would be delighted to hear what the issue is and if I should or should not report it. [ 0.000000] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/ Pm1aControlBlock: 16/32 (20150930/tbfadt-623) [ 0.000000] ACPI BIOS Warning (bug): Invalid length for FADT/ Pm1aControlBlock: 32, using default 16 (20150930/tbfadt-704) Other ACPI warnings (but not claiming a bug) are: [ 19.623856] ACPI Warning: SystemIO range 0x0000000000001028-0x000000000000102F conflicts with OpRegion 0x0000000000001000-0x000000000000107F (\_SB_.PCI0.LPC_.PMIO) (20150930/ utaddress-254) [ 19.623860] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.623868] ACPI Warning: SystemIO range 0x00000000000011C0-0x00000000000011CF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\_SB_.PCI0.LPC_.LPIO) (20150930/ utaddress-254) [ 19.623869] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.623871] ACPI Warning: SystemIO range 0x00000000000011B0-0x00000000000011BF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\_SB_.PCI0.LPC_.LPIO) (20150930/ utaddress-254) [ 19.623877] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.623878] ACPI Warning: [ 19.623882] SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\_SB_.PCI0.LPC_.LPIO) (20150930/utaddress-254) [ 19.623883] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.623885] lpc_ich: Resource conflict(s) found affecting gpio_ich Could these be responsible for these "black screens" after tty changing? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Ifconfig - wrong IPv6 address type
by James Knott 13 Oct '17

13 Oct '17

I just noticed a minor issue. I just used ifconfig to display interface addresses and got the following: eth0 Link encap:Ethernet HWaddr F0:DE:F1:8C:DC:99 inet addr:172.16.4.100 Bcast:172.16.4.255 Mask:255.255.255.0 inet6 addr: fd48:1a37:2160:4:f2de:f1ff:fe8c:dc99/128 Scope:Global inet6 addr: fe80::f2de:f1ff:fe8c:dc99/64 Scope:Link The first IPv6 address is a type known as a Unique Local Address (ULA), which is used in a manner similar to IPv4 RFC 1918 addresses. However, despite this, ifconfig shows it's scope as global. A global address is a public address reachable from the Internet. ULA addresses are not. Shouldn't ifconfig show the proper scope? The same applies to the ip command. However, the link local and global addresses show the correct scope. ULA addresses are in the range of fc::/7. This is with OpenSUSE 42.3. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Tab window section in XFCE4 terminal too large
by Carlos E. R. 13 Oct '17

13 Oct '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I updated XFCE to the one in X11:XFCE repo, version 4.12.1, I think. I wanted the new Pulse Audio Panel Plugin. Everything is nice, except that the TAB area in the Terminal is too large, compared to the menu area, and I don't see if this can be adjusted or is coded. I tried many settings, didn't see any change. See attached photo, if it passes through, to see my meaning. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlngr4QACgkQtTMYHG2NR9XN4ACdEmFbEOHY6tWR9VLoqtWRwsXj 1+QAn2EObUtiuNljElktIiD/Sn7RYpcB =rU4R -----END PGP SIGNATURE-----

2 2

[opensuse] Install unsigned packages with Zypper
by Bjoern Voigt 12 Oct '17

12 Oct '17

I usually use Zypper also to install foreign RPM packages, among other things it resolves dependencies. Unfortunately since some weeks, I have to confirm each unsigned package with "i" (ignore). The useful switches --gpgcheck-allow-unsigned (Short hand for --gpgcheck-allow-unsigned-repo --gpgcheck-allow-unsigned-package) are only available for the actions addrepo|ar and modifyrepo|mr. Is there a work-around or should I file a feature request? # zypper in $(find LibreOffice_5.4.2.2_Linux_x86-64_rpm* -name '*.rpm') [...] 55 packages to reinstall. Overall download size: 293.6 MiB. Already cached: 6.2 MiB. No additional space will be used or freed after the operation. Continue? [y/n/...? shows all options] (y): y In cache libreoffice5.4-freedesktop-menus-5.4.2-2.noarch.rpm (1/55), 6.2 MiB ( 30.1 MiB unpacked) Retrieving package libreoffice5.4-ure-5.4.2.2-2.x86_64 (2/55), 14.7 MiB ( 39.4 MiB unpacked) libreoffice5.4-ure-5.4.2.2-2.x86_64.rpm: Package is not signed! libreoffice5.4-ure-5.4.2.2-2.x86_64 (Plain RPM files cache): Signature verification failed [6-File is unsigned] Abort, retry, ignore? [a/r/i] (a): i Retrieving package libobasis5.4-core-5.4.2.2-2.x86_64 (3/55), 115.6 MiB (358.3 MiB unpacked) libobasis5.4-core-5.4.2.2-2.x86_64.rpm: Package is not signed! libobasis5.4-core-5.4.2.2-2.x86_64 (Plain RPM files cache): Signature verification failed [6-File is unsigned] Abort, retry, ignore? [a/r/i] (a): ? No help available for this prompt. [a/r/i] (a): a Problem occurred during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint. Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] bluetooth mouse
by jdd＠dodin.org 12 Oct '17

12 Oct '17

-> what may I do to recover my mouse? I'm not sure what was the real solution, because I tried too many things, but now it - almost - works If I get it correctly, for the device to be detected, it needs to come after the wifi is, or something similar. so after the start, if BT don't works, systemctl restart bluetooth.service rfkill unblock bluetooth should make the bluetooth to be actionable in the widget that said, at some time in the configuration, I was asked for the root passwd to continue and since then at boot I have to give root passwd in a notification windows to get bluetooth. This is a bit odd, so is there a way to avoid this? I wonder if blacklisting the bluetooth could make the system work, but I fear to try because I don't want to fix a working system :-( thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1