- openSUSE Support

[opensuse-support] Wine experts? How to reconfigure?
by Peter Suetterlin 06 Sep '19

06 Sep '19

Hi list, I wonder if there's some wine experts around here? My issue: I have a wine setup here on my Tumbleweed system, slowly grown with various applications over three years. I'm now trying to run some new program (Maskulator, a fresnel propagation optics program). It crashes :( However, if I rename .wine to .wine.bak and then run the program, I get a notification it is doing some configurations - and now the program runs! But of course all my previously installed stuff is gone. Is there a way to merge old and new, or to enforce a reconfiguration of things? -- 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] Tumbleweed: usb: Cannot enable. Maybe the USB cable is bad?
by mh＠mike.franken.de 04 Sep '19

04 Sep '19

Hi *, on my DELL XPS13 9370 I get the message usb usb10-port1: Cannot enable. Maybe the USB cable is bad? when connecting a device to the first (closer to the front) of the two Thunderbolt/USB-C ports on the left side. Is this a hardware problem or can it be a kernel driver problem? Thx. Bye. Michael. P.S.: Sorry if this is a double post - my original posting probably wasn't sent. -- Michael Hirmke -- 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] Tumbleweed: usb: Cannot enable. Maybe the USB cable is bad?
by mh＠mike.franken.de 03 Sep '19

03 Sep '19

Hi *, on my DELL XPS13 9370 I get the message usb usb10-port1: Cannot enable. Maybe the USB cable is bad? when connecting a device to the first (closer to the front) of the two Thunderbolt/USB-C ports on the left side. Is this a hardware problem or can it be a kernel driver problem? Thx. 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 0

[opensuse-support] Tumbleweed: usb: Cannot enable. Maybe the USB cable is bad?
by mh＠mike.franken.de 03 Sep '19

03 Sep '19

Hi *, on my DELL XPS13 9370 I get the message usb usb10-port1: Cannot enable. Maybe the USB cable is bad? when connecting a device to the first (closer to the front) of the two Thunderbolt/USB-C ports on the left side. Is this a hardware problem or can it be a kernel driver problem? Thx. 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 0

[opensuse-support] Annoying issue with KDE panel / NetworkManager
by Till Dörges 03 Sep '19

03 Sep '19

