September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185613] New: groff: .Os macro uses BSD as default
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1185613 Bug ID: 1185613 Summary: groff: .Os macro uses BSD as default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: sbrabec(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: werner(a)suse.com Found By: --- Blocker: --- The .Os macro in man pages when used without parameters produces "BSD". The built-in default for "doc-default-operating-system" in groff needs to be changed, ideally to read /etc/os-release. # man ssh|tail -1 BSD July 15, 2020 BSD # (. /etc/os-release; echo .ds doc-default-operating-system $PRETTY_NAME) >> /usr/share/groff/site-tmac/mdoc.local tw-systemd:/tmp # man ssh|tail -1 openSUSE Tumbleweed July 15, 2020 openSUSE Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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 1199270] New: Chromium 100.0.4896.127 high GPU usage after resume (NVIDIA)
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199270 Bug ID: 1199270 Summary: Chromium 100.0.4896.127 high GPU usage after resume (NVIDIA) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: denni.granata(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Chromium browser GPU escalation when resumed from suspend to RAM. How to duplicate: Open Chromium Browse the web Put the PC in susped to RAM Resume Wait for some seconds Open the Chromium task manager (Shift+Esc) Find the GPU process and observe it raises above 100% Kill the process or your GPU fan will go crazy. OpenSUSE Tumbleweed 20220503 Chromium 100.0.4896.127 Nvidia-GfxG06 510.68.02-7.1 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 12 �� Intel�� Core�� i7-9750H CPU @ 2.60GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1198137] New: [Build 6.44] openQA test fails in sshd: busybox- packages in the repo
by bugzilla_noreply＠suse.com 18 Dec '22

18 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1198137 Bug ID: 1198137 Summary: [Build 6.44] openQA test fails in sshd: busybox- packages in the repo Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/2283453/modules/sshd /steps/24 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: lubos.kocman(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dcermak(a)suse.com, mlin(a)suse.com Found By: openQA Blocker: Yes busybox-foo packages are provided as alternatives to packages like e.g. coreutils and psmisc, but zypper picks them by default because they are earlier in the alphabet. This breaks installing packages which explicitly require the non-busybox variant and will also cause other issues. Like in SLE, the busybox- packages must not be visible to users, only inside OBS, because the distro is not prepared for that yet. ## Observation openQA test in scenario opensuse-15.4-JeOS-for-kvm-and-xen-x86_64-jeos@64bit_virtio-2G fails in [sshd](https://openqa.opensuse.org/tests/2283453/modules/sshd/steps/24) ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [6.28](https://openqa.opensuse.org/tests/2263801) ## Expected result Last good: [6.24](https://openqa.opensuse.org/tests/2258177) (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 11

[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 1201521] New: chromium crashes when using 'control your music, videos and more' functionality
by bugzilla_noreply＠suse.com 17 Dec '22

17 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201521 Bug ID: 1201521 Summary: chromium crashes when using 'control your music, videos and more' functionality Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: piotr.turski(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- whenver i try to control music played inside chromium (youtube, internet radio, etc), entire chromium crashes Version 103.0.5060.114 (openSUSE Build) stable (64-bit) [0714/160405.242542:ERROR:elf_dynamic_array_reader.h(64)] tag not found Received signal 11 SEGV_MAPERR 000000000008 #0 0x55c0a51062e9 base::debug::CollectStackTrace() #1 0x55c0a515ce86 base::debug::StackTrace::StackTrace() #2 0x55c0a51067b1 base::debug::(anonymous namespace)::StackDumpSignalHandler() #3 0x7effc534a7c0 (/usr/lib64/libc.so.6+0x567bf) #4 0x55c0a8b83ad1 media_router::MediaRouterUI::~MediaRouterUI() #5 0x55c0a8b83cc1 media_router::MediaRouterUI::~MediaRouterUI() #6 0x55c0a8d2fed9 MediaItemUIDeviceSelectorView::~MediaItemUIDeviceSelectorView() #7 0x55c0a8d30091 MediaItemUIDeviceSelectorView::~MediaItemUIDeviceSelectorView() #8 0x55c0a846a505 views::View::~View() #9 0x55c0a92118f1 global_media_controls::MediaItemUIView::~MediaItemUIView() #10 0x55c0a846a505 views::View::~View() #11 0x55c0a846aab1 views::View::~View() #12 0x55c0a846a505 views::View::~View() #13 0x55c0a84dec93 views::ScrollView::Viewport::~Viewport() #14 0x55c0a846a505 views::View::~View() #15 0x55c0a920e7b1 global_media_controls::MediaItemUIListView::~MediaItemUIListView() #16 0x55c0a846a505 views::View::~View() #17 0x55c0a83eca52 views::BubbleDialogDelegateView::~BubbleDialogDelegateView() #18 0x55c0a8d29a51 MediaDialogView::~MediaDialogView() #19 0x55c0a8488fa5 views::WidgetDelegate::DeleteDelegate() #20 0x55c0a847a70e views::Widget::OnNativeWidgetDestroyed() #21 0x55c0a849a160 views::NativeWidgetAura::OnWindowDestroyed() #22 0x55c0a6ab84d6 aura::Window::~Window() #23 0x55c0a6ab8ac1 aura::Window::~Window() #24 0x55c0a50bc51c base::TaskAnnotator::RunTaskImpl() #25 0x55c0a50d72ef base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl() #26 0x55c0a50d7ad0 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() #27 0x55c0a50609db base::MessagePumpGlib::Run() #28 0x55c0a50d62bf base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run() #29 0x55c0a50946fb base::RunLoop::Run() #30 0x55c0a145f32c content::BrowserMainLoop::RunMainMessageLoop() #31 0x55c0a1461ba5 content::BrowserMainRunnerImpl::Run() #32 0x55c0a145cce3 content::BrowserMain() #33 0x55c0a47b5aa9 content::RunBrowserProcessMain() #34 0x55c0a47b5cf4 content::ContentMainRunnerImpl::RunBrowser() #35 0x55c0a47b74fc content::ContentMainRunnerImpl::Run() #36 0x55c0a47b462a content::RunContentProcess() #37 0x55c0a47b508f content::ContentMain() #38 0x55c09f18b4d7 ChromeMain #39 0x7effc53345b0 __libc_start_call_main #40 0x7effc5334679 __libc_start_main_alias_2 #41 0x55c09f18b335 _start r8: 0000000000000001 r9: 0000000000000000 r10: 00007ffcb7db6080 r11: 0000000000be17a6 r12: 0000000000000000 r13: 000025bc0fc46770 r14: 0000000000000000 r15: 000025bc11e7b480 di: 000025bc0bdb0100 si: 000025bc0bdaef88 bp: 00007ffcb7c12940 bx: 000025bc0bdaef80 dx: 000025bc0bf19fd0 ax: 0000000000000000 cx: 0000000000000000 sp: 00007ffcb7c12920 ip: 000055c0a8b83ad1 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000008 [end of stack trace] Segmentation fault (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1194200] New: org-read-date function in emacs fails to parse input string containing capital letters in TBLFM line
by bugzilla_noreply＠suse.com 17 Dec '22

17 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194200 Bug ID: 1194200 Summary: org-read-date function in emacs fails to parse input string containing capital letters in TBLFM line Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: buntu(a)bonhomierch.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 854888 --> http://bugzilla.opensuse.org/attachment.cgi?id=854888&action=edit Org mode test file using org-read-date in TBLFM The function, org-read-date, fails to produce a correct output date when given a string parameter containing uppercase such as "-Thu" when used in a Calc formula. See attached test org-mode file for complete version information. See also https://www.reddit.com/r/orgmode/comments/rruunf/comment/hqpsjlm/?utm_sourc… Uppercase-containing input: | Date: | Friday 12/31/2021 | *unexpected* | | Date: | Friday 12/31/2021 | *unexpected* | #+TBLFM: @1$2='(format-time-string "%A %m/%d/%Y" (org-read-date nil t "-Wed"))::@2$2='(format-time-string "%A %m/%d/%Y" (org-read-date nil t "-Thu")) Lowercase input: | Date: | Wednesday 12/29/2021 | *expected* | | Date: | Thursday 12/30/2021 | *expected* | #+TBLFM: @1$2='(format-time-string "%A %m/%d/%Y" (org-read-date nil t "-wed"))::@2$2='(format-time-string "%A %m/%d/%Y" (org-read-date nil t "-thu")) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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 1203800] New: Recent Kernel Updates (likely) broke backintime
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203800 Bug ID: 1203800 Summary: Recent Kernel Updates (likely) broke backintime Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dsims(a)usa.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Did some updates on 9/21 to a newer kernel 5.3.18-150300.59.93-default. Previous kernel was 5.3.18-150300.59.90-default. Now the backup application "backintime" (which was running nicely for many months) suddenly will not launch. Back In Time Version: 1.2.1 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 177, in activate_name_owner return self.get_name_owner(bus_name) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 363, in get_name_owner 's', (bus_name,), **keywords) File "/usr/lib/python3.6/site-packages/dbus/connection.py", line 653, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'net.launchpad.backintime.serviceHelper': no such name During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/backintime/qt/app.py", line 1592, in <module> cfg = backintime.startApp('backintime-qt') File "/usr/share/backintime/common/backintime.py", line 521, in startApp return getConfig(args, False) File "/usr/share/backintime/common/backintime.py", line 669, in getConfig cfg = config.Config(config_path = args.config, data_path = args.share_path) File "/usr/share/backintime/common/config.py", line 279, in __init__ self.setupUdev = tools.SetupUdev() File "/usr/share/backintime/common/tools.py", line 1715, in __init__ conn = bus.get_object(SetupUdev.CONNECTION, SetupUdev.OBJECT) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 243, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python3.6/site-packages/dbus/proxies.py", line 250, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 182, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/python3.6/site-packages/dbus/bus.py", line 280, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/python3.6/site-packages/dbus/connection.py", line 653, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program net.launchpad.backintime.serviceHelper: Permission denied I have tried several "fixes". None seem to work. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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