July 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 838107] New: Activities overview background changes to a green oval background
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=838107 https://bugzilla.novell.com/show_bug.cgi?id=838107#c0 Summary: Activities overview background changes to a green oval background Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: firebird209(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 I encountered this issue on openSUSE 13.1 Milestone 4, while using the gnome live cd. When I go to the Activities Overview, the background, which is otherwise the background that 12.3 uses, changes to that of a background with a green oval on it. When exiting the Activities Overview, the screen fades to being completely green (bright green) for a split second, then goes back to the gnome desktop (and the default background shows again). Reproducible: Always Steps to Reproduce: 1. Boot openSUSE 13.1 Milestone 4 live gnome 2. Open Activities Overview (and watch the background change) 3. Exit Activities Overview Actual Results: The Activities Overview background changed from the default gnome background to that of background with a green oval. Expected Results: The expected result would be that the background for Activities Overview is a dim version of the default background. -- 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 848065] New: splitting backgrounds in metatheme-adwaita-common to a separate subpackage
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=848065 https://bugzilla.novell.com/show_bug.cgi?id=848065#c0 Summary: splitting backgrounds in metatheme-adwaita-common to a separate subpackage Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: fcrozat(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently, the backgrounds in /usr/share/themes/Adwaita/backgrounds are part of the main metatheme-adwaita-common, which will cause those to be installed by default, even when openSUSE background is the default. It might be worth splitting those backgrounds in a separate subpackage. Installing or not this subpackage by default is a separate question (Vincent was suggesting it might be nice to install it by default, to please upstream). -- 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 3

[Bug 864823] New: Gedit 3.11.9 won't launch
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=864823 https://bugzilla.novell.com/show_bug.cgi?id=864823#c0 Summary: Gedit 3.11.9 won't launch Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: 64bit OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: Antoine.Saroufim(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X) AppleWebKit/538.15 (KHTML, like Gecko) Safari/538.15 SUSE/13.2 (3.11.4) Epiphany/3.11.4 gedit 3.11.9 won't start. It spews out the following terminal output: edit: symbol lookup error: gedit: undefined symbol: g_application_add_main_option_entries Reproducible: Always Steps to Reproduce: 1.open a terminal 2.type "gedit" 3.observe error Actual Results: gedit won't start Expected Results: gedit starts -- 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 3

[Bug 866522] New: Bijiben crashes when trying to open a note
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=866522 https://bugzilla.novell.com/show_bug.cgi?id=866522#c0 Summary: Bijiben crashes when trying to open a note Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: Antoine.Saroufim(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X) AppleWebKit/538.15 (KHTML, like Gecko) Safari/538.15 SUSE/13.2 (3.11.90) Epiphany/3.11.90 Bijiben crashes when trying to open a note. I filed this bug upstream but the developer told me to take it downstream. Here's the upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=725396 Reproducible: Always Steps to Reproduce: 1.open bijiben 2.click on an existing note 3.notice the crash Actual Results: Bijiben crashes when trying to view notes Expected Results: Bijiben not to crash -- 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 3

