January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 675064] New: [zypper] no interface to query/set RequestedLocales
by bugzilla_noreply＠novell.com 15 Feb '19

15 Feb '19

https://bugzilla.novell.com/show_bug.cgi?id=675064 https://bugzilla.novell.com/show_bug.cgi?id=675064#c0 Summary: [zypper] no interface to query/set RequestedLocales Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: ma(a)novell.com QAContact: qa(a)suse.de Found By: Community User Blocker: --- Maintaining the RequestedLocales (packages with language support) with zypper is not possible. Also queries for language supporting packages. -- 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 899819] New: YaST (Qt4) loads gnome icons instead of oxygen
by bugzilla_noreply＠novell.com 15 Feb '19

15 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=899819 Bug ID: 899819 Summary: YaST (Qt4) loads gnome icons instead of oxygen Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: i586 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: quentin(a)links2linux.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Since a couple of weeks (on factory), YaST in Qt4 loads gnome icons instead of the default KDE ones (oxygen). Here is the list of yast packages on my system: http://paste.opensuse.org/81871809 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 692694] New: zypper: add using an inferior version to the problem solver
by bugzilla_noreply＠novell.com 14 Feb '19

14 Feb '19

https://bugzilla.novell.com/show_bug.cgi?id=692694 https://bugzilla.novell.com/show_bug.cgi?id=692694#c0 Summary: zypper: add using an inferior version to the problem solver Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- Suppose this happens: 16:15 server01:~ # zypper in php5-xmlwriter Loading repository data... Reading installed packages... Resolving package dependencies... Problem: php5-xmlwriter-5.3.6.201105090040-73.1.x86_64 requires php5 = 5.3.6.201105090040, but this requirement cannot be provided uninstallable providers: php5-5.3.6.201105090040-73.1.i586[server_php] php5-5.3.6.201105090040-73.1.x86_64[server_php] Solution 1: Following actions will be done: replacement of php5-hash-5.3.3-0.17.1.x86_64 with php5-5.3.6.201105090040-73.1.x86_64 install php5-5.3.6.201105090040-73.1.x86_64 (with vendor change) openSUSE --> obs://build.opensuse.org/server:php install php5-zip-5.3.6.201105090040-73.1.x86_64 (with vendor change) openSUSE --> obs://build.opensuse.org/server:php [...] install apache2-mod_php5-5.3.6.201105090040-73.1.x86_64 (with vendor change) openSUSE --> obs://build.opensuse.org/server:php Solution 2: do not install php5-xmlwriter-5.3.6.201105090040-73.1.x86_64 Solution 3: break php5-xmlwriter by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c): It would be welcome if zypper could offer a "Solution 4: Install php5-xmlwriter-5.3.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 6

[Bug 500134] New: on checksumm errors yast2 software management produces non-informative message
by bugzilla_noreply＠novell.com 14 Feb '19

