June 2019 - openSUSE Support - openSUSE Mailing Lists

[opensuse-support] Webcam not found on latest Tumbleweed
by Christian Boltz 13 Jun '19

13 Jun '19

Hello, with latest Tumbleweed, my webcam (built-in in my Tuxedo laptop) no longer works - both Chromium and Webcamoid say "no webcam found". About a month ago (2019-05-14), the webcam still worked. I didn't need it since then, therefore I can't give a smaller timeframe. Is this a known problem/regression, or do I need to dig for possible reasons? Regards, Christian Boltz -- Ich mag die Entwickler, die denken so herrlich pervers. Wäre mir allerdings lieber, wenn sie nicht auch so programmieren würden ;) [Werner Flamme in opensuse-de] -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 6

[opensuse-support] Leap 15.1 Problem with yast2-alternatives
by JigsTheorem 12 Jun '19

12 Jun '19

Hi all Installed 15.1 with Plasma and SDDM Display Manager. I am trying to replace SDDM with KDM [as a staging post towards using XDMCP - yes, I know this is BAD, but that is not an issue for me]. yast2-alternatives successfully makes the change to KDM, but also changes me from Plasma to ICEWM. HOWEVER, when doing this, yast2-alternatives shows * default-displaymanager = ~/kdm * default-session.desktop = ~/plasma5.desktop If I then change back to SDDM, I do get Plasma. As a workaround, I could accept ICEWM, but the dolphin icons are missing, so I am regarding this as a yast2-alternatives issue. So [1] Generally, this has a look to me of a bug in yast2-alternatives, although to be entirely fair, it looks to me more like a problem with external dependencies towards the systemd config files. Should I be raising this as a bug? [nb, I probably can't because the validation email for site signup is broken] And [2] where should I look to stop KDM setting the desktop to ICEWM regardless of yast2-alternatives? Regards JT -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 4

[opensuse-support] LG Gram 17"
by Jordi Relats 11 Jun '19

11 Jun '19

Hello All, After install Opesuse Tumbleweed on a LG Gram 17", I had to use pci=noacpi, but now the touchpad don't work. In theory in the new Kernels has better suport of ths laptop, but i dont know how to configure it. Any one can help me? Jordi Relats -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 7

[opensuse-support] Tumbleweed - Clementine always crashing
by mh＠mike.franken.de 10 Jun '19

10 Jun '19

Hi *, any idea, why Clementine on my Tumbleweed machine is crashing always? It runs from a few seconds to one or two hours, but then it is crashing in 10 of 10 cases. No crash information is shown and I find no message, that points to the reason of the crash 8-< TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 3

[opensuse-support] NetworkManager requires root permissions
by Patrick Shanahan 10 Jun '19

10 Jun '19

new install of Tw using NetworkManager. starting/stopping/changing network requires root permissions. I cannot even remotely restart the subj computer w/o physical access to provide root password. none of my other Tw installs with NM require this. how to change? found discussion on google but nothing that appears relevant. polkit configs are the same on all Tw boxes. wtf! 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-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 8

[opensuse-support] partition mounted && unmounted during boot
by Daniele 06 Jun '19

06 Jun '19

Hi guys, since snapshot 529, I have a problem with one partition. my setup: SDA with /, /home and swap SDB with 2 unused partition and one mounted under /local this since 2 years. After the upgrade I get this: > dmesg | grep XFS [ 5.126978] SGI XFS with ACLs, security attributes, no debug enabled [ 5.128135] XFS (sda2): Mounting V5 Filesystem [ 5.128230] XFS (sdb5): Mounting V5 Filesystem [ 5.149536] XFS (sda2): Ending clean mount [ 5.255220] XFS (sdb5): Ending clean mount [ 6.182167] XFS (sdb5): Unmounting Filesystem ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Why ?? My fstab (btrfs subvolumes removed just for this post): UUID=565e589b-71ff-4d5a-b289-59b29f66c181 / btrfs defaults 0 0 UUID=44dccc07-9527-4ea7-8e15-5dc63486a9cd /local xfs defaults 0 0 UUID=99c78e04-da7c-4291-9944-1e11510d8af8 /home xfs defaults 0 0 UUID=71043c82-a659-4e7b-8a2e-0a5645c424f7 swap swap defaults 0 0 I can mount the partition with Dolphin, also mount -a "fix" the problem till the next reboot. I also checked the partition with xfs_repair (no issues at all). Any ideas ? Thanks, Daniele. -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 7

[opensuse-support] Citrix Receiver / Workspace App -> coredump in libc
by mh＠mike.franken.de 05 Jun '19

05 Jun '19

Hi *, one of the latest Tumbleweed updates broke my Citrix Workspace App. It worked up to the first week of May. After updating the system last week, Citrix stopped working. I get: ------------------------< snip snip snip >----------------------------- Code: 84 00 00 00 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 1f <c5> fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1 systemd[1]: Started Process Core Dump (PID 12705/UID 0). systemd-coredump[12706]: Process 12682 (wfica) of user 10000 dumped core. Stack trace of thread 12688: #0 0x00007fb44a755311 __strlen_avx2 (libc.so.6) #1 0x00007fb449c02d75 bio_puts (libcrypto.so.1.1) #2 0x00007fb446e261a1 doSslHandshake_internal (libproxy.so) #3 0x00007fb446e25f32 doClientHandshake (libproxy.so) #4 0x00007fb446dee358 n/a (libproxy.so) #5 0x00007fb446deedf5 n/a (libproxy.so) #6 0x00000000005b6733 n/a (wfica) #7 0x00007fb446e008a3 IPSTACKconnect (libproxy.so) #8 0x00000000004fc25a n/a (wfica) #9 0x00000000004fa6cd n/a (wfica) #10 0x00007fb4468dd7fd n/a (PDCRYPT1.DLL) #11 0x00000000004e8b25 Wd_ConnectStream (wfica) #12 0x000000000054d290 NCSbind (wfica) #13 0x000000000049ac49 n/a (wfica) #14 0x00007fb44a8b267d n/a (libglib-2.0.so.0) #15 0x00007fb44a81ffaa start_thread (libpthread.so.0) #16 0x00007fb44a6f271f __clone (libc.so.6) Stack trace of thread 12692: #0 0x00007fb44a825e05 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007fb445e2dfc3 thread_decode (ctxjpeg_fb_8.so) #2 0x00007fb44a81ffaa start_thread (libpthread.so.0) #3 0x00007fb44a6f271f __clone (libc.so.6) Stack trace of thread 12695: #0 0x00007fb44a825e05 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007fb445e2dfc3 thread_decode (ctxjpeg_fb_8.so) #2 0x00007fb44a81ffaa start_thread (libpthread.so.0) #3 0x00007fb44a6f271f __clone (libc.so.6) Stack trace of thread 12697: #0 0x00007fb44a825e05 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007fb445e2dfc3 thread_decode (ctxjpeg_fb_8.so) #2 0x00007fb44a81ffaa start_thread (libpthread.so.0) #3 0x00007fb44a6f271f __clone (libc.so.6) Stack trace of thread 12694: #0 0x00007fb44a825e05 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007fb445e2dfc3 thread_decode (ctxjpeg_fb_8.so) #2 0x00007fb44a81ffaa start_thread (libpthread.so.0) #3 0x00007fb44a6f271f __clone (libc.so.6) Stack trace of thread 12698: #0 0x00007fb44a6f2a46 epoll_wait (libc.so.6) #1 0x00000000004e2f5b n/a (wfica) #2 0x00007fb44a81ffaa start_thread (libpthread.so.0) #3 0x00007fb44a6f271f __clone (libc.so.6) Stack trace of thread 12682: #0 0x00007fb44a6e7c9f __poll (libc.so.6) #1 0x00007fb44a889d2e n/a (libglib-2.0.so.0) #2 0x00007fb44a88a0d3 g_main_loop_run (libglib-2.0.so.0) #3 0x00007fb44b076dfa gtk_main (libgtk-x11-2.0.so.0) #4 0x000000000049aed7 OldMain (wfica) #5 0x0000000000581b83 PlatAppMain (wfica) #6 0x000000000054b4ec AppMain (wfica) #7 0x000000000049820a main (wfica) #8 0x00007fb44a61bbcb __libc_start_main (libc.so.6) #9 0x0000000000498259 _start (wfica) systemd[1]: systemd-coredump(a)6-12705-0.service: Succeeded. ------------------------< snip snip snip >----------------------------- Any idea how to solve this? I already tested a few older versions of Citrix, but didn't succeed. Thx and bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 1

[opensuse-support] Possible dependency problem upon boot with wicked?
by Till Dörges 04 Jun '19

04 Jun '19

Hello all, it appears that wicked and I are not on the best possible terms. I'm now also struggling with a host that I recently upgraded to openSUSE Leap 15.1 (zypper dup). Because of changed requirements I made the SSHD listen to only one IP (/etc/ssh/sshd_config: ListenAddress 1.2.3.4). Previously the default was configured, i.e. bind to all interfaces. Additionally the external interface (eth1) which physically handles the IP 1.2.3.4 is part of a bridge. For some reason, when SSHD is started at boot time it always complains with: Jun 3 13:22:13 box sshd[2520]: error: Bind to port 22 on 1.2.3.4 failed: Cannot assign requested address. Jun 3 13:22:13 box sshd[2520]: fatal: Cannot bind any address. If I manually restart SSHD 1 minute later, everything is fine. On a different machine with a fairly similar setup I don't see any problems. To me this looks like a dependency problem. So I tried forcing SSH to start later, by copying /usr/lib/systemd/system/sshd.service to /etc/systemd/system/sshd.service and adding another unit to the 'After' line: After=network.target sys-devices-virtual-net-BRIDGE.device But that didn't work. Besides 'After=network.target' all by itself should be enough, shouldn't it? Thanks in advance and regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] wicked (auto4, dhcp4, dhcp6) timeouts/fails with static network configuration
by Till Dörges 04 Jun '19

