July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 1201963] New: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70°C until it reaches 54°C
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1201963 Bug ID: 1201963 Summary: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70�C until it reaches 54�C Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: gryffus(a)hkfree.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860458 --> https://bugzilla.suse.com/attachment.cgi?id=860458&action=edit Turbostat log output I have a Dell Latitude 5420 laptop and i am experiencing CPU slowdown when using any graphical / CPU demanding application. The laptop contains 11th Gen Intel(R) Core(TM) i5-1145G7 which can do 4,4GHz on turbo. When the system reaches about 70�C, all cores switch to 400MHz and stay there until temperature hits 53-54�C. I can see this behavior especially in Vulkan graphics applications, but not only in them, it just happens almost instantly there, since the 70�C is reached within about 30 seconds there. I would want to raise the temperature limits to at least 80-90�C or disable throttling completely (at my own responsibility of cooking it). But throttling from 70�C seems as a complete nonsense to me - the CPU package gets to this temperature in 10-20 seconds under load, so i basically never make use of the 4,4GHz. What i have tried: 1) Kernel 5.19 from Kernel:HEAD - no change 2) installed throttled ( https://github.com/erpalma/throttled ) - no change 3) blacklisted intel_powerclamp, intel_rapl_msr, processor_thermal_rapl, intel_rapl_common kernel modules - no change 4) cpupower frequency-set -g performance - no change # cat /sys/devices/platform/*/uuids/current_uuid INVALID # cat /sys/devices/platform/*/uuids/available_uuids UNKNOWN # cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.40 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 4.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 3.16 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes # cpupower idle-info CPUidle driver: intel_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 4 Available idle states: POLL C1_ACPI C2_ACPI C3_ACPI POLL: Flags/Description: CPUIDLE CORE POLL IDLE Latency: 0 Usage: 265266 Duration: 8068126 C1_ACPI: Flags/Description: ACPI FFH MWAIT 0x0 Latency: 1 Usage: 10617293 Duration: 1984558460 C2_ACPI: Flags/Description: ACPI FFH MWAIT 0x31 Latency: 253 Usage: 273458 Duration: 261649941 C3_ACPI: Flags/Description: ACPI FFH MWAIT 0x60 Latency: 1048 Usage: 206150 Duration: 509227956 # cpupower info analyzing CPU 0: perf-bias: 0 Turbostat debug log attached. Some further reading with probably related reports: https://www.dell.com/community/Latitude/Latitude-5420-7420-7520-CPU-Throttl… https://github.com/intel/thermal_daemon/issues/341 https://github.com/intel/thermal_daemon/issues/293 https://github.com/erpalma/throttled Any clues? -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[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 1194875] New: GCC 12: ceph package fails
by bugzilla_noreply＠suse.com 15 Dec '22

15 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1194875 Bug ID: 1194875 Summary: GCC 12: ceph package fails 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: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… due to: [ 100s] [ 11%] Building CXX object src/erasure-code/jerasure/CMakeFiles/jerasure_objs.dir/jerasure_init.cc.o [ 101s] In file included from /home/abuild/rpmbuild/BUILD/ceph-16.2.6-463-g22e7612f9ad/src/include/rados/rados_types.hpp:10, [ 101s] from /home/abuild/rpmbuild/BUILD/ceph-16.2.6-463-g22e7612f9ad/src/librados/snap_set_diff.h:8, [ 101s] from /home/abuild/rpmbuild/BUILD/ceph-16.2.6-463-g22e7612f9ad/src/librados/snap_set_diff.cc:6: [ 101s] /home/abuild/rpmbuild/BUILD/ceph-16.2.6-463-g22e7612f9ad/src/include/rados/buffer.h:98:52: error: expected template-name before '<' token [ 101s] 98 | struct unique_leakable_ptr : public std::unique_ptr<T, ceph::nop_delete<T>> { [ 101s] | ^ [ 101s] /home/abuild/rpmbuild/BUILD/ceph-16.2.6-463-g22e7612f9ad/src/include/rados/buffer.h:98:52: error: expected '{' before '<' token [ 101s] /home/abuild/rpmbuild/BUILD/ceph-16.2.6-463-g22e7612f9ad/src/include/rados/buffer.h:374:17: error: 'unique_ptr' in namespace 'std' does not name a template type [ 101s] 374 | static std::unique_ptr<ptr_node, disposer> [ 101s] | ^~~~~~~~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1198762] New: [Raspberry Pi 400] Wired network sometimes doesn't come up on boot (and needs reboot to fix)
by bugzilla_noreply＠suse.com 15 Dec '22

15 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1198762 Bug ID: 1198762 Summary: [Raspberry Pi 400] Wired network sometimes doesn't come up on boot (and needs reboot to fix) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)opensuse.org Found By: --- Blocker: --- The eth0 is detected but the link doesn't come up (also as shown by the switch). Rebooting helps most of the time. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[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 1201074] New: Greybird and Greybird-geeko themes need newer sassc version
by bugzilla_noreply＠suse.com 14 Dec '22

14 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1201074 Bug ID: 1201074 Summary: Greybird and Greybird-geeko themes need newer sassc version Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: maurizio.galli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Newer versions of themes Greybird and Greybird-geeko (default with openSUSE Xfce) fail to build with current sassc version 3.5.0. The errors are resolved with version 3.6.2 in Factory. I'd like to update sassc in openSUSE Leap 15.4 to 3.6.2 to match current Factory. -- You are receiving this mail because: You are on the CC list for the bug.

1 4