14 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=500134 Summary: on checksumm errors yast2 software management produces non-informative message Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: grey-olli(a)ya.ru QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=289482) --> (http://bugzilla.novell.com/attachment.cgi?id=289482) 1st time the problem found User-Agent: Opera/9.64 (X11; Linux i686; U; en) Presto/2.1.1 On start of software management repository refresh is started. If checksumm is wrong for a file related to the repository the resulting message doesn't inform to which repository it relates. So if you've a few repositories installed the message is non-informative. Reproducible: Always Expected Results: Should at least tell to which repository the problem relates. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 1017342] New: KDE:Extra: Bug digikam crash when selcting map tool
by bugzilla_noreply＠novell.com 12 Feb '19

12 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 Bug ID: 1017342 Summary: KDE:Extra: Bug digikam crash when selcting map tool Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: kde-maintainers(a)suse.de Reporter: epistemepromeneur(a)free.fr QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- opensuse 42.2 digikam 5.3.0 i replaced all system packages by those of kde applications and kde extra when i click on the map tool then digikam disappears after a short delay. here is the crash report **************************************************************************** Application: digikam (5.3.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: i was clicking on map tool to display the map corresponding to a photo The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Floating point exception Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1c7d63e9c0 (LWP 20881))] Thread 12 (Thread 0x7f1bbffff700 (LWP 20912)): #0 0x00007f1c75110458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c7930c5a8 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x00007f1c793089a0 in ?? () from /usr/lib64/libQt5Core.so.5 #3 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f1be7fff700 (LWP 20897)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6dc8e6e3 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6dfb0341 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f1beffff700 (LWP 20896)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6dc8e6e3 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6dfb0341 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f1bf4dae700 (LWP 20895)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6dc8e6e3 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6dfb0341 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f1bf55af700 (LWP 20894)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6dc8d70d in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6dfb0341 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f1bf657a700 (LWP 20893)): #0 0x00007f1c6fd6269e in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x00007f1c6fd648fb in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f1c6fd65230 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f1c6fd6542c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x00007f1c7951e32b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007f1c794cbfdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #6 0x00007f1c79306f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #9 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f1c3729a700 (LWP 20890)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6df81873 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6df81899 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f1c49880700 (LWP 20887)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c7930c65b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x00007f1c7bf7dc99 in Digikam::ParkingThread::run (this=0x1ea9050) at /usr/src/debug/digikam-5.3.0/core/libs/threads/threadmanager.cpp:115 #3 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f1c4a081700 (LWP 20884)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c7930c65b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x00007f1c7cb99f40 in Digikam::ScanController::run (this=0x7f1c7d4a6ae0 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at /usr/src/debug/digikam-5.3.0/core/libs/database/utils/scancontroller.cpp:677 #3 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f1c4a91a700 (LWP 20883)): #0 0x00007f1c789fc51d in read () from /lib64/libc.so.6 #1 0x00007f1c6fda5670 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f1c6fd64e49 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f1c6fd652a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x00007f1c6fd6542c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x00007f1c7951e32b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #6 0x00007f1c794cbfdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #7 0x00007f1c79306f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x00007f1c753371d5 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #11 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f1c525e5700 (LWP 20882)): #0 0x00007f1c78a0049d in poll () from /lib64/libc.so.6 #1 0x00007f1c6a2cc3e2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007f1c6a2cdfcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x00007f1c540c7839 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #6 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f1c7d63e9c0 (LWP 20881)): [KCrash Handler] #6 0x00007f1c79a65279 in QImageData::create(QSize const&, QImage::Format) () from /usr/lib64/libQt5Gui.so.5 #7 0x00007f1c79a652cb in QImage::QImage(int, int, QImage::Format) () from /usr/lib64/libQt5Gui.so.5 #8 0x00007f1c79a655f3 in QImage::copy(QRect const&) const () from /usr/lib64/libQt5Gui.so.5 #9 0x00007f1c79a65a58 in QImage::QImage(QImage const&) () from /usr/lib64/libQt5Gui.so.5 #10 0x00007f1c73c19f19 in Marble::LabelGraphicsItem::image() const () from /usr/lib64/libmarblewidget-qt5.so.25 #11 0x00007f1b6c891465 in Marble::ElevationProfileMarker::isInitialized (this=<optimized out>) at /usr/src/debug/marble-16.12.0/src/plugins/render/elevationprofilemarker/ElevationProfileMarker.cpp:129 #12 0x00007f1c73ccdf0c in ?? () from /usr/lib64/libmarblewidget-qt5.so.25 #13 0x00007f1c73ccd69e in Marble::MarbleWidgetInputHandler::MarbleWidgetInputHandler(Marble::MarbleAbstractPresenter*, Marble::MarbleWidget*) () from /usr/lib64/libmarblewidget-qt5.so.25 #14 0x00007f1c73c629c1 in ?? () from /usr/lib64/libmarblewidget-qt5.so.25 #15 0x00007f1c73c6285b in ?? () from /usr/lib64/libmarblewidget-qt5.so.25 #16 0x00007f1c73c61ef8 in Marble::MarbleWidget::MarbleWidget(QWidget*) () from /usr/lib64/libmarblewidget-qt5.so.25 #17 0x00007f1c7c293037 in GeoIface::BackendMarble::mapWidget (this=0x2891250) at /usr/src/debug/digikam-5.3.0/core/utilities/geolocation/geoiface/backends/backendmarble.cpp:235 #18 0x00007f1c7c2b7363 in GeoIface::MapWidget::setActive (this=0x28896a0, state=<optimized out>) at /usr/src/debug/digikam-5.3.0/core/utilities/geolocation/geoiface/mapwidget.cpp:2060 #19 0x00007f1c7c0c3ffc in Digikam::ImagePropertiesGPSTab::setActive (this=0x2888630, state=<optimized out>) at /usr/src/debug/digikam-5.3.0/core/libs/imageproperties/imagepropertiesgpstab.cpp:440 #20 0x00007f1c7ccc1784 in Digikam::ImagePropertiesSideBarDB::slotChangedTab (this=0x271c2c0, tab=0x2888630) at /usr/src/debug/digikam-5.3.0/core/libs/imageproperties/imagepropertiessidebardb.cpp:388 #21 0x00007f1c7c0c7e00 in Digikam::ImagePropertiesSideBar::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/digikam-5.3.0/build/core/libs/imageproperties/moc_imagepropertiessidebar.cpp:97 #22 0x00007f1c794f7bb1 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #23 0x00007f1c7c08c42f in Digikam::Sidebar::signalChangedTab (this=<optimized out>, _t1=0x2888630) at /usr/src/debug/digikam-5.3.0/build/core/libs/widgets/moc_sidebar.cpp:536 #24 0x00007f1c7c09201b in Digikam::Sidebar::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/digikam-5.3.0/build/core/libs/widgets/moc_sidebar.cpp:458 #25 0x00007f1c794f7bb1 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #26 0x00007f1c7c08c3ee in Digikam::DMultiTabBarButton::clicked (this=<optimized out>, _t1=3) at /usr/src/debug/digikam-5.3.0/build/core/libs/widgets/moc_sidebar.cpp:208 #27 0x00007f1c794f7bb1 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #28 0x00007f1c7a2cb702 in QAbstractButton::clicked(bool) () from /usr/lib64/libQt5Widgets.so.5 #29 0x00007f1c7a2cb8fa in ?? () from /usr/lib64/libQt5Widgets.so.5 #30 0x00007f1c7a2cc928 in ?? () from /usr/lib64/libQt5Widgets.so.5 #31 0x00007f1c7a2ccaa4 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #32 0x00007f1c7a216c9a in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #33 0x00007f1c7a1d4e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #34 0x00007f1c7a1d9d14 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #35 0x00007f1c794cdfc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #36 0x00007f1c7a1d8a10 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib64/libQt5Widgets.so.5 #37 0x00007f1c7a22f911 in ?? () from /usr/lib64/libQt5Widgets.so.5 #38 0x00007f1c7a231eb3 in ?? () from /usr/lib64/libQt5Widgets.so.5 #39 0x00007f1c7a1d4e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #40 0x00007f1c7a1d949a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #41 0x00007f1c794cdfc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #42 0x00007f1c79a2168b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #43 0x00007f1c79a22e05 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #44 0x00007f1c79a04eeb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Gui.so.5 #45 0x00007f1c540f4bc0 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #46 0x00007f1c6fd65134 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #47 0x00007f1c6fd65388 in ?? () from /usr/lib64/libglib-2.0.so.0 #48 0x00007f1c6fd6542c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #49 0x00007f1c7951e30c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #50 0x00007f1c794cbfdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #51 0x00007f1c794d3ec6 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #52 0x0000000000408946 in main (argc=1, argv=<optimized out>) at /usr/src/debug/digikam-5.3.0/core/app/main/main.cpp:237 ******************************************************************************* gilles caulier says : It crash in Marble shared lib from your system. Use digiKam AppImage instead. It do not crash. Marble used in bundle is clean... -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 989998] New: Tracker Bug nextcloud upstream release
by bugzilla_noreply＠novell.com 12 Feb '19

