September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1199020] Wrong resolution at Installation / Window background not cleared
by bugzilla_noreply＠suse.com 01 Sep '22

01 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199020 https://bugzilla.suse.com/show_bug.cgi?id=1199020#c55 --- Comment #55 from Stefan Hundhammer <shundhammer(a)suse.com> --- Now for the font sizes. Analyzing the first set of y2logs from comment #2 (jsudermann): Xorg.0.log: [ 82.995] (II) modeset(0): clock: 152.8 MHz Image Size: 344 x 193 mm [ 82.995] (II) modeset(0): h_active: 1920 h_sync: 2000 h_sync_end 2054 h_blank_end 2250 h_border: 0 [ 82.995] (II) modeset(0): v_active: 1080 v_sync: 1086 v_sync_end 1094 v_blanking: 1132 v_border: 0 y2start.log: Stage [call]: Monitor size: eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm Stage [call]: Monitor width mm: 344 Stage [call]: Monitor width px: 1920 Stage [call]: Monitor dpi: 144 Stage [call]: Xft.dpi set to: 144 y2log: 2022-04-29 14:43:46 <1> install(4700) [qt-ui] YQApplication.cc(pickAutoFonts):471 Selecting auto fonts - normal: 10, heading: 12 (bold) YQApplication.cc(currentFont):339 Loaded 10 pixel font: Sans Serif,-1,10,5,50,0,0,0,0,0 This sounds very reasonable so far. Except for this: YQUI.cc(calcDefaultSize):370 -fullscreen: using 960 x 540 for `opt(`defaultsize) YQUI.cc(calcDefaultSize):404 Default size: 960 x 540 ?!? Why does it use 960 x 540 for -fullscreen? https://github.com/libyui/libyui/blob/master/libyui-qt/src/YQUI.cc#L370 QSize availableSize = screen->availableSize(); So Qt thinks we are in HiDPI mode, scaling everything? It's using half the resolution values of 1920 x 1080 in both dimensions. And we also requested only a moderate font size: 10 px for normal text, 12 px for headings. Yet the screenshots show that those are massively scaled up; probably to 20 px for normal text (I can only guess). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1134838] New: No Raspberry Pi official 7' touchscreen support with DRM/VC4
by bugzilla_noreply＠novell.com 01 Sep '22

01 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1134838 Bug ID: 1134838 Summary: No Raspberry Pi official 7' touchscreen support with DRM/VC4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: nsaenzjulienne(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- So far we've been able to use the official 7' touchscreen using the frame buffer device provided by UEFI. This comes with the downside that VC4 has to be disabled in order for the setup to work. The alternative is to use VC4 and the raspberrypi-panel driver. This comes with some downsides: the setup depends on an overlay which isn't provided by anyone (Raspbian uses a custom firmware based frame buffer device) and the back-light is operated through the I2C0 bus, which is owned by the firmware. We should work towards getting the firmware based back-light implementation into the upstream kernel and with that discuss on integrating a suitable overlay into raspbian's kernel tree. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1200446] opensuse-release introduces fixed-URL repositories, fails without internet access
by bugzilla_noreply＠suse.com 01 Sep '22

01 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1200446 https://bugzilla.suse.com/show_bug.cgi?id=1200446#c23 --- Comment #23 from Ladislav Slez�k <lslezak(a)suse.com> --- (In reply to Jens Mozdzen from comment #22) > Could you introduce an installation-time flag that could be set by the admin > (or rather the AutoYaST file, in the reported case) with a "do not add > repositories" semantics? No, the repositories can be defined at many places: the system, RPM packages, AutoYaST profile, repository service, libzypp plugin script, boot parameters, add-on.xml on the medium, control.xml on the medium, SMT/RMT/SCC... And you actually want that repositories to be present, just in same cases you might need to disable them. And that disabling can be quite easily implemented by an AutoYaST chroot script, I do not think we need any special support for this relatively rare case. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202341] Raspi 4 (4GB): boots to blank screen with kernel 5.14.21-150400.24.11-default
by bugzilla_noreply＠suse.com 01 Sep '22

01 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202341 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202341] Raspi 4 (4GB): boots to blank screen with kernel 5.14.21-150400.24.11-default
by bugzilla_noreply＠suse.com 01 Sep '22

01 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202341 https://bugzilla.suse.com/show_bug.cgi?id=1202341#c4 --- Comment #4 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Created attachment 861246 --> https://bugzilla.suse.com/attachment.cgi?id=861246&action=edit vc4 crashes at vc4_hdmi_enable_scrambling -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200446] opensuse-release introduces fixed-URL repositories, fails without internet access
by bugzilla_noreply＠suse.com 01 Sep '22

