June 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212257] CIFS mount with DFS crashing the system
by bugzilla_noreply＠suse.com 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212257 https://bugzilla.suse.com/show_bug.cgi?id=1212257#c8 --- Comment #8 from Luiz Angelo Daros de Luca <luizluca(a)tre-sc.jus.br> --- I renamed the bug to match the real issue. It is a cifs issue with DFS shares. It is not only during the login. The system can crash at any time when the cifs share with DFS is mounted. It happens more frequently during login because restoring kde session might access multiple files in parallel from that share. All coworker that use tumbleweed are experiencing similar issues. The system crashes or freezes at unexpected moments. If the share is not mounted, the system is rock solid. We switched to userland cifs access (kio-cifs or smbclient) to workaround the issue. I got a kdump but crash couldn't open it (it looks like this bug https://www.spinics.net/linux/fedora/redhat-crash-utility/msg10076.html) Anyway, I don't know how useful it would be as the bug seems to damage near memory regions. For example, I once got a xfs crash instead of the typical cifs crash. All systems affected have plenty of cores (20) and fast M2 storage. This issue might require more parallelism to appear and it might not manifest with slower machines with less core (like VMs), or when debug msgs are enabled. There are just a few tumbleweed users and none of them using slower machines. No leap user reported this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212257] CIFS mount with DFS crashing the system
by bugzilla_noreply＠suse.com 29 Jun '23

