http://bugzilla.suse.com/show_bug.cgi?id=1012825
Bug ID: 1012825
Summary: YaST2 hung "retrieving cracklib-dict-full.rpm
extension" if rpm passed in DUD
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
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: ---
Created attachment 704263
--> http://bugzilla.suse.com/attachment.cgi?id=704263&action=edit
installation_overview-y2logs.tar.bz2
YaST2 hung "retrieving cracklib-dict-full.rpm extension"
while investigating bug https://bugzilla.suse.com/show_bug.cgi?id=1009472
I tried to pass a DUD=*dud containing the rpm*.rpm
The consequence is that YaST2 hungs at "retrieving cracklib-dict-full.rpm
extension"
The y2log ends is stuck at Calling: extend,
note that there is no /var/log/extend in reported tarball
and no trace of extend in /var/log/linuxrc.log
steps:
===
$mkdud -c /tmp/boo1009472.dud --install instsys --force -d 20161122
/tmp/powerpc-utils-1.3.2-9.ppc64le.rpm /tmp/rpm-4.12.0.1-0.ppc64le.rpm
===
/var/lib/openqa/script/client jobs post
ISO=openSUSE-Tumbleweed-DVD-ppc64le-Snapshot20161122-Media.iso ARCH=ppc64le
BUILD=20161122 DESKTOP=minimalx DISTRI=opensuse DVD=1 FLAVOR=DVD HDDSIZEGB=40
MACHINE=ppc64le-multipath MULTIPATH=1 OFW=1 QEMU=ppc64 QEMUCPU=host QEMUCPUS=8
QEMURAM=4096 QEMUTHREADS=8 TEST=install_minimalx VERSION=Tumbleweed
Test=install_minimalx VGA=std WORKER_CLASS=qemu_ppc64le
DUD=http://stade.lab.toulouse-stg.fr.ibm.com/~normand/boo1009472.dud
=== extract y2log
install(8235) [Ruby] modules/InstExtensionImage.rb:386 Calling: extend
'cracklib-dict-full.rpm'
===
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=973590
Bug ID: 973590
Summary: weird layout of bootloader screen
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: dmueller(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
While updating the openQA needle for openSUSE on AArch64 people noted that the
"indentation" of the items in the ncurses ui looks slightly awkward.
Is it intended that there is this huge empty space at the top left corner?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=958483
Bug ID: 958483
Summary: 3rd party application UI is not behaving as required
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: 2015*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: tchvatal(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
When using 3rd party module (like Virtualization) that tries to install
additional packages it at this moment works like this when you are in X
environment:
For each package there is pop-up showing progress and then this pop-up is
closed.
This causes severe issue if user runs compoziting enabled environment.
Imagine it like disco-bulb turning on and off as only on-top window is supposed
to be rendered right and all the underlying windows are greyed out.
More apps you install the more "funky" blinking you get.
Prefferable solution would be to somehow include the yast2 sw_single interface
that has the bottom progressbar and prints the installed packages.
Added value would be mostly for openSUSE, where the default DE's have enabled
compositing, but also for SLE case it would get at minimal prettier and at best
more understandable about what is happening for the installed packages.
For openSUSE it is quite commonly reported issue as I closed 3-4 during the
bugzilla cleanup mentioning this problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1057976
Bug ID: 1057976
Summary: Patch for gtk3 (openSUSE-2017-1032) requires
vietnamese, inuktitut, thai, and amharic
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: x86-64
OS: openSUSE 42.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: libzypp
Assignee: zypp-maintainers(a)forge.provo.novell.com
Reporter: Ulrich.Windl(a)rz.uni-regensburg.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 740114
--> http://bugzilla.opensuse.org/attachment.cgi?id=740114&action=edit
Screen shot showing Yast's suggestions
When online updating the gtk3-3.20.10-5.3.1 to gtk3-3.20.10-5.6.1, Yast2
insists to add additional language modules like
gtk3-immodule-{ietnamese,inuktitut,thai,amharic} which I don't need. See
attachment.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=966042
Bug ID: 966042
Summary: yast command-line usage emits "unable to close
filehandle properly" warning at exit
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: 2015*
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: bk(a)ancilla.ca
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Specifically, it says:
Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line
21 during global destruction (#1)
(S io) An error occurred when Perl implicitly closed a filehandle. This
usually indicates your file system ran out of disk space.
This happens with (as far as I can tell, I haven't tested exhaustively) all
command-line yast invokations that involve a module. So, e.g., "yast users
help" or "yast sysconfig help" will produce this message. "yast help" on its
own, however, won't.
It does not appear to affect yast's exit code, or it's ability to do its job;
if I run "yast sysconfig set LOADER_TYPE=none", it does the right thing and
then produces that message while exiting.
Despite the hint that it may be space-related, this happens on multiple
computers, all of them with plenty of space available on all filesystems. These
systems are all running recent (~2 weeks) versions of Tumbleweed.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=997317
Bug ID: 997317
Summary: grub2-branding lacks posttrans
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bootloader
Assignee: jsrain(a)suse.com
Reporter: ohering(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
grub2-branding creates a grub2.cfg in its %post.
this is a very expensive operation, in combination with os-prober.
there is nothing in that pkg which requires immediate action.
cumulate the required steps and do it once in a single %posttrans.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047852
Bug ID: 1047852
Summary: knotify_libjack audio kcrash on pthread_key_create()
at ../common/JackError.cpp:88
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE3
Assignee: anixx(a)opensuse.org
Reporter: drankinatty(a)suddenlinkmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 731684
--> http://bugzilla.opensuse.org/attachment.cgi?id=731684&action=edit
knotify_libjack wdebug kcrash file (the 6 is just the 6th one I saved)
A knotify/libjack.so.0 crash will regularly occur once during a session. It may
take a day or two for the bug to appear, but on access to sound theme sound (no
one in particular, e.g. dialog-open, minimize, etc.) a kcrash report appears
and the desktop sounds no longer play until you restart the desktop. This time
it took 2 days 5:29 minutes under heavy use to occur.
It is strangely random when it happens, but very consistent that it *will*
happen. This is not new and has been around at least since 13.1 (it may go back
to 11.4). I have experiences this on two separate laptops with 13.1 and Leap
42.2. (I really think it was there in 11.4, but I'm far too old to remember)
I have attached a wdebug.kcrash that details the error.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=952799
Bug ID: 952799
Summary: bogofilter-{db,sqlite3} insists on using wordlist.tc
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: 2015*
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: gour(a)atmarama.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
In the past, when using other Linux distros I was mostly using bogofilter with
sqlite3 back-end, but after switching to openSUSE I've decided to convert to
'default' (Berkeley) DB backend.
Unfortunately, after bogofilter package was updated in openSUSE, it looks it
does insist on using $HOME/.bogofilter/wordlist.tc for the database name even
if one uses Berkeley DB or Sqlite3 back-ends?
When I try to use my old wordlist.db, Bogofilter plugin (Claws & Evolution)
starts from the scratch and creates wordlist.tc.
I wonder about this line in *.spec:
%if 0%{?suse_version} > 1320
iow. whether the new Bogofilter package is ready to use existing setup with
appropriate back-end (not equal to TokyoCabinet)?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=907495
Bug ID: 907495
Summary: adding a manual route to a dhcp configured interface
results in failed dhcp setup (wicked managed)
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Hardware: Other
OS: openSUSE 13.2
Status: NEW
Severity: Major
Priority: P5 - None
Component: Network
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: hpj(a)urpla.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
When adding a manual route to a dhcp configured eth interface managed by
wicked, the dhcp setup fails with a silly message:
device enp7s0 failed: "call to
org.opensuse.Network.Addrconf.ipv4.static.requestLease failed: General failure"
Add a manual route to a dhcp configured interface and restart your system.
Be prepared, that this interface will not come up correctly.
BTW: the routing editor allows selecting configured interfaces only. The usual
order is: setup interface, add route, but you have to confirm the interface
setup first, reenter yast network and add the interface based route there
after.
--
You are receiving this mail because:
You are on the CC list for the bug.
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.