January 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1173891] New: BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook
by bugzilla_noreply＠suse.com 20 Jan '23

20 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1173891 Bug ID: 1173891 Summary: BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: richard(a)nod.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While installing Tumbleweed (openSUSE-Tumbleweed-NET-i586-Snapshot20200701-Media.iso) on my old notbook I got the following crash: ---cut--- [ 3448.675690] BUG: kernel NULL pointer dereference, address: 0000000d [ 3448.675713] #PF: supervisor read access in kernel mode [ 3448.675723] #PF: error_code(0x0000) - not-present page [ 3448.675733] *pde = 00000000 [ 3448.675746] Oops: 0000 [#1] SMP [ 3448.675759] CPU: 1 PID: 13684 Comm: rpm Not tainted 5.7.5-1-default #1 openSUSE Tumbleweed (unreleased) [ 3448.675771] Hardware name: Dell Inc. Latitude 2100 /0W785N, BIOS A01 06/02/2009 [ 3448.675792] EIP: __vfs_write+0x83/0x200 [ 3448.675805] Code: 00 00 8b 73 24 89 55 b0 89 4d b4 89 f0 89 75 ac c1 e8 09 83 e0 02 81 e6 00 40 00 00 0f 85 fd 00 00 00 8b b3 a4 00 00 00 8b 36 <f6> 46 0d 20 0f 85 eb 00 00 00 f7 45 ac 00 10 00 00 75 15 8b b3 a4 [ 3448.675825] EAX: 00000000 EBX: ddb3a180 ECX: 00005e44 EDX: bfd3af6c [ 3448.675836] ESI: 00000000 EDI: c28fdf7c EBP: c28fdf4c ESP: c28fdef4 [ 3448.675848] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010246 [ 3448.675859] CR0: 80050033 CR2: 0000000d CR3: 32744000 CR4: 000006d0 [ 3448.675868] Call Trace: [ 3448.675885] ? apparmor_file_permission+0x56/0x160 [ 3448.675902] ? security_file_permission+0x2c/0x150 [ 3448.675916] ? rw_verify_area+0x44/0x90 [ 3448.675928] vfs_write+0x9b/0x1c0 [ 3448.675942] ? ktime_get_real_ts64+0x4f/0x150 [ 3448.675955] ksys_write+0x58/0xd0 [ 3448.675968] __ia32_sys_write+0x15/0x20 [ 3448.675982] do_int80_syscall_32+0x41/0x120 [ 3448.675996] entry_INT80_32+0xfc/0xfc [ 3448.676007] EIP: 0xb7d71522 [ 3448.676018] Code: 90 66 90 66 90 66 90 90 56 53 83 ec 14 8b 5c 24 20 8b 4c 24 24 8b 54 24 28 65 a1 0c 00 00 00 85 c0 75 1d b8 04 00 00 00 cd 80 <89> c3 3d 00 f0 ff ff 77 4d 83 c4 14 89 d8 5b 5e c3 8d 74 26 00 90 [ 3448.676039] EAX: ffffffda EBX: 00000009 ECX: bfd3af6c EDX: 00005e44 [ 3448.676050] ESI: 02486bf0 EDI: b7e5ba90 EBP: 02481c50 ESP: bfd3aea0 [ 3448.676061] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246 [ 3448.676077] ? nmi+0xc5/0x2b0 [ 3448.676085] Modules linked in: nls_utf8 isofs usbhid parport_pc parport btrfs xor raid6_pq libcrc32c dm_multipath dm_mod 8021q garp mrp stp llc arc4 fan nfs lockd grace fscache nls_iso8859_1 nls_cp437 af_packet sg st sr_mod cdrom iscsi_ibft iscsi_boot_sysfs sunrpc b43 cordic bcma mac80211 cfg80211 i915 ums_realtek uas usb_storage libarc4 dell_laptop gpio_ich ledtrig_audio dell_wmi rfkill sparse_keymap wmi_bmof dell_smbios dell_wmi_descriptor dcdbas i2c_algo_bit ahci drm_kms_helper libahci syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 cec joydev libata rc_core pcspkr serio_raw i2c_i801 libphy lpc_ich drm uhci_hcd ssb ehci_pci ehci_hcd mmc_core usbcore ptp pps_core hwmon pcmcia pcmcia_core thermal wmi tiny_power_button battery button ac video acpi_cpufreq scsi_dh_rdac scsi_dh_emc scsi_dh_alua edd squashfs loop [ 3448.676246] CR2: 000000000000000d [ 3448.676258] ---[ end trace 2e9b3e59a1582583 ]--- ---cut--- Filesystem is btrfs. Thanks, //richard -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1157764] New: [Feature request] Add local resolver with support for DNS-over-TLS and DNS-over-HTTPS
by bugzilla_noreply＠novell.com 19 Jan '23