[Bug 871638] New: YaST got signal 11 at YCP file /usr/share/YaST2/modules/PackageCallbacks.rb:253
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=871638 https://bugzilla.novell.com/show_bug.cgi?id=871638#c0 Summary: YaST got signal 11 at YCP file /usr/share/YaST2/modules/PackageCallbacks.rb:253 Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: mpluskal(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=584739) --> (http://bugzilla.novell.com/attachment.cgi?id=584739) y2logs Steps to reproduce: 1) Start yast2 squid module 2) squid is not installed therefore yast2 squid asks if I want to install squid 3) yes error occurs: YaST got signal 11 at YCP file /usr/share/YaST2/modules/PackageCallbacks.rb:253 /sbin/yast2: line 429: 14804 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS from y2log: 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 Error: signal 11 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [hd]: (-3) /usr/lib64/libzypp.so.1416 : zypp::dumpBacktrace(std::ostream&)+0x26 [0x7fa114dc5366] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [hd]: (-2) /usr/lib64/libzypp.so.1416 : +0x302cde [0x7fa114d80cde] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [hd]: (-1) /lib64/libc.so.6 : +0x35880 [0x7fa1185fa880] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 vvvvvvvvvv---------------------------------------- 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (0) /usr/lib64/libkdecore.so.5 : +0x9f1ce [0x7fa0effdf1ce] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (1) /lib64/ld-linux-x86-64.so.2 : +0xe92a [0x7fa11ac4592a] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (2) /lib64/ld-linux-x86-64.so.2 : +0xea13 [0x7fa11ac45a13] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (3) /lib64/ld-linux-x86-64.so.2 : +0x12b68 [0x7fa11ac49b68] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (4) /lib64/ld-linux-x86-64.so.2 : +0xe7e4 [0x7fa11ac457e4] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (5) /lib64/ld-linux-x86-64.so.2 : +0x1235b [0x7fa11ac4935b] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (6) /lib64/libdl.so.2 : +0x102b [0x7fa1195b202b] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (7) /lib64/ld-linux-x86-64.so.2 : +0xe7e4 [0x7fa11ac457e4] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (8) /lib64/libdl.so.2 : +0x15dd [0x7fa1195b25dd] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (9) /lib64/libdl.so.2 : dlopen+0x31 [0x7fa1195b20c1] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (10) /usr/lib64/libmodman.so.1 : libmodman::module_manager::load_file(std::string, bool)+0x375 [0x7fa111e96f25] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (11) /usr/lib64/libmodman.so.1 : libmodman::module_manager::load_dir(std::string, bool)+0x253 [0x7fa111e972b3] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (12) /usr/lib64/libproxy.so.1 : +0xce16 [0x7fa113c93e16] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (13) /usr/lib64/libproxy.so.1 : px_proxy_factory_new+0x1b [0x7fa113c949cb] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (14) /usr/lib64/libzypp.so.1416 : zypp::media::ProxyInfoLibproxy::ProxyInfoLibproxy()+0x261 [0x7fa114b70dc1] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (15) /usr/lib64/libzypp.so.1416 : zypp::media::ProxyInfo::ProxyInfo()+0x1c [0x7fa114b9b0ac] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (16) /usr/lib64/libzypp.so.1416 : zypp::media::fillSettingsSystemProxy(zypp::Url const&, zypp::media::TransferSettings&)+0x22 [0x7fa114b9c202] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (17) /usr/lib64/libzypp.so.1416 : zypp::media::MediaCurl::setupEasy()+0x263 [0x7fa114ba4353] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (18) /usr/lib64/libzypp.so.1416 : zypp::media::MediaMultiCurl::setupEasy()+0xe [0x7fa114bb0d2e] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (19) /usr/lib64/libzypp.so.1416 : zypp::media::MediaCurl::attachTo(bool)+0xae [0x7fa114b9d90e] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (20) /usr/lib64/libzypp.so.1416 : zypp::media::MediaHandler::attach(bool)+0x94 [0x7fa114b81054] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (21) /usr/lib64/libzypp.so.1416 : zypp::media::MediaAccess::attach(bool)+0x1d [0x7fa114b76e8d] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (22) /usr/lib64/libzypp.so.1416 : zypp::media::MediaManager::attach(unsigned int)+0x104 [0x7fa114bc2dd4] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (23) /usr/lib64/libzypp.so.1416 : zypp::MediaSetAccess::provide(boost::function<void (unsigned int, zypp::filesystem::Pathname const&)>, zypp::OnMediaLocation const&, zypp::base::Flags<zypp::MediaSetAccess::ProvideFileOption>, zypp::filesystem::Pathname const&)+0x29b [0x7fa114cf1a4b] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (24) /usr/lib64/libzypp.so.1416 : zypp::MediaSetAccess::provideFile(zypp::OnMediaLocation const&, zypp::base::Flags<zypp::MediaSetAccess::ProvideFileOption>, zypp::filesystem::Pathname const&)+0x4e [0x7fa114cf2c8e] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (25) /usr/lib64/libzypp.so.1416 : zypp::Fetcher::Impl::provideToDest(zypp::MediaSetAccess&, zypp::OnMediaLocation const&, zypp::filesystem::Pathname const&, zypp::filesystem::Pathname const&)+0xa6 [0x7fa114cccd66] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (26) /usr/lib64/libzypp.so.1416 : zypp::Fetcher::Impl::start(zypp::filesystem::Pathname const&, zypp::MediaSetAccess&, boost::function<bool (zypp::ProgressData const&)> const&)+0x5fc [0x7fa114cd028c] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (27) /usr/lib64/libzypp.so.1416 : zypp::repo::RepoMediaAccess::provideFile(zypp::RepoInfo, zypp::OnMediaLocation const&, zypp::ProvideFilePolicy const&)+0x800 [0x7fa114c00250] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (28) /usr/lib64/libzypp.so.1416 : zypp::repo::PackageProvider::Impl::doProvidePackage() const+0x48a [0x7fa114bf8a3a] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (29) /usr/lib64/libzypp.so.1416 : zypp::repo::RpmPackageProvider::doProvidePackage() const+0xdb [0x7fa114bfc39b] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (30) /usr/lib64/libzypp.so.1416 : zypp::repo::PackageProvider::Impl::providePackage() const+0x5b2 [0x7fa114bf9662] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (31) /usr/lib64/libzypp.so.1416 : zypp::repo::PackageProvider::providePackage() const+0x11 [0x7fa114bfa9f1] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (32) /usr/lib64/libzypp.so.1416 : +0x1dee7b [0x7fa114c5ce7b] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (33) /usr/lib64/libzypp.so.1416 : +0x1cb6c6 [0x7fa114c496c6] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (34) /usr/lib64/libzypp.so.1416 : zypp::target::CommitPackageCacheReadAhead::get(zypp::PoolItem const&)+0x7f [0x7fa114c4aaff] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (35) /usr/lib64/libzypp.so.1416 : zypp::target::CommitPackageCache::get(zypp::PoolItem const&)+0x12 [0x7fa114c49262] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (36) /usr/lib64/libzypp.so.1416 : zypp::target::TargetImpl::commit(zypp::ResPool, zypp::ZYppCommitPolicy const&)+0x10c3 [0x7fa114c5ae93] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (37) /usr/lib64/libzypp.so.1416 : zypp::zypp_detail::ZYppImpl::commit(zypp::ZYppCommitPolicy const&)+0x14d [0x7fa114d852cd] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (38) /usr/lib64/libzypp.so.1416 : zypp::ZYpp::commit(zypp::ZYppCommitPolicy const&)+0x12 [0x7fa114d7e032] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (39) /usr/lib64/YaST2/plugin/libpy2Pkg.so.2 : PkgFunctions::CommitHelper(zypp::ZYppCommitPolicy const*)+0x7f [0x7fa1151fc4af] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (40) /usr/lib64/YaST2/plugin/libpy2Pkg.so.2 : PkgFunctions::PkgCommit(YCPInteger const&)+0x69 [0x7fa1151fd3a9] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (41) /usr/lib64/YaST2/plugin/libpy2Pkg.so.2 : Y2PkgFunction::evaluateCall()+0xb6cc [0x7fa11526555c] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (42) /usr/lib64/ruby/vendor_ruby/2.1.0/x86_64-linux-gnu/yastx.so : +0xa3d2 [0x7fa116e263d2] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (43) /usr/lib64/libruby.so.2.1 : +0x173a54 [0x7fa117aeaa54] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (44) /usr/lib64/libruby.so.2.1 : +0x18055d [0x7fa117af755d] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (45) /usr/lib64/libruby.so.2.1 : +0x177ee5 [0x7fa117aeeee5] 2014-04-02 14:23:12 <5> theseus(14804) [zypp] ZYppFactory.cc(sigsegvHandler):53 [bt]: (46) /usr/lib64/libruby.so.2.1 : +0x17bc78 [0x7fa117af2c78] 2014-04-02 14:23:12 <2> theseus(14804) [qt-ui] YQUI.cc(qMessageHandler):716 <libqt-warning> QFSFileEngine::open: No file name specified -- 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 4

