August 2019 - openSUSE Support - openSUSE Mailing Lists

[opensuse-support] Cannot complete registration with openSUSEforums
by JigsTheorem 13 Jun '20

13 Jun '20

Hi all I have a problem with Leap 15.1 and went to sign up with openSUSE forums. I received a validation email, which contained neatly ordered garbage but no validation code. The sender of this email is the webmaster from microfocus, but an email to that address just bounces. I have since discovered that openSUSE and microfocus are no longer associated. So, given that the validation process is broken, how do I get signed up to the forums? Regards JT -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

8 14

[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] 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

[opensuse-support] Is there a way to preserve RPM packages installed via autoinst.xml?
by Brian Reichert 30 Aug '19

30 Aug '19

We're using the SLES 12 SP3 DVD, and AutoYaST, to install a subset of that DVD into a new server. I want to retain the RPM packages of the installed RPMs somewhere on the filesystem. I don't see a hook in any docs for autoyast.xml / autoinst.xml to do this. Maybe there's a way of presenting a flag to zypper to retain them? I'm open to any advice people may have. Thanks! -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 5

[opensuse-support] tracking for a fix for Samba bug
by Brian Reichert 30 Aug '19

30 Aug '19

I'm trying to reproduce an issue one of our customers is having. They are running one of our servers, based on the SLES 12 SP3 DVD. That DVD came with this version of samba: samba-client-4.6.5+git.27.6afd48b1083-2.11.x86_64.rpm There are, of course, several samba-related RPMs with the same version number. I think our customer is getting bit by the bug, while accessing a NetApp: https://bugzilla.samba.org/show_bug.cgi?id=13009 I know that version 4.6.16+git.154.2998451b912-3.40.3 of the samba packages is available to us, but it's unclear to me, from it's changelog, if that fix was backported to the SLES-provided RPMs. Can anyone provide some insight? -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- 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] WTF, why does systemd-logind power down my computer?
by Peter Suetterlin 30 Aug '19

30 Aug '19

Just happened the second time. I had pressed CTRL-ALT-Backspace twice to kill the X server - and the system shuts down instead of restarting it! The log reveals Aug 23 12:35:51 woodstock.pitnet kdeinit5[4101]: kdeinit5: sending SIGTERM to children. Aug 23 12:35:51 woodstock.pitnet kdeinit5[4101]: kdeinit5: Exit. Aug 23 12:35:51 woodstock.pitnet kwin_x11[4139]: The X11 connection broke (error 1). Did the X11 server die? Aug 23 12:35:51 woodstock.pitnet kscreen_backend_launcher[4138]: The X11 connection broke (error 1). Did the X11 server die? Aug 23 12:35:51 woodstock.pitnet systemd-logind[960]: System is powering down. Is that the latest "invention" of the systemd crew? -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 13

[opensuse-support] Accessing SD cards broken in Tumbleweed?
by Christian Boltz 29 Aug '19

29 Aug '19

Hello, am I the only one who can't access SD cards with current Tumbleweed? (Last updated yesterday, but I'm quite sure that this problem existed for at least a week. Actually I had a similar problem months ago, but it magically fixed itsself before I had time to report it.) Both the internal SD card reader of my laptop, and an USB-connected card reader refuse to work. This means: - for the internal card reader, I don't get a /dev/mmc* device or any log message when inserting a SD card - the external card reader starts to flash its LEDs, I sometimes (not always) get a message about a possibly bad cable [1], but it doesn't recognize the SD card. - using another cable with the external card reader, I was able to access a 512 MB SD card, but not a 16 GB card. For this, I get a flood of mtp-probe messages [2]. I tested on my old laptop (with terribly outdated Tumbleweed 20160603, it lived in the shelf since then), and things just worked: - the internal card reader of the old laptop works - the external card reader (using the same cable that caused [1]) works - (I didn't test with the other cable) IMHO it's very unlikely that the internal and external card reader (or its cable) broke at the same time, while everything still works with the old laptop. Oh, of course I tested with multiple SD cards to exclude a broken SD card as a reason. (All cards worked in my old laptop, and they also work in other devices like a camera.) Therefore - does someone else have problems accessing SD cards with internal or external card readers using current Tumbleweed? Do I need to provide some more details for debugging? Regards, Christian Boltz [1] Aug 28 22:43:51 tux kernel: usb usb1-port3: Cannot enable. Maybe the USB cable is bad? [2] Aug 28 22:50:01 tux kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6362, bcdDevice= 1.10 Aug 28 22:50:01 tux kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 28 22:50:01 tux kernel: usb 1-3: Product: Mass Storage Device Aug 28 22:50:01 tux kernel: usb 1-3: Manufacturer: Generic Aug 28 22:50:01 tux kernel: usb 1-3: SerialNumber: 058F312D81A Aug 28 22:50:01 tux kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Aug 28 22:50:01 tux kernel: scsi host7: usb-storage 1-3:1.0 Aug 28 22:50:02 tux kmail[4150]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdd" Aug 28 22:50:02 tux kdeinit5[3623]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdd" Aug 28 22:50:02 tux kmail[4150]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdd" Aug 28 22:50:02 tux kdeinit5[3623]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdd" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux kmozillahelper[5902]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux krunner[3702]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux krunner[2521]: Last message 'org.kde.solid.udisks' repeated 1 times, suppressed by syslog-ng on tux Aug 28 22:50:02 tux org_kde_powerdevil[3740]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux kmozillahelper[5902]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sdc" Aug 28 22:50:02 tux kmail[4150]: org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/block_devices/sde" Aug 28 22:50:02 tux kmail[2521]: Last message 'org.kde.solid.udisks' repeated 1 times, suppressed by syslog-ng on tux Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmozillahelper[2521]: Last message 'UdevQt: unhandled de' repeated 1 times, suppressed by syslog-ng on tux Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmail[2521]: Last message 'UdevQt: unhandled de' repeated 1 times, suppressed by syslog-ng on tux Aug 28 22:50:02 tux mtp-probe[3837]: checking bus 1, device 48: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 28 22:50:02 tux mtp-probe[3837]: bus: 1, device: 48 was not an MTP device Aug 28 22:50:02 tux kernel: usb 1-3: USB disconnect, device number 48 Aug 28 22:50:02 tux kernel: usb 1-3: new high-speed USB device number 49 using xhci_hcd Aug 28 22:50:02 tux kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6362, bcdDevice= 1.10 Aug 28 22:50:02 tux kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 28 22:50:02 tux kernel: usb 1-3: Product: Mass Storage Device Aug 28 22:50:02 tux kernel: usb 1-3: Manufacturer: Generic Aug 28 22:50:02 tux kernel: usb 1-3: SerialNumber: 058F312D81A Aug 28 22:50:02 tux kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Aug 28 22:50:02 tux kernel: scsi host6: usb-storage 1-3:1.0 Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux mtp-probe[3865]: checking bus 1, device 49: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 28 22:50:02 tux mtp-probe[3865]: bus: 1, device: 49 was not an MTP device Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "bind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" Aug 28 22:50:02 tux mtp-probe[3866]: checking bus 1, device 49: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 28 22:50:02 tux mtp-probe[3866]: bus: 1, device: 49 was not an MTP device Aug 28 22:50:03 tux kernel: usb 1-3: USB disconnect, device number 49 Aug 28 22:50:03 tux kernel: usb 1-3: new high-speed USB device number 50 using xhci_hcd Aug 28 22:50:03 tux kernel: usb 1-3: New USB device found, idVendor=058f, idProduct=6362, bcdDevice= 1.10 Aug 28 22:50:03 tux kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 28 22:50:03 tux kernel: usb 1-3: Product: Mass Storage Device Aug 28 22:50:03 tux kernel: usb 1-3: Manufacturer: Generic Aug 28 22:50:03 tux kernel: usb 1-3: SerialNumber: 058F312D81A Aug 28 22:50:03 tux kernel: usb-storage 1-3:1.0: USB Mass Storage device detected Aug 28 22:50:03 tux kernel: scsi host6: usb-storage 1-3:1.0 Aug 28 22:50:03 tux kmozillahelper[5902]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kdeinit5[3623]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kmail[4150]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux krunner[3702]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux mtp-probe[3899]: checking bus 1, device 50: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Aug 28 22:50:03 tux mtp-probe[3899]: bus: 1, device: 50 was not an MTP device Aug 28 22:50:03 tux kdeinit5[3623]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux krunner[3702]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kmail[4150]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kmozillahelper[5902]: UdevQt: unhandled device action "bind" Aug 28 22:50:03 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kdeinit5[3623]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kmail[4150]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux krunner[3702]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux org_kde_powerdevil[3740]: UdevQt: unhandled device action "unbind" Aug 28 22:50:03 tux kmozillahelper[5902]: UdevQt: unhandled device action "unbind" -- So feel free to add Skimmed-by: Seth Arnold <seth.arnold(a)canonical.com> or whatever says I didn't spot anything wrong but I also didn't understand the finer points of what I've read. :) [Seth Arnold in apparmor] -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 3

[opensuse-support] bash script problem
by Patrick Shanahan 29 Aug '19

29 Aug '19

I regularly import photos from a flash drive and rename them with a script to YYMODD_HHMMSS_<orig_file_name>.ext Sometime recently my script, which I have used successfully for quite a few years, failed me and I cannot determine why. The script: exiv2 mv \-k \-r %y%m%d_%H%M%S_:basename: \.\/*.{nef,jpg} exiv2 is a compiled app similar to exiftool, a perl app directory contents before script: -rwxr-xr-x 1 paka users 57253957 aug 21 16:12 aaa_3410.nef -rwxr-xr-x 1 paka users 56087308 aug 21 16:12 aaa_3411.nef -rwxr-xr-x 1 paka users 54191672 aug 21 16:12 aaa_3412.nef -rwxr-xr-x 1 paka users 54679653 aug 21 16:12 aaa_3413.nef -rwxr-xr-x 1 paka users 59877177 aug 21 16:12 aaa_3414.nef -rwxr-xr-x 1 paka users 59788737 aug 21 16:12 aaa_3415.nef -rwxr-xr-x 1 paka users 58250749 aug 21 16:12 aaa_3416.nef screen output of the failure: > rename2date -k: Failed to open the file -r: Failed to open the file %y%m%d_%H%M%S_:basename:: Failed to open the file exiv2: File `./20190821_201219.nef' exists. [O]verwrite, [r]ename or [s]kip? ^C directory contents after script: -rwxr-xr-x 1 paka users 57253957 Aug 21 16:12 20190821_201216.nef -rwxr-xr-x 1 paka users 56087308 Aug 21 16:12 20190821_201217.nef -rwxr-xr-x 1 paka users 54191672 Aug 21 16:12 20190821_201219.nef -rwxr-xr-x 1 paka users 54679653 Aug 21 16:12 aaa_3413.nef -rwxr-xr-x 1 paka users 59877177 Aug 21 16:12 aaa_3414.nef -rwxr-xr-x 1 paka users 59788737 Aug 21 16:12 aaa_3415.nef -rwxr-xr-x 1 paka users 58250749 Aug 21 16:12 aaa_3416.nef in exiv2 :basename: is the original filename w/o extension I understand the failure as the script is trying to write the next filename as an existing filename. What I do not understand is why ":basename:" is not being applied. If ":basename:" was being applied there would be no failure as there would be no duplication of filenames. and I tried escaping, \:basename\: tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri 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

5 6