19 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1157764 Bug ID: 1157764 Summary: [Feature request] Add local resolver with support for DNS-over-TLS and DNS-over-HTTPS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sionescu(a)cddr.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since Dnsmasq doesn't support either protocols, perhaps adding support for Unbound or Stubby would be a good idea. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1190416] New: lxd broken
by bugzilla_noreply＠suse.com 17 Jan '23

17 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1190416 Bug ID: 1190416 Summary: lxd broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- after update lxd want start [werwolf@zabugor] ~ �� rpm -qa | grep lxd lxd-4.18-1.2.x86_64 [werwolf@zabugor] ~ �� sudo systemctl status lxd.service �� [sudo] �� root: �� lxd.service - LXD Container Hypervisor Loaded: loaded (/usr/lib/systemd/system/lxd.service; enabled; vendor preset: disabled) Active: activating (start-post) (Result: exit-code) since Sun 2021-09-12 01:44:17 EDT; 42s ago Docs: man:lxd(1) Process: 2440 ExecStart=/usr/bin/lxd --group=lxd --logfile=/var/log/lxd/lxd.log (code=exited, status=1/FAILURE) Main PID: 2440 (code=exited, status=1/FAILURE); Control PID: 2441 (lxd) Tasks: 4 CPU: 162ms CGroup: /system.slice/lxd.service ��.control ��2441 /usr/bin/lxd waitready --timeout=600 �� 12 01:44:17 zabugor systemd[1]: Starting LXD Container Hypervisor... �� 12 01:44:17 zabugor lxd[2440]: Error: exec: "setfattr": executable file not found in $PATH �� 12 01:44:17 zabugor systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1187478] New: Suddenly, cannot launch YaST2 because won't launch with root permissions
by bugzilla_noreply＠suse.com 17 Jan '23

17 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1187478 Bug ID: 1187478 Summary: Suddenly, cannot launch YaST2 because won't launch with root permissions Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: tonysu(a)su-networking.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Although am setting this as an openSUSE 14.2 problem, I also noticed this happening on 15.3 so don't believe this is an OS problem. As recently as yesterday, it was possible to launch YAST2 from the menu, but now cannot on both a 15.2 and a newly installed and updated 15.3. At first, noticed trying to install an app using One Click Install on to the 15.3 machine, and the install failed because root permissions not set. Then, noticed the same problem unable to launch YAST2 on a 15.2 from the menu... Was able to enter credentials but then failed saying that root permissions required. Of course in the case of the 15.2 machine I could get around the problem by launching from a root console. This all seems to have happened within the past 24 hours. In both cases the machines were freshly updated. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1172327] New: YaST 2 ".desktop" files are not working with lxqt-sudo
by bugzilla_noreply＠suse.com 16 Jan '23

16 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1172327 Bug ID: 1172327 Summary: YaST 2 ".desktop" files are not working with lxqt-sudo Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: LXQt Assignee: mvetter(a)suse.com Reporter: arkadii0324(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm clicking on different links for YaST software from start menu in LXQt but nothing happens after administrator's password typing in "lxqt-sudo" program. I tried to enter the command from one of YaST links in /usr/share/applications/YaST2: $ LC_ALL=C xdg-su -c "/sbin/yast2 users" No protocol specified bash: /sbin/yast2 users: No such file or directory $ I have installed my system from netinstall image (29 May) with basic X11 environment and "lxqt" pattern. Thanks for help. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1192310] New: chrome general protection fault in libc
by bugzilla_noreply＠suse.com 16 Jan '23

16 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1192310 Bug ID: 1192310 Summary: chrome general protection fault in libc Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: kl(a)httgmbh.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since some time (weeks/months?) when closing chromium browser I see general protection faults in libc. On openSUSE Leap 15.3 dmesg shows: [ 3095.177712] show_signal: 55 callbacks suppressed [ 3095.177717] traps: chrome[6342] general protection fault ip:7f6da946b517 sp:7fff85c3af20 error:0 in libc-2.31.so[7f6da9430000+1cb000] [ 3097.129713] traps: chrome[6380] general protection fault ip:7f6da946b517 sp:7fff85c3af20 error:0 in libc-2.31.so[7f6da9430000+1cb000] CPU (lscpu): Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 48 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: AuthenticAMD CPU family: 21 Model: 2 Model name: AMD FX(tm)-8350 Eight-Core Processor Stepping: 0 Frequency boost: enabled CPU MHz: 1400.000 CPU max MHz: 4000.0000 CPU min MHz: 1400.0000 BogoMIPS: 8037.84 Virtualization: AMD-V L1d cache: 64 KiB L1i cache: 256 KiB L2 cache: 8 MiB L3 cache: 8 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Full AMD retpoline, IBPB conditional, STIBP disabled, RSB filling Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nons top_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate ssbd ibpb vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vm cb_clean flushbyasid decodeassists pausefilter pfthreshold The same happens on other machines as well and in openSUSE Leap 15.2: dmesg: [Nov 3 09:51] traps: chrome[10538] general protection fault ip:7fb143397af4 sp:7fffa6936bd0 error:0 in libc-2.26.so[7fb14335d000+1b1000] [Nov 3 10:25] traps: chrome[115913] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [ +32,092832] traps: chrome[117578] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [ +2,958182] traps: chrome[117663] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [Nov 3 10:26] traps: chrome[115903] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [Nov 3 10:27] traps: chrome[121555] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [ +8,946133] traps: chrome[122014] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [ +2,563519] traps: chrome[122179] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [Nov 3 10:28] traps: chrome[121543] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [ +31,635640] traps: chrome[126916] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [ +22,005454] traps: chrome[128192] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [Nov 3 10:29] traps: chrome[128286] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] [ +31,039070] traps: chrome[126900] general protection fault ip:7f94ee4d9af4 sp:7fff13858c00 error:0 in libc-2.26.so[7f94ee49f000+1b1000] CPU: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 43 bits physical, 48 bits virtual CPU(s): 128 On-line CPU(s) list: 0-127 Thread(s) per core: 2 Core(s) per socket: 32 Socket(s): 2 NUMA node(s): 8 Vendor ID: AuthenticAMD CPU family: 23 Model: 1 Model name: AMD EPYC 7601 32-Core Processor Stepping: 2 CPU MHz: 2656.409 BogoMIPS: 4391.45 Virtualization: AMD-V L1d cache: 32K L1i cache: 64K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0,8,16,24,32,40,48,56,64,72,80,88,96,104,112,120 NUMA node1 CPU(s): 2,10,18,26,34,42,50,58,66,74,82,90,98,106,114,122 NUMA node2 CPU(s): 4,12,20,28,36,44,52,60,68,76,84,92,100,108,116,124 NUMA node3 CPU(s): 6,14,22,30,38,46,54,62,70,78,86,94,102,110,118,126 NUMA node4 CPU(s): 1,9,17,25,33,41,49,57,65,73,81,89,97,105,113,121 NUMA node5 CPU(s): 3,11,19,27,35,43,51,59,67,75,83,91,99,107,115,123 NUMA node6 CPU(s): 5,13,21,29,37,45,53,61,69,77,85,93,101,109,117,125 NUMA node7 CPU(s): 7,15,23,31,39,47,55,63,71,79,87,95,103,111,119,127 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid amd_dcm aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1101747] New: no cursor after using e in plain text grub-efi menu
by bugzilla_noreply＠novell.com 15 Jan '23