[Bug 876764] New: RFC: should system-config-printer-applet be still recommend to be installed?
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=876764 https://bugzilla.novell.com/show_bug.cgi?id=876764#c0 Summary: RFC: should system-config-printer-applet be still recommend to be installed? Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: SUSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: jsmeix(a)suse.com QAContact: qa-bugs(a)suse.de CC: fcrozat(a)suse.com Found By: Development Blocker: No This is a request for comments whether or not system-config-printer-applet should be still recommend to be installed? "man system-config-printer-applet" reads: --------------------------------------------------------------------------- As well as displaying a printer icon in the notification area, the applet also provides a D-BUS server for the com.redhat.PrintDriverSelection interface, to help configure a new printer when it is plugged in. --------------------------------------------------------------------------- This seems to indicate that system-config-printer-applet is somehow needed to configure a new printer when it is plugged in. But a few days ago Frederic Crozat told me: --------------------------------------------------------------------------- On Fedora, upstream is not starting the applet under GNOME environment ... And upstream manpage is obsolete, com.redhat.PrintDriverSelection is not provided by anything in system-config-printer upstream tarball --------------------------------------------------------------------------- Now it seems system-config-printer-applet does no longer make sense. At least it seems it does no longer make sense to install system-config-printer-applet by whatever automatism. Currently such an automatism is that udev-configure-printer and system-config-printer recommend system-config-printer-applet so that zypper would "silently" install system-config-printer-applet whenever it is available to be installed. In GNOME:Factory system-config-printer system-config-printer.spec there is (long lines shown wrapped here): --------------------------------------------------------------------------- Name: system-config-printer ... # PATCH-FIX-UPSTREAM system-config-printer-no-applet-in-gnome.patch rh#677676 fcrozat(a)suse.com -- Do not start applet in GNOME Patch21: system-config-printer-no-applet-in-gnome.patch ... # The applet is not strictly necessary, but it really makes sense Recommends: %{name}-applet . . . %package -n udev-configure-printer ... Recommends: %{name}-applet --------------------------------------------------------------------------- For me it looks contradictory to have a patch that does no longer start the applet but recommend it to be installed. Therefore I wonder whether or not system-config-printer-applet should be still recommend to be installed. -- 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 1