04 Jun '19

Hello all, after doing a 'zypper dup' from openSUSE Leap 42.3 (x86_64) to openSUSE Leap 15.1 (only openSUSE Repos) wickedd-auto4.service, wickedd-dhcp4.service, wickedd-dhcp6.service enter failed status roughly 50% of the boots. Even worse sometimes network services like SSH don't start up, either. Everything was working fine under openSUSE Leap 42.3. What really puzzles me is that the entire network configuration is static and only IPv4. So why do these 3 services have to run at all? The versions used are: --- snip --- box:~ # rpm -qa | grep wick | sort libwicked-0-6-0.6.54-lp151.1.1.x86_64 wicked-0.6.54-lp151.1.1.x86_64 wicked-service-0.6.54-lp151.1.1.x86_64 --- snap --- If it works, they roughly take a minute (still, way too long): --- snip --- box:~ # systemd-analyze blame | less -S 1min 1.899s wickedd-dhcp4.service 1min 1.893s wickedd-dhcp6.service 1min 1.887s wickedd-auto4.service 5.586s wicked.service 3.322s postfix.service [...] --- snap --- If it doesn't, they run ~ 90 seconds and timeout: --- snip --- box:~ # systemd-analyze blame | less -S 1min 30.242s wickedd-dhcp4.service 1min 30.241s wickedd-dhcp6.service 1min 30.240s wickedd-auto4.service 48.125s wickedd.service 5.674s wicked.service [...] --- snap --- Upon failure I see this in /var/log/messages: --- snip --- Jun 1 01:25:18 box systemd[1]: Starting wicked AutoIPv4 supplicant service... Jun 1 01:25:18 box systemd[1]: Starting wicked DHCPv4 supplicant service... Jun 1 01:25:18 box systemd[1]: Starting wicked DHCPv6 supplicant service... Jun 1 01:26:48 box systemd[1]: wickedd-auto4.service: Start operation timed out. Terminating. Jun 1 01:26:48 box systemd[1]: wickedd-dhcp6.service: Start operation timed out. Terminating. Jun 1 01:26:48 box systemd[1]: wickedd-dhcp4.service: Start operation timed out. Terminating. --- snap --- Sometimes accompanied by: --- snip --- Jun 1 08:36:19 box wickedd-nanny[879]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: Jun 1 08:36:19 box wickedd-nanny[879]: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files Jun 1 08:36:19 box wickedd-nanny[879]: Couldn't refresh list of active network interfaces --- snap --- If it's working I just see the services reading their config files: --- snip --- Jun 1 01:18:50 box systemd[1]: Starting wicked DHCPv4 supplicant service... Jun 1 01:18:50 box systemd[1]: Starting wicked DHCPv6 supplicant service... Jun 1 01:18:50 box systemd[1]: Starting wicked AutoIPv4 supplicant service... Jun 1 01:19:51 box wickedd-dhcp6[888]: Reading config file /etc/wicked/common.xml Jun 1 01:19:51 box wickedd-auto4[889]: Reading config file /etc/wicked/common.xml --- snap --- Like I said, no DHCP, no IPv6 configured at all. I tried disabling them via 'systemctl mask wickedd-auto4.service' etc. but that doesn't seem to change the overall behavior (works roughly 50% of the time). I'd appreciate any help/pointers/... in getting this to work! Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 5