15 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1101747 Bug ID: 1101747 Summary: no cursor after using e in plain text grub-efi menu Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 777365 --> http://bugzilla.opensuse.org/attachment.cgi?id=777365&action=edit /etc/default/grub and /boot/grub2/grub.cfg from TW host ab250 initial summary: no cursor after using e in plain text grub-efi menu First noticed in TW20180712 and continues in 20180714. After entering "e" on any plain text grub-efi boot menu, there is no kind of cursor blinking anywhere, and as a practical matter it's not possible to do any editing of grub stanzas. All keyboard keys seem to work, but without cursor they're virtually useless. -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 1088564] New: "ssh-agent" is not started on login to Plasma5-Wayland
by bugzilla_noreply＠novell.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1088564 Bug ID: 1088564 Summary: "ssh-agent" is not started on login to Plasma5-Wayland Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build Identifier: This happens in both Leap 15.0 and Tumbleweed. When I login to a Plasma5-Wayland session, "ssh-agent" is not running for the desktop session. This happens whether I use SDDM or GDM for the login manager. I'm aware that Plasma5-Wayland isn't really ready for prime time. Still, it would be nice to have this fixed by the time Leap 15.0 is officially released. My current workaround -- I'm starting "ssh-agent" in the shell startup file (with cross checks so that it isn't started if already running). Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1186930] New: Vidcutter cannot edit or reproduce m4v files
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1186930 Bug ID: 1186930 Summary: Vidcutter cannot edit or reproduce m4v files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 849977 --> http://bugzilla.opensuse.org/attachment.cgi?id=849977&action=edit cli output of vidcutter with mp4 files The program does not specifically complain about anything. It takes a long time to show the thumbnails. When trying to reach a new cut position the program blocks with a black scree (thumbnails remain visible). I join the txt file with the cli output in attachment. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1186360] New: Linphone does not wake up correctly in about 40% of awake from suspend to disk
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1186360 Bug ID: 1186360 Summary: Linphone does not wake up correctly in about 40% of awake from suspend to disk Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- the program itself behaves normally here on one user, but when awaking from suspend to disk or suspend to ram (when system idles for one night on another user) the program shows the account as not connected, searching. When telling to connect explicitly it does not work, however, when exiting the program and opening it again it connects at once problem free. If there is a log or setting were I can see what could be the cause, please advise. I set this to minor because once understood you have to just restart it, it is not really an issue. However,for some user (depending on use case) it may be an annoyance. What the program does: after idling long time on another user account, the application does not manage to log into the voip account, searching constantly to connect. What the program should do: normal reconnect when the user becomes active, according to the settings of the respective account. Reproducible: always Network on this machine is via wicked. -- You are receiving this mail because: You are on the CC list for the bug.

1 1