May 2022 - openSUSE Bugs - openSUSE Mailing Lists

[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 1196778] New: amdgpu bug
by bugzilla_noreply＠suse.com 15 Jan '23

15 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1196778 Bug ID: 1196778 Summary: amdgpu bug Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: james(a)sevener.us QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When plugging my laptop (Lenovo E14 Gen3, Ryzen 5500U) amdgpu spams the journal, and I can no longer run two screens at 2560x1440. This started on 2/15/2022 after updating. I have been able to get both screens working now, but I have to run one at 1080p and one at 1440p. It used to work great with both at 1440p. In the one log file (it's rolled a few times) I got the following which seems to show once per error. grep -c drivers/gpu/drm/drm_dp_mst_topology.c messages 177772 Full error: 2022-02-18T09:08:02.625936-05:00 localhost kernel: [ 91.051548][ T5215] ------------[ cut here ]------------ 2022-02-18T09:08:02.625954-05:00 localhost kernel: [ 91.051554][ T5215] WARNING: CPU: 10 PID: 5215 at drivers/gpu/drm/drm_dp_mst_topology.c:4404 drm_dp_atomic_find_vcpi_slots.cold+0x0/0x24 2022-02-18T09:08:02.625958-05:00 localhost kernel: [ 91.051567][ T5215] Modules linked in: rfcomm xt_CHECKSUM xt_conntrack ipt_REJECT xt_tcpudp nf_nat_tftp nf_conntrack_tftp bridge stp llc xt_mark xt_MASQUERADE xt_comment tun nft_objref af_packet nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nfnetlink snd_usb_audio snd_usbmidi_lib ebtable_filter snd_rawmidi snd_seq_device ebtables ip6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep dmi_sysfs r8153_ecm cdc_ether usbnet r8152 mii btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ecdh_generic mc intel_rapl_msr intel_rapl_common edac_mce_amd 2022-02-18T09:08:02.625960-05:00 localhost kernel: [ 91.051650][ T5215] kvm_amd kvm irqbypass snd_ctl_led snd_hda_codec_realtek pcspkr snd_hda_codec_generic snd_hda_codec_hdmi joydev snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_pci_acp6x r8169 snd_hwdep thinkpad_acpi snd_pcm snd_pci_acp5x realtek mdio_devres think_lmi snd_rn_pci_acp3x ledtrig_audio efi_pstore firmware_attributes_class wmi_bmof k10temp snd_timer i2c_piix4 snd_pci_acp3x libphy platform_profile snd soundcore tiny_power_button ac ucsi_acpi i2c_scmi typec_ucsi typec roles acpi_cpufreq button nls_iso8859_1 nls_cp437 vfat fat fuse configfs ip_tables x_tables dm_crypt essiv authenc trusted asn1_encoder tee hid_logitech_hidpp hid_logitech_dj hid_generic usbhid rtw89pci(OE) rtw89core(OE) amdgpu crct10dif_pclmul crc32_pclmul ghash_clmulni_intel mac80211 libarc4 xhci_pci xhci_pci_renesas cfg80211 xhci_hcd aesni_intel crypto_simd cryptd usbcore drm_ttm_helper nvme ttm serio_raw ccp iommu_v2 nvme_core sp5100_tco gpu_sched rfkill wmi battery 2022-02-18T09:08:02.625962-05:00 localhost kernel: [ 91.051742][ T5215] video btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs 2022-02-18T09:08:02.625964-05:00 localhost kernel: [ 91.051759][ T5215] CPU: 10 PID: 5215 Comm: kwin_wayland Tainted: G OE 5.16.8-1-default #1 openSUSE Tumbleweed 257f8f36371552cd38032922fd021edb6811ecdc 2022-02-18T09:08:02.625967-05:00 localhost kernel: [ 91.051766][ T5215] Hardware name: LENOVO 20Y7003EUS/20Y7003EUS, BIOS R1OET31W (1.10 ) 11/29/2021 2022-02-18T09:08:02.625968-05:00 localhost kernel: [ 91.051770][ T5215] RIP: 0010:drm_dp_atomic_find_vcpi_slots.cold+0x0/0x24 2022-02-18T09:08:02.625970-05:00 localhost kernel: [ 91.051776][ T5215] Code: 28 ea 57 a4 e8 a4 7c fe ff 49 8b 45 58 48 89 ea 48 c7 c6 70 88 90 a4 48 8b 78 08 e8 78 14 00 00 b8 f4 ff ff ff e9 55 fc c5 ff <0f> 0b 49 8b 46 58 4c 89 e2 48 c7 c6 a0 88 90 a4 41 bf ea ff ff ff 2022-02-18T09:08:02.625972-05:00 localhost kernel: [ 91.051779][ T5215] RSP: 0018:ffffc35b81daf790 EFLAGS: 00010246 2022-02-18T09:08:02.625973-05:00 localhost kernel: [ 91.051783][ T5215] RAX: ffff9f65d94afd98 RBX: ffff9f65d94afd80 RCX: 0000000000000000 2022-02-18T09:08:02.625974-05:00 localhost kernel: [ 91.051786][ T5215] RDX: ffff9f65d94afcc0 RSI: ffff9f661018a500 RDI: ffff9f6660a7d580 2022-02-18T09:08:02.625976-05:00 localhost kernel: [ 91.051788][ T5215] RBP: ffff9f65d94af508 R08: 0000000000000013 R09: ffffc35b81daf8a8 2022-02-18T09:08:02.625977-05:00 localhost kernel: [ 91.051790][ T5215] R10: 00000000000001b5 R11: 0000000000000000 R12: ffff9f65d3d8b800 2022-02-18T09:08:02.625979-05:00 localhost kernel: [ 91.051792][ T5215] R13: ffff9f65d94af500 R14: ffff9f661018a500 R15: 0000000000000013 2022-02-18T09:08:02.625980-05:00 localhost kernel: [ 91.051794][ T5215] FS: 00007fa96d006e40(0000) GS:ffff9f6860080000(0000) knlGS:0000000000000000 2022-02-18T09:08:02.625981-05:00 localhost kernel: [ 91.051798][ T5215] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2022-02-18T09:08:02.625982-05:00 localhost kernel: [ 91.051800][ T5215] CR2: 00007fa95c50d0e0 CR3: 000000014a278000 CR4: 0000000000350ee0 2022-02-18T09:08:02.626005-05:00 localhost kernel: [ 91.051803][ T5215] Call Trace: 2022-02-18T09:08:02.626007-05:00 localhost kernel: [ 91.051806][ T5215] <TASK> 2022-02-18T09:08:02.626008-05:00 localhost kernel: [ 91.051812][ T5215] ? dc_link_should_enable_fec+0x3d/0x60 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630215-05:00 localhost kernel: [ 91.052250][ T5215] compute_mst_dsc_configs_for_link+0x7dd/0xa20 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630227-05:00 localhost kernel: [ 91.052432][ T5215] compute_mst_dsc_configs_for_state+0x1eb/0x340 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630230-05:00 localhost kernel: [ 91.052605][ T5215] amdgpu_dm_atomic_check+0xce4/0xf00 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630232-05:00 localhost kernel: [ 91.052777][ T5215] drm_atomic_check_only+0x595/0x8d0 2022-02-18T09:08:02.630234-05:00 localhost kernel: [ 91.052781][ T5215] drm_mode_atomic_ioctl+0x73c/0xaf0 2022-02-18T09:08:02.630236-05:00 localhost kernel: [ 91.052784][ T5215] ? drm_plane_get_damage_clips.cold+0x1c/0x1c 2022-02-18T09:08:02.630237-05:00 localhost kernel: [ 91.052788][ T5215] ? drm_atomic_set_property+0xb50/0xb50 2022-02-18T09:08:02.630238-05:00 localhost kernel: [ 91.052789][ T5215] drm_ioctl_kernel+0xb0/0x140 2022-02-18T09:08:02.630239-05:00 localhost kernel: [ 91.052794][ T5215] drm_ioctl+0x220/0x3e0 2022-02-18T09:08:02.630241-05:00 localhost kernel: [ 91.052796][ T5215] ? drm_atomic_set_property+0xb50/0xb50 2022-02-18T09:08:02.630243-05:00 localhost kernel: [ 91.052797][ T5215] ? amdgpu_drm_ioctl+0x6a/0x80 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630246-05:00 localhost kernel: [ 91.052938][ T5215] amdgpu_drm_ioctl+0x49/0x80 [amdgpu 24ef79240fc120e4583a1855d40c25a864867216] 2022-02-18T09:08:02.630247-05:00 localhost kernel: [ 91.053078][ T5215] __x64_sys_ioctl+0x82/0xb0 2022-02-18T09:08:02.630249-05:00 localhost kernel: [ 91.053081][ T5215] do_syscall_64+0x5c/0x80 2022-02-18T09:08:02.630250-05:00 localhost kernel: [ 91.053084][ T5215] ? __x64_sys_ioctl+0x9a/0xb0 2022-02-18T09:08:02.630251-05:00 localhost kernel: [ 91.053085][ T5215] ? syscall_exit_to_user_mode+0x18/0x40 2022-02-18T09:08:02.630252-05:00 localhost kernel: [ 91.053088][ T5215] ? do_syscall_64+0x69/0x80 2022-02-18T09:08:02.630254-05:00 localhost kernel: [ 91.053089][ T5215] ? do_syscall_64+0x69/0x80 2022-02-18T09:08:02.630265-05:00 localhost kernel: [ 91.053091][ T5215] ? do_syscall_64+0x69/0x80 2022-02-18T09:08:02.630267-05:00 localhost kernel: [ 91.053092][ T5215] ? exc_page_fault+0x68/0x150 2022-02-18T09:08:02.630268-05:00 localhost kernel: [ 91.053094][ T5215] entry_SYSCALL_64_after_hwframe+0x44/0xae 2022-02-18T09:08:02.630270-05:00 localhost kernel: [ 91.053097][ T5215] RIP: 0033:0x7fa96f8a688b 2022-02-18T09:08:02.630272-05:00 localhost kernel: [ 91.053099][ T5215] Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5d 75 0f 00 f7 d8 64 89 01 48 2022-02-18T09:08:02.630274-05:00 localhost kernel: [ 91.053101][ T5215] RSP: 002b:00007ffc93f8fbb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 2022-02-18T09:08:02.630275-05:00 localhost kernel: [ 91.053103][ T5215] RAX: ffffffffffffffda RBX: 00007ffc93f8fc00 RCX: 00007fa96f8a688b 2022-02-18T09:08:02.630277-05:00 localhost kernel: [ 91.053104][ T5215] RDX: 00007ffc93f8fc00 RSI: 00000000c03864bc RDI: 0000000000000013 2022-02-18T09:08:02.630278-05:00 localhost kernel: [ 91.053105][ T5215] RBP: 00000000c03864bc R08: 0000000000000000 R09: 0000000000000000 2022-02-18T09:08:02.630279-05:00 localhost kernel: [ 91.053106][ T5215] R10: 000000000000000d R11: 0000000000000246 R12: 000055c2e2d4dbf0 2022-02-18T09:08:02.630281-05:00 localhost kernel: [ 91.053106][ T5215] R13: 0000000000000013 R14: 000055c2e2d87840 R15: 000055c2e2d201f0 2022-02-18T09:08:02.630282-05:00 localhost kernel: [ 91.053108][ T5215] </TASK> 2022-02-18T09:08:02.630283-05:00 localhost kernel: [ 91.053109][ T5215] ---[ end trace dd8544f5a3a3564e ]--- 2022-02-18T09:08:02.630285-05:00 localhost kernel: [ 91.053111][ T5215] amdgpu 0000:04:00.0: [drm] *ERROR* cannot allocate and release VCPI on [MST PORT:00000000224748f2] in the same state The error I'm seeing now from journalctl -f -g amdgpu is: amdgpu 0000:05:00.0: [drm] *ERROR* cannot allocate and release VCPI on [MST PORT:0000000050490ba5] in the same state Mar 04 12:18:28 localhost.localdomain kernel: snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi think_lmi wmi_bmof firmware_at> Mar 04 12:18:28 localhost.localdomain kernel: ? dc_link_should_enable_fec+0x3d/0x60 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: compute_mst_dsc_configs_for_link+0x949/0xa20 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: compute_mst_dsc_configs_for_state+0x1eb/0x340 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: amdgpu_dm_atomic_check+0xce4/0xf00 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] Mar 04 12:18:28 localhost.localdomain kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu a112560892c61ad1d7b16506e460ce7b00266659] -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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