Hello all, everything was working fine with a stock openSUSE Leap 15.0 installation. Since I went to Leap 15.1 'zypper dup' I experience issues with the KDE panel. There's one panel configured (among other things with an application launcher (the gecko icon), a task manager (i.e. a list of open windows), and a systray). After a certain time, some functions of the panel cease to work - for no apparent reason. Most notably autohide and the task manager (i.e. I can't jump to another window by just clicking on it). The application launcher or controlling a music player via its systray icon continue to work. My current workaround is: killall plasmashell ; sleep 3; plasmashell & but that leaves me with another annoying issue with Network Manager. After restarting plasmashell I cannot activate network connections that require a password. Normally a PW dialog for unlocking kwallet appears, but not after a restart. With journalctl I find this: --- snip --- Aug 28 12:37:21 box NetworkManager[28889]: <info> [1566988641.8457] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 28 12:37:21 box NetworkManager[28889]: <info> [1566988641.8467] device (wlan1): Activation: (wifi) access point 'WLANSSID' has security, but secrets are required. Aug 28 12:37:21 box NetworkManager[28889]: <info> [1566988641.8467] device (wlan1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 28 12:37:21 box NetworkManager[28889]: <warn> [1566988641.8500] device (wlan1): No agents were available for this request. Aug 28 12:37:21 box NetworkManager[28889]: <info> [1566988641.8501] device (wlan1): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Aug 28 12:37:21 box NetworkManager[28889]: <warn> [1566988641.8511] device (wlan1): Activation: failed for connection 'WLANSSID' --- snap --- But I have no idea why there was no agent. Is this possibly another instance of https://bugzilla.opensuse.org/show_bug.cgi?id=1108570 ? So I guess, I'm looking for help in either preventing the panel from acting up or how to restart the panel such that NetworkManager can ask for a password. Any hints are greatly appreciated! TIA -- Till -- 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 ***ZUR INFO*** *Auch dieses Jahr sind wir auf der it-sa in Nürnberg zu finden: 8.-10. Oktober 2019, Halle 11, Stand 519 (Matrix42) -- 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] 'Moving' a running X session to another monitor
by Peter Suetterlin 02 Sep '19

02 Sep '19

Hi list, I wonder if here's some eXperts that know the solution to this: I have a small computer (for astronomy, mount and camera control) that is running openSUSE Tumbleweed. It usually has no monitor or keyboard connected. But it does run graphical.target with an icewm session (autologin). I'm using that via x11vnc_ssh to run the guiding software (phd2). Every now and then I'd like to do something at the mount and would like to see the session on a display that I connect to the (already running) computer. However, the X session won't display there :( I had tried also connecting a keyboard. I can use that to switch to a virtual console, and that is displayed on the newly connected monitor. As soon as I ALT-F7 back to X it goes black again :( Is there a way to get the session to display on a newly connected monitor? I've looked at various xrandr options, but they look quite confusing to a mere mortal :o Thanks for any hints/pointers! -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 2

[opensuse-support] where can I retrieve the information given in virtual console F10?
by stakanov 01 Sep '19

01 Sep '19

When I go to ctl+alt+F10 I got a kind of journal. However, I was not able to find the information given neither in journalctl nor in dmesg. As there is an indication about a probable bug in alsa, I would to be able to recover the text. Thank you. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 2

[opensuse-support] delete snapshots from btrfs subvolume
by Matthias Brugger 01 Sep '19

01 Sep '19

Hi, I'm trying to delete snapshots in /.snapshots from my HDD using the rescue disk. mount shows me the partition mounted as rw but if I try to delete a file by hand it says: rm: cannot remove '<path-to-file>': Read-only file system I also tried snapper --no-dbus -r /mnt rm 44 I tried mounting the partition in the following ways: mount /dev/sda6 /mnt mount -o subvol=.snapshots /dev/sda6 /mnt mount -o recovery,nospace_cache,clear_cache /dev/sda6 /mnt But nothing helps. How can I get rid of the snapshots or any other files? Regards, Matthias

5 17

[opensuse-support] lots of old initrd/config/vmlinuz in /boot
by Axel Braun 01 Sep '19

01 Sep '19

Hi, while checking the diskspace I found tons of fragements from pld kernels - back int the 4.18.x day in /boot. Should there not be a regular job that purges old kernels (and what belons to it)? Thanks Axel -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

6 10

[opensuse-support] Bug in iwlwifi?
by Felix Saphir 31 Aug '19

31 Aug '19

Hi, Since upgrading to kernel 4.12.14-lp150.12.70 (from 12.67), I cannot connect to an ipsec/l2tp vpn anymore, because the kernel crashes consistently after a few seconds. This worked fine before the upgrade, and it still works, when I boot the previous kernel or the current debug kernel. crash reports: KERNEL: vmlinux-4.12.14-lp150.12.70-default.gz DEBUGINFO: /usr/lib/debug/boot/vmlinux-4.12.14-lp150.12.70-default.debug DUMPFILE: vmcore [PARTIAL DUMP] CPUS: 4 DATE: Sat Aug 24 15:03:33 2019 UPTIME: 00:03:35 LOAD AVERAGE: 0.36, 0.37, 0.18 TASKS: 345 NODENAME: espresso.site RELEASE: 4.12.14-lp150.12.70-default VERSION: #1 SMP Wed Aug 7 07:03:51 UTC 2019 (3643f11) MACHINE: x86_64 (2393 Mhz) MEMORY: 7.8 GB PANIC: "BUG: unable to handle kernel NULL pointer dereference at 0000000000000003" PID: 595 COMMAND: "irq/27-iwlwifi" TASK: ffff8802283422c0 [THREAD_INFO: ffff8802283422c0] CPU: 3 STATE: TASK_RUNNING (PANIC) and the bt is crash> bt PID: 595 TASK: ffff8802283422c0 CPU: 3 COMMAND: "irq/27-iwlwifi" #0 [ffffc90001507808] machine_kexec at ffffffff8105f75f #1 [ffffc90001507858] __crash_kexec at ffffffff8111e8fe #2 [ffffc90001507910] crash_kexec at ffffffff8111f5fd #3 [ffffc90001507928] oops_end at ffffffff8102f4ef #4 [ffffc90001507948] no_context at ffffffff8106ee96 #5 [ffffc900015079a0] __do_page_fault at ffffffff8106f668 #6 [ffffc90001507a08] do_page_fault at ffffffff8106fa9a #7 [ffffc90001507a30] page_fault at ffffffff818017b5 [exception RIP: __netif_receive_skb_core+646] RIP: ffffffff816832e6 RSP: ffffc90001507ae0 RFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff8801eb3bf401 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff8801d33b40ce RDI: ffff8801eb3b3f00 RBP: ffffc90001507b60 R8: ffff880223772d40 R9: 000000000000000e R10: ffff880225937c1c R11: 0000000000000026 R12: ffff88022373e000 R13: ffffffff82165ee0 R14: ffffffff82163ec0 R15: 0000000000000008 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #8 [ffffc90001507b70] netif_receive_skb_internal at ffffffff816853fd #9 [ffffc90001507bc8] ieee80211_deliver_skb at ffffffffa0877d76 [mac80211] #10 [ffffc90001507bf0] ieee80211_rx_handlers at ffffffffa087a056 [mac80211] #11 [ffffc90001507c88] ieee80211_prepare_and_rx_handle at ffffffffa087c2e3 [mac80211] #12 [ffffc90001507d08] ieee80211_rx_napi at ffffffffa087d156 [mac80211] #13 [ffffc90001507dc0] iwl_pcie_rx_handle at ffffffffa080570f [iwlwifi] #14 [ffffc90001507e60] iwl_pcie_irq_handler at ffffffffa080778f [iwlwifi] #15 [ffffc90001507ea0] irq_thread_fn at ffffffff810e6a91 #16 [ffffc90001507ec0] irq_thread at ffffffff810e6da1 #17 [ffffc90001507f10] kthread at ffffffff810aa09a #18 [ffffc90001507f50] ret_from_fork at ffffffff81800235 That's probably not enough information to file a bug report, is it? What else should I look at or try? Zypper tells me, that everything's up to date and that there are no updates ... Thanks, Felix -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0