[Bug 888822] New: Radeon driver distributed with OS13.1 restarts X when the Mathematica 10.0 file picker is activated.
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=888822 https://bugzilla.novell.com/show_bug.cgi?id=888822#c0 Summary: Radeon driver distributed with OS13.1 restarts X when the Mathematica 10.0 file picker is activated. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: hattons(a)globalsymmetry.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 The trial version of Mathematica 10.0 for Linux x86 (64-bit) (June 29, 2014) causes X to restart when the file-picker icon is clicked. This happens with the Radeon driver distributed with OS13.1. I replaced the driver with the driver found here: http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_13.1/ That corrected the problem. I have a Radeon HD 7700 graphics device. This is used the KDE distributed with OS13.1. All patches are current. Reproducible: Always Steps to Reproduce: 1. Download the Mathematica 10.0 trial http://www.wolfram.com/mathematica/trial/ 2. Install Mathematica 3. Launch Mathematica 4. Attempt to open a file. Actual Results: X-Windows restarts and a new login screen is displayed. Expected Results: Mathematica file picker opens and displays available files. Even though there is a fix, the problem indicates a fundamental vulnerability in the Radeon driver distributed with OS13.1. -- 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 1

[Bug 879775] New: Apparent timeouts initializing USB ports
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=879775 https://bugzilla.novell.com/show_bug.cgi?id=879775#c0 Summary: Apparent timeouts initializing USB ports Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: nrickert(a)ameritech.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=591923) --> (http://bugzilla.novell.com/attachment.cgi?id=591923) Typescript (from "script" command) showing some relevant output User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 The computer is a Lenovo ThinkServer TS140. During boot, there are apparent error messages relating to USB ports. I'm using crypto, and prompted for an encryption key. But what I type in is ignored for around 2 minutes, after which it starts to work. I see similar behavior with 13.1, with Ubuntu 14.04, and with the siduction LXQt live image. The problem started to show up after a BIOS update. So this is likely related to the way that the BIOS initializes/configures USB ports. The system is still usable -- I just have to wait out those timeouts on booting. I'm not really expecting a fix. I'm reporting, because I suspect this might be a future problem that we will see more of. I'll attach a "typescript" showing the output from: dmesg | grep -i usb lsusb Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 1

