May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1113225] New: shim build failed with hash is unmatched
by bugzilla_noreply＠novell.com 14 Sep '20

14 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1113225 Bug ID: 1113225 Summary: shim build failed with hash is unmatched Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- shim in Leap 15.1 build failed recently, the error log: [ 60s] + chmod 755 /home/abuild/rpmbuild/SOURCES/timestamp.pl [ 60s] + test -n /home/abuild/rpmbuild/SOURCES/signature-opensuse.asc [ 60s] + head -1 /home/abuild/rpmbuild/SOURCES/signature-opensuse.asc [ 60s] + cp shim.efi shim.efi.bak [ 60s] + /home/abuild/rpmbuild/SOURCES/timestamp.pl --set-from-file /home/abuild/rpmbuild/SOURCES/signature-opensuse.asc shim.efi [ 60s] + pesign -h -P -i shim.efi [ 60s] + cat hash1 hash2 [ 60s] hash: 3be8e7eb348d35c1928f19c769846788991641d1f6cf09514ca10269934f7359 [ 60s] hash: 162c2814c4319dad606e51b9bb5041a5e7ba126ce183794a5ddf439798973bca [ 60s] + cmp -s hash1 hash2 [ 60s] + echo 'ERROR: opensuse binary changed, need to request new signature!' [ 60s] ERROR: opensuse binary changed, need to request new signature! [ 60s] + false This is not caught in staging project period because shim_enforce_ms_signature is not set. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1108570] New: After restarting NetworkManager service, it cannot read passwords from wallet
by bugzilla_noreply＠novell.com 12 Sep '20

12 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1108570 Bug ID: 1108570 Summary: After restarting NetworkManager service, it cannot read passwords from wallet Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: adam(a)mizerski.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Requirements: - KDE - NetworkManager that has a wifi password saved in kwallet Steps to reproduce: - connect to password protected wifi - sudo systemctl restart NetworkManager Expected result: - wifi is set up correctly Actual result: - passwords don't show in gui in wifi security section - connecting to wifi fails, logs says: <info> [1537078992.8413] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') <warn> [1537078992.9063] device (wlp1s0): No agents were available for this request. <info> [1537078992.9067] device (wlp1s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Workarounds: - `nmcli connection up <connection name> --ask` - log out and log in again -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1109373] New: [HPC, slurm] slurm-node & slurm-config not setup right in %pre/%post scriptlets due to missing Requires(pre/post)
by bugzilla_noreply＠novell.com 11 Sep '20

11 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1109373 Bug ID: 1109373 Summary: [HPC, slurm] slurm-node & slurm-config not setup right in %pre/%post scriptlets due to missing Requires(pre/post) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: CONFIRMED Severity: Major Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de CC: hpc-maintainer-bugs(a)forge.provo.novell.com, nicolas.bock(a)suse.com Found By: Development Blocker: --- Symptoms: when installed during initial system installation, the slurm user may not be set up correctly. Reason: 'slurm-config' requires 'shadow' during pre-install. This is however wrongly added as Requires(pre) to 'slurm'. Fix: Move the requires from 'slurm' to 'slurm-node'. Moreover, it should have access to systemd due to the use of 'systemd-tmpfiles' (or the correspondig macro if available). 'slurm-node' should have the access to systemd during %pre/%post. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1085606] New: [SLURM] standard epilog will kill all remaining processes
by bugzilla_noreply＠novell.com 11 Sep '20

11 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1085606 Bug ID: 1085606 Summary: [SLURM] standard epilog will kill all remaining processes Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The standard epilog script will kill all remaining processes on a node. This should be mentioned in in the config and as well in the release nodes. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1112645] New: tuned-profiles-oracle partially does not work
by bugzilla_noreply＠novell.com 08 Sep '20

08 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1112645 Bug ID: 1112645 Summary: tuned-profiles-oracle partially does not work Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: achim(a)klaurie.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed tuned and tuned-profiles-oracle and the following values are not set respectively modified: kernel.shmall kernel.shmmax kernel.shmmni vm.dirty_ratio Steps to install: zypper install tuned tuned-profiles-oracle systemctl enable tuned systemctl start tuned tuned-adm profile oracle My database is 'Oracle Express Edition 11'. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1068647] New: btrfs send bails out on orphan inode
by bugzilla_noreply＠novell.com 01 Sep '20

