February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 976384] New: Qt-Creator Documentation is not found out-of-the-box
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=976384 Bug ID: 976384 Summary: Qt-Creator Documentation is not found out-of-the-box Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: VMWare OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gorgoglione(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In Qt-Creator 3.6.0, selecting Help -> Contents from menu, the following error message is displayed: The page could not be found Error loading: qthelp://org.qt-project.qtcreator.360/doc/index.html Check that you have the corresponding documentation set installed. Probably the documentation it's not installed into the default folder and Qt-Creator configuration was not updated to point to the right location. The fix which worked for me was to select Tools -> Options... -> Help -> Documentation -> Add, and select the following file: /usr/share/doc/packages/libqt5/qtcreator.qch -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1208763] New: Desktop: KDE Opensuse: Tumbleweed, standard installation with KDE and latest updates On the sddm login screen, you can choose between KDE X11 and KDE Wayland (and another, which is not used). Choosing KDE X11, after entering the password the session is s
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208763 Bug ID: 1208763 Summary: Desktop: KDE Opensuse: Tumbleweed, standard installation with KDE and latest updates On the sddm login screen, you can choose between KDE X11 and KDE Wayland (and another, which is not used). Choosing KDE X11, after entering the password the session is s Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: miguel(a)kehrer.cc QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0 Build Identifier: https://paste.opensuse.org/pastes/dfeed6217b7b My Laptop: System: Host: MiguelLaptop Kernel: 6.1.10-1-default arch: x86_64 bits: 64 compiler: gcc v: 12.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.10-1-default root=UUID=0c4d5db9-9774-4df2-b510-aa1c069ea31b splash=silent quiet mitigations=auto Desktop: KDE Plasma v: 5.27.0 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM Distro: openSUSE Tumbleweed 20230214 Graphics: Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5.1 code: Vega-2 process: TSMC n7 (7nm) built: 2018-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 05:00.0 chip-ID: 1002:164c class-ID: 0300 temp: 27.0 C Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo bus-ID: 1-3:2 chip-ID: 13d3:56ff class-ID: 0e02 Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8 compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 506x285mm (19.92x11.22") s-diag: 581mm (22.86") Monitor-1: eDP-1 mapped: eDP model: ChiMei InnoLux 0x140a built: 2019 res: 1920x1080 hz: 60 dpi: 158 gamma: 1.2 size: 309x173mm (12.17x6.81") diag: 354mm (13.9") ratio: 16:9 modes: max: 1920x1080 min: 640x480 API: OpenGL v: 4.6 Mesa 22.3.5 renderer: AMD Radeon Graphics (renoir LLVM 15.0.7 DRM 3.49 6.1.10-1-default) direct render: Yes Reproducible: Always Steps to Reproduce: 1.log out 2. Switch to Plasma Wayland 3. Try to log in Actual Results: Screen Blackouts and returns to log in screen Expected Results: Enter the Plasma Wayland Session -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1065388] New: apparmor is breaking tool file in lessopen.sh
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1065388 Bug ID: 1065388 Summary: apparmor is breaking tool file in lessopen.sh Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tracing lessopen.sh with export LESS_ADVANCED_PREPROCESSOR=yes shows [...] ++ file -L ./less.1 + type='./less.1: writable, regular file, no read permission' but it should be noether less/less-487> file -L ./less.1 ./less.1: troff or preprocessor input, ASCII text in /etc/apparmor.d/usr.bin.lessopen.sh I found /usr/bin/file rix, but no rule for /usr/bin/file its self! All tools listed in /etc/apparmor.d/usr.bin.lessopen.sh should be able to read files as otherwise nothings goes. -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[Bug 1204162] Win10 in all versions have no network
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1204162 https://bugzilla.suse.com/show_bug.cgi?id=1204162#c22 --- Comment #22 from ulfbart <ub22(a)gmx.net> --- (In reply to Lin Ma from comment #21) > (In reply to ulfbart from comment #20) > > Actually, Even if the above one can workaround the issue, Using > paravirtualized nic(virtio-net) is recommended. > > > * Using virtio-net instead of e1000e/rtl8139.(vmdp-win driver is required) > > > E.g. > > > <interface type="network"> > > > <mac address="xx:xx:xx:xx:xx:xx"/> > > > <source network="default"/> > > > <model type="virtio"/> > > > </interface> I changed interface to: <interface type="network"> <mac address="xx:xx:xx:xx:xx:xx"/> <source network="default"/> <model type="e1000e"/> <address type="pci" domain="0x0000" bus="0x06" slot="0x00" function="0x0"/> </interface> And now it worked again (before it was the rtl8139 used). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187137] New: Syntax error in qtconcurrent header
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1187137 Bug ID: 1187137 Summary: Syntax error in qtconcurrent header Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: uhhadd(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: andresbs2000(a)protonmail.com Found By: --- Blocker: --- This causes anything including QtConcurrent to fail to build with the following message or similar: [ 67s] ERROR: In file included from /usr/include/qt5/QtConcurrent/qtconcurrentiteratekernel.h:49, [ 67s] from /usr/include/qt5/QtConcurrent/qtconcurrentfilterkernel.h:47, [ 67s] from /usr/include/qt5/QtConcurrent/qtconcurrentfilter.h:47, [ 67s] from /usr/include/qt5/QtConcurrent/QtConcurrent:8, [ 67s] from /home/abuild/rpmbuild/BUILD/tok-0.0.1+git.20210605.035ab76/src/client_p.cpp:5: [ 67s] /usr/include/qt5/QtConcurrent/qtconcurrentthreadengine.h:250:50: error: invalid declarator before '*' token [ 67s] 250 | ThreadEngineStarter<void>(ThreadEngine<void> *_threadEngine) [ 67s] | ^ [ 67s] /usr/include/qt5/QtConcurrent/qtconcurrentthreadengine.h:250:49: error: expected ')' before '*' token [ 67s] 250 | ThreadEngineStarter<void>(ThreadEngine<void> *_threadEngine) [ 67s] | ~ ^~ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1201089] [META] GCC 13 package failures
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1201089 Bug 1201089 depends on bug 1208736, which changed state. Bug 1208736 Summary: GCC 13: xen package fails https://bugzilla.suse.com/show_bug.cgi?id=1208736 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208657] New: QEMU failing to build with kernel 6.2 due to header issues
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208657 Bug ID: 1208657 Summary: QEMU failing to build with kernel 6.2 due to header issues Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: dfaggioli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The problem is described here: https://lore.kernel.org/qemu-devel/20230110174901.2580297-1-berrange@redhat… So, quoting from there: > It didn't appear that glibc was going to fix the problem > breaking includes of linux/mount.h vs sys/mount.h, so > QEMU applied a workaround copying the symbols/structs we > need into a local header. > > Since then Linux modified linux/btrfs.h to pull in > linux/fs.h which caused a clash with our workaround. > Rather than invent workarounds for our workarounds, > we can luckily just drop our previous workarounds. > glibc has been fixed after all, and backported this > fix to the stable 2.36 release series too. We should > just expect distros to pull in the stable fix, which > Fedora at least has already done. The mentioned workaround is something we included in our QEMU 7.1 package as a downstream patch (see bug 1204001). And now we're suffering the consequences described in the second paragraph. The actual error, when trying to build QEMU with kernel 6.2's headers is this one: > [ 56s] In file included from /usr/include/linux/btrfs.h:29, > [ 56s] from ../linux-user/syscall.c:163: > [ 56s] /usr/include/linux/fs.h:50:8: error: redefinition of 'struct file_clone_range' > [ 56s] 50 | struct file_clone_range { > [ 56s] | ^~~~~~~~~~~~~~~~ > [ 56s] ../linux-user/syscall.c:129:8: note: originally defined here > [ 56s] 129 | struct file_clone_range { > [ 56s] | ^~~~~~~~~~~~~~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1208681] New: Plasma 5.27.1 application font sizes too small after update
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208681 Bug ID: 1208681 Summary: Plasma 5.27.1 application font sizes too small after update 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: michael(a)actrix.gen.nz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating to Plasma 5.27.1 TW 20230224, the application font sizes became tiny, both in KDE applications such as kate and konsole and non KDE applications such as google-chrome and jetbrains pycharm. On the other hand the size of the window decoration fonts, panel fonts, and desktop widgets remained unchanged. I attempted to use Settings to change the default font sizes, but then window decoration fonts, panel fonts, and desktop widget fonts became huge. I have one 27" 4K monitor and one 1920x1200 monitor. Perhaps the 4K monitor has something to do with it. I run the 4K monitor unscaled in KDE and use xrandr to scale the 1920x1200 display by 1.75 (which is fine for text): xrandr --output DP-4 --auto --output DP-0 --auto --scale 1.75x1.75 --right-of DP-4 I've reverted to 5.27.0 which has fixed the issue, although I should note that since Plasma 5.27.0. I've seen the odd problem with google-chrome switching to tiny fonts, and this was resolved by logging out and starting a new session. I should probably also note that kscreen2 is disabled (to avoid the hot-plug actions associated with turning off DisplayPort screens). I tried to log this bug before, but it seems to have disappeared - apologies if this appears as a duplicate. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1208736] GCC 13: xen package fails
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208736 http://bugzilla.opensuse.org/show_bug.cgi?id=1208736#c2 --- Comment #2 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1208736) was mentioned in https://build.opensuse.org/request/show/1068230 Factory / xen -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208106] New: Backport request: perf/x86/intel/pt: Fix sampling using single range output
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208106 Bug ID: 1208106 Summary: Backport request: perf/x86/intel/pt: Fix sampling using single range output Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got a new work laptop (with alderlake i7-1250U), ran the gdb testsuite and ran into issues with the "record btrace" command, on openSUSE Leap 15.4, but not on openSUSE Tumbleweed. The responsible gdb maintainer pointed me to a linux kernel commit that should fix this: ... $ git show ce0d998be9274dd3a3d971cbeaa6fe28fd2c3062 commit ce0d998be9274dd3a3d971cbeaa6fe28fd2c3062 Author: Adrian Hunter <adrian.hunter(a)intel.com> Date: Sat Nov 12 17:15:08 2022 +0200 perf/x86/intel/pt: Fix sampling using single range output Deal with errata TGL052, ADL037 and RPL017 "Trace May Contain Incorrect Data When Configured With Single Range Output Larger Than 4KB" by disabling single range output whenever larger than 4KB. Fixes: 670638477aed ("perf/x86/intel/pt: Opportunistically use single range output mode") Signed-off-by: Adrian Hunter <adrian.hunter(a)intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz(a)infradead.org> Cc: stable(a)vger.kernel.org Link: https://lkml.kernel.org/r/20221112151508.13768-1-adrian.hunter@intel.com ... I went as far as applying the patch to tag v5.14.21, and it applied cleanly. So, can we backport this to leap 15.4? Related gdb PRs: - https://sourceware.org/bugzilla/show_bug.cgi?id=30073 - https://sourceware.org/bugzilla/show_bug.cgi?id=30075 -- You are receiving this mail because: You are on the CC list for the bug.

1 6