[Bug 1188122] New: Latest update to TW breaks Kwallet integration to Kmail
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188122 Bug ID: 1188122 Summary: Latest update to TW breaks Kwallet integration to Kmail Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When starting Kmail now, the password is asked for every server as "it was not able to access kwallet". But Kwallet is open and the passwords are there. copy paste to the password prompt does fix the issue for one session. No new entry is generated in Kwallet. Entries in Kwallet seem normal. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1195393] New: KDE Plasma sound level starts with 74% after every reboot
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1195393 Bug ID: 1195393 Summary: KDE Plasma sound level starts with 74% after every reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: 64bit OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: datenteiler(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36 Build Identifier: I want to start with a lower sound level, because 74%, the default level, is too loud. But when I change the sound level in KDE Plasma to e.g. 42% it's back on 74% after the next reboot. When I log out and log back in, the sound level stays at the value I set, but the volume level is back to 74% after reboot. I have configured my sound card in YaST but this didn't changed anything. Reproducible: Always Steps to Reproduce: 1. Set sound level to a different level then 74% in KDE Plasma (maybe other DE are also effected) 2. Restart openSUSE Leap 15.4 3. Sound level is on 74% again Actual Results: Sound level is on 74%, always. After every reboot. Expected Results: Sound level stays at the value I set. Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Device-2: AMD Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] driver: snd_hda_intel Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo Device-4: RODE Microphones RODE NT-USB type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server-1: ALSA v: k5.14.21-150400.3-default running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.39 running: yes ps -e | grep pipewire 2513 ? 00:00:00 pipewire 2514 ? 00:00:00 pipewire-media- -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1199973] New: Regression: samba update to 4.15.7+git.376 broke Nautilus share access for NT1 protocol
by bugzilla_noreply＠suse.com 13 Jan '23