29 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212257 Luiz Angelo Daros de Luca <luizluca(a)tre-sc.jus.br> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|KDE login (wayland and x11) |CIFS mount with DFS |freezes HW |crashing the system -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206745] Unnecessary log entries for rtkit
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1206745 https://bugzilla.suse.com/show_bug.cgi?id=1206745#c16 Scott Reeves <sreeves(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #16 from Scott Reeves <sreeves(a)suse.com> --- SR accepted to Factory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206281] External monitor loses signal after power off (X11+NVIDIA+Plasma)
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1206281 https://bugzilla.suse.com/show_bug.cgi?id=1206281#c12 --- Comment #12 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks for the update! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190434] crash is unable to find debuginfo of usrmerged kernel
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1190434 https://bugzilla.suse.com/show_bug.cgi?id=1190434#c29 --- Comment #29 from David Mair <dmair(a)suse.com> --- For the record, the current discussion is a different bug from the original report. However... After debugging in gdb, the following error: > WARNING: invalid linux_banner pointer: 65762078756e694c > crash: /var/tmp/vmlinux.xz_CSsIpp and /var/crash/2023-05-02-00:13/vmcore > do not match! Occurs in this: > if (!(sp = symbol_search("linux_banner"))) > error(FATAL, "linux_banner symbol does not exist?\n"); > else > if ((sp->type == 'R') || (sp->type == 'r') || > (THIS_KERNEL_VERSION >= LINUX(2,6,11) && > (sp->type == 'D' || sp->type == 'd')) || > (machine_type("ARM") && sp->type == 'T') || > (machine_type("ARM64"))) > linux_banner = symbol_value("linux_banner"); > else > get_symbol_data("linux_banner", sizeof(ulong), The reason in the case of the coredump I'm looking at is that sp->type for linux_banner is 'B' so we take the last false block and get_symbol_data() when we should set linux_banner = symbol_value() instead. I can test my case but I won't commit it until I've seen the others experiencing it that I'm aware of reporting a patch to test sp->type == 'B' works for their versions. I don't have a crash 7 patched for now but I have a teammate who should be able to check the result using a crash 8.0.3 build I just made with a fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212698] gcc-c++-13 LTO introduces non-determinism
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212698 https://bugzilla.suse.com/show_bug.cgi?id=1212698#c3 Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bwiedemann(a)suse.c | |om) | --- Comment #3 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- The difference is with osc build -j1 and -j2 : so 1-core-VM vs 2-core-VM which influences scheduling of forked processes / threads. You might be able to replicate it with taskset 1 vs 3. Here is the full reproducer script: #!/bin/sh osc co openSUSE:Factory/photoqt && cd $_ for N in 1 2 ; do osc build --vm-type=kvm --noservice -j $N --keep-pkg=RPMS.$N unrpm RPMS.$N/photoqt-*.x86_64.rpm hexdump -C usr/bin/photoqt > $N.strings done diff -u {1,2}.strings and I noticed more diff: 00548030 08 6a 54 00 00 00 00 00 00 00 00 00 00 00 00 00 |.jT.............| 00548040 70 68 6f 74 6f 71 74 2e 64 65 62 75 67 00 00 00 |photoqt.debug...| -00548050 76 67 8b 32 00 2e 73 68 73 74 72 74 61 62 00 2e |vg.2..shstrtab..| +00548050 cf 99 c4 a7 00 2e 73 68 73 74 72 74 61 62 00 2e |......shstrtab..| 00548060 69 6e 74 65 72 70 00 2e 6e 6f 74 65 2e 67 6e 75 |interp..note.gnu| 00548070 2e 70 72 6f 70 65 72 74 79 00 2e 6e 6f 74 65 2e |.property..note.| 00548080 67 6e 75 2e 62 75 69 6c 64 2d 69 64 00 2e 6e 6f |gnu.build-id..no| -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175219] OpenVPN fails with certificates on smart cards on Leap 15.2 and TW
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1175219 https://bugzilla.suse.com/show_bug.cgi?id=1175219#c9 Otto Hollmann <otto.hollmann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED --- Comment #9 from Otto Hollmann <otto.hollmann(a)suse.com> --- This issue seems to be resolved. Fixed version is available in SLE15-SP4/5 and Leap 15.4/5 Factory version is not affected, because in Factory we have latest version (1.29). So I'm closing this issue, reopen if needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212801] drop lockdev
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212801 https://bugzilla.suse.com/show_bug.cgi?id=1212801#c1 --- Comment #1 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1212801) was mentioned in https://build.opensuse.org/request/show/1095861 Factory / rxtx-java -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210546] bugzilla.opensuse.org bugmail apparently stopped after bugzilla software upgrade
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1210546 https://bugzilla.suse.com/show_bug.cgi?id=1210546#c13 --- Comment #13 from Frank Krüger <fkrueger(a)mailbox.org> --- (In reply to Thomas Muntaner from comment #12) > Georg Pfuetzenreuter suggested that I share what the issue was, so here is > what I found: > > A custom extension in our bugzilla deployment automatically adds the > openSUSE bugs user to CC for bugs in openSUSE projects. Previously, the > extension handled this through a regex, matching the string "openSUSE" in a > project’s name, but this changed during the migration. > > Now, there is a database column for products which allows us to set the CC > user for a product. Previously, no one set this column for the openSUSE > products. It's working agin, thank you! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190434] crash is unable to find debuginfo of usrmerged kernel
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1190434 https://bugzilla.suse.com/show_bug.cgi?id=1190434#c28 --- Comment #28 from David Mair <dmair(a)suse.com> --- In the source examples below I re-post some from comment #27 where I correct a line I ended with a comma but the source ends with a semi-colon. To show why I am bogged down by this, here's the source for symbol_search(): > ulong > symbol_value(char *symbol) > { > struct syment *sp; > > if (!(sp = symbol_search(symbol))) > error(FATAL, "cannot resolve \"%s\"\n", symbol); > > return(sp->value); > } This sets it's own struct syment sp in an identical way to the following source sample from comment #27 except that the use of symbol_value in the following set's linux_banner to the ASCII text 0x65762078756e694c, which is the value linux_banner holds a pointer to: > if (!(sp = symbol_search("linux_banner"))) > error(FATAL, "linux_banner symbol does not exist?\n"); > else > if ((sp->type == 'R') || (sp->type == 'r') || > (THIS_KERNEL_VERSION >= LINUX(2,6,11) && > (sp->type == 'D' || sp->type == 'd')) || > (machine_type("ARM") && sp->type == 'T') || > (machine_type("ARM64"))) > linux_banner = symbol_value("linux_banner"); > else > get_symbol_data("linux_banner", sizeof(ulong); Yet, if I insert the single line linux_banner = sp->value instead of that symbol_value call and use the sp structure pointer we already have the error doesn't happen: > if (!(sp = symbol_search("linux_banner"))) > error(FATAL, "linux_banner symbol does not exist?\n"); > else > if ((sp->type == 'R') || (sp->type == 'r') || > (THIS_KERNEL_VERSION >= LINUX(2,6,11) && > (sp->type == 'D' || sp->type == 'd')) || > (machine_type("ARM") && sp->type == 'T') || > (machine_type("ARM64"))) > linux_banner = sp->value > else > get_symbol_data("linux_banner", sizeof(ulong); So far, that makes no sense! I believe calling get_symbol_data() would do it but if we took the false path in the nested conditional the change I show in the true path would never be executed. Hence I am deep debugging at present and it's quite nasty for all the reasons I've described... -- You are receiving this mail because: You are on the CC list for the bug.

1 0