01 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1200446 https://bugzilla.suse.com/show_bug.cgi?id=1200446#c22 --- Comment #22 from Jens Mozdzen <jens.mozdzen(a)suse.com> --- Could you introduce an installation-time flag that could be set by the admin (or rather the AutoYaST file, in the reported case) with a "do not add repositories" semantics? If someone sets this flag, it's that one's responsibility to make sure all required repositories are available. If that flag were introduced via some wrapper that you ask everyone to use, then this wrapper could also record all blocked "add repository" attempts and report these in the installation logs. This would help in debugging issues if the "admin" (the one setting the "don't add repositories" flag) messed up the extra repository setup. Potentionally the "wrapper" could be "zypper", if that's what every RPM script is using to add repositories. Yes, indeed, the wrapper would need to be able to distinguish between repositories added by the installation environment, vs. those added by RPM scripts - if the installation environment does use the same mechanism to update the repository list. But even then, it could be handled in a manner that the installation env sets the flag *after* having set up all "manual" repositories, blocking only further updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202975] Installing kwrite also installs kate
by bugzilla_noreply＠suse.com 01 Sep '22

01 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202975 https://bugzilla.suse.com/show_bug.cgi?id=1202975#c4 --- Comment #4 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Eugene Popov from comment #3) > These are two different executables. Yeah, but /usr/bin/kwrite doesn't really do anything other than calling into the library. It's smaller than /usr/bin/true... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200446] opensuse-release introduces fixed-URL repositories, fails without internet access
by bugzilla_noreply＠suse.com 01 Sep '22

01 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1200446 https://bugzilla.suse.com/show_bug.cgi?id=1200446#c21 --- Comment #21 from Lubos Kocman <lubos.kocman(a)suse.com> --- Max mentioned that he thinks that this issue might not appear in 15.4 nor latest Quaterly Update of 15.3. Seems like we've had issue in skelcd-control which is also being parsed by autoyast. What we'd like ot see is to double check on current 15.3 and 15 SP4 installation if this is still an issue. If so then Max has concerns why this shouldn't be touched in 15.5 (last release, possible brings new issues). If we have solution / workaround for this then I'd recommend perhaps to document it. Go with the rpm-repos-openSUSE (which is currently only for DNF) to Factory first. And then take it perhaps for ALP. We've had rough upgrades with CtLG and this could trigger another set of complains in 15.5 retrospective. I've learned that documenting change in release-notes and System upgrade wiki doesn't mean that people will read it :-) They'll hit issue, we'll forward them to information but it will still be on retro :-) So please consider my previous SR as rejected, as it doesn't follow factory first. I can try to submit the change to factory (after reworking rpm-repos-openSUSE) and we can re-discuss this once it's accepted. But I'm afraid it's only moving the issue arround and in case of Leap triggers possible new issues with zypper dup --releasever 15.5. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203022] Keyboard layout is US international with dead keys, but konsole and lokalize do not accept dead key
by bugzilla_noreply＠suse.com 01 Sep '22

01 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203022 https://bugzilla.suse.com/show_bug.cgi?id=1203022#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freek(a)opensuse.org, | |fvogt(a)suse.com Flags| |needinfo?(freek(a)opensuse.or | |g) --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Sounds like ibus. Do you have that installed? If yes and you don't need it, uninstall it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202947] After enabling disk encryption (LUKS) in openSUSE MicroOS, the system asks the password two times and boots very slow
by bugzilla_noreply＠suse.com 01 Sep '22

01 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202947 https://bugzilla.suse.com/show_bug.cgi?id=1202947#c2 --- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Eduardo Medina from comment #1) > I saw this, but it's not possible to follow the steps because the filesystem > is read only. > https://en.opensuse.org/SDB: > Encrypted_root_file_system#Avoiding_to_type_the_passphrase_twice Of course it is possible, why shouldn't it be? You just shouldn't call deprecated, outdated tools (mkinitrd) as described there (somebody should update that page) but the correct tool for this task depending on the OS (so dracut on Tumbleweed and transactional-update initrd on MicroOS) > If I separate the /boot partition, the subvolumes for GRUB disappears, so I > have to recreate them. I will try it, but I think it's a complicated process. Separate /boot will break snapshot and rollback. -- You are receiving this mail because: You are on the CC list for the bug.

1 0