September 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225688] New: [tw] [hexchat] gnome-shell The program 'hexchat' received an X Window System error when connecting to netwok
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225688 Bug ID: 1225688 Summary: [tw] [hexchat] gnome-shell The program 'hexchat' received an X Window System error when connecting to netwok Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/4236088/modules/hexc hat/steps/28 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Description The issue is a sporadic one, but I can see the issue several times in openQA automation tests. it can be seen on both x86_64 and aarch64 platforms. Steps to reproduce the issue: 1. Upgrade the system from leap15.x to tw 2. start hexchat 3. config a nickname and connect to "Libera.Chat" Error logs like below: >May 30 09:49:37.300575 susetest gnome-shell[30709]: The program 'hexchat' received an X Window System error. >May 30 09:49:37.300575 susetest gnome-shell[30709]: This probably reflects a bug in the program. >May 30 09:49:37.307179 susetest gnome-shell[30709]: The error was 'BadWindow (invalid Window parameter)'. >May 30 09:49:37.307179 susetest gnome-shell[30709]: (Details: serial 6056 error_code 3 request_code 38 minor_code 0) >May 30 09:49:37.307179 susetest gnome-shell[30709]: (Note to programmers: normally, X errors are reported asynchronously; >May 30 09:49:37.307179 susetest gnome-shell[30709]: that is, you will receive the error a while after causing it. >May 30 09:49:37.307179 susetest gnome-shell[30709]: To debug your program, run it with the --sync command line >May 30 09:49:37.307179 susetest gnome-shell[30709]: option to change this behavior. You can then get a meaningful >May 30 09:49:37.307179 susetest gnome-shell[30709]: backtrace from your debugger if you break on the gdk_x_error() function.) Please refer to the attached log for more information. ## openQA Observation as below: openQA test in scenario opensuse-Tumbleweed-NET-aarch64-zdup-Leap-15.5-gnome@aarch64 fails in [hexchat](https://openqa.opensuse.org/tests/4236088/modules/hexchat/steps/28) ## Test suite description Maintained by qe-core ## Reproducible Fails since (at least) Build [20240529](https://openqa.opensuse.org/tests/4235968) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1230418] New: [REGRESSION] laptop refuses to go to sleep and starts stuttering when battery is full
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230418 Bug ID: 1230418 Summary: [REGRESSION] laptop refuses to go to sleep and starts stuttering when battery is full Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: PC OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: pinchon.guillaume(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877263 --> https://bugzilla.suse.com/attachment.cgi?id=877263&action=edit System details I've had these issues a while back and it was fixed, but it's back ONCE AGAIN ! When I get my laptop out of its pouch I often find its battery is completely empty or it overheated itself to sleep! I also find myself having to reboot every time the battery gets fully charged because the CPU gets locked at 400Mhz (THIS WAS FIXED 3 OR 4 MONTH AGO) Sorry for the tone but this is becoming very frustrating, this issue comes back at random when the kernel is updated and is damaging for both the battery and the CPU/GPU. I feel like someone is pushing old code back into the main branch every time they're merging their work... For the love of god, I beg of you to do some testing on this bug on every update -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1229022] New: keepassxc: "invisible" process, throws kf.i18n errors instead
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229022 Bug ID: 1229022 Summary: keepassxc: "invisible" process, throws kf.i18n errors instead Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: t.rother(a)netzwissen.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- latest keepassxc starts "invisible" on the KDE 6 UI. On cli it shows a strange error on command line instead: thommie@locutus:~> keepassxc kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Save All" msgid_plural: "" msgctxt: "@action:button" kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "&Yes" msgid_plural: "" msgctxt: "@action:button" thommie@locutus:~> ps -aux | grep keepass thommie 33053 0.0 0.4 562496 132688 pts/1 SLl+ 07:45 0:00 keepassxc So the process itself is there but not visible in the Plasma UI. Same error when starting keepassxc from flatpak. The error appears in all local users, therefore I assume something is wrong on the Plasma platform side, but the strange thing is that I see this only with keepassxc (which is pretty essential ;-) ) and only on ONE machine. rpm dependencies are all solved and the keepassxc-cli is still usable. I would need some help for debugging ... Environment: plasma 6.1.3, framework 6.4.0, QT 6.7.2, Wayland (same error appears with X11!) -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1231067] New: X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - driver does not function after kernel 6.10
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231067 Bug ID: 1231067 Summary: X11:Drivers:Video:Redesign/nvidia-open-driver-G06-sign ed: Bug - driver does not function after kernel 6.10 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: sndirsch(a)suse.com Reporter: pallaswept(a)proton.me QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Please refer to https://forums.opensuse.org/t/issues-with-kernel-6-11-0-1-default-and-nvidi… Symptom: The nvidia driver has a bug (fixed upstream in 550.120) which causes the fbdev interface to fail. KDE's kwin (apparently?) was using this interface. This meant that kwin would fail after the kernel update, resulting in a mostly-unresponsive system. Workaround: A workaround for this has been found, which is to enable kernel modesetting for the driver, using the kernel boot parameter nvidia_drm.modeset=1 The real problem: However, this should not be necessary, and for many users was not necessary, since the driver package installs a file to /usr/lib/modprobe.d/50-nvidia-default.conf, which specifies this option for this kernel module. All of this suggests that there is a fault in this driver package, which was hidden, and was exposed by the driver bug. If the modprobe conf file were functioning, then the module should have been loaded with the parameters it specifies, and the DE would load. We have a workaround, and future drivers will successfully work without the modprobe conf files, but it would be good to make sure the modprobe conf files actually work 100%. We presently have no clue as to why some users were uneffected by this. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1229732] New: [SELinux] investigate why relabeling sometime does not work
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229732 Bug ID: 1229732 Summary: [SELinux] investigate why relabeling sometime does not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- investigate why relabeling sometime does not work after a new policy is installed e.g. see bsc#1229587 also there were some other bugs where there was a similar issue -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225296] New: Dual monitor not recognised after upgrade 15.5 to 15.6
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225296 Bug ID: 1225296 Summary: Dual monitor not recognised after upgrade 15.5 to 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: martin.schmidt(a)io-warnemuende.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Moin, moin, I am using openSUSE 15.5 on an old intel based x86 PC, equipped with a simple nvidia gforce and two monitors. The monitors are using a displayport connnection from the graphics card to the monitors via an Y-shaped cable. Both monitors are recognised correctly and can be configured to form a single graphical work space, when the system is up and running. After upgrading to openSUSE 15.6 this does not work any more. When booting, monitor 1 shows some firmware screen and the openSUSE boot screen, where the OS version (several subversions of 15.6 and frozen snapshots of 15.5) can be selected. Using the default option (15.6 from harddrive), the output of the boot process is moving to monitor 2, but monitor 1 is going to a "power saving sleep mode" and stays inactive frome here on. The boot process is finished correctly with monitor 2 as the only graphical device. Monitor 1 cannot be activated again. Switching off monitor 2 before booting, the system comes up without any valid output device. Monitor 1 goes to sleep after the system boot started. I did not check the system status with a remote ssh-connection yet. Switching off monitor 1 before booting, lets the system come up completely with monitor 2. Also the initial hardware screen is diplayerd there. In turn, booting from a read-only snapshot with openSUSE 15.5, both monitors are used as before. The nouveau-dri drivers are used, no propriatary nvidia driver is installed. Some upgrade history: - just to test, if the few graphic card cores could be used in a cuda environment, cuda was installed under 15.5. This failed and cuda was deinstalled. However, when upgrading later from 15.5 to 15.6 the cuda development environment was reinstalled automatically together with nvidia drivers. As a result the nvidia drivers allowed only for a single low resolution vga monitor. May be, this happened, since the nvidia repository was not deleted and there was some leftover from the cuda test. - with the ascii-yast the nvidia drivers (gforce003/004) and cuda could be removed and the nouveau-dri drivers where reinstalled - together with dependencies. This allows for a single monitor OS_15.6 system with high resolution, but the second monitor (monitor 1) is lost during the boot process as described above. Before I try to install from scratch just with the hope that the error goes away, I am reporting this strange behaviour here. May be, this helps to streamline the distribution. Any hints are very welcome - especially how to modify the bootloader options. Cheers, Martin Schmidt -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[Bug 1231079] New: mc 4.8.32 , wrong date is displayed for directories
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231079 Bug ID: 1231079 Summary: mc 4.8.32 , wrong date is displayed for directories Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: holgerbruenjes(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877654 --> https://bugzilla.suse.com/attachment.cgi?id=877654&action=edit mc 4.8.32 with wrong datestamp of dirs the new mc release 4.8.32 show the wrong date is displayed for directories when I open a tarball with mc the directories show the DATE from 1 Jan 1970 and not the correct DATE. The date display of the files is correct -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1230629] New: Lenovo T14 Gen 5 (Intel Meteor Lake) immediately wakes up from suspend
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230629 Bug ID: 1230629 Summary: Lenovo T14 Gen 5 (Intel Meteor Lake) immediately wakes up from suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: shundhammer(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877385 --> https://bugzilla.suse.com/attachment.cgi?id=877385&action=edit Tarball with system logs, hwinfo, packages info, BIOS screenshots My brand new Lenovo ThinkPad T14 Gen 5 (Intel Core 5 Ultra 125U with Meteor Lake chipset) immediately wakes up again when I try to suspend it to RAM, and there are some errors in the logs: sudo systemctl suspend ...screen goes black... ...screen flickers... ...power LED blinks... ...screen comes back again... ...network status icon shows disconnected... ...network reconnects... -> the machine is back awake as if nothing ever happened. This happens with the current Slowroll kernel and with the current Tumbleweed kernel. It does work with a Xubuntu 22.04.01 LTS live ISO with the older 6.8 kernel, though: - kernel-default-6.10.9-1.1.x86_64 (Tumbleweed) -> wakes up immediately - kernel-default-6.10.8-1.1.x86_64 (Slowroll) -> wakes up immediately - kernel 6.8.? (Xubuntu 22.04.01 live ISO) -> suspends as expected, resumes as expected >> inxi >> >> CPU: 12-core (2-mt/10-st) Intel Core Ultra 5 125U (-MST AMCP-) >> speed/min/max: 400/400/4300:3600:2100 MHz Kernel: 6.10.9-1-default x86_64 >> Up: 0h 7m Mem: 1.08/15.12 GiB (7.1%) Storage: 953.87 GiB (12.2% used) >> Procs: 361 Shell: Zsh inxi: 3.3.36 I already did update the (UEFI) BIOS to the latest one, reset the BIOS settings to factory defaults, and updated the kernel-firmware packages to the latest one from Tumbleweed; none of that helped. For more system info, please see the attached tarball: Lenovo-T14-suspend-bug ├── BIOS-screenshots │ ├── T14-BIOS-01-Main.jpg │ ├── T14-BIOS-02-Power-Settings.jpg │ └── T17-BIOS-03-Power-On.jpg ├── hardware │ ├── hwinfo.log │ ├── inxi-full.log │ ├── inxi.log │ └── inxi-machine.log ├── messages │ ├── dmesg-after-suspend.log │ ├── dmesg-before-suspend.log │ ├── dmesg.diff │ ├── journalctl-b-after-suspend.log │ ├── journalctl-b-before-suspend.log │ └── journalctl-b.diff └── packages ├── rpm-qa-last.txt └── zypp-history.log journalctl -b diff before and after the suspend: >> Sep 17 10:35:22 meteor systemd-logind[976]: The system will suspend now! >> Sep 17 10:35:22 meteor ModemManager[1079]: <info> [sleep-monitor-systemd] system is about to suspend >> Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7931] manager: sleep: sleep requested (sleeping: no enabled: yes) >> Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7932] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7938] manager: NetworkManager state is now ASLEEP >> Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7940] device (wlp0s20f3): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:22 meteor sudo[2349]: pam_unix(sudo:session): session closed for user root >> Sep 17 10:35:22 meteor systemd[1]: Starting Network Manager Script Dispatcher Service... >> Sep 17 10:35:22 meteor systemd[1]: Started Network Manager Script Dispatcher Service. >> Sep 17 10:35:22 meteor kernel: wlp0s20f3: deauthenticating from c8:0e:14:46:50:44 by local choice (Reason: 3=DEAUTH_LEAVING) >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0377] device (wlp0s20f3): supplicant interface state: completed -> disconnected >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0379] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0384] dhcp4 (wlp0s20f3): canceled DHCP transaction >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0384] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0384] dhcp4 (wlp0s20f3): state changed no lease >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0386] dhcp6 (wlp0s20f3): canceled DHCP transaction >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0386] dhcp6 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0386] dhcp6 (wlp0s20f3): state changed no lease >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0819] device (wlp0s20f3): set-hw-addr: set MAC address to D6:6B:75:DD:7E:C9 (scanning) >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.1987] device (wlp0s20f3): supplicant interface state: disconnected -> interface_disabled >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.1988] device (wlp0s20f3): supplicant interface state: interface_disabled -> disconnected >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.1991] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:23 meteor chronyd[1208]: Removed source fd00::ca0e:14ff:fe46:503e >> Sep 17 10:35:23 meteor chronyd[1208]: Source 192.168.178.1 offline >> Sep 17 10:35:23 meteor chronyd[1208]: Can't synchronise: no selectable sources >> Sep 17 10:35:23 meteor chronyd[1208]: Source 85.215.189.120 offline >> Sep 17 10:35:23 meteor dns-dnsmasq.sh[2368]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.3482] device (wlp0s20f3): set-hw-addr: reset MAC address to 28:A0:6B:33:40:FA (unmanage) >> Sep 17 10:35:23 meteor systemd[1]: Reached target Sleep. >> Sep 17 10:35:23 meteor systemd[1]: Starting System Suspend... >> Sep 17 10:35:23 meteor dns-dnsmasq.sh[2384]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:23 meteor systemd-sleep[2378]: User sessions remain unfrozen (add $SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=1 to override), >> Sep 17 10:35:23 meteor systemd-sleep[2378]: relying on kernel to perform the freeze. >> Sep 17 10:35:23 meteor systemd-sleep[2378]: This is a temporary downstream workaround for https://github.com/systemd/systemd/issues/33083. >> Sep 17 10:35:23 meteor systemd-sleep[2392]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend >> Sep 17 10:35:23 meteor systemd-sleep[2378]: Performing sleep operation 'suspend'... >> Sep 17 10:35:23 meteor kernel: PM: suspend entry (s2idle) >> Sep 17 10:35:23 meteor kernel: Filesystems sync: 0.002 seconds >> Sep 17 10:35:24 meteor kernel: Freezing user space processes >> Sep 17 10:35:24 meteor kernel: Freezing user space processes completed (elapsed 0.001 seconds) >> Sep 17 10:35:24 meteor kernel: OOM killer disabled. >> Sep 17 10:35:24 meteor kernel: Freezing remaining freezable tasks >> Sep 17 10:35:24 meteor kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) >> Sep 17 10:35:24 meteor kernel: printk: Suspending console(s) (use no_console_suspend to debug) >> Sep 17 10:35:24 meteor kernel: e1000e: EEE TX LPI TIMER: 00000011 >> Sep 17 10:35:24 meteor kernel: e1000e 0000:00:1f.6: PM: pci_pm_suspend(): e1000e_pm_suspend [e1000e] returns -2 >> Sep 17 10:35:24 meteor kernel: e1000e 0000:00:1f.6: PM: dpm_run_callback(): pci_pm_suspend returns -2 >> Sep 17 10:35:24 meteor kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 >> Sep 17 10:35:24 meteor kernel: PM: Some devices failed to suspend, or early wake event detected >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.29.2 >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.29.2 >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4 >> Sep 17 10:35:24 meteor kernel: nvme nvme0: 14/0/0 default/read/poll queues >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: submission enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: RC enabled >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x80 >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4 >> Sep 17 10:35:24 meteor kernel: mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915]) >> Sep 17 10:35:24 meteor kernel: OOM killer enabled. >> Sep 17 10:35:24 meteor kernel: Restarting tasks ... done. >> Sep 17 10:35:24 meteor kernel: random: crng reseeded on system resumption >> Sep 17 10:35:25 meteor kernel: PM: suspend exit >> Sep 17 10:35:25 meteor kernel: PM: suspend entry (s2idle) >> Sep 17 10:35:25 meteor kernel: Filesystems sync: 0.019 seconds >> Sep 17 10:35:26 meteor kernel: Freezing user space processes >> Sep 17 10:35:26 meteor kernel: Freezing user space processes completed (elapsed 0.001 seconds) >> Sep 17 10:35:26 meteor kernel: OOM killer disabled. >> Sep 17 10:35:26 meteor kernel: Freezing remaining freezable tasks >> Sep 17 10:35:26 meteor kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) >> Sep 17 10:35:26 meteor kernel: printk: Suspending console(s) (use no_console_suspend to debug) >> Sep 17 10:35:26 meteor kernel: e1000e: EEE TX LPI TIMER: 00000011 >> Sep 17 10:35:26 meteor kernel: e1000e 0000:00:1f.6: PM: pci_pm_suspend(): e1000e_pm_suspend [e1000e] returns -2 >> Sep 17 10:35:26 meteor kernel: e1000e 0000:00:1f.6: PM: dpm_run_callback(): pci_pm_suspend returns -2 >> Sep 17 10:35:26 meteor kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 >> Sep 17 10:35:26 meteor kernel: PM: Some devices failed to suspend, or early wake event detected >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.29.2 >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.29.2 >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4 >> Sep 17 10:35:26 meteor kernel: nvme nvme0: 14/0/0 default/read/poll queues >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: submission enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: RC enabled >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x80 >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4 >> Sep 17 10:35:26 meteor kernel: mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915]) >> Sep 17 10:35:26 meteor kernel: OOM killer enabled. >> Sep 17 10:35:26 meteor kernel: Restarting tasks ... done. >> Sep 17 10:35:26 meteor kernel: random: crng reseeded on system resumption >> Sep 17 10:35:26 meteor systemd[1502]: Started dbus-:1.2-org.xfce.Xfconf@1.service. >> Sep 17 10:35:26 meteor systemd-sleep[2378]: Failed to put system to sleep. System resumed again: No such file or directory >> Sep 17 10:35:26 meteor kernel: PM: suspend exit >> Sep 17 10:35:26 meteor systemd-sleep[2468]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend >> Sep 17 10:35:26 meteor systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE >> Sep 17 10:35:26 meteor systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. >> Sep 17 10:35:26 meteor systemd[1]: Failed to start System Suspend. >> Sep 17 10:35:26 meteor systemd[1]: Dependency failed for Suspend. >> Sep 17 10:35:26 meteor systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. >> Sep 17 10:35:26 meteor systemd-logind[976]: Operation 'suspend' finished. >> Sep 17 10:35:26 meteor systemd[1]: Stopped target Sleep. >> Sep 17 10:35:26 meteor ModemManager[1079]: <info> [sleep-monitor-systemd] system is resuming >> Sep 17 10:35:26 meteor NetworkManager[1089]: <info> [1726562126.5424] manager: sleep: wake requested (sleeping: yes enabled: yes) >> Sep 17 10:35:26 meteor NetworkManager[1089]: <info> [1726562126.5425] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:28 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error >> Sep 17 10:35:29 meteor ModemManager[1079]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin >> Sep 17 10:35:29 meteor ModemManager[1079]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin >> Sep 17 10:35:29 meteor NetworkManager[1089]: <info> [1726562129.9289] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') >> Sep 17 10:35:29 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down >> Sep 17 10:35:31 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error >> Sep 17 10:35:33 meteor systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.3875] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.3884] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.3887] manager: NetworkManager state is now DISCONNECTED >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4327] device (wlp0s20f3): supplicant interface state: internal-starting -> disconnected >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4327] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', sys-iface-state: 'removed') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4331] Wi-Fi P2P device controlled by interface wlp0s20f3 created >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4333] manager: (p2p-dev-wlp0s20f3): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5) >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4335] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4337] device (wlp0s20f3): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4341] device (p2p-dev-wlp0s20f3): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1404] policy: auto-activating connection 'wlp0s20f3' (ed77ffbb-f7b5-3841-8b21-258e99306b9f) >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1409] device (wlp0s20f3): Activation: starting connection 'wlp0s20f3' (ed77ffbb-f7b5-3841-8b21-258e99306b9f) >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1409] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1413] manager: NetworkManager state is now CONNECTING >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1418] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1422] device (wlp0s20f3): Activation: (wifi) access point 'wlp0s20f3' has security, but secrets are required. >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1422] device (wlp0s20f3): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1425] sup-iface[2dde45278d9b93ec,1,wlp0s20f3]: wps: type pbc start... >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1437] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1440] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1443] device (wlp0s20f3): Activation: (wifi) connection 'wlp0s20f3' has security, and secrets exist. No new secrets needed. >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'ssid' value 'Hundhammer' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'scan_ssid' value '1' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'bgscan' value 'simple:30:-65:300' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'auth_alg' value 'OPEN' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1445] Config: added 'psk' value '<hidden>' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1452] device (wlp0s20f3): supplicant interface state: disconnected -> scanning >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1452] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1955] device (wlp0s20f3): supplicant interface state: scanning -> authenticating >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1955] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: authenticate with c8:0e:14:46:50:44 (local address=28:a0:6b:33:40:fa) >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: send auth to c8:0e:14:46:50:44 (try 1/3) >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2279] device (wlp0s20f3): supplicant interface state: authenticating -> associating >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2279] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: authenticated >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: associate with c8:0e:14:46:50:44 (try 1/3) >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: RX AssocResp from c8:0e:14:46:50:44 (capab=0x1511 status=0 aid=5) >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: associated >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2422] device (wlp0s20f3): supplicant interface state: associating -> associated >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2422] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2493] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2493] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3140] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3141] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Hundhammer" >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3141] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: Limiting TX power to 20 (23 - 3) dBm as advertised by c8:0e:14:46:50:44 >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3359] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3364] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3439] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.178.166, acd pending >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.5129] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.178.166 >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.5134] policy: set 'wlp0s20f3' (wlp0s20f3) as default for IPv4 routing and DNS >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.5196] device (wlp0s20f3): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor systemd[1]: Starting Network Manager Script Dispatcher Service... >> Sep 17 10:35:38 meteor systemd[1]: Started Network Manager Script Dispatcher Service. >> Sep 17 10:35:38 meteor chronyd[1208]: Source 192.168.178.1 online >> Sep 17 10:35:38 meteor chronyd[1208]: Source 85.215.189.120 online >> Sep 17 10:35:38 meteor dns-dnsmasq.sh[2493]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6113] device (wlp0s20f3): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6116] device (wlp0s20f3): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6120] manager: NetworkManager state is now CONNECTED_SITE >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6128] device (wlp0s20f3): Activation: successful, device activated. >> Sep 17 10:35:38 meteor chronyd[1208]: Could not add source 192.168.178.1 : Already in use >> Sep 17 10:35:38 meteor dns-dnsmasq.sh[2520]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:38 meteor dns-dnsmasq.sh[2534]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.7622] manager: NetworkManager state is now CONNECTED_GLOBAL >> Sep 17 10:35:38 meteor chronyd[1208]: Selected source 192.168.178.1 >> Sep 17 10:35:38 meteor dns-dnsmasq.sh[2547]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:39 meteor NetworkManager[1089]: <info> [1726562139.5709] dhcp6 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) >> Sep 17 10:35:39 meteor NetworkManager[1089]: <info> [1726562139.5717] policy: set 'wlp0s20f3' (wlp0s20f3) as default for IPv6 routing and DNS >> Sep 17 10:35:39 meteor NetworkManager[1089]: <info> [1726562139.5833] dhcp6 (wlp0s20f3): state changed new lease >> Sep 17 10:35:39 meteor chronyd[1208]: Could not add source 192.168.178.1 : Already in use >> Sep 17 10:35:39 meteor chronyd[1208]: Added source fd00::ca0e:14ff:fe46:503e >> Sep 17 10:35:39 meteor dns-dnsmasq.sh[2576]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:49 meteor systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. >> Sep 17 10:36:13 meteor sudo[2589]: pam_unix(sudo:session): session opened for user root(uid=0) by sh(uid=1000) >> Sep 17 10:36:13 meteor sudo[2589]: pam_unix(sudo:session): session closed for user root >> Sep 17 10:36:25 meteor sudo[2593]: pam_unix(sudo:session): session opened for user root(uid=0) by sh(uid=1000) It doesn't make a difference if I use "sudo systemctl suspend", select "suspend" from the LightDM menu or from the Xfce4 menu, or if I close the laptop lid. -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1228652] New: ibus-setup-libpinyin crashes on a fresh Leap 15.6
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228652 Bug ID: 1228652 Summary: ibus-setup-libpinyin crashes on a fresh Leap 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- hillwood@hillwood-HP:~> /usr/lib64/ibus/ibus-setup-libpinyin (ibus-setup-libpinyin:13262): Gtk-CRITICAL **: 20:30:15.860: _gtk_css_lookup_resolve: assertion '(((__extension__ ({ GTypeInstance *__inst = (GTypeInstance*) ((provider)); GType __t = ((_gtk_style_provider_private_get_type ())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && __inst->g_class->g_type == __t) __r = (!(0)); else __r = g_type_check_instance_is_a (__inst, __t); __r; }))))' failed /usr/share/ibus-libpinyin/setup/main2.py:78: Warning: g_object_set_data_full: assertion 'G_IS_OBJECT (object)' failed self.__builder.add_from_file("ibus-libpinyin-preferences.ui") (ibus-setup-libpinyin:13262): Gtk-ERROR **: 20:30:15.864: Can't create a GtkStyleContext without a display connection 追踪与中断点陷阱 (核心已转储) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1231048] New: systemd-experimental: error message about homed
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231048 Bug ID: 1231048 Summary: systemd-experimental: error message about homed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If I install systemd-experimental I get the following error message: Failed to preset unit: Unit systemd-homed.service does not exist systemd-homed is not part of systemd-experimental. -- You are receiving this mail because: You are on the CC list for the bug.

1 2