July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 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

[Bug 1213181] New: ddclient dose not work for cloudflare
by bugzilla_noreply＠suse.com 11 Sep '24

11 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1213181 Bug ID: 1213181 Summary: ddclient dose not work for cloudflare Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- openSUSE-HW:/home/hillwood # ddclient FATAL: Error loading the Perl module JSON::Any needed for cloudflare update. It's my config: # /etc/ddclient.conf daemon=300 # check every 300 seconds syslog=yes # log update msgs to syslog #mail=root # mail all msgs to root mail-failure=root # mail failed update msgs to root pid=/run/ddclient/ddclient.pid # record PID in file. ssl=yes protocol=cloudflare ttl=1 # use=web # web=checkip.dyndns.org usev6=if, if=br0 login=email password=API Key zone=hillwoodhome.net cloud.home.hillwoodhome.net ddclient 3.10.0 works fine with this config. We should provide an update for Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213521] New: shairport-sync: missing dependency: avahi
by bugzilla_noreply＠suse.com 05 Sep '24

05 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1213521 Bug ID: 1213521 Summary: shairport-sync: missing dependency: avahi Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- openSUSE:Factory/shairport-sync shairport-sync.spec is missing: Requires: avahi Steps to reproduce on a minimal Tumbleweed installation: # zypper in shairport-sync # systemctl start shairport-sync > Failed to start shairport-sync.service: Unit avahi-daemon.service not found. `zypper in avahi` fixes this. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213486] New: [Build 44.3] openQA test fails in fanotify14
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1213486 Bug ID: 1213486 Summary: [Build 44.3] openQA test fails in fanotify14 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/3439183/modules/fano tify14/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-15.4-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@64bit_virtio fails in [fanotify14](https://openqa.opensuse.org/tests/3439183/modules/fanotify14/st… ## Test suite description ## Reproducible Fails since (at least) Build [44.2](https://openqa.opensuse.org/tests/3438422) ## Expected result Last good: [44.1](https://openqa.opensuse.org/tests/3436580) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1213162] New: kf.kio.core: Invalid URL: QUrl("//@/<smtp>.xfb")
by bugzilla_noreply＠suse.com 31 Aug '24

31 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1213162 Bug ID: 1213162 Summary: kf.kio.core: Invalid URL: QUrl("//@/<smtp>.xfb") 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting on 06/272023, probably after installing Tumbleweed snapshot 20230625, I no longer can invite people using korganizer, if the invitation mail address has a format like "lastname, firstname" <opensuse(a)mike.franken.de> "firstname lastname" <opensuse(a)mike.franken.de> "anything" <opensuse(a)mike.franken.de> Using such an address produces the following warning messages in my log: kontact[4212]: kf.kio.core: Invalid URL: QUrl("//@/opensuse@mike.franken.de.xfb") kontact[4212]: kf.kio.core: Invalid URL: QUrl("//@/opensuse@mike.franken.de.ifb") kontact[4212]: kf.kio.core: Invalid URL: QUrl("//@/opensuse@mike.franken.de.vfb") No invitation mail is sent in this case. Using just <opensuse(a)mike.franken.de> works ok. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213154] New: openSUSE/mariadb container stops with non-zero exit code when calling podman stop
by bugzilla_noreply＠suse.com 12 Aug '24

12 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1213154 Bug ID: 1213154 Summary: openSUSE/mariadb container stops with non-zero exit code when calling podman stop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: khanich.opensource(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Steps to reproduce: 1. Start a container, for testing: podman run --detach --env MYSQL_ROOT_PASSWORD=p --name mariadb registry.opensuse.org/opensuse/mariadb:latest 2. wait until initialized 3. Stop the container: podman stop mariadb 4. Check the exit code: podman ls -a; Exited (143) 5. Look at logs: podman logs mariadb example output: -------------------------------------------------------------------------------- Session terminated, killing shell...2023-07-08 22:55:08 0 [Note] mysqld (initiated by: unknown): Normal shutdown 2023-07-08 22:55:08 0 [Note] InnoDB: FTS optimize thread exiting. 2023-07-08 22:55:08 0 [Note] InnoDB: Starting shutdown... 2023-07-08 22:55:08 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool 2023-07-08 22:55:08 0 [Note] InnoDB: Buffer pool(s) dump completed at 230708 22:55:08 2023-07-08 22:55:08 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2023-07-08 22:55:08 0 [Note] InnoDB: Shutdown completed; log sequence number 46456; transaction id 15 2023-07-08 22:55:08 0 [Note] mysqld: Shutdown complete ...killed. -------------------------------------------------------------------------------- This causes trouble when using the image with a systemd service unit since systemd is going to interpret this as a failed unit. The official image from Docker Hub does not experience this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 4