November 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 902464] autoyast after reboot does not load network before scripts
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=902464 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #6 from Stefan Schubert <schubi(a)suse.com> --- As far I see in the documentation and the source code <network_needed config:type="boolean">true</network_needed> is not supported in the <ask> section of autoyast. So, a solution would bee to save the settings of the ask section in a temporary file and call your script in the post_install_script or init_scripts section of autoyast. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903551] New: zypper: terminate called after throwing an instance of 'std::out_of_range'
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903551 Bug ID: 903551 Summary: zypper: terminate called after throwing an instance of 'std::out_of_range' Classification: openSUSE Product: openSUSE Factory Version: NO 13.2 BUGS!! Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: ma(a)suse.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- During zypper dup, when one of repositories had somehow corrupted metadata, following occured: Continuing might be risky. Continue anyway? [yes/no] (no): yes File './repodata/f2820a883d58529e0598989d7e177dd2fd1bec288196477ae3a8e6c8b35cd1e8-primary.xml.gz' not found on medium 'http://download.suse.de/ibs/QA:/Maintenance/openSUSE_Factory/' Abort, retry, ignore? [a/r/i/? shows all options] (a): i Retrieving repository 'tools specific to QA Maintenance (no test suites!) (openSUSE_Factory)' metadata .......................................................................................................................[error] Repository 'tools specific to QA Maintenance (no test suites!) (openSUSE_Factory)' is invalid. [QA_Maintenance|http://download.suse.de/ibs/QA:/Maintenance/openSUSE_Factory/] Valid metadata not found at specified URL Please check if the URIs defined for this repository are pointing to a valid repository. ... Retrieving package apparmor-docs-2.9.0-1.1.noarch (17/500), 0 B ( 0 B unpacked) terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::substr Aborted (core dumped) bt (from coredump): #0 0x00007f09eb7600f7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x00007f09eb7614ca in __GI_abort () at abort.c:78 #2 0x00007f09ec046145 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 #3 0x00007f09ec0442e6 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38 #4 0x00007f09ec044313 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48 #5 0x00007f09ec044532 in __cxxabiv1::__cxa_throw (obj=0x1e10500, tinfo=0x7f09ec2cd1d0 <typeinfo for std::out_of_range>, dest=0x7f09ec058380 <std::out_of_range::~out_of_range()>) at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:87 #6 0x00007f09ec0956f7 in std::__throw_out_of_range (__s=__s@entry=0x7f09ecb6bd67 "basic_string::substr") at ../../../../../libstdc++-v3/src/c++11/functexcept.cc:80 #7 0x00007f09ec8a0fa6 in _M_check (__s=0x7f09ecb6bd67 "basic_string::substr", __pos=1, this=0x7fff03b6d0f0) at /usr/include/c++/4.8/bits/basic_string.h:324 #8 substr (__n=18446744073709551615, __pos=1, this=0x7fff03b6d0f0) at /usr/include/c++/4.8/bits/basic_string.h:2208 #9 zypp::media::MediaCurl::getFileUrl (this=this@entry=0x1e49d60, filename_r=...) at /usr/src/debug/libzypp-14.29.4/zypp/media/MediaCurl.cc:854 #10 0x00007f09ec8ac827 in zypp::media::MediaCurl::getFileCopy (this=0x1e49d60, filename=..., target=...) at /usr/src/debug/libzypp-14.29.4/zypp/media/MediaCurl.cc:880 #11 0x00007f09ec89f9a1 in zypp::media::MediaCurl::getFile (this=0x1e49d60, filename=...) at /usr/src/debug/libzypp-14.29.4/zypp/media/MediaCurl.cc:871 #12 0x00007f09ec881b6d in zypp::media::MediaHandler::provideFile (this=0x1e49d60, filename=...) at /usr/src/debug/libzypp-14.29.4/zypp/media/MediaHandler.cc:997 #13 0x00007f09ec87aed3 in zypp::media::MediaAccess::provideFile (this=0x1e35860, filename=...) at /usr/src/debug/libzypp-14.29.4/zypp/media/MediaAccess.cc:346 #14 0x00007f09ec8c785e in zypp::media::MediaManager::provideFile (this=this@entry=0x7fff03b6d55e, accessId=accessId@entry=4, filename=...) at /usr/src/debug/libzypp-14.29.4/zypp/media/MediaManager.cc:693 #15 0x00007f09eca0b250 in operator() (file=..., media=4, this=0x7fff03b6d8f0) at /usr/src/debug/libzypp-14.29.4/zypp/MediaSetAccess.cc:114 #16 boost::detail::function::void_function_ref_invoker2<zypp::ProvideFileOperation, void, unsigned int, zypp::filesystem::Pathname const&>::invoke (function_obj_ptr=..., a0=4, a1=...) at /usr/include/boost/function/function_template.hpp:188 #17 0x00007f09eca0888a in operator() (a1=..., a0=4, this=0x7fff03b6d900) at /usr/include/boost/function/function_template.hpp:767 #18 zypp::MediaSetAccess::provide(boost::function<void (unsigned int, zypp::filesystem::Pathname const&)>, zypp::OnMediaLocation const&, zypp::base::Flags<zypp::MediaSetAccess::ProvideFileOption>, zypp::filesystem::Pathname con&) (this=this@entry=0x332d210, op=..., resource=..., options=..., deltafile=...) at /usr/src/debug/libzypp-14.29.4/zypp/MediaSetAccess.cc:210 #19 0x00007f09eca09b5e in zypp::MediaSetAccess::provideFile (this=this@entry=0x332d210, resource=..., options=..., deltafile=...) at /usr/src/debug/libzypp-14.29.4/zypp/MediaSetAccess.cc:160 #20 0x00007f09ec9e3a66 in zypp::Fetcher::Impl::provideToDest (this=this@entry=0x1e16cc0, media=..., resource=..., dest_dir=..., deltafile=...) at /usr/src/debug/libzypp-14.29.4/zypp/Fetcher.cc:552 #21 0x00007f09ec9e7181 in zypp::Fetcher::Impl::start(zypp::filesystem::Pathname const&, zypp::MediaSetAccess&, boost::function<bool (zypp::ProgressData const&)> const&) (this=0x1e16cc0, dest_dir=..., media=..., progress_receiver=...) at /usr/src/debug/libzypp-14.29.4/zypp/Fetcher.cc:799 #22 0x00007f09ec9e79e0 in zypp::Fetcher::start(zypp::filesystem::Pathname const&, zypp::MediaSetAccess&, boost::function<bool (zypp::ProgressData const&)> const&) (this=this@entry=0x7fff03b6e4a0, dest_dir=..., media=..., progress_receiver=...) at /usr/src/debug/libzypp-14.29.4/zypp/Fetcher.cc:916 #23 0x00007f09ec90503c in zypp::repo::RepoMediaAccess::provideFile (this=0x1da4270, repo_r=..., loc_r=..., policy_r=...) at /usr/src/debug/libzypp-14.29.4/zypp/repo/RepoProvideFile.cc:309 #24 0x00007f09ec8fc4da in zypp::repo::PackageProvider::Impl::doProvidePackage (this=this@entry=0x1e3ed80) at /usr/src/debug/libzypp-14.29.4/zypp/repo/PackageProvider.cc:206 #25 0x00007f09ec9013db in zypp::repo::RpmPackageProvider::doProvidePackage (this=0x1e3ed80) at /usr/src/debug/libzypp-14.29.4/zypp/repo/PackageProvider.cc:384 #26 0x00007f09ec8fd512 in zypp::repo::PackageProvider::Impl::providePackage (this=0x1e3ed80) at /usr/src/debug/libzypp-14.29.4/zypp/repo/PackageProvider.cc:266 #27 0x00007f09ec8ffa31 in zypp::repo::PackageProvider::providePackage (this=this@entry=0x7fff03b6f7c0) at /usr/src/debug/libzypp-14.29.4/zypp/repo/PackageProvider.cc:489 #28 0x00007f09ec950adb in zypp::target::RepoProvidePackage::operator() (this=0x1da4238, pi=..., fromCache_r=<optimized out>) at /usr/src/debug/libzypp-14.29.4/zypp/target/CommitPackageCache.cc:95 #29 0x00007f09ec96668c in boost::detail::function::function_obj_invoker2<zypp::target::RepoProvidePackage, zypp::AutoDispose<zypp::filesystem::Pathname const>, zypp::PoolItem const&, bool>::invoke (function_obj_ptr=..., a0=..., a1=<optimized out>) at /usr/include/boost/function/function_template.hpp:132 #30 0x00007f09ec951cf6 in operator() (a1=false, a0=..., this=<optimized out>) at /usr/include/boost/function/function_template.hpp:767 #31 zypp::target::CommitPackageCache::Impl::sourceProvidePackage (this=<optimized out>, pi=...) at /usr/src/debug/libzypp-14.29.4/zypp/target/CommitPackageCacheImpl.h:82 #32 0x00007f09ec95352a in zypp::target::CommitPackageCacheReadAhead::get (this=0x1da4210, citem_r=...) at /usr/src/debug/libzypp-14.29.4/zypp/target/CommitPackageCacheReadAhead.cc:179 #33 0x00007f09ec9510a2 in zypp::target::CommitPackageCache::get (this=this@entry=0x7fff03b6fe20, citem_r=...) at /usr/src/debug/libzypp-14.29.4/zypp/target/CommitPackageCache.cc:133 #34 0x00007f09ec964613 in zypp::target::TargetImpl::commit (this=0xb7bbf0, pool_r=..., policy_rX=...) at /usr/src/debug/libzypp-14.29.4/zypp/target/TargetImpl.cc:1409 #35 0x00007f09ecaa258d in zypp::zypp_detail::ZYppImpl::commit (this=0xa8b2a0, policy_r=...) at /usr/src/debug/libzypp-14.29.4/zypp/zypp_detail/ZYppImpl.cc:145 #36 0x00007f09eca9b1c2 in zypp::ZYpp::commit (this=<optimized out>, policy_r=...) at /usr/src/debug/libzypp-14.29.4/zypp/ZYpp.cc:99 #37 0x00000000004d218f in solve_and_commit (zypper=...) at /usr/src/debug/zypper-1.11.14/src/solve-commit.cc:763 #38 0x0000000000459ccc in Zypper::doCommand (this=this@entry=0xa791f0) at /usr/src/debug/zypper-1.11.14/src/Zypper.cc:4689 #39 0x000000000046789d in Zypper::safeDoCommand (this=0xa791f0) at /usr/src/debug/zypper-1.11.14/src/Zypper.cc:1042 #40 0x0000000000435af3 in Zypper::main (this=0xa791f0, argc=argc@entry=2, argv=argv@entry=0x7fff03b72248) at /usr/src/debug/zypper-1.11.14/src/Zypper.cc:188 #41 0x0000000000434df1 in main (argc=2, argv=0x7fff03b72248) at /usr/src/debug/zypper-1.11.14/src/main.cc:111 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 903468] WARNING: CPU: 0 PID: 2092 at ../fs/btrfs/extent_io.c:430 insert_state+0x13d/0x160 [btrfs]()
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=903468 David Sterba <dsterba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from David Sterba <dsterba(a)suse.com> --- Fixed in 3.17.2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903672] New: polarssl 1.3.8 used in a server picks weaker signature algorithm than available
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903672 Bug ID: 903672 Summary: polarssl 1.3.8 used in a server picks weaker signature algorithm than available Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: fisiu(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- "On the security front this release fixes a mistake in the negotiation introduced in PolarSSL 1.3.8. The mistake resulted in servers negotiating a weaker signature algorithm than available. In addition two remotely-triggerable memory leaks were found by the Codenomicon Defensics tool and fixed in this release. No new features are introduced in this release. A number of changes in behaviour and bug fixes are included." https://polarssl.org/tech-updates/releases/polarssl-1.3.9-released -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 871798] New: using displaylink device for extended desktop renders desktop unusable
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

https://bugzilla.novell.com/show_bug.cgi?id=871798 https://bugzilla.novell.com/show_bug.cgi?id=871798#c0 Summary: using displaylink device for extended desktop renders desktop unusable Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: All Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: damianatorrpm(a)gmail.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.152 Safari/537.36 Description of problem: I try to use the Plugable UD160A as a docking station for an extended desktop. To do this as Lennart Poettering suggested http://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg12801.ht… I dropped the auto seat logic in /etc/udev/rules.d/ After reboot as expected the display is detected at the same seat and is available, but whole X and every application is unusable slow, the window moving and every click happens with very long delay. Immediately after disconnecting the displaylink device the system is perfectly fast again. How reproducible: always (openSUSE 13.1 - latest updates), happens with GNOME and KDE (with and without desktop acceleration enabled) Steps to Reproduce: 1. Drop autoseat for multiseat device Plugable UD160A 2. Connect the device (or if it is connected, reboot). 3. System is unusable. PS: As multiseat config both seats are perfectly fast. Does with the udl driver the rendering happen in the main GPU (I know there was work on it)? Maybe the rendering is set to happen on the main GPU only if it is set as a separate seat but not when set as extended desktop to current seat? Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 903468] WARNING: CPU: 0 PID: 2092 at ../fs/btrfs/extent_io.c:430 insert_state+0x13d/0x160 [btrfs]()
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=903468 Filipe Manana <fdmanana(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdmanana(a)suse.com --- Comment #1 from Filipe Manana <fdmanana(a)suse.com> --- Fixed in 3.18-rc1: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902628] Installer does not disable other option when choosing location to install bootcode
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.suse.com/show_bug.cgi?id=902628 Jiri Srain <jsrain(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jsrain(a)suse.com) | --- Comment #5 from Jiri Srain <jsrain(a)suse.com> --- The problem here, which I see, is that the options are not mutually exclusive. It can make sense to keep the additional copy in boot sector - in case MBR gets accidentally rewritten by other operating system, for example. Also, when enabling MBR, accidentally keeping BL also in root partition does not cause any harm (otherwise, it would). Instead of changing the logic, I would rather think about a redesign of the solution - instead of having the links change settings instantaly, they could show a pop-up with a selection of possible targets. Anyway, this is for discussion with usability experts. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903661] New: Application:Geo/postgis: Bug
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903661 Bug ID: 903661 Summary: Application:Geo/postgis: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dassau(a)gbd-consult.de Reporter: kdejaeger(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: opensuse(a)dstoecker.de, tzotsos(a)gmail.com Found By: --- Blocker: No Is it possible to make an rpm for postgis for OpenSuse 13.2? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 730147] Incorrect hostname displayed on login screen
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=730147 Per Jessen <per(a)computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|KDE4 Workspace |KDE4 Workspace Version|Final |13.2 Beta 1 Resolution|WONTFIX |--- Product|openSUSE 12.1 |openSUSE Factory --- Comment #6 from Per Jessen <per(a)computer.org> --- I am reopening this, the problem is still present in openSUSE 13.2 & Factory -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902154] VUL-0: phpMyAdmin: XSS vulnerabilities in SQL debug output and server monitor page.
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=902154 --- Comment #2 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2014:1347-1: An update that fixes one vulnerability is now available. Category: security (moderate) Bug References: 902154 CVE References: CVE-2014-8326 Sources used: openSUSE 13.1 (src): phpMyAdmin-4.1.14.6-20.1 openSUSE 12.3 (src): phpMyAdmin-4.1.14.6-1.28.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0