13 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199973 Bug ID: 1199973 Summary: Regression: samba update to 4.15.7+git.376 broke Nautilus share access for NT1 protocol Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: martin.wilck(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- We've got an old NAS server that requires the "NT1" protocol. We can connect using "client min protocol = NT1" in /etc/samba/smb.conf. This used to work also with Nautilus and it's smb:// URI scheme, until the last update of samba-client. Since the update to samba-client 4.15.7+git.376.dd43aca9ab2, accessing shares via nautilus doesn't work any more. Nautilus opens a pop-up showing "invalid argument". In the previous version 4.15.4+git.324.8332acf1a63, Nautilus would show a password prompt and connect successfully with the right password. The password prompt is never shown with 4.15.7+git.376. But I can still connect via command line: # smbclient -d5 //nasobem.local/josefine -U josefine lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[global]" doing parameter workgroup = MITTAGSTUNDE doing parameter passdb backend = tdbsam doing parameter printing = cups doing parameter printcap name = cups doing parameter printcap cache time = 750 doing parameter cups options = raw doing parameter map to guest = Bad User doing parameter logon path = \\%L\profiles\.msprofile doing parameter logon home = \\%L\%U\.9xprofile doing parameter logon drive = P: doing parameter usershare allow guests = No doing parameter client min protocol = NT1 pm_process() returned Yes added interface wlan0 ip=fd00::5430:8914:8532:921b bcast= netmask=ffff:ffff:ffff:ffff:: added interface wlan0 ip=fd00::a395:90ab:5502:d78a bcast= netmask=ffff:ffff:ffff:ffff:: added interface wlan0 ip=192.168.1.36 bcast=192.168.1.255 netmask=255.255.255.0 Password for [MITTAGSTUNDE\josefine]: Client started (version 4.15.7-git.376.dd43aca9ab2150300.3.32.1-SUSE-oS15.0-x86_64). Opening cache file at /var/lib/samba/lock/gencache.tdb sitename_fetch: No stored sitename for realm '' namecache_fetch: name nasobem.local#20 found. Connecting to 192.168.1.169 at port 445 socket options: SO_KEEPALIVE=0, SO_REUSEADDR=0, SO_BROADCAST=0, TCP_NODELAY=1, TCP_KEEPCNT=9, TCP_KEEPIDLE=7200, TCP_KEEPINTVL=75, IPTOS_LOWDELAY=0, IPTOS_THROUGHPUT=0, SO_REUSEPORT=0, SO_SNDBUF=87040, SO_RCVBUF=131072, SO_SNDLOWAT=1, SO_RCVLOWAT=1, SO_SNDTIMEO=0, SO_RCVTIMEO=0, TCP_QUICKACK=1, TCP_DEFER_ACCEPT=0, TCP_USER_TIMEOUT=0 session request ok negotiated dialect[NT1] against server[nasobem.local] cli_session_creds_prepare_krb5: Doing kinit for josefine@MITTAGSTUNDE to access nasobem.local Kinit for josefine@MITTAGSTUNDE to access nasobem.local failed: Cannot find KDC for requested realm cli_session_setup_spnego_send: Connect to nasobem.local as josefine@MITTAGSTUNDE using SPNEGO GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'spnego' registered GENSEC backend 'schannel' registered GENSEC backend 'naclrpc_as_system' registered GENSEC backend 'sasl-EXTERNAL' registered GENSEC backend 'ntlmssp' registered GENSEC backend 'ntlmssp_resume_ccache' registered GENSEC backend 'http_basic' registered GENSEC backend 'http_ntlm' registered GENSEC backend 'http_negotiate' registered GENSEC backend 'krb5' registered GENSEC backend 'fake_gssapi_krb5' registered Starting GENSEC mechanism spnego gensec_spnego_client_negTokenInit_start: Server claims it's principal name is NONE Starting GENSEC submechanism gse_krb5 smb_gss_krb5_import_cred ccache[MEMORY:cliconnect] failed with [Es wurden keine Anmeldedaten �bergeben oder die Anmeldedaten waren nicht verf�gbar bzw. ein Zugriff darauf nicht m�glich.: kein Anmeldedatenzwischenspeicher gefunden] -the caller may retry after a kinit. Failed to start GENSEC client mech gse_krb5: NT_STATUS_INTERNAL_ERROR Starting GENSEC submechanism ntlmssp Got challenge flags: Got NTLMSSP neg_flags=0x628a8215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_ALWAYS_SIGN NTLMSSP_TARGET_TYPE_SERVER NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY NTLMSSP_NEGOTIATE_TARGET_INFO NTLMSSP_NEGOTIATE_VERSION NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP: Set final flags: Got NTLMSSP neg_flags=0x62088215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_ALWAYS_SIGN NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY NTLMSSP_NEGOTIATE_VERSION NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x62088215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_ALWAYS_SIGN NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY NTLMSSP_NEGOTIATE_VERSION NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x62088215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_ALWAYS_SIGN NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY NTLMSSP_NEGOTIATE_VERSION NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH session setup ok tconx ok Try "help" to get a list of possible commands. smb: \> -- You are receiving this mail because: You are on the CC list for the bug.

1 10