September 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1214913] New: jhead deletes EXIF data
by bugzilla_noreply＠suse.com 13 Nov '23

13 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1214913 Bug ID: 1214913 Summary: jhead deletes EXIF data Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bob(a)vickers.simplyms.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869225 --> https://bugzilla.suse.com/attachment.cgi?id=869225&action=edit Image before rotation jhead version 3.06.0.1-bp155.4.6 deletes EXIF data when rotating images. $ exiftool rotated.jpg | wc -l 92 $ jhead -autorot rotated.jpg Nonfatal Error : 'rotated.jpg' Command has invalid characters. $ exiftool rotated.jpg | wc -l 23 I found a report for this bug on an Debian site: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023303 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213702] New: VUL-0: CVE-2023-38285: modsecurity: DoS Vulnerability in Four Transformations
by bugzilla_noreply＠suse.com 13 Nov '23

13 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1213702 Bug ID: 1213702 Summary: VUL-0: CVE-2023-38285: modsecurity: DoS Vulnerability in Four Transformations Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache Assignee: apache-bugs(a)suse.de Reporter: gianluca.gabrielli(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Vulnerability Details Included in ModSecurity functionality are dozens of transformation actions which support altering the representation of values so that further processing can be done on the modified values. This may be either more convenient to work with, or less prone to rule evasion. The ModSecurity team was recently alerted to a possible DoS issue in four of these transformations in ModSecurity v3. Thanks to the reporter for the investigation and for responsibly disclosing the issue. The affected transformations are: removeWhitespace, removeNull, replaceNull, and removeCommentsChar. The affected transformations were functionally correct. However, the implemented solutions would be inefficient if a malicious user were to submit a specially crafted HTTP request that triggered worst-case performance. The most dramatic delays can typically be prevented through common configuration items such as SecRequestBodyNoFilesLimit with the default value of 131072 suggested in modsecurity.conf-recommended. However, even with this limit in place, a dozen or more executions of these transformations could result in multiple seconds of delay for a single HTTP transaction. If a large enough number of such malicious requests are running simultaneously, this could render the webserver unable to respond to legitimate requests in a timely manner. Mitigation For installations where immediate upgrade to the new version of the software is impractical, some mitigation possibilities are available. The nature of the issue results in large values causing a much greater effect on resources than numerous smaller values. A separate ModSecurity rule could be included to limit the size of each value to be processed, but still allow legitimate content to be processed unimpeded. For example, if there are many rules with the affected transformations executing against the ARGS collection, a rule such as the following could be included before other phase 2 rules: SecRule ARGS "@gt 16000" "id:1,phase:2,t:length,deny,status:403,msg:’ARG exceeds length limit'" Optionally, combined with further reducing the configured value for SecRequestBodyNoFilesLimit, potential delays precipitated by worst-case input can be significantly reduced. References https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity… https://github.com/SpiderLabs/ModSecurity/commit/ab5658f2d4cfa5126db256cf3f… -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215647] New: [aarch64][LenovoX13s] Need to install DTB on ESP since NO ACPI support for Linux on X13s
by bugzilla_noreply＠suse.com 10 Nov '23

10 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215647 Bug ID: 1215647 Summary: [aarch64][LenovoX13s] Need to install DTB on ESP since NO ACPI support for Linux on X13s Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: chester.lin(a)suse.com Reporter: chester.lin(a)suse.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, guillaume.gardet(a)arm.com, ivan.ivanov(a)suse.com, jlee(a)suse.com, mbenes(a)suse.com, mbrugger(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Plan to submit a new package arm64laptop-firmware-dt in hardware:boot and then openSUSE:Factory, which installs sc8280xp-lenovo-thinkpad-x13s.dtb on ESP since the Lenovo X13s' ACPI doesn't support Linux and its UEFI FW has to preload the DTB file from ESP and then apply some runtime DT overlays before booting to grub2 and then Linux. Without preloading the DTB, the system wouldn't boot since the UEFI FW does not contain a default DTB. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215341] New: devel:gcc/binutils: devel subpackage should depend on zstd-devel
by bugzilla_noreply＠suse.com 09 Nov '23

09 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215341 Bug ID: 1215341 Summary: devel:gcc/binutils: devel subpackage should depend on zstd-devel Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: matz(a)suse.com Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: screening-team-bugs(a)suse.de CC: rguenther(a)suse.com Target Milestone: --- Found By: --- Blocker: --- As zstd compression is enabled for current distribution versions, the devel package should also pull in zstd-devel ``` %if %{suse_version} > 1500 BuildRequires: libzstd-devel %endif ``` -> ``` %package devel ... %if %{suse_version} > 1500 Requires: libzstd-devel %endif ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215699] New: drbd: fix build error against kernel v6.5.4
by bugzilla_noreply＠suse.com 08 Nov '23

08 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215699 Bug ID: 1215699 Summary: drbd: fix build error against kernel v6.5.4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: heming.zhao(a)suse.com QA Contact: qa-bugs(a)suse.de CC: qa-bugs(a)suse.de, zzhou(a)suse.com Depends on: 1206791 Target Milestone: --- Found By: --- Blocker: --- some KAPIs changed and was blocking drbd building for kernel v6.4.5. create this bug for passing build drbd on v6.4.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215617] New: GNOME Software shows failed to build result for 362301da643102b9f38477387e2193e57abaa590
by bugzilla_noreply＠suse.com 06 Nov '23

06 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215617 Bug ID: 1215617 Summary: GNOME Software shows failed to build result for 362301da643102b9f38477387e2193e57abaa590 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: philip.raets(a)telenet.be QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading tumbleweed 20230920, GNOME software on each login shows the following warning: failed to build result for 362301da643102b9f38477387e2193e57abaa590 according to https://github.com/fwupd/fwupd/issues/6101 it is an issue with fwupd and needs to be updated. In Tumbleweed the version of fwupd is 1.8.17. Is there an option that we can get the latest version? Thanks, Philip -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1214988] New: btrfs-cleaner hangs and: watchdog: BUG: soft lockup - CPU#8 stuck for
by bugzilla_noreply＠suse.com 06 Nov '23

06 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1214988 Bug ID: 1214988 Summary: btrfs-cleaner hangs and: watchdog: BUG: soft lockup - CPU#8 stuck for Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: diego.ercolani(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In my system I use btrfs and sometimes I have this entry in journal: Sep 05 09:52:53 pc-diego kernel: watchdog: BUG: soft lockup - CPU#8 stuck for 26s! [btrfs-cleaner:2833] Sep 05 09:52:53 pc-diego kernel: Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache netfs rfcomm tcp_diag inet_diag af_packet 8021q garp m> Sep 05 09:52:53 pc-diego kernel: platform_profile syscopyarea rfkill mdio_devres sysfillrect snd sysimgblt irqbypass video pcspkr efi_pstore(N) wmi_bmof> Sep 05 09:52:53 pc-diego kernel: Supported: No, Proprietary and Unsupported modules are loaded Sep 05 09:52:53 pc-diego kernel: CPU: 8 PID: 2833 Comm: btrfs-cleaner Tainted: P OE X N 5.14.21-150500.55.19-default #1 SLE15-SP5 a29285bac85> Sep 05 09:52:53 pc-diego kernel: Hardware name: System manufacturer System Product Name/PRIME B450M-A, BIOS 3002 03/10/2021 Sep 05 09:52:53 pc-diego kernel: RIP: 0010:generic_bin_search.constprop.31+0xc4/0x190 [btrfs] Sep 05 09:52:53 pc-diego kernel: Code: 92 52 36 e9 48 c1 ff 06 48 c1 e7 0c 48 01 f8 49 8b 7d 00 48 01 d7 81 e7 ff 0f 00 00 48 8d 3c 38 4c 89 fe e8 9e f7 > Sep 05 09:52:53 pc-diego kernel: RSP: 0018:ffffb672c8063b00 EFLAGS: 00000286 Sep 05 09:52:53 pc-diego kernel: RAX: 00000000ffffffff RBX: 0000000000000033 RCX: 000000000000006c Sep 05 09:52:53 pc-diego kernel: RDX: 00000000000009f6 RSI: ffffb672c8063bef RDI: ffff99a90581b560 Sep 05 09:52:53 pc-diego kernel: RBP: 0000000000000036 R08: ffffb672c8063b98 R09: 0000000000000000 Sep 05 09:52:53 pc-diego kernel: R10: 0000000000000001 R11: ffff99a850d23e78 R12: 0000000000000031 Sep 05 09:52:53 pc-diego kernel: R13: ffff99a850d23e00 R14: 0000000000000019 R15: ffffb672c8063bef Sep 05 09:52:53 pc-diego kernel: FS: 0000000000000000(0000) GS:ffff99b2bec00000(0000) knlGS:0000000000000000 Sep 05 09:52:53 pc-diego kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 05 09:52:53 pc-diego kernel: CR2: 00007f6ae7b3c000 CR3: 0000000ba9a10000 CR4: 00000000003506e0 Sep 05 09:52:53 pc-diego kernel: Call Trace: Sep 05 09:52:53 pc-diego kernel: <TASK> Sep 05 09:52:53 pc-diego kernel: btrfs_search_slot+0x400/0x920 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: btrfs_lookup_file_extent+0x4a/0x70 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: btrfs_get_extent+0x141/0x870 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? __x86_return_thunk+0x5/0x6 Sep 05 09:52:53 pc-diego kernel: ? lock_extent_bits+0x4a/0xa0 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: defrag_lookup_extent+0xcf/0x120 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: btrfs_defrag_file+0x90a/0x1230 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? __x86_return_thunk+0x5/0x6 Sep 05 09:52:53 pc-diego kernel: ? __x86_return_thunk+0x5/0x6 Sep 05 09:52:53 pc-diego kernel: ? btrfs_iget_path+0x67/0x700 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? btrfs_get_root_ref+0x18d/0x310 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? btrfs_run_defrag_inodes+0x27c/0x360 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? __x86_return_thunk+0x5/0x6 Sep 05 09:52:53 pc-diego kernel: btrfs_run_defrag_inodes+0x221/0x360 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: cleaner_kthread+0xec/0x130 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? csum_one_extent_buffer+0x110/0x110 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: kthread+0x156/0x180 Sep 05 09:52:53 pc-diego kernel: ? set_kthread_struct+0x50/0x50 Sep 05 09:52:53 pc-diego kernel: ret_from_fork+0x22/0x30 Sep 05 09:52:53 pc-diego kernel: </TASK> I think the problem is related on some issue on a btrfs filesystem but I don't know on wich as every "btrfs scrub" finish correctly: pc-diego:~ # mount | grep btrfs /dev/mapper/raid-rootfs on / type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=256,subvol=/@) /dev/mapper/raid-usr on /usr type btrfs (rw,relatime,compress=zstd:9,space_cache,autodefrag,subvolid=5,subvol=/) /dev/mapper/raid-usr on /usr/local type btrfs (rw,relatime,compress=zstd:9,space_cache,autodefrag,subvolid=257,subvol=/local) /dev/mapper/raid-rootfs on /root type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=260,subvol=/@/root) /dev/mapper/raid-rootfs on /srv type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=259,subvol=/@/srv) /dev/mapper/raid-rootfs on /var type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=257,subvol=/@/var) /dev/mapper/raid-boot on /boot type btrfs (rw,relatime,space_cache,subvolid=5,subvol=/) /dev/sdc1 on /M2 type btrfs (rw,relatime,compress=zlib:3,ssd,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-var_lib_systemd_coredump on /var/lib/systemd/coredump type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-openwrt on /opt/openwrt type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-OVA on /dati/OVA type btrfs (rw,relatime,compress=zlib:9,space_cache,subvolid=5,subvol=/) /dev/mapper/raid-ISO on /dati/ISO type btrfs (rw,relatime,compress=zlib:3,space_cache,autodefrag,subvolid=5,subvol=/) /dev/mapper/nonraid-akonadi_data on /home/SSISNET/diego/.local/share/akonadi type btrfs (rw,noatime,compress=zstd:9,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-var_tmp on /var/tmp type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-NextCloud on /home/SSISNET/diego/Nextcloud type btrfs (rw,noatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/raid-virtualmachines on /dati/virtualmachines type btrfs (rw,relatime,compress=zstd:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-tmp on /tmp type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/raid-samba on /dati/samba type btrfs (rw,relatime,compress=zlib:3,space_cache,autodefrag,subvolid=5,subvol=/) /dev/mapper/nonraid-baloo on /home/SSISNET/diego/.local/share/baloo type btrfs (rw,relatime,compress=zstd:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-var_log on /var/log type btrfs (rw,relatime,compress=zstd:3,space_cache=v2,autodefrag,subvolid=5,subvol=/) /dev/mapper/nonraid-var_cache on /var/cache type btrfs (rw,relatime,compress=zstd:3,space_cache,subvolid=5,subvol=/) /dev/bcache0 on /dati/virtualmachines/nonraid/bcache type btrfs (rw,noatime,compress=zlib:3,ssd,space_cache,subvolid=5,subvol=/) the processlist is full of btrfs-cleaner but I don't know how to undestand which partition raise the problem: pc-diego:~ # ps axuww | grep btrfs-cleaner root 1049 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 1104 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 1251 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 1554 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2178 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2283 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2371 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2479 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2538 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2638 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2696 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2756 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2779 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2797 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2815 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2833 4.0 0.0 0 0 ? S 09:46 4:09 [btrfs-cleaner] root 2852 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2901 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] ah, by the way, qcroups are off: pc-diego:~ # snapper get-config | grep QGROUP QGROUP | pc-diego:~ # mount | grep btrfs | cut -f 3 -d " " | while read a; do btrfs qgroup show $a; done ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1215178] New: qt6-base-6.4.2-150500.3+ leads to qt6-creator hang
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215178 Bug ID: 1215178 Summary: qt6-base-6.4.2-150500.3+ leads to qt6-creator hang Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: andrey.v.novikoff(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the current revision of libQt6Gui6-6.4.2-150500.3.7.4 from the official openSUSE repos, the qt6-creator-9.0.2 hangs when showing the Issues pane and consumes all memory in an infinite loop. The bug is the same as described on https://bugreports.qt.io/browse/QTCREATORBUG-28593 and connected with https://bugreports.qt.io/browse/QTBUG-109474 This is a regression in Qt6Gui cased by patch https://codereview.qt-project.org/c/qt/qtbase/+/435080 for Qt-6.5 branch. As per changelog, this patch was also applied to the qt6-base-6.4.2 from the "Updates from SUSE Linux Enterprise 15" repository (source file `0002-QTextLayout-fix-maximumWidth-for-a-text-containing-line.patch`). Thus, the problem appears now in Qt-6.4 branch including qt6-creator hang. Downgrading libQt6Gui6-6.4.2 to the original revision of libQt6Gui6-6.4.2-150500.1.14 from the Main OpenSUSE repository do resolves the issue with Qt6-creator. The problematic qt6base patch 435080 was superseded in the upstream via https://codereview.qt-project.org/c/qt/qtbase/+/453906 . Hope, this can be backported to the 6.4.2 as well. Or, the bad 435080 patch can be just removed altogether. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213048] New: telegram-desktop cannot start
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213048 Bug ID: 1213048 Summary: telegram-desktop cannot start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: diegops(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Fresh 15.5 with XFCE. telegram-desktop 4.7.1 diego@localhost:~$ telegram-desktop Cannot connect to server socket err = No existe el fichero o el directorio Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock QPainter::begin: Paint device returned engine == 0, type: 2 QWidget::render: Cannot render with an inactive painter Abortado (`core' generado) diego@localhost:~$ -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1215137] New: Firefox all tabs list issues on KDE Wayland - full list not displaying/not scrollable, cannot move tabs in list
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215137 Bug ID: 1215137 Summary: Firefox all tabs list issues on KDE Wayland - full list not displaying/not scrollable, cannot move tabs in list Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: pallaswept(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Please see https://bugzilla.mozilla.org/show_bug.cgi?id=1851503 and https://bugzilla.mozilla.org/show_bug.cgi?id=1851505 I initially files these as firefox bugs but it turns out they are specific to OpenSUSE KDE Wayland. OS KDE X11, Ubuntu 23.04 wayland, OpenSUSE IceWM are not effected. -- You are receiving this mail because: You are on the CC list for the bug.

1 5