October 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215639] New: Provide the user with a choice of where they want their SWAP partition to be.
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215639 Bug ID: 1215639 Summary: Provide the user with a choice of where they want their SWAP partition to be. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When installing OpenSUSE with multiple internal drives, per https://forums.opensuse.org/t/how-to-transfer-swap-partition-to-os-drive-fr…, the OSTW installer places the SWAP partition on a (seemingly random) secondary internal drive. I don't want this - if I don't select the other drives when asked, it shouldn't touch them (I realize the quoted post states I did, but it refers to a previous installation; I've tested both). Consequently, either don't put the SWAP partiton on another drive unless multiple have been selected (this is the reason for this issue's designation as a bug rather than an enhancement) or allow the user to choose separately where the SWAP partition should be without needing to use the expert partitioner. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1213784] New: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213784 Bug ID: 1213784 Summary: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Target Milestone: --- Found By: --- Blocker: --- When I file a report at opensuse.bugzilla.org and receive a message via e-mail about it, all links in the post direct me to bguzilla.suse.com instead. This is quite the hassle when dealing with frequent notifications on multiple tickets. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213156] New: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213156 Bug ID: 1213156 Summary: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ftake(a)geeko.jp QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This report is created in order to summarize related report caused by the same issues of systemd-xdg-autostart-generator in 15.5. systemd-xdg-autostart-generator is a mechanism to start XDG autostart (e.g., /etc/xdg/autostart) instead of desktop environments. In Leap 15.5, KDE plasma started to use this mechanism. However, due to the following problems, xdg-autostart-generator cannot start desktop files derived from Leap 15.4. Some essential services including IBus does not work in 15.5 (#1211977). * systemd-xdg-autostart-generator inappropriately ignores desktop files with X-GNOME-Autostart-Phase (#1201728) [1] * systemd-xdg-autostart-generator cannot start process that forks another process [2, 3, 4] [1] https://github.com/systemd/systemd/issues/18791 (resolved) [2] https://bugs.kde.org/show_bug.cgi?id=433299 [3] https://github.com/systemd/systemd/pull/20813 (merged) [4] https://github.com/systemd/systemd/issues/27919 (unresolved) FYI: Upstream bug tracker related xdg-autostart https://github.com/systemd/systemd/labels/xdg-autostart Some other fixes also might be necessary for 15.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1215865] New: VUL-0: CVE-2023-0809: mosquitto: excessive memory being allocated based on malicious initial packets that are not CONNECT packets
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215865 Bug ID: 1215865 Summary: VUL-0: CVE-2023-0809: mosquitto: excessive memory being allocated based on malicious initial packets that are not CONNECT packets Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://security-tracker.debian.org/tracker/DSA-5511-1 CVE-2023-0809 Fix excessive memory being allocated based on malicious initial packets that are not CONNECT packets. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215864] New: VUL-0: CVE-2023-3592: mosquitto: memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215864 Bug ID: 1215864 Summary: VUL-0: CVE-2023-3592: mosquitto: memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://security-tracker.debian.org/tracker/DSA-5511-1 CVE-2023-3592 Fix memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213339] New: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1213339 Bug ID: 1213339 Summary: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0 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: vojta.kottas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: When setting up a sqlite database using gda-control-center-6.0 as a test in a folder (/tmp/test_db in my case), the gui crashed and the command line showed that a segmentation fault had occurred. This issue does not happen on other distros. Reproducible: Always Steps to Reproduce: 1. Run gda-control-center-6.0 2. Set up database with sqlite Actual Results: Segmentation fault Expected Results: A database is set up in the specified folder. This all came from me trying to install the Pano extension, which upon install crashed the gnome-shell. I tracked the issue to this github issue: https://github.com/oae/gnome-shell-pano/issues/178 Which further tracks the issue down to a problem with the sqlite3 package on openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1214915] New: Please build Qt5 with configure option -xcb-native-painting
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1214915 Bug ID: 1214915 Summary: Please build Qt5 with configure option -xcb-native-painting 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: Woebbeking(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, this is an experimental feature to let Qt5 paint as Qt4 did. This improves performance of Qt5 applications under X2Go a lot. First this option was enabled by default but some years later it was disabled to reduce the size of the platform plugin libqxcb.so a little bit. You don't have to worry that you brake something if you enable this option as the user also have to set the environment variable QT_XCB_NATIVE_PAINTING to make it work. Thanks in advance! Cheers, André -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215851] New: code generated by swig < 4.0.0 is incompatible with Python 3.12
by bugzilla_noreply＠suse.com 15 Oct '24

15 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1215851 Bug ID: 1215851 Summary: code generated by swig < 4.0.0 is incompatible with Python 3.12 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869858 --> https://bugzilla.suse.com/attachment.cgi?id=869858&action=edit _log.txt Code generated by swig < 4.0.0 (all Leap and SLE) generates code importing `imp` module, which has been deprecated in 3.4 (i.e., in all our supported Pythons 3) and removed in 3.12. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1212995] New: KDE Plasma System Settings's printer module cannot add new printers
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1212995 Bug ID: 1212995 Summary: KDE Plasma System Settings's printer module cannot add new printers Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: sfalken(a)cloverleaf-linux.org Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Overview: Upon attempting to add a new printer in KDE Plasma System Settings, the user is denied permission to do so. Steps to Reproduce: 1) Open System Settings 2) Select Printers 3) Click 'Click here to add a new printer) Actual Results: The window that appears returns no printers and says at the top: "Failed to get a list of devices: 'Forbidden'" Expected Results: The window returns a list of printers and allows you to add them Build date: openSUSE Kalpa 20230619 Additional Information: * This does occur on openSUSE Aeon; the built in printer settings work as expected. * Currently this can be worked around by navigating to https://localhost:631 and adding a printer through the CUPS interface, logging in as the root user when prompted. This implies that it is a permissions issue. * This bug also occurs in openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213446] New: connecting dock station network enables wifi - reverse behaviour
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1213446 Bug ID: 1213446 Summary: connecting dock station network enables wifi - reverse behaviour Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Dell XPS 9700 I have a Dell WD19 dock. It used to work fine. Now when I have e dock station connected with the cable there WIFI is disabled as it should When I unplug Ethernet cable from the dock the wifi remains OFF and RFKILL shows hard block. When I plug the Ethernet cable back to the dock the wifi comes up for 2-3 seconds and sets up a connection and then I get e message that wifi gets disabled and connection is switched back to Ethernet. It used to work fine that unplugging the cable from dock would bring the wifi up. So having a dock station it is not possible to disconnect its ethernet and have laptop enable Wifi. It works ok in Ubuntu. -- You are receiving this mail because: You are on the CC list for the bug.

1 1