http://bugzilla.suse.com/show_bug.cgi?id=992494
Bug ID: 992494
Summary: áÁéÉíÍóÓúÚüÜ cannot be typed in any app using Asturian
language and spanish Asturian variant keyboard
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: enolp(a)softastur.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The key combination for typing áÁéÉíÍóÓúÚüÜ does not working, (they appear as
aAeEiIoOuUuU), by setting "España - asturianu (ast_ES)" locale and "Asturian
(Spain, with bottom-dot H and bottom-dot L)" keyboard layout in any
application. However, Ḥḥ, Ḷḷ and Ññ Asturian letters are typed correctly in KDE
and GTK applications except Firefox, where all works perfectly.
yast2-country package was recently patched because of a similar bug, but
updating it, doesn't fix the problem.
https://bugzilla.suse.com/show_bug.cgi?id=981008
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=938955
Bug ID: 938955
Summary: Desktop selection overridden when installing without
recommended packages.
Classification: openSUSE
Product: openSUSE Factory
Version: 201505*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
Assignee: yast2-maintainers(a)suse.de
Reporter: cwh(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Chosing not to install recommnded packages leads to a minimal installation even
without xorg and desktop environment although a desktop environment has been
selected before.
Either the patterns have to be fixed or the no-recommends option should only be
allowed for the minimal pattern.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1074138
Bug ID: 1074138
Summary: Yast2 package manager UI very slow
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: amajer(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
I have a basic install. I would like to look through installed package list and
uninstall extra things I don't really need anymore. So,
1. yast2 -> Package Manager
2. list all packages
3. click on a package like Mesa-libGLESv2-devel and click uninstall
4. wait 30+ seconds while Package Manager window is completely unresponsive
and 100% CPU usage.
workaround,
1. filter to only list few packages.
2. click uninstall
Please fix. There is no reason Qt based UI should be slow, especially for
simple tables like this.
This problems seems to exist in all versions of Yast.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=948370
Bug ID: 948370
Summary: One-Click-Installer YMP file cannot match group
section for Tumbleweed
Classification: openSUSE
Product: openSUSE Factory
Version: 2015*
Hardware: Other
OS: openSUSE 13.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: tgoettlicher(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:39.0) Gecko/20100101
Firefox/39.0
Build Identifier:
One-Click-Installer YMP files can contain sections for different distribution
versions, e.g.:
<group distversion="openSUSE 13.2">
You can match against a specific Tumbleweed build:
<group distversion="openSUSE 20150924">
But it's not possible to match for Tumbleweed in general because the version of
Tumbleweed changes with every build.
Can the one-click-installer be extended to not only match against the version
but also against the codename?
For example:
<group distcodename="openSUSE Tumbleweed">
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=930110
Bug ID: 930110
Summary: yast ncurses menus not properly formatted for
tumbleweed ppc64 guest install
Classification: openSUSE
Product: openSUSE Factory
Version: 201503*
Hardware: PowerPC-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: normand(a)linux.vnet.ibm.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
yast ncurses menus not properly formatted for tumbleweed ppc64 guest install
Detailed flow:
* On a Power KVM host I defined a libvirt twppc64.xml
using the Tumbleweed-BE-DVD-ppc64-Snapshot20150505-Media.iso
retrieved from https://openqa.opensuse.org/tests/60778/asset/3110
* from a ssh session to the PowerKVM I started a screen window
from which I started the ppc64 guest.
===
virsh define twppc64.xml
virsh start --console twppc64
===
* I captured successively the ncurses menus and did a
yast2_ncurse_bad_format.tgz tarball with all those png files.
* The first problem is that the text is not properly aligned
eg: yast2_img1_installation.png
* The 2nd problem is that some characters from previous menu
are not cleaned up when new menu is presented.
eg: yast2_img4_installation_option.png
* The third problem is popup window hardly visible
eg: yast2_img9_confirm_password.png
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=980750
Bug ID: 980750
Summary: Plymouth prevents loading DRM/KMS driver for newly
installed graphics card
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.1
Hardware: All
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: maximilian.staudt(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
When changing a VGA card in an already installed system, Plymouth will prevent
its modern (DRM/KMS) kernel mode driver to be loaded.
Example:
1. Install Leap 42.1 in QEMU using the emulated Cirrus card (-vga cirrus).
2. The system boots up with a splash screen.
3. Shut down the system.
4. Start the VM, this time with the Bochs VGA card (-vga std).
5. A splash screen will be shown, but then X falls back to the VESA driver.
As a bonus, switching to a text VT (Ctrl-Alt-F1) only gives a blinking cursor.
The VT works just fine and is usable, except the user has to operate it blindly
as no video is shown.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
Bug ID: 1012883
Summary: System hangs at reboot/shutdown: A stop job is running
for User Manager for UID 1000 (1min30)
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: 64bit
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bootloader
Assignee: jsrain(a)suse.com
Reporter: jeckferson(a)gmail.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
It's an upstream systemd bug as described in:
https://github.com/systemd/systemd/issues/1615
It also manifested in 42.2.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1073043
Bug ID: 1073043
Summary: Krusader hang when copy or move files
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE Applications
Assignee: opensuse-kde-bugs(a)opensuse.org
Reporter: seifert(a)alesak.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
After some recent updates Krusader is unable to copy or move files (F5 or F6)
however Dolphin, Copy/Paste or Drag and Drop in Krusader works normally
There is no errors or crashes, running in gdb and break in hang state:
#0 0x00007ffff17f7f40 in nanosleep () from /lib64/libc.so.6
#1 0x00007ffff2493cad in ?? () from /usr/lib64/libQt5Core.so.5
#2 0x00007ffff236e770 in QLockFile::tryLock(int) () from
/usr/lib64/libQt5Core.so.5
#3 0x00007ffff49f3d69 in ?? () from /usr/lib64/libKF5ConfigCore.so.5
#4 0x00007ffff49ddb8f in KConfig::sync() () from
/usr/lib64/libKF5ConfigCore.so.5
#5 0x00007ffff49de8e5 in KConfig::~KConfig() () from
/usr/lib64/libKF5ConfigCore.so.5
#6 0x00007ffff4f155a6 in KRecentDocument::add(QUrl const&, QString const&) ()
from /usr/lib64/libKF5KIOCore.so.5
#7 0x00007ffff4f156cf in KRecentDocument::add(QUrl const&) () from
/usr/lib64/libKF5KIOCore.so.5
#8 0x000055555567d113 in ?? ()
#9 0x000055555567dbdd in ?? ()
#10 0x0000555555636191 in ?? ()
#11 0x0000555555647ae9 in ?? ()
#12 0x0000555555647d2a in ?? ()
#13 0x00007ffff246b63a in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#14 0x00007ffff33cd982 in QAction::triggered(bool) () from
/usr/lib64/libQt5Widgets.so.5
#15 0x00007ffff33cfe1c in QAction::activate(QAction::ActionEvent) () from
/usr/lib64/libQt5Widgets.so.5
#16 0x00007ffff33d0625 in QAction::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#17 0x00007ffff33d3afc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#18 0x00007ffff33daeb4 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#19 0x00007ffff243e128 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#20 0x00007ffff2a32272 in QShortcutMap::dispatchEvent(QKeyEvent*) () from
/usr/lib64/libQt5Gui.so.5
#21 0x00007ffff2a3233a in QShortcutMap::tryShortcut(QKeyEvent*) () from
/usr/lib64/libQt5Gui.so.5
#22 0x00007ffff29e4897 in QWindowSystemInterface::handleShortcutEvent(QWindow*,
unsigned long, int, QFlags<Qt::KeyboardModifier>, unsigned int, unsigned int,
unsigned int, QString const&, bool, unsigned short) () from
/usr/lib64/libQt5Gui.so.5
#23 0x00007ffff2a029e7 in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
()
from /usr/lib64/libQt5Gui.so.5
#24 0x00007ffff2a076e5 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
()
from /usr/lib64/libQt5Gui.so.5
#25 0x00007ffff29e0f9b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>)
()
from /usr/lib64/libQt5Gui.so.5
#26 0x00007fffe876d420 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#27 0x00007fffed2f9f97 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#28 0x00007fffed2fa1d0 in ?? () from /usr/lib64/libglib-2.0.so.0
#29 0x00007fffed2fa25c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#30 0x00007ffff249423f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/libQt5Core.so.5
#31 0x00007ffff243c73a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQt5Core.so.5
#32 0x00007ffff2444fc4 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#33 0x00005555555edcb9 in ?? ()
#34 0x00007ffff1752f4a in __libc_start_main () from /lib64/libc.so.6
#35 0x00005555555ef49a in _start ()
to me it looks like it is waiting to obtain some lock but not sure...
Interestingly enough when same Krusader is running in Root mode everything
works normally.
Version 2.6.0
Frameworks 5.40.0
Qt 5.9.2
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1041443
Bug ID: 1041443
Summary: Raspberry Pi 3: zypper unclear conflict resolution
problem message
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: libzypp
Assignee: zypp-maintainers(a)forge.provo.novell.com
Reporter: jeroen.forums.opensuse.org(a)pluimers.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 726808
--> http://bugzilla.suse.com/attachment.cgi?id=726808&action=edit
part of zypper.solverTestCase files
# Steps leading into this
1. Install Tumbleweed on Raspberry Pi 3 from
https://web.archive.org/web/20170526140155/http://download.opensuse.org/rep…
2. On 20170525 perform `zypper --versbose refresh --force` and `zypper
dist-upgrade`
3. On 20170528 perform `zypper dist-upgrade --no-allow-vendor-change`
Expected: succeed
Actual:
```
# zypper dist-upgrade --no-allow-vendor-change
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Problem: problem with installed package kernel-default-4.4.68-7.1.aarch64
Solution 1: keep obsolete kernel-default-4.4.68-7.1.aarch64
Choose the above solution using '1' or cancel using 'c' [1/c] (c):
```
Two important points:
1. Basically both the 1 and c will abort the upgrade so there is no way to
perform `--no-allow-vendor-change` upgrades any more.
2. The reason for the "problem" is not revealed so it is unclear to get out
of 1.
Details: https://gist.github.com/jpluimers/a9ed0802d4314ba3bd662663c2b219a9
which has all the zypper.solverTestCase files
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1036969
Bug ID: 1036969
Summary: VUL-1: libmad: assertion failure in layer3.c
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Security
Assignee: security-team(a)suse.de
Reporter: mikhail.kasimov(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 723246
--> http://bugzilla.opensuse.org/attachment.cgi?id=723246&action=edit
00213-libmad-heapoverflow-mad_layer_III_reproducer
Ref:
https://blogs.gentoo.org/ago/2017/04/30/libmad-assertion-failure-in-layer3-…
================================================
Description:
libmad stays for “M”peg “A”udio “D”ecoder library.
The same testcase provided in the article: libmad: heap-based buffer overflow
in mad_layer_III (layer3.c) is able to show an assertion failure if libmad was
compiled with debug (–enable-debugging).
The complete output of the failure:
# madplay -v -i -o raw:out $FILE
madplay:
/tmp/portage/media-libs/libmad-0.15.1b-r8/work/libmad-0.15.1b/layer3.c:2633:
mad_layer_III: Assertion `stream->md_len + md_len - si.main_data_begin <=
MAD_BUFFER_MDLEN' failed.
Affected version:
0.15.1b
Fixed version:
N/A
Commit fix:
N/A
Credit:
This bug was discovered by Agostino Sarubbo of Gentoo.
CVE:
N/A
Reproducer:
https://github.com/asarubbo/poc/blob/master/00213-libmad-heapoverflow-mad_l…
Timeline:
2017-01-01: bug discovered and reported to upstream
2017-04-30: blog post about the issue
Note:
This bug was found with American Fuzzy Lop.
================================================
(open-)SUSE: https://software.opensuse.org/package/libmad
0.15.1b (TW, 42.{1,2}, multimedia:libs repo)
--
You are receiving this mail because:
You are on the CC list for the bug.