http://bugzilla.opensuse.org/show_bug.cgi?id=1187477
Bug ID: 1187477
Summary: Selecting LXQt thems works badly or not at all
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: x86-64
OS: openSUSE Leap 15.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: LXQt
Assignee: mvetter(a)suse.com
Reporter: tonysu(a)su-networking.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
In the LXQt Configuration > Appearance > LXQt themes, switching between theeme
does not work for most, and works badly even for those that preview only after
clicking around.
This reminds me of a problem that has happened often in the past when the path
to the directory holding the themes is incorrect but back then there was a way
to define a path to the directory holding the themes. I don't see that now so
there is no way to manually correct the problem.
It should also be noted that if LXQt is chosen as the only Desktop installed
during installation (by first selecting Generic Desktop, then in the
Installation summary click on "Software" and then adding the LXQt pattern), the
generic openSUSE wallpaper displays instead of any of the LXQt themes, further
suggesting a bad path.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175037
Bug ID: 1175037
Summary: Sporadic endless loop in claws-mail/RSSyl - pango or
harfbuzz related?
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
Assignee: gnome-bugs(a)suse.de
Reporter: d_werner(a)gmx.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 840462
--> http://bugzilla.opensuse.org/attachment.cgi?id=840462&action=edit
gdb backtrace of claws-mail
In claws-mails (3.17.6 from Tumbleweed) RSS reader RSSyl some messages cause
"endless loops".
The problem happens in Tumbleweed and Leap 15.2 (in Leap 15.2 observed with
claws-mail 3.17.5 from GA and also with 3.17.6 from the update - repo).
But it is not identical, a message which triggers the endless loop in
Tumbleweed can be viewed without problem in Leap 15.2.
Luckily it is only a small percentage of messages which cause this, but if it
happens claws-mail needs to be killed. Viewing the same message after the
restart will trigger the problem again.
In backtraces taken while in this endless loop state I always observed harfbuzz
or pango related entries last on the stack. So maybe the actual problem is in
this area.
Attached several stack traces from claws-mail looping over the same message.
38 is the related message which caused this in Tumbleweed snapshot 20200807
which can be opened in Leap 15.2 with up to date fixes.
I did not observe something similar with Leap 15.1.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1190256
Bug ID: 1190256
Summary: Keyboard not working on ASUS Zenbook 14 UM425UA
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: screening-team-bugs(a)suse.de
Reporter: mkrapp(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I got a new ASUS Zenbook 14 UM524UA. Unfortunately keyboard is not at all
working in latest Tumbleweed with kernel 5.14.0-1-default.
I: Bus=0018 Vendor=04f3 Product=3134 Version=0100
N: Name="ASUE140A:00 04F3:3134 Keyboard"
P: Phys=i2c-ASUE140A:00
S:
Sysfs=/devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input8
U: Uniq=
H: Handlers=sysrq kbd leds event5
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f
It's recognized during boot:
> Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input3
> Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input4
> Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Keyboard as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input5
> Aug 31 20:00:01 localhost kernel: hid-generic 0018:04F3:3134.0001: input,hidraw0: I2C HID v1.00 Mouse [ASUE140A:00 04F3:3134] on i2c-ASUE140A:00
but not working at all. no events created when pressing/releasing keys.
The touchpad works fine, albeit I didn't try to get the extra function working
(numpad on touchpad) yet.
I'll attach hwinfo and journal in a minute.
Any idea how I can get the keyboard working?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
Bug ID: 1195775
Summary: apparmor fails to build with 5.16.7
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: jslaby(a)suse.com
Reporter: jslaby(a)suse.com
QA Contact: qa-bugs(a)suse.de
CC: dimstar(a)opensuse.org, suse-beta(a)cboltz.de
Found By: ---
Blocker: ---
This is a failure in openSUSE:Factory:Staging:K:
> [ 133s] + parser/apparmor_parser --config-file /home/abuild/rpmbuild/BUILD/apparmor-3.0.3/parser/parser.conf --write-cache -QT -L /home/abuild/rpmbuild/BUILD/apparmor-3.0.3/profiles/cache -I profiles/apparmor.d/ profiles/apparmor.d/
> [ 133s] Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
...
> [ 138s] + cp -a 'profiles/cache/*' /home/abuild/rpmbuild/BUILDROOT/apparmor-3.0.3-10.3.x86_64/usr/share/apparmor/cache
> [ 138s] cp: cannot stat 'profiles/cache/*': No such file or directory
> [ 138s] error: Bad exit status from /var/tmp/rpm-tmp.Q3LG8a (%install)
Likely missing systemd in kernel-obs-build (commit ef4c569b9986) causes
/sys/kernel/security not to be mounted and:
8873 newfstatat(-1, "/sys/kernel/security/apparmor/features", 0x7ffec91f0d00,
0) = -1 ENOENT (No such file or directory)
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193652
Bug ID: 1193652
Summary: Logitech mouse and keyboard stop working on the latest
kernel.
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: benthomasgeorge7899(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 854509
--> http://bugzilla.opensuse.org/attachment.cgi?id=854509&action=edit
Logs of the said issue
The mouse and keyboard stopped working randomly first while working. Later on
reboot it works fine with bios and grub encryption password but within minutes
the kernel is loaded it disconnects the keyboard and mouse.
Possible reasons have been checked for-
1. Issue is not cause due to tlp
2. Issue not caused due to autosuspend of usb.
Both the mouse and keyboard and mouse are working fine on the previous kernel
5.15.5-1. Rollback to the previous kernel has solved the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1199895
Bug ID: 1199895
Summary: PackageKit does not honor zypper package locks
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: Other
OS: openSUSE Leap 15.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: epistemepromeneur(a)free.fr
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I opened a bug report on 2 Jun 2019.
https://github.com/PackageKit/PackageKit/issues/325
A pull request has been made for merging a fix on 17 April 2022.
https://github.com/PackageKit/PackageKit/pull/543
3 years !
Stefan Dirsch suggest to me to ask you to
"to add the fix from github to our package, since apparently nobody is looking
into the issue and the fix upstream. :-("
see comment #9 here
https://bugzilla.opensuse.org/show_bug.cgi?id=1199791
Thanks
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1199429
Bug ID: 1199429
Summary: [Build20220508] nothing provides
'libprotobuf.so.30()(64bit)' needed by the to be
installed tensorflow2-2.7.1-1.3.x86_64
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: deepthi.venkatachala(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
#zypper -n in python3-tensorflow
Loading repository data...
Reading installed packages...
'python3-tensorflow' not found in package names. Trying capabilities.
Resolving package dependencies...
Problem: nothing provides 'libprotobuf.so.30()(64bit)' needed by the to be
installed tensorflow2-2.7.1-1.3.x86_64
Solution 1: do not ask to install a solvable providing python3-tensorflow
Solution 2: break tensorflow2-2.7.1-1.3.x86_64 by ignoring some of its
dependencies
Openqa Execution link:
https://openqa.opensuse.org/tests/2339547#step/tflite2/30
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1199354
Bug ID: 1199354
Summary: Running live snapshot fails with "usb-redir connection
broken during migration"
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Virtualization:Other
Assignee: virt-bugs(a)suse.de
Reporter: felix.niederwanger(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Running/reverting a snapshot of a VM in Running state on Tumbleweed fails with
a broken usb-redir connection:
> phoenix@racetrack-7290:~> virsh snapshot-revert --snapshotname snapshot-running --domain tumbleweed-mate
> error: internal error: qemu unexpectedly closed the monitor: qxl_send_events: spice-server bug: guest stopped, ignoring
> 2022-05-09T14:51:46.932083Z qemu-system-x86_64: warning: usb-redir connection broken during migration
>
> 2022-05-09T14:51:46.932121Z qemu-system-x86_64: usbredirparser: unserialization must use a pristine parser
> 2022-05-09T14:51:46.932126Z qemu-system-x86_64: Failed to load usb-redir:parser
> 2022-05-09T14:51:46.932129Z qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:02.1:00.0/2/usb-redir'
> 2022-05-09T14:51:46.933563Z qemu-system-x86_64: Error -1 while loading VM state
I tested this now with two different VMs, both return the same error. The error
appears in virt-manager and when running from the CLI (see above).
Restoring a snapshot in Shutoff VM state works without any issues.
## Reproducer
Easiest to reproduce is in virt-manager.
* Start any VM
* Create a snapshot of that VM in Running state
* Run the created snapshot
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172059
Bug ID: 1172059
Summary: windows:mingw:win{32,64}: packages including native
and cross packages does not build with enabled debug
info
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: 3rd party software
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: ralf.habacker(a)freenet.de
QA Contact: bnc-team-screening(a)forge.provo.novell.com
Found By: ---
Blocker: ---
If debug information support is enabled in the mentioned project, some packages
will not be built due to a conflict when collecting debug information for
native and cross-compiled packages.
How to reproduce:
1. branch one of the following package into a local project
mingw32-libqt4
mingw32-libqt4-static
mingw32-libqt5-qtbase
mingw32-libqt5-qtdeclarative
mingw32-libqt5-qttools
2. enable debug info support at the created project
What happens:
The build fails with "error: Installed (but unpackaged) file(s) found:"
/usr/lib/debug/...
What is expected:
The build should not fail with debug info support enabled at project or package
level
Adding debug information at the project level was originally proposed as a
workaround for a non-stripping problem with the cross-gcc package reported at
https://bugzilla.opensuse.org/show_bug.cgi?id=1116889.
--
You are receiving this mail because:
You are on the CC list for the bug.