[Bug 885053] New: dns problem /etc/resolv, if link-local-adress is given - host and dig don't work properly
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=885053 https://bugzilla.novell.com/show_bug.cgi?id=885053#c0 Summary: dns problem /etc/resolv, if link-local-adress is given - host and dig don't work properly Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tschaefer(a)t-online.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 Some routers (Telekom speedports, Vodafone W5101) provide IPv6-link-local-adresses for resolving DNS: nameserver fe80::d27a:b5ff:fe7b:e152%wlan0 This works well in browsers and some other applications , also ping works: hpmini:/# ping6 heise.de PING heise.de(redirector.heise.de) 56 data bytes 64 bytes from redirector.heise.de: icmp_seq=1 ttl=53 time=785 ms 64 bytes from redirector.heise.de: icmp_seq=2 ttl=53 time=325 ms 64 bytes from redirector.heise.de: icmp_seq=3 ttl=53 time=303 ms ^C --- heise.de ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 303.937/471.463/785.384/222.143 ms But tools like host and dig don't work: host heise.de ;; connection timed out; no servers could be reached dig heise.de ; <<>> DiG 9.9.4-rpz2.13269.14-P2 <<>> heise.de ;; global options: +cmd ;; connection timed out; no servers could be reached Of course most sites use dualstack. But also in an IPv6-only-environment some important diagnose tools should work. Reproducible: Always Steps to Reproduce: Switch off IPv4 at your Router. Connect via Networkmanager. Everything works fine, except the things above. Actual Results: connection timed out; no servers could be reached Expected Results: normal answer -- 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 1

[Bug 885927] New: System re-resumes ca. one hour after resume from hibernation
by bugzilla_noreply＠novell.com 24 Jul '14

24 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=885927 https://bugzilla.novell.com/show_bug.cgi?id=885927#c0 Summary: System re-resumes ca. one hour after resume from hibernation Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joerg.strebel(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=597364) --> (http://bugzilla.novell.com/attachment.cgi?id=597364) /Var/log/messages User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36 After upgrading from openSuSe 12.3 64bit to 13.1 64bit, the system starts the resume process ca. one hour after it has first resumed from hibernation. When working in KDE4, I suddenly see the text console with the a resume message, and it re-resumes the old session from the last hibernation, although I've been working with the system for ca. an hour after the last resume. After the re-resume was successful (it is always successful), I see the logon screen of KDE4. When I enter my password, it does not log me onto the system, but it briefly flashes the KDE desktop and then the KDE logon screen re-appears. I cannot escape the loop except through a reboot. Reproducible: Sometimes Steps to Reproduce: 1. Start KDE4, log on 2. Hibernate system 3. Start up system (resume) 4. Work in KDE4 5. Re-resume happens (without the user triggering it) 6. Logon loop Actual Results: The system gets stuck in a logon loop (logon is no longer successful, although password is correctly given) Expected Results: No automatic re-resume -- 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 2