February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1086804] fonts-config warns about ninitialized HOME in posttrans
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1086804 http://bugzilla.opensuse.org/show_bug.cgi?id=1086804#c1 --- Comment #1 from Marguerite Su <i(a)marguerite.su> --- *** Bug 1124118 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124118] fonts-config: use of uninitialized value
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124118 http://bugzilla.opensuse.org/show_bug.cgi?id=1124118#c4 Marguerite Su <i(a)marguerite.su> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Marguerite Su <i(a)marguerite.su> --- it's a duplicate of boo#1086804. *** This bug has been marked as a duplicate of bug 1086804 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124665] New: Imagewriter cant write exotic formats (Windows-ISO)
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124665 Bug ID: 1124665 Summary: Imagewriter cant write exotic formats (Windows-ISO) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Imagewriter 1.10 is properly writing openSUSE Images onto a USB-Stick. Anyway, it fails to write proprietary ISO formats like Windows-ISO (so the assumption, ISO is ISO, independent of content, is wrong) Expected behaviour: Imagewriter should as well write other ISO formats -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124648] New: Please update clamav to version 0.101.1
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124648 Bug ID: 1124648 Summary: Please update clamav to version 0.101.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Freshclam shows the warning: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.100.2 Recommended version: 0.101.1 DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav A repository with version 1.101.1 can be found here: https://build.opensuse.org/package/show/home%3Alrupp/clamav BTW, software.opensuse.org shows the outdated version 0.97.4 for clamav on Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1124647] fwbuilder segfaults when adding new address object from menu
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124647 http://bugzilla.suse.com/show_bug.cgi?id=1124647#c5 --- Comment #5 from alex runge <alexander.runge(a)suse.com> --- > I doubt that upstream has a fix. According to this > https://github.com/fwbuilder/fwbuilder/issues/81 > the issue still exists in 6.0.0 beta (which presumably is master as there is > no such release on github). Sorry, that's not correct, I just noticed that there is a tag v6.0.0-beta -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 978449] zypper creates /var/cache/zypper/ directory and forgets to cleanup (zypper in ./foo.rpm)
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=978449 http://bugzilla.novell.com/show_bug.cgi?id=978449#c2 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WORKSFORME |FIXED --- Comment #2 from Michael Andres <ma(a)suse.com> --- JFYI: fixed in zypper-1.13.23 (Leap-42.2) - Use private temporary repos to collect rpms passed on the command line -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124647] fwbuilder segfaults when adding new address object from menu
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124647 http://bugzilla.suse.com/show_bug.cgi?id=1124647#c4 --- Comment #4 from alex runge <alexander.runge(a)suse.com> --- (In reply to Matthias Gerstner from comment #2) > I can reproduce this issue. The stacktrace in gdb looks like this: > > ``` > at ObjectManipulator_tree_ops.cpp:777 > at ObjectManipulator_create_new.cpp:252 > (_o=0x5555570dc010, _c=QMetaObject::InvokeMetaMethod, _id=24, > _a=0x7fffffffcd10) > at .moc/moc_ObjectManipulator.cpp:297 > [...] > ``` > > It seems the lastClickedItem member variable has an undefined value, > resulting > in the crash. This variable is never initialized to zero. But it *is* set > when > you open the context menu. This allows for a workaround: open a context menu > via right click before continuing with the other actions. Then the segfault > doesn't occur. > > I don't know if upstream fixed this already, can't find anything at first > glance. Thanks for looking into this so quickly :) I doubt that upstream has a fix. According to this https://github.com/fwbuilder/fwbuilder/issues/81 the issue still exists in 6.0.0 beta (which presumably is master as there is no such release on github). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 978449] zypper creates /var/cache/zypper/ directory and forgets to cleanup (zypper in ./foo.rpm)
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=978449 http://bugzilla.novell.com/show_bug.cgi?id=978449#c1 Benjamin Zeller <bzeller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |bzeller(a)suse.com Resolution|--- |WORKSFORME --- Comment #1 from Benjamin Zeller <bzeller(a)suse.com> --- The current zypper version stores temporary repositories in /var/tmp, also the repository is removed when zypper exits. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124152] /etc/resolv.conf no symlink to /run/netconfig/resolv.conf
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124152 http://bugzilla.opensuse.org/show_bug.cgi?id=1124152#c14 --- Comment #14 from Ludwig Nussel <lnussel(a)suse.com> --- is the %post snippet the right way to fix this? In transactional mode rpms are not meant to mess with the running system, right? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124647] fwbuilder segfaults when adding new address object from menu
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124647 http://bugzilla.suse.com/show_bug.cgi?id=1124647#c3 --- Comment #3 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- Sorry, my stacktrace above is incomplete. Here it is again: > #0 0x00005555556fcf9a in ObjectTreeViewItem::getUserFolderParent() (this=0x6874202c796c7065) at ObjectTreeViewItem.h:60 > #1 0x0000555555707871 in ObjectManipulator::moveItems(ObjectTreeViewItem*, std::__cxx11::list<libfwbuilder::FWObject*, std::allocator<libfwbuilder::FWObject*> > const&) (this=0x5555570dc010, dest=0x6874202c796c7065, items=...) > at ObjectManipulator_tree_ops.cpp:777 > #2 0x000055555570b4e0 in ObjectManipulator::createNewObject() (this=0x5555570dc010) > at ObjectManipulator_create_new.cpp:252 > #3 0x0000555555a33881 in ObjectManipulator::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) > (_o=0x5555570dc010, _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0x7fffffffcd10) > at .moc/moc_ObjectManipulator.cpp:297 > #4 0x00007ffff56e104a in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 > #5 0x00007ffff67c1cf2 in QAction::triggered(bool) () at /usr/lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 0