http://bugzilla.opensuse.org/show_bug.cgi?id=1207807
Bug ID: 1207807
Summary: khugepaged consumes 100% cpu apparently causing
virtual machine to freeze for extended times
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.4
Hardware: x86-64
OS: openSUSE Leap 15.4
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: obs(a)akr.yagii.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I am running a Windows 10 virtual machine guest in VMware Workstation 16.2. The
guest becomes unresponsive for 10-60s after each mouse click and khugepaged is
run at 100% cpu.
This is reproducible after almost every suspend of the guest or a suspend of
the host.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184334
Bug ID: 1184334
Summary: Missing translation fixes for YaST and Welcome screen
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Translations
Assignee: ke(a)suse.com
Reporter: noga.dany(a)gmail.com
QA Contact: ke(a)suse.com
Found By: ---
Blocker: ---
openSUSE-Leap-15.3-DVD-x86_64-Build117.13-Media.iso
During installation via YaST with Czech translation I saw strange czech text
"Zm��rn��n�� CPU" . I wanted to fix it, but it looks correct here
https://l10n.opensuse.org/translate/yast-installation/master/cs/?checksum=6…
Another wrong translation was with Welcome screen, where is czech text "Uk��zat
p��i p������t��m sup��t��n��", where is typo, which I fixed almost year ago:
https://l10n.opensuse.org/translate/opensuse-welcome/master/cs/?checksum=f7…
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202078
Bug ID: 1202078
Summary: Plasma wayland cannot be set as default with autologin
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.4
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE Workspace (Plasma)
Assignee: opensuse-kde-bugs(a)opensuse.org
Reporter: noga.dany(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Leap 15.4 with Plasma KDE 5.24.4 and all updates installed with autologin
enabled. It works fine on X11. I tried to set Plasma Wayland as default via
"System Settings-->Startup and Shutdown-->Login Screen
(SDDM)-->Behavior-->choose Plasma Wayland", but then I will end in console
instead in Plasma.
Plasma Wayland itself works, if I keep old settings with autologin into X11 and
then I just unlog to SDDM, change session and log with Wayland, it is ok. Just
autologin will not boot.
I can reproduce it both on my freshly installed Laptop with i5-11400H cpu with
integrated graphics and in VirtualBox. I tested behavior in Fedora 36 without
updates (similar components, Plasma 5.24.3, etc) and there autologin settings
works fine.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185441
Bug ID: 1185441
Summary: "system is compromised" during boot after grub2+shim
update
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: Other
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bootloader
Assignee: screening-team-bugs(a)suse.de
Reporter: robert.simai(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I installed the most recent
kernel-default-5.3.18-lp152.72.1.x86_64
shim-15.4-lp152.4.8.1.x86_64
grub2-2.04-lp152.7.25.1.x86_64
on my Dell Precision 3620 this week and rebooted as required. The system
doesn't come up but shows "system is compromised" for a second, followed by
power down.
If I change from "UEFI with secure boot" to "UEFI without secure boot" it
behaves well again and just boots.
I've set "mokutil --set-verbosity true" as advised which outputs a lot of
messages, I unfortunately have no serial console at hand to connect and save
them. I'll try to attach a video from the screen that shows the boot process
and messages.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184490
Bug ID: 1184490
Summary: mame creates a cfg directory in PWD instead of ~/.mame
and ignoring ~/.mame/cfg
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: ilya(a)ilya.pp.ua
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
After updating mame to 0.226, mame started ignoring the configuration directory
~/.mame/cfg/ and started creating it in PWD, i.e. the directory where mame runs
from (~/ if you run mame via the menu).
In 0.229 nothing has changed.
In 0.211 it was no problem.
To reproduce, just run "cd /tmp && mame", wait for mame to load the interface,
then press Esc to quit mame, and then check /tmp "ls -lah /tmp | grep cfg".
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1202281
Bug ID: 1202281
Summary: UTF-8 smileys gone (or mutilated) in gnome-terminal,
xemacs,...
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X.Org
Assignee: gfx-bugs(a)suse.de
Reporter: gp(a)suse.com
QA Contact: gfx-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 860713
--> https://bugzilla.suse.com/attachment.cgi?id=860713&action=edit
Testfile with some UTF-8 smiley characters
This is a recent (Tumbleweed 20220805) regression.
UTF-8 smiley characters either are not rendered any more at all when
viewed in gnome-terminal, XEmacs, LibreOffice Writer ... or rendered
monochrome instead of yellow and harder to view.
Firefox interestingly shows them properly, as I had it for the last
years, when contents is pasted into a text field.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206853
Bug ID: 1206853
Summary: gajim crashes with output about nbxmpp/task.py
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: stakanov(a)disroot.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
## Versions:
- OS: Linux 6.1.1-1-default
- GTK Version: 3.24.35
- PyGObject Version: 3.42.2
- GLib Version : 2.74.0
- python-nbxmpp Version: 3.2.5
- Gajim Version: 1.5.4
## Traceback
```
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/nbxmpp/task.py", line 306, in
_on_timeout
self._set_finished()
File "/usr/lib/python3.10/site-packages/nbxmpp/task.py", line 242, in
_set_finished
self._finalize()
File "/usr/lib/python3.10/site-packages/nbxmpp/task.py", line 368, in
_finalize
self._client._dispatcher.remove_iq_callback(self._iq_id)
AttributeError: 'NoneType' object has no attribute 'remove_iq_callback'
```
## Steps to reproduce the problem
start the program and connect for a while, program will crash
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186315
Bug ID: 1186315
Summary: Flatpak packages installed without pre-configured
repo, making "out-of-the-box" usage impossible
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: x86-64
OS: openSUSE Leap 15.2
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: blst(a)arcor.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Flatpak's goal to make software installation easier on Linux systems. This
approach was also designed for less experienced users. But the way it is
implemented in Leap 15.2 makes it hard to use.
1) It is not installed per default (other distributions install the packages
during the setup process)
2) The user can install the Flatpak system via the package manager, but after
the installation it requires additional configuration. It seems that there are
no Flatpak repos configured per default.
The main source for Flakpak is flathub.org.
To make at least the install command lines at Flathub working, I had to
>flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
Suggestion
a) add the Flathub repo per default
or
b) make a seperate flathub.org repo installation package available
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188023
Bug ID: 1188023
Summary: GNOME:Apps/fractal:
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: 3rd party software
Assignee: os.gnome.maintainers(a)gmail.com
Reporter: william.brown(a)suse.com
QA Contact: screening-team-bugs(a)suse.de
Found By: ---
Blocker: ---
I've recently started a project to automatically scan for potential security
issues in rust packages with cargo audit. I noticed the following on fractal:
* RUSTSEC-2021-0026 -> crate: comrak, cvss: None, class: ['format-injection']
* RUSTSEC-2021-0063 -> crate: comrak, cvss: None, class: ['format-injection']
* RUSTSEC-2020-0060 -> crate: futures-task, cvss: None, class:
['code-execution', 'memory-corruption']
* RUSTSEC-2020-0059 -> crate: futures-util, cvss: None, class:
['thread-safety']
* RUSTSEC-2020-0146 -> crate: generic-array, cvss: None, class:
['memory-corruption']
* RUSTSEC-2021-0020 -> crate: hyper, cvss: None, class: ['format-injection']
Most of these should be able to be resolved with cargo update and re-vendoring
the dependencies. Alternately upstream may have released a
Cargo.toml/Cargo.lock with updates for this.
It would be great if you could look into updating and resolving these :)
Thank you!
-- more info
https://github.com/openSUSE/obs-service-cargo_audit/blob/main/README.mdhttps://en.opensuse.org/Packaging_Rust_Software
--
You are receiving this mail because:
You are on the CC list for the bug.