October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1191244] New: USB speaker working when plugged while system is up but not on reboot
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191244 Bug ID: 1191244 Summary: USB speaker working when plugged while system is up but not on reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: peter.stark(a)storck.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have multiple raspberry PI 4Bs with openSUSE Leap 15.3 and some with raspbian 9. I got a USB speaker (e2b7:0811) which I connected to the 4Bs using Leap 15.3. This speaker works fine when I plug it in when the PI is already running: rpi15:~ # uname -a Linux rpi15 5.3.18-59.24-default #1 SMP Mon Sep 13 15:06:42 UTC 2021 (2f872ea) aarch64 aarch64 aarch64 GNU/Linux rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 007: ID e2b7:0811 Jie Li CD002 Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 [Sa Okt 2 10:56:09 2021] usb 1-1.2: USB disconnect, device number 4 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 6 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 7 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has no interface number 0 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device found, idVendor=e2b7, idProduct=0811, bcdDevice= 1.00 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Product: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Manufacturer: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: SerialNumber: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: 9:1: bogus dB values (-12800/-12700), disabling dB reporting [Sa Okt 2 10:56:17 2021] input: CD002 CD002 as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.3/0003:E2B7:0811.0003/input/input1 However, after a reboot with the device still connected (no change) the kernel boots and does not even see the device. rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 rpi15:~ # I have tried the same USB speaker on another PI4B with Leap 15.3 with the same result. So, it doesn't seem to be that PI. When I connect the speaker to a PI3 with raspbian 9, it works as expected. root@rpi13:~# dmesg -T |grep 1-1.3 [Sa Okt 2 10:33:08 2021] usb 1-1.3: new full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:33:08 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0001/input/input0 [Sa Okt 2 10:42:57 2021] usb 1-1.3: reset full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:42:58 2021] usb 1-1.3: USB disconnect, device number 4 [Sa Okt 2 10:42:58 2021] usb 1-1.3: 9:1: cannot get min/max values for control 2 (id 9) [Sa Okt 2 10:43:04 2021] usb 1-1.3: new full-speed USB device number 6 using dwc_otg [Sa Okt 2 10:43:04 2021] usb 1-1.3: device descriptor read/64, error -32 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:43:04 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0002/input/input1 I noticed that the raspbian uses dwc_otg vs. xhci_hcd on Leap. However, dwc_otg doesn't seem to be a separate module in raspbian nor it is available on leap. As the speaker is working when I un-plug and plug it in again, I wonder what may causes this strange behavior. Especially as I do not see the device via lsusb after reboot, though it is still connected. Any ideas on how to fix it? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1187951] New: Contacts synchronization not working for google
by bugzilla_noreply＠suse.com 17 Dec '22

17 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187951 Bug ID: 1187951 Summary: Contacts synchronization not working for google Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running latest TW with Contacts Version 5.17.2 (21.04.2) I noticed that around 25% of ma contacts on google is missing. Tried refreshing the collection, but that did not help. Finally I deleted the addressbook and created a new one. Some error messages occured: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fbf4c1bb420) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fbf4c1bb420) identified as "AgentBaseChangeRecorder - 94763683329824" kf.coreaddons: Trying to attach UI delegate: KIO::JobUiDelegate(0x564c71fc43b0) to job KJob(0x564c71ff4270) but this delegate is already attached to a different job KIO::OpenUrlJob(0x564c71fc9520) kf.calendarcore: Invalid dtStart kf.calendarcore: Invalid dtStart kf.calendarcore: Invalid dtStart kf.calendarcore: Invalid dtStart (some more....) kf.calendarcore: Invalid dtStart kf.calendarcore: Invalid dtStart org.kde.pim.akonadiserver: Error while handling command DeleteItems on connection akonadi_google_resource_1 (0x55b7f4780580) org.kde.pim.akonadicore: Deleting items from the akonadi database failed: "No items found" org.kde.kgapi: Requested resource does not exist org.kde.kgapi: Requested resource does not exist org.kde.kgapi: Requested resource does not exist (some more as well) org.kde.kgapi: Requested resource does not exist org.kde.kgapi: Requested resource does not exist org.kde.kgapi: Bad request, Google replied ' "Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration." ' org.kde.pim.google: Got error: KGAPI2::ContactFetchPhotoJob(0x562fe53147d0) "Fehlerhafte Anfrage." The API change seems to be the issue..... Reported upstream https://bugs.kde.org/show_bug.cgi?id=439285 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1188923] New: Mate-Panel system-tray shows double icons for NetworkManager-applet
by bugzilla_noreply＠suse.com 17 Dec '22