01 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1068647 Bug ID: 1068647 Summary: btrfs send bails out on orphan inode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I can't create backups of my currently active subvolume with btrfs send any more. It proceeeds for several minutes, than bails out with the error message ERROR: send ioctl failed with -2: No such file or directory This situation has persisted throughout several reboots, remounts, and kernel updates. This first occured while I was doing lots of experiments with btrfs-send, working on my "btrfs-clone" utility (https://github.com/mwilck/btrfs-clone) and testing the efficiency of various cloning strategies within this tool. I made several successful snapshots, until suddenly the described situation came to pass which makes it impossible to do any more snapshots of the "main" subvol. Thus it's possible that the situation was caused by btrfs-send. I admit I did this while the subvolume was mounted. Of course I'd always set the cloned subvolume and its parent to read-only mode while ran btrfs-send (it will abort otherwise). Except for the btrfs-send, no other problems have been observed so far. All other tools (btrfs image, btrfs scrub, btrfs inspect-internal dump-tree) silently ignored this situation. I've traced the error down to the following call stack: > send_subvol() > full_send_tree() > changed_cb [btrfs]() > finish_inode_if_needed [btrfs]() > get_inode_info.constprop.48 [btrfs]() > apply_children_dir_moves [btrfs]() > send_utimes [btrfs]() > get_cur_path [btrfs]() > __get_cur_name_and_parent [btrfs]() > is_inode_existent.part.15 [btrfs]() > get_first_ref [btrfs]() get_first_ref() returns with -ENOENT. I used some instrumentation to find out what was causing this problem, and found the following situation in the file system tree: root tree 28090400768(level 0) / 28058992640(1) - subvol @/.subvols/1/snapshot is item 89 at 28061384704 > root tree > node 28058992640 level 1 items 5 free 488 generation 188885 owner 1 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > key (EXTENT_TREE ROOT_ITEM 0) block 28090400768 (1714502) gen 188885 > > leaf 28090400768 items 98 free space 6117 generation 188885 owner 1 > leaf 28090400768 flags 0x1(WRITTEN) backref revision 1 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > > item 5 key (ROOT_TREE_DIR INODE_ITEM 0) itemoff 14770 itemsize 160 > generation 3 transid 0 size 0 nbytes 16384 > block group 0 mode 40755 links 1 uid 0 gid 0 rdev 0 > sequence 0 flags 0x0(none) > atime 1493728330.0 (2017-05-02 14:32:10) > ctime 1493728330.0 (2017-05-02 14:32:10) > mtime 1493728330.0 (2017-05-02 14:32:10) > otime 1493728330.0 (2017-05-02 14:32:10) > > item 12 key (257 ROOT_ITEM 0) itemoff 13191 itemsize 439 > generation 180352 root_dirid 256 bytenr 36967874560 level 0 refs 1 > lastsnap 12 byte_limit 0 bytes_used 16384 flags 0x0(none) > uuid d4ad4958-2cc1-004e-934d-f223ef4c5f2a > ctransid 180352 otransid 8 stransid 0 rtransid 0 > drop key (0 UNKNOWN.0 0) level 0 > item 13 key (257 ROOT_BACKREF 5) itemoff 13172 itemsize 19 > root backref key dirid 256 sequence 2 name @ > > item 33 key (258 ROOT_ITEM 0) itemoff 12290 itemsize 439 > generation 188511 root_dirid 256 bytenr 17933533184 level 1 refs 1 > lastsnap 0 byte_limit 0 bytes_used 163840 flags 0x0(none) > uuid e99de79b-c494-9445-812b-d08389f82947 > ctransid 188511 otransid 11 stransid 0 rtransid 0 > drop key (0 UNKNOWN.0 0) level 0 > item 34 key (258 ROOT_BACKREF 257) itemoff 12262 itemsize 28 > root backref key dirid 256 sequence 3 name .snapshots > > item 89 key (259 ROOT_ITEM 12) itemoff 10419 itemsize 439 > generation 188884 root_dirid 256 bytenr 28061384704 level 2 refs 1 > lastsnap 186971 byte_limit 0 bytes_used 259981312 flags 0x0(none) > uuid 17c54832-5028-694c-9f97-1be0a1df8757 > parent_uuid d4ad4958-2cc1-004e-934d-f223ef4c5f2a > ctransid 188884 otransid 12 stransid 0 rtransid 0 > drop key (0 UNKNOWN.0 0) level 0 > item 90 key (259 ROOT_BACKREF 258) itemoff 10393 itemsize 26 > root backref key dirid 257 sequence 2 name snapshot File system tree 28061384704 - btrfs path 28052832256(level 0) / 28045197312(1) / 28061384704(2) - item 8 (1746132 INODE_ITEM 0) has "links 0" and no ref - item 86 is an ORPHAN node linking to item 8. > file tree key (259 ROOT_ITEM 12) > node 28061384704 level 2 items 56 free 437 generation 188884 owner 259 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > > key (1732417 INODE_REF 830626) block 28045197312 (1711743) gen 188860 > > node 28045197312 level 1 items 341 free 152 generation 188860 owner 259 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > ... > key (1746122 INODE_ITEM 0) block 28052832256 (1712209) gen 188821 > > leaf 28052832256 items 66 free space 8146 generation 188821 owner 259 > leaf 28052832256 flags 0x1(WRITTEN) backref revision 1 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > ... > item 7 key (1746123 EXTENT_DATA 4096) itemoff 15701 itemsize 53 > generation 188295 type 1 (regular) > extent data disk byte 470392832 nr 4096 > extent data offset 0 nr 4096 ram 4096 > extent compression 0 (none) > item 8 key (1746132 INODE_ITEM 0) itemoff 15541 itemsize 160 > generation 188295 transid 188472 size 940 nbytes 4096 > block group 0 mode 100644 links 0 uid 465 gid 464 rdev 0 > sequence 16 flags 0x6(PREALLOC) > atime 1510830949.715375999 (2017-11-16 12:15:49) > ctime 1510838729.976180731 (2017-11-16 14:25:29) > mtime 1510830949.687375946 (2017-11-16 12:15:49) > otime 1510830949.687375946 (2017-11-16 12:15:49) > item 9 key (1746132 EXTENT_DATA 0) itemoff 15488 itemsize 53 > generation 188295 type 1 (regular) > extent data disk byte 470614016 nr 4096 > extent data offset 0 nr 4096 ram 4096 > extent compression 0 (none) > item 10 key (1746213 INODE_ITEM 0) itemoff 15328 itemsize 160 > generation 188342 transid 188819 size 6498 nbytes 8192 > block group 0 mode 100600 links 1 uid 0 gid 0 rdev 0 > sequence 0 flags 0x4(none) > atime 1510849204.24960545 (2017-11-16 17:20:04) > ctime 1510833103.94629539 (2017-11-16 12:51:43) > mtime 1510833103.86629524 (2017-11-16 12:51:43) > otime 1510833037.158509427 (2017-11-16 12:50:37) > ... > item 85 key (1746369 EXTENT_DATA 0) itemoff 7030 itemsize 53 > generation 188860 type 1 (regular) > extent data disk byte 368373760 nr 4096 > extent data offset 0 nr 4096 ram 4096 > extent compression 0 (none) > item 86 key (ORPHAN ORPHAN_ITEM 1746132) itemoff 7030 itemsize 0 > orphan item So, while trying to process inode 1746213, btrfs send runs finish_inode_if_needed() on 1746132, and fails to send the utimes for this inode because it can't figure out the path. The way I'm reading the btrfs code, it seems that btrfs-send assumes that all orphans have been cleaned up when it starts running. Indeed, btrfs should have got rid of orphan nodes by running btrfs_orphan_cleanup() via btrfs_cleanup_fs_roots() at mount time, but that doesn't seem to be the case. In fact, I've run btrfs-debug tree on this file system two times with different FS generations, and found that the orphan inode hat changed its position (inode number) in the tree. Unfortunately I didn't keep the output of the first debug run, but I'm positive that the inode number of the failing inode was in the 1743xxx range first, and is now 1746132. Therefore I'm filing this as a kernel bug. The problem was first seen with kernel 4.13.11-1.1.g0526da3 now I'm running 4.14.0-1.1.gab9e909. There are 3 aspects to this problem: 1) how did it come to pass? 2) why doesn't the kernel clean up the orphan at boot time? Why does the orphan change inode number? Or is the orphan actually cleaned, but a new one is generated instead? 3) how do I recover? I'd really love to get rid of this broken inode. I could simply switch to a different snapshot of the file system, but AFAICS as long as I don't delete the offending subvolume, the situation would persist. Anyway, as long as 1) and 2) are open, I guess I'd rather keep the subvolume around to facilitate further debugging. I'm unsure if this is easily reproducible. -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[Bug 1133893] New: Incorrect colors being displayed by "display" for a 10-bit LUT (it seems)
by bugzilla_noreply＠novell.com 01 Sep '20