12 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=989998 Bug ID: 989998 Summary: Tracker Bug nextcloud upstream release Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: asemen(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tracker Bug nextcloud upstream release to version 9.0.53 https://nextcloud.com/ -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 787382] New: 'zypper rm -u' is not thorough enough when dealing with patterns
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

https://bugzilla.novell.com/show_bug.cgi?id=787382 https://bugzilla.novell.com/show_bug.cgi?id=787382#c0 Summary: 'zypper rm -u' is not thorough enough when dealing with patterns Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: yoshi314(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 A simple example to illustate the problem : ------------------------------------------------------------------ a system is installed with no kde4 related patterns. rpm -qa |grep pattern patterns-openSUSE-base-12.2-5.5.1.x86_64 patterns-openSUSE-enhanced_base-12.2-5.5.1.x86_64 patterns-openSUSE-fonts-12.2-5.5.1.x86_64 patterns-openSUSE-minimal_base-12.2-5.5.1.x86_64 patterns-openSUSE-sw_management-12.2-5.5.1.x86_64 patterns-openSUSE-yast2_install_wf-12.2-5.5.1.x86_64 patterns-openSUSE-yast2_basis-12.2-5.5.1.x86_64 A command to install kde4 pattern is issued : ~ # zypper in -t pattern kde4 after installation, a command to remove the same pattern is issued : ~ # zypper rm -u patterns-openSUSE-kde4 ~ # rpm -qa |grep pattern patterns-openSUSE-base-12.2-5.5.1.x86_64 patterns-openSUSE-x11-12.2-5.5.1.x86_64 patterns-openSUSE-enhanced_base-12.2-5.5.1.x86_64 patterns-openSUSE-fonts-12.2-5.5.1.x86_64 patterns-openSUSE-non_oss-12.2-5.5.1.x86_64 patterns-openSUSE-minimal_base-12.2-5.5.1.x86_64 patterns-openSUSE-x11_opt-12.2-5.5.1.x86_64 patterns-openSUSE-imaging-12.2-5.5.1.x86_64 patterns-openSUSE-sw_management-12.2-5.5.1.x86_64 patterns-openSUSE-non_oss_opt-12.2-5.5.1.x86_64 patterns-openSUSE-kde4_basis-12.2-5.5.1.x86_64 patterns-openSUSE-yast2_install_wf-12.2-5.5.1.x86_64 patterns-openSUSE-yast2_basis-12.2-5.5.1.x86_64 ------------------------------------------------------------------------------ A diff of those two outputs : --- pre_pattern.txt 2012-10-30 09:58:46.123122931 -0400 +++ post_pattern.txt 2012-10-30 10:09:09.267068467 -0400 @@ -1,7 +1,13 @@ patterns-openSUSE-base-12.2-5.5.1.x86_64 +patterns-openSUSE-x11-12.2-5.5.1.x86_64 patterns-openSUSE-enhanced_base-12.2-5.5.1.x86_64 patterns-openSUSE-fonts-12.2-5.5.1.x86_64 +patterns-openSUSE-non_oss-12.2-5.5.1.x86_64 patterns-openSUSE-minimal_base-12.2-5.5.1.x86_64 +patterns-openSUSE-x11_opt-12.2-5.5.1.x86_64 +patterns-openSUSE-imaging-12.2-5.5.1.x86_64 patterns-openSUSE-sw_management-12.2-5.5.1.x86_64 +patterns-openSUSE-non_oss_opt-12.2-5.5.1.x86_64 +patterns-openSUSE-kde4_basis-12.2-5.5.1.x86_64 patterns-openSUSE-yast2_install_wf-12.2-5.5.1.x86_64 patterns-openSUSE-yast2_basis-12.2-5.5.1.x86_64 Some patterns remain, even though they were just installed as dependencies for kde4 pattern and should be classified as optional. Reproducible: Always Steps to Reproduce: 1. Install a pattern that pulls in other (not yet installed) patterns 2. Uninstall that pattern with zypper rm -u 3. Subpatterns that were installed as dependencies in 1. are still installed. Actual Results: Pulled in subpatterns remain installed Expected Results: Pulled in subpatterns should be removed if they were not explictly installed by user and are not depended upon by some other packages openSUSE 12.2 ; libzypp 11.6.2-2.1.2.x86_64 zypper-1.7.3-1.2.2.x86_64 -- 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 6

[Bug 536846] New: rebuild RPM DB automatically and silently when necessary
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=536846 Summary: rebuild RPM DB automatically and silently when necessary Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: urwald(a)gmx-topmail.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-2.4 Firefox/3.5.2 Sometimes, the RPM database is broken. Than, when you try to install packages with YaST, you get some complicate error messages like Subprocess failed. Error: RPM fallido: error: db4 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found error: error(-30987) setting "System/Libraries" records from Group index error: db4 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found error: error(-30987) getting "System/Libraries" records from Group index or Subprocess failed. Error: RPM fallido: error: db4 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found error: error(-30987) getting "" records from Requireversion index Executing 'rpm --rebuilddb' fixes the problem, but that's not user friendly. It would be great if libzypper could the this automatically when it notices that there are problems with the RPM database. Reproducible: Always -- Configure bugmail: http://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 1018736] New: random freezes and filesystem errors
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1018736 Bug ID: 1018736 Summary: random freezes and filesystem errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: diamantis.karagkiaouris.dev(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 709003 --> http://bugzilla.suse.com/attachment.cgi?id=709003&action=edit Journalctl log I face some random freezes which i could not understand the cause of them. Sometimes it happens when i zypper dup, i searching in google or watching videos. I could not investigate the issue. My thought from the attached log of journalclt is that somehow my partitions become non writable. I am on a ssd with ext4 partitions (home/ root). Did anyone encounter something like this? -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 546594] New: zypper ignores lock while update
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=546594 Summary: zypper ignores lock while update Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 8 Platform: All OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: lmuelle(a)novell.com QAContact: qa(a)suse.de Found By: --- zypper ignores existing locks while perfoming an upgrade. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5