17 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188923 Bug ID: 1188923 Summary: Mate-Panel system-tray shows double icons for NetworkManager-applet 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: mateleap(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 851435 --> http://bugzilla.opensuse.org/attachment.cgi?id=851435&action=edit Screenshot of the double icons for networkmanager applet in Mate-Panel system-tray Upon logging-in to Mate desktop environment on openSUSE Leap 15.3 (x86_64), NetworkManager-applet (gtk) icon appears twice i.e. double icon in Mate-Panel system-tray. After long search, it looks like this bug is a result of the built-in support of libappindicator3.so.1()(64bit) for package NetworkManager-applet-1.8.24-5.2.x86_64.rpm. This bug also can be generated in another distribution such as Ubuntu Mate because Ubuntu's nm-applet is built with appindicator support. However, this bug cannot be generated with Debian because Debian's nm-applet is not built with appindicator support. Mate-Panel could be patched to prevent this bug. I found the following code and it could be a soultion or a work-around for this bug. I'm neither a coder not a software developer, thus the package maintainer review on the below code is necessary. public void register_status_notifier_item(string service, BusName sender) { var is_path = (service[0]=='/') ? true : false; string path, name; if (is_path) { name = (string)sender; path = service; } else { name = service; path = "/StatusNotifierItem"; } var id = get_id(name,path); if (id in name_watcher) { warning("Trying to register already registered item. Reregistering new..."); remove(id); } var name_handler = Bus.watch_name(BusType.SESSION,name,GLib.BusNameWatcherFlags.NONE, ()=>{ try { ItemIface ping_iface = Bus.get_proxy_sync(BusType.SESSION,name,path); ping_iface.notify.connect((pspec)=>{ if (ping_iface.id == null || ping_iface.title == null || ping_iface.id.length <= 0 || ping_iface.title.length <= 0) remove(get_id(name,path)); }); } catch (Error e) {remove(get_id(name,path));} }, () => {remove(get_id(name,path));} ); name_watcher.insert(id,name_handler); status_notifier_item_registered(id); this.notify_property("registered-status-notifier-items"); } -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1093592] New: redshift doesn't work after geoclue2 update
by bugzilla_noreply＠novell.com 16 Dec '22

16 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 Bug ID: 1093592 Summary: redshift doesn't work after geoclue2 update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmarcoux(a)posteo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 770512 --> http://bugzilla.opensuse.org/attachment.cgi?id=770512&action=edit redshift error Hello, I updated to the latest snapshot (2018 05 15) and since then, redshift with geoclue2 doesn't work. After launching, it displays an error (see attachment). This wasn't happening with the previous snapshot I had, but I'm not sure which one. The issue seems to arise due to changes within the recent revisions of the geoclue2 package, so as far as 2 months ago. So by looking at the snapshots, I suspect it is in one of those: - 2018 03 04 - 2018 04 24 - 2018 05 11 - 2018 05 13 The workaround is to provide the latitude and longitude manually with the option -l. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1181533] New: Is not possible to set date with UTC format and 2038 year using hwclock
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1181533 Bug ID: 1181533 Summary: Is not possible to set date with UTC format and 2038 year using hwclock Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ionut_n2001(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi SUSE Team, I try to set date with UTC format and 2038 Year. This is not working. Steps for reproduce: # date -s "Jan 20 15:42:59 UTC 2038" # hwclock -w # hwclock -s hwclock: settimeofday() failed: Invalid argument -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1173319] New: Move /etc/logrotate.d/* to /usr/etc/logrotate.d
by bugzilla_noreply＠suse.com 15 Dec '22

15 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1173319 Bug ID: 1173319 Summary: Move /etc/logrotate.d/* to /usr/etc/logrotate.d Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm currently working on the config file switch /etc --> /usr/etc (find Details on https://en.opensuse.org/openSUSE:Packaging_UsrEtc) and now I'm wondering what should be done with /etc/logrotate.d/* files. Thorsten Kukuk: Somebody need to rewrite logrotate first. ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1144506] New: sphinx-build requires python-attrs to run but does not require it
by bugzilla_noreply＠novell.com 14 Dec '22

14 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1144506 Bug ID: 1144506 Summary: sphinx-build requires python-attrs to run but does not require it Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dcermak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The sphinxcontrib-autopgrogram and sphinxcontrib-asyncio packages started to fail to build on OBS with the following error: [ 43s] + sphinx-build -b html -d doc/_build/doctrees doc doc/_build/html [ 43s] Traceback (most recent call last): [ 43s] File "/usr/bin/sphinx-build", line 6, in <module> [ 43s] from pkg_resources import load_entry_point [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3241, in <module> [ 43s] @_call_aside [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3225, in _call_aside [ 43s] f(*args, **kwargs) [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3254, in _initialize_master_working_set [ 43s] working_set = WorkingSet._build_master() [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 583, in _build_master [ 43s] ws.require(__requires__) [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 900, in require [ 43s] needed = self.resolve(parse_requirements(requirements)) [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 786, in resolve [ 43s] raise DistributionNotFound(req, requirers) [ 43s] pkg_resources.DistributionNotFound: The 'attrs' distribution was not found and is required by packaging [ 43s] error: Bad exit status from /var/tmp/rpm-tmp.tYlY4G (%build) Both invoke sphinx-build during %build. For some reason sphinx-build appears to require python-attrs now, but this is not reflected in the rpm. Thus OBS does not know about this dependency and leaves out python-attrs out of the buildroot (thereby causing the above error). Affected packages: - https://build.opensuse.org/package/show/devel:languages:python/python-sphin… - https://build.opensuse.org/package/show/devel:languages:python/python-sphin… -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1111657] New: python-cffi build fail with glibc maintenance update
by bugzilla_noreply＠novell.com 14 Dec '22

14 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1111657 Bug ID: 1111657 Summary: python-cffi build fail with glibc maintenance update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With glibc maintenance update https://build.opensuse.org/request/show/639803 , python-cffi build failed due to it can not pass unittest[1]. Both package are from SLE. [1] https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.1:Stagin… -- You are receiving this mail because: You are on the CC list for the bug.

2 31

[Bug 1177900] New: openSUSE Tumbleweed: Boot from Live ISO - only emergency mode
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177900 Bug ID: 1177900 Summary: openSUSE Tumbleweed: Boot from Live ISO - only emergency mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Live Medium Assignee: dimstar(a)opensuse.org Reporter: adrian.feliks(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0 Build Identifier: All Tumbleweed versions do not start when booting from the ISO image by Grub2 ("iso-scan/filename=$iso_path") Stuck in Emergency Mode. I tested on my laptop and in QEMU (EFI and bios). Last time it was ok. openSUSE Leap 15.2 boots correctly. openSUSE-Tumbleweed-*-Live-x86_64-Snapshot20201014-Media.iso openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20201014-Media.iso Grub config file: https://github.com/Mexit/MultiOS-USB/blob/master/config/openSUSE/openSUSE-L… Reproducible: Always Actual Results: Stuck in Emergency Mode Expected Results: Starts to the desktop I attach a screenshot and rdsosreport.txt -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1149754] New: Translations are good!
by bugzilla_noreply＠novell.com 12 Dec '22

12 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1149754 Bug ID: 1149754 Summary: Translations are good! Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: snwint(a)suse.com QA Contact: ke(a)suse.com Found By: --- Blocker: --- Weblate creates automated github commits that unfortunately don't align to the usual workflow as there a bugzilla (or jira) reference is required. So I've created this bug to auto-add its number to every Weblate commit message. -- You are receiving this mail because: You are on the CC list for the bug.

2 12