01 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1133893 Bug ID: 1133893 Summary: Incorrect colors being displayed by "display" for a 10-bit LUT (it seems) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 803995 --> http://bugzilla.opensuse.org/attachment.cgi?id=803995&action=edit Windows-Shot of incorrect display When I use ImageMagick-7.0.7.34-lp150.2.26.1.x86_64 to display an image, the colors look significantly wrong, and the image is partly transparent. However when I open the same image on the same display with GIMP or Firefox, the image looks correct. The only special thing seems to be my "HDR" display featuring a 10-bit lookup-table (LUT) for my ATI Radeon: "ATI Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X]" Driver: "amdgpu" The visual probably is like this: visual: visual id: 0x5af class: TrueColor depth: 32 planes available colormap entries: 1024 per subfield red, green, blue masks: 0x3ff00000, 0xffc00, 0x3ff significant bits in color specification: 10 bits -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 1051159] New: GTK3 file picker in print section of Firefox/Thunderbird
by bugzilla_noreply＠novell.com 31 Aug '20

31 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1051159 Bug ID: 1051159 Summary: GTK3 file picker in print section of Firefox/Thunderbird Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: roman(a)pletka.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Change the gtk3 file picker when printing a page as a pdf file. Steps: firefox is on any web page, print (Ctrl +P, or file->print...) select "print to file" click on file name opens a gtk3 file picker. The whole file dialog is GTK3, that needs to be implemented in mozilla-kde.patch. Thanks, Roman -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1117502] New: xemacs Unable to load any usable
by bugzilla_noreply＠novell.com 31 Aug '20

31 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1117502 Bug ID: 1117502 Summary: xemacs Unable to load any usable Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: ericj(a)mcalvin.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Build Identifier: With locale set to en_US.UTF-8, xemacs (and xclock and xfd) all show the warning: Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Note that this issue did not exist in Leap 42.3. It appeared in 15.0. Reproducible: Always Steps to Reproduce: 1. ensure locale is set to: en_US.UTF-8 2. run: xemacs Actual Results: Console shows warning: Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset And xemacs (vm mail module) will not be able to display mail. Error displayed is: xintl/error Can't initialize XIM: Can't get fontset resource for Input Method Expected Results: xemacs should not display that warning, and vm module will be able to display the mail without that error message. As a workaround, you can run: export LANG=en_US xemacs Which corrects the issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 20

[Bug 1135237] New: modesetting driver and xvnc: bad performance
by bugzilla_noreply＠novell.com 29 Aug '20

29 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1135237 Bug ID: 1135237 Summary: modesetting driver and xvnc: bad performance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: P.Suetterlin(a)royac.iac.es QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Not sure if that is a real bug, but I thought I report it here: I am running Tumbleweed (latest version, as of now 20190512) on an ASUS PN40 (Celeron N4000(a)1.1GHz, Gemini lake) for controlling a small telescope (via INDI). It is running headless, and I use x11vnc_ssh to connect to it (it runs a real X session with autologin, icewm as session). The xserver by default uses the modesetting driver. With that, when I connect using xvnc, the CPU load of the X server (X, not xvnc) goes up to some 80-90% just for displaying the empty desktop, still the display is sluggish close to being unusable, with sometimes latencies in the second range (this is on a Gbit cable network). If instead I use the intel driver (xf86-video-intel) CPU load is below 10%, screen updates are very quick, without much latency. -- You are receiving this mail because: You are on the CC list for the bug.

2 24