December 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1206029] Can't run Falkon Browser in Docker Image
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206029 https://bugzilla.suse.com/show_bug.cgi?id=1206029#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fvogt(a)suse.com Resolution|--- |INVALID --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- You cannot simply run applications like this in docker containers. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205585] [Build 20221110] Broken font rendering in installations over VNC
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205585 https://bugzilla.suse.com/show_bug.cgi?id=1205585#c32 --- Comment #32 from Stefan Hundhammer <shundhammer(a)suse.com> --- SR to Factory: https://build.opensuse.org/request/show/1040221 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206029] New: Can't run Falkon Browser in Docker Image
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206029 Bug ID: 1206029 Summary: Can't run Falkon Browser in Docker Image Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: 64bit OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: hierher(a)ymail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello fellow Geekos! I created a Docker image based on registry.opensuse.org/opensuse/leap:15.4; with added icewm and VNC to connect. In the image, I tried to run Falkon Webbrowser, which I installed from the main repos using 'zypper in falkon' without any issue. Unfortunately, when trying to launch it, I get the following output: tuxy@709289fccf0c:~> falkon QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-yaepts' Failed to connect to session bus! Failed to connect to session bus! Falkon: 1 extensions loaded Trace/breakpoint trap My understanding is that the first line is just a warning (I got the same warning with other Qt-related programmes). The failed section seems to be based on the fact that the Docker image of openSUSE does not come with systemd. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205585] [Build 20221110] Broken font rendering in installations over VNC
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205585 https://bugzilla.suse.com/show_bug.cgi?id=1205585#c31 --- Comment #31 from Stefan Hundhammer <shundhammer(a)suse.com> --- PR to drop the '-depth 16' argument to Xvnc: https://github.com/yast/yast-installation/pull/1071 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199592] azure-cli and python-azure-mgmt-authorization package versions are incompatible
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1199592 https://bugzilla.suse.com/show_bug.cgi?id=1199592#c3 Anton Smorodskyi <anton.smorodskyi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anton.smorodskyi(a)suse.com --- Comment #3 from Anton Smorodskyi <anton.smorodskyi(a)suse.com> --- (In reply to John Paul Adrian Glaubitz from comment #2) > Upstream bug report: https://github.com/Azure/azure-cli/issues/23933 FYI upstream issue closed as fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206026] [Build 20221204] openQA test fails in sshfs
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206026 Dan ��erm��k <dcermak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|containers-bugowner(a)suse.de |dcermak(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206026] New: [Build 20221204] openQA test fails in sshfs
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206026 Bug ID: 1206026 Summary: [Build 20221204] openQA test fails in sshfs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2928458/modules/sshf s/steps/22 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: dcermak(a)suse.com Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-RPi-aarch64-jeos_extra_tests_vagrant@RPi4 fails in [sshfs](https://openqa.opensuse.org/tests/2928458/modules/sshfs/steps/22) It seems that "vagrant up" does not work as expected. ## Test suite description Test vagrant on top of JeOS (for RPi4) ## Reproducible Fails since (at least) Build [20221202](https://openqa.opensuse.org/tests/2923728) ## Expected result Last good: [20221129](https://openqa.opensuse.org/tests/2917968) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120608] Mounting external USB disk with udisks2 causes internal disk to spin-up from standby
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1120608 https://bugzilla.suse.com/show_bug.cgi?id=1120608#c23 --- Comment #23 from Thomas Blume <thomas.blume(a)suse.com> --- And of course, I will submit my backported patches. ;) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120608] Mounting external USB disk with udisks2 causes internal disk to spin-up from standby
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1120608 https://bugzilla.suse.com/show_bug.cgi?id=1120608#c22 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM Flags|needinfo?(one(a)contezero.com | |) | --- Comment #22 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Michele Cherici from comment #21) > Unfortunately I can't test it, I don't have that disk anymore. Ok, thanks for the feedback. I will assume that the issue is fixed therewith and close the bug. If you ever experience that issue again, please open a new bug and reference this one. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205585] [Build 20221110] Broken font rendering in installations over VNC
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205585 https://bugzilla.suse.com/show_bug.cgi?id=1205585#c30 --- Comment #30 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Stefan Hundhammer from comment #28) > OK, thanks all for your investigations. This all sounds very promising. > > So, to summarize (please correct me if I am wrong): > > - There was a bug in the Qt libs. > > - We now have a fix as a patch on top of our Qt libs build. > > - That patch was also sent upstream, but of course it will take a while > until the fixed version trickles down to us again. > > > Is there anything left for the installer to do? I don't see anything. Yes, consider moving from "-depth 16" to use the Xvnc default, see comments 26 and 27. (In reply to Stefan Hundhammer from comment #29) > Since Qt now does all pixel rendering locally into a pixel buffer and sends > that whole buffer to the X server (no more Xlib primitives), does it even > matter if the X visual has an alpha channel? I don't think it should; it > should all be done on the Qt level before the pixel buffer is even sent. It doesn't - the X11 target surface doesn't use alpha in this case. The difference was RGB565 vs. RGB888. -- You are receiving this mail because: You are on the CC list for the bug.

1 0