September 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1145328] calamaris does not generate a report
by bugzilla_noreply＠novell.com 01 Sep '19

01 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1145328 http://bugzilla.suse.com/show_bug.cgi?id=1145328#c3 --- Comment #3 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2019:2042-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1145328 CVE References: Sources used: openSUSE Leap 15.1 (src): calamaris-2.59-lp151.3.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1145328] calamaris does not generate a report
by bugzilla_noreply＠novell.com 01 Sep '19

01 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1145328 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:10955:moderate | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1149068] New: pipenv fails to install any dependencies
by bugzilla_noreply＠novell.com 01 Sep '19

01 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1149068 Bug ID: 1149068 Summary: pipenv fails to install any dependencies Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: n0-0ne+opensuse(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Build Identifier: On openSUSE Tumbleweed with all updates installed the pipenv command can successfully initialize an environment. However, any time I try to install a dependency into it, it crashes. Reproducible: Always Steps to Reproduce: $ mkdir test $ cd test $ pipenv install Creating a virtualenv for this project… Pipfile: /home/jm/test/Pipfile Using /usr/bin/python3 (3.7.3) to create virtualenv… ⠏ Creating virtual environment...Already using interpreter /usr/bin/python3 Using base prefix '/usr' New python executable in /home/jm/.local/share/virtualenvs/test-2t7aXW0E/bin/python3 Also creating executable in /home/jm/.local/share/virtualenvs/test-2t7aXW0E/bin/python Installing setuptools, pip, wheel... done. ✔ Successfully created virtual environment! Virtualenv location: /home/jm/.local/share/virtualenvs/test-2t7aXW0E Creating a Pipfile for this project… Pipfile.lock not found, creating… Locking [dev-packages] dependencies… Locking [packages] dependencies… Updated Pipfile.lock (a65489)! Installing dependencies from Pipfile.lock (a65489)… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1142263] New: [keepassxc] All passwords except latest one lost in group after closing database
by bugzilla_noreply＠novell.com 01 Sep '19

01 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1142263 Bug ID: 1142263 Summary: [keepassxc] All passwords except latest one lost in group after closing database Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fniepelt(a)takios.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, at first I wanted to report this bug upstream but I noticed that the bug does not appear in their official AppImage, so maybe it's got something to do with how openSUSE ships keepassxc? ## Expected Behavior After creating a new password, all passwords in the same group are retained. ## Current Behavior When I create a new password, save the database and then close the database, only the newest password in that group will be available after opening the database again. All other passwords are **lost** (thankfully I noticed this bug in a small group with passwords I can recover easily...). Anything else accessing the database is disabled (e.g. Nextcloud synchronization and the Firefox keepassxc extension). I have this behavior in my current database file and in newly created ones as well. I *think* the bug appeared after I had upgraded to 2.4.3, but I am not sure if I even created a password while being on 2.4.2. ## Steps to Reproduce 1. Create a new database 2. Create two passwords in the Root group 3. Save and close the database 4. Reopen the database. Only the second password will be available. ## keepassxc Debug Info KeePassXC - Version 2.4.3 Revision: 5d6ef0c Qt 5.13.0 Debugging mode is disabled. Operating system: openSUSE Tumbleweed CPU architecture: x86_64 Kernel: linux 5.1.16-1-default Enabled extensions: - Auto-Type - Browser-Integration - SSH-Agent - KeeShare (signed and unsigned sharing) - YubiKey Cryptographic libraries: libgcrypt 1.8.4 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1148317] New: Cannot mount external usb disk 125f:a94a because of "Invalid command operation code"
by bugzilla_noreply＠novell.com 01 Sep '19

01 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1148317 Bug ID: 1148317 Summary: Cannot mount external usb disk 125f:a94a because of "Invalid command operation code" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jzl(a)volny.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.9) Goanna/4.3 NewMoon/28.6.1 Build Identifier: I have 2 similar external usb disks ADATA CH94 (125f:a94a). One of them works OK, other is attached with errors in new kernel and cannot be mounted. In older kernals both works OK. The disks differ in capacity and bcdDevice. My system is current openSUSE Tumbleweed jizbox:~ # uname -a Linux jizbox 5.2.9-1-default #1 SMP Fri Aug 16 20:25:11 UTC 2019 (80c0ffe) x86_64 x86_64 x86_64 GNU/Linux Excerptions from journal. Disk with attach errors: Aug 27 11:59:20 jizbox kernel: usb 2-2.2.2: new high-speed USB device number 12 using xhci_hcd Aug 27 11:59:20 jizbox kernel: usb 2-2.2.2: New USB device found, idVendor=125f, idProduct=a94a, bcdDevice= 1.60 Aug 27 11:59:20 jizbox kernel: usb 2-2.2.2: New USB device strings: Mfr=1, Product=3, SerialNumber=2 Aug 27 11:59:20 jizbox kernel: usb 2-2.2.2: Product: Portable HDD CH94 Aug 27 11:59:20 jizbox kernel: usb 2-2.2.2: Manufacturer: ADATA Aug 27 11:59:20 jizbox kernel: usb 2-2.2.2: SerialNumber: CH0150805213 Aug 27 11:59:20 jizbox kernel: usb-storage 2-2.2.2:1.0: USB Mass Storage device detected Aug 27 11:59:20 jizbox kernel: scsi host7: usb-storage 2-2.2.2:1.0 Aug 27 11:59:20 jizbox mtp-probe[3547]: checking bus 2, device 12: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/2-2.2.2" Aug 27 11:59:20 jizbox mtp-probe[3547]: bus: 2, device: 12 was not an MTP device Aug 27 11:59:21 jizbox kdeinit5[2171]: UdevQt: unhandled device action "bind" Aug 27 11:59:21 jizbox org_kde_powerdevil[2301]: UdevQt: unhandled device action "bind" Aug 27 11:59:21 jizbox plasmashell[2255]: UdevQt: unhandled device action "bind" Aug 27 11:59:21 jizbox mtp-probe[3569]: checking bus 2, device 12: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/2-2.2.2" Aug 27 11:59:21 jizbox mtp-probe[3569]: bus: 2, device: 12 was not an MTP device Aug 27 11:59:21 jizbox kdeinit5[2171]: UdevQt: unhandled device action "bind" Aug 27 11:59:21 jizbox org_kde_powerdevil[2301]: UdevQt: unhandled device action "bind" Aug 27 11:59:21 jizbox plasmashell[2255]: UdevQt: unhandled device action "bind" Aug 27 11:59:21 jizbox kernel: scsi 7:0:0:0: Direct-Access ADATA HDD CH94 PQ: 0 ANSI: 0 Aug 27 11:59:21 jizbox kernel: sd 7:0:0:0: Attached scsi generic sg3 type 0 Aug 27 11:59:21 jizbox kernel: sd 7:0:0:0: [sdd] 1250263728 512-byte logical blocks: (640 GB/596 GiB) Aug 27 11:59:21 jizbox kernel: sd 7:0:0:0: [sdd] Write Protect is off Aug 27 11:59:21 jizbox kernel: sd 7:0:0:0: [sdd] Mode Sense: 03 00 00 00 Aug 27 11:59:21 jizbox kernel: sd 7:0:0:0: [sdd] No Caching mode page found Aug 27 11:59:21 jizbox kernel: sd 7:0:0:0: [sdd] Assuming drive cache: write through Aug 27 11:59:21 jizbox kernel: sdd: sdd1 Aug 27 11:59:21 jizbox kernel: sd 7:0:0:0: [sdd] Attached SCSI disk Aug 27 11:59:45 jizbox kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Aug 27 11:59:45 jizbox kernel: sd 7:0:0:0: [sdd] tag#0 Sense Key : Illegal Request [current] Aug 27 11:59:45 jizbox kernel: sd 7:0:0:0: [sdd] tag#0 Add. Sense: Invalid command operation code Aug 27 11:59:45 jizbox kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 4a 85 6e af 00 00 08 00 Aug 27 11:59:45 jizbox kernel: print_req_error: critical target error, dev sdd, sector 1250258607 flags 80700 Aug 27 11:59:50 jizbox kio_http_cache_cleaner[2416]: QIODevice::skip (QBuffer): WriteOnly device Aug 27 11:59:56 jizbox kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Aug 27 11:59:56 jizbox kernel: sd 7:0:0:0: [sdd] tag#0 Sense Key : Illegal Request [current] Aug 27 11:59:56 jizbox kernel: sd 7:0:0:0: [sdd] tag#0 Add. Sense: Invalid command operation code Aug 27 11:59:56 jizbox kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 4a 85 6e af 00 00 08 00 Aug 27 11:59:56 jizbox kernel: print_req_error: critical target error, dev sdd, sector 1250258607 flags 0 Aug 27 11:59:56 jizbox kernel: Buffer I/O error on dev sdd1, logical block 625129272, async page read Aug 27 11:59:56 jizbox kernel: Buffer I/O error on dev sdd1, logical block 625129273, async page read Aug 27 11:59:56 jizbox kernel: Buffer I/O error on dev sdd1, logical block 625129274, async page read Aug 27 11:59:56 jizbox kernel: Buffer I/O error on dev sdd1, logical block 625129275, async page read For comparision with disk which works OK: Aug 27 12:03:27 jizbox kernel: usb 2-2.2.2: new high-speed USB device number 13 using xhci_hcd Aug 27 12:03:27 jizbox kernel: usb 2-2.2.2: New USB device found, idVendor=125f, idProduct=a94a, bcdDevice= 2.00 Aug 27 12:03:27 jizbox kernel: usb 2-2.2.2: New USB device strings: Mfr=1, Product=3, SerialNumber=2 Aug 27 12:03:27 jizbox kernel: usb 2-2.2.2: Product: Portable HDD CH94 Aug 27 12:03:27 jizbox kernel: usb 2-2.2.2: Manufacturer: ADATA Aug 27 12:03:27 jizbox kernel: usb 2-2.2.2: SerialNumber: 034000002187 Aug 27 12:03:27 jizbox kernel: usb-storage 2-2.2.2:1.0: USB Mass Storage device detected Aug 27 12:03:27 jizbox kernel: scsi host7: usb-storage 2-2.2.2:1.0 Aug 27 12:03:27 jizbox mtp-probe[3766]: checking bus 2, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/2-2.2.2" Aug 27 12:03:27 jizbox mtp-probe[3766]: bus: 2, device: 13 was not an MTP device Aug 27 12:03:27 jizbox plasmashell[2255]: UdevQt: unhandled device action "bind" Aug 27 12:03:27 jizbox kdeinit5[2171]: UdevQt: unhandled device action "bind" Aug 27 12:03:27 jizbox org_kde_powerdevil[2301]: UdevQt: unhandled device action "bind" Aug 27 12:03:27 jizbox mtp-probe[3788]: checking bus 2, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/2-2.2.2" Aug 27 12:03:27 jizbox mtp-probe[3788]: bus: 2, device: 13 was not an MTP device Aug 27 12:03:27 jizbox org_kde_powerdevil[2301]: UdevQt: unhandled device action "bind" Aug 27 12:03:27 jizbox plasmashell[2255]: UdevQt: unhandled device action "bind" Aug 27 12:03:27 jizbox kdeinit5[2171]: UdevQt: unhandled device action "bind" Aug 27 12:03:28 jizbox kernel: scsi 7:0:0:0: Direct-Access ADATA HDD CH94 PQ: 0 ANSI: 0 Aug 27 12:03:28 jizbox kernel: sd 7:0:0:0: Attached scsi generic sg3 type 0 Aug 27 12:03:28 jizbox kernel: sd 7:0:0:0: [sdd] 1953525167 512-byte logical blocks: (1.00 TB/932 GiB) Aug 27 12:03:28 jizbox kernel: sd 7:0:0:0: [sdd] Write Protect is off Aug 27 12:03:28 jizbox kernel: sd 7:0:0:0: [sdd] Mode Sense: 03 00 00 00 Aug 27 12:03:28 jizbox kernel: sd 7:0:0:0: [sdd] No Caching mode page found Aug 27 12:03:28 jizbox kernel: sd 7:0:0:0: [sdd] Assuming drive cache: write through Aug 27 12:03:28 jizbox kernel: sdd: sdd1 Aug 27 12:03:28 jizbox kernel: sd 7:0:0:0: [sdd] Attached SCSI disk Aug 27 12:03:28 jizbox udisksd[2186]: Mounted /dev/sdd1 at /run/media/jzl/videojzl on behalf of uid 1955 Aug 27 12:03:28 jizbox kernel: EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null) And log excerption on another computer with openSUSE 15.2 in current state (4.12.14-lp151.28.13-default) for first disk which on tumbleweed shows errors: srp 27 12:08:50 jizhp440 kernel: usb 1-1: new high-speed USB device number 7 using xhci_hcd srp 27 12:08:50 jizhp440 kernel: usb 1-1: New USB device found, idVendor=125f, idProduct=a94a srp 27 12:08:50 jizhp440 kernel: usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=2 srp 27 12:08:50 jizhp440 kernel: usb 1-1: Product: Portable HDD CH94 srp 27 12:08:50 jizhp440 kernel: usb 1-1: Manufacturer: ADATA srp 27 12:08:50 jizhp440 kernel: usb 1-1: SerialNumber: CH0150805213 srp 27 12:08:50 jizhp440 kernel: usb-storage 1-1:1.0: USB Mass Storage device detected srp 27 12:08:50 jizhp440 kernel: scsi host3: usb-storage 1-1:1.0 srp 27 12:08:50 jizhp440 mtp-probe[4380]: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1" srp 27 12:08:50 jizhp440 mtp-probe[4380]: bus: 1, device: 7 was not an MTP device srp 27 12:08:51 jizhp440 kernel: scsi 3:0:0:0: Direct-Access ADATA HDD CH94 PQ: 0 ANSI: 0 srp 27 12:08:51 jizhp440 kernel: sd 3:0:0:0: [sdc] 1250263728 512-byte logical blocks: (640 GB/596 GiB) srp 27 12:08:51 jizhp440 kernel: sd 3:0:0:0: [sdc] Write Protect is off srp 27 12:08:51 jizhp440 kernel: sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00 srp 27 12:08:51 jizhp440 kernel: sd 3:0:0:0: [sdc] No Caching mode page found srp 27 12:08:51 jizhp440 kernel: sd 3:0:0:0: [sdc] Assuming drive cache: write through srp 27 12:08:51 jizhp440 kernel: sdc: sdc1 srp 27 12:08:51 jizhp440 kernel: sd 3:0:0:0: [sdc] Attached SCSI disk srp 27 12:09:21 jizhp440 ntfs-3g[4440]: Version 2016.2.22 external FUSE 29 srp 27 12:09:21 jizhp440 ntfs-3g[4440]: Mounted /dev/sdc1 (Read-Write, label "JzlAdata", NTFS 3.1) srp 27 12:09:21 jizhp440 ntfs-3g[4440]: Cmdline options: rw,nodev,nosuid,uid=1955,gid=100,uhelper=udisks2 srp 27 12:09:21 jizhp440 ntfs-3g[4440]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdc1,blkdev,blksize=4096 srp 27 12:09:21 jizhp440 ntfs-3g[4440]: Global ownership and permissions enforced, configuration type 7 srp 27 12:09:21 jizhp440 udisksd[1646]: Mounted /dev/sdc1 at /run/media/jzl/JzlAdata on behalf of uid 1955 usb-storage.quirks=125f:a94a:u didnt help. Reproducible: Always Steps to Reproduce: 1. Attach extarnal usb disk "idVendor=125f, idProduct=a94a, bcdDevice= 1.60" 2. Show logs for errors 3. Actual Results: Unaccessible disk Expected Results: Disk mounted -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1135523] New: Check EFI System Partition VFAT filesystem on boot
by bugzilla_noreply＠novell.com 01 Sep '19

01 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1135523 Bug ID: 1135523 Summary: Check EFI System Partition VFAT filesystem on boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: marcosfrm(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Currently YaST sets fs_passno to 0 in /etc/fstab for the ESP VFAT filesystem: https://github.com/yast/yast-storage-ng/blob/SLE-15-SP1/src/lib/y2storage/m… My machine (openSUSE 15.0): UUID=XXXX-XXXX /boot/efi vfat defaults 0 0 I am not sure how my ESP filesystem become dirty (power outage?). Kernel complains on every boot: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Everything works despite the warning, but if fs_passno was set, systemd-fsck would run, call "fsck.vfat -a /dev/foo" and fix it, no? Fedora folks made this change in 2015: https://bugzilla.redhat.com/show_bug.cgi?id=1077917 https://github.com/storaged-project/blivet/commit/f536c7d2bec580c34847d18f0… -- You are receiving this mail because: You are on the CC list for the bug.

1 1