February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 916587] New: zypper does not update package when used with -C
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=916587 Bug ID: 916587 Summary: zypper does not update package when used with -C Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: tchatzimichos(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I try to `zypper in -C pkg`, zypper only checks if the package is installed. I would expect it to update it as well, like when specifying the original name of it. zypper outputs below, let me know if you need further info from me please. # zypper lu ... v | home:tampakrap | dummy | 0.0.1-2.1 | 0.0.1-3.1 | noarch # zypper -v in -C dummy Verbosity: 1 Non-option program arguments: 'dummy' Initializing Target ... Loading repository data... Reading installed packages... Force resolution: No 'dummy' is already installed. Resolving package dependencies... Force resolution: No Nothing to do. # zypper -v in dummy Verbosity: 1 Non-option program arguments: 'dummy' Initializing Target ... Loading repository data... Reading installed packages... Force resolution: No Selecting 'dummy-0.0.1-3.1.noarch' from repository 'home:tampakrap' for installation. Resolving package dependencies... Force resolution: No The following package is going to be upgraded: dummy 0.0.1-2.1 -> 0.0.1-3.1 1 package to upgrade. Overall download size: 5.7 KiB. Already cached: 0 B No additional space will be used or freed after the operation. Continue? [y/n/? shows all options] (y): -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 987900] New: selecting Wayland with Plasma 5 (plasma5-session-wayland) from sddm produces black screen and then returns to login screen
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=987900 Bug ID: 987900 Summary: selecting Wayland with Plasma 5 (plasma5-session-wayland) from sddm produces black screen and then returns to login screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: rainer.klier(a)gmx.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 683225 --> http://bugzilla.opensuse.org/attachment.cgi?id=683225&action=edit journald log with unsuccessfull wayland session i am using openSUSE x86_64 Tumbleweed on a notebook with a geforce gtx 765m with the latest proprietary nvidia driver 367.27. Xorg is working fine without problems. today i updated to latest kde framework 5.7.0, and had the idea of trying out wayland, as i read that kde framework 5.7.0 should at least support wayland in some way. but it does not work at all. if i select the Wayland plasma session from the wayland sessions from sddm (the one which comes from the config file /usr/share/wayland-sessions/plasmawayland.desktop which comes from the package plasma5-session-wayland) and trying to login, i only see a black screen for some seconds, and then i am back at the sddm greetings screen. i have attached the part of journald logs where the unsuccessfull login happens: at 17:18:04 you can see the attempt to start new session using /usr/share/wayland-sessions/plasmawayland.desktop. at about 17:18:11 you can see that it was not successfull and then i selected the normal Xorg based session /usr/share/xsessions/kde-plasma.desktop and loged in successfully. what did i wrong? why does it not even start the session? -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 738050] New: server:database/mongodb: Failure on db.dropDatabase() using the RPM version
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

https://bugzilla.novell.com/show_bug.cgi?id=738050 https://bugzilla.novell.com/show_bug.cgi?id=738050#c0 Summary: server:database/mongodb: Failure on db.dropDatabase() using the RPM version Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: asn(a)cryptomilk.org ReportedBy: patrick.meinusch(a)seitenbau.net QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- to reproduce: 1. install mongodb-2.0.1-5.2.x86_64.rpm from http://download.opensuse.org/repositories/server:/database/SLE_11_SP1/x86_6… 2. start mongod: /etc/init.d/mongodb start 3. open a mongo shell to localhost:27017 4. use new database: use testdb (optional) 5. insert document to a collection: db.coll.insert( { "key":"value" } ) 6. try to drop database: db.dropDatabase() expected: database is dropped without any error got: database is dropped but getting this error: in shell: { "errmsg" : "exception: assertion db/pdfile.cpp:2158", "code" : 0, "ok" : 0 } in log: Wed Dec 21 13:31:23 [conn1] dropDatabase newdb Wed Dec 21 13:31:23 [conn1] removeJournalFiles Wed Dec 21 13:31:23 [conn1] Assertion failure i <= DiskLoc::MaxFiles db/pdfile.cpp 2158 0x56ec5e 0x577d4f 0x811b9a 0x8121d8 0x8a0fdc 0x89d661 0x89df85 0x88df2a 0x89071b 0x7f54fa 0x973c3c 0x60c06a 0x7f1841eb45f0 0x7f184065684d /usr/sbin/mongod(_ZN5mongo12sayDbContextEPKc+0x9e) [0x56ec5e] /usr/sbin/mongod(_ZN5mongo8assertedEPKcS1_j+0xbf) [0x577d4f] /usr/sbin/mongod(_ZN5mongo19_applyOpToDataFilesEPKcRNS_6FileOpEbRKSs+0x45a) [0x811b9a] /usr/sbin/mongod(_ZN5mongo16_deleteDataFilesEPKc+0xc8) [0x8121d8] /usr/sbin/mongod(_ZN5mongo15CmdDropDatabase3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0xec) [0x8a0fdc] /usr/sbin/mongod(_ZN5mongo11execCommandEPNS_7CommandERNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb+0x871) [0x89d661] /usr/sbin/mongod(_ZN5mongo12_runCommandsEPKcRNS_7BSONObjERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi+0x565) [0x89df85] /usr/sbin/mongod(_ZN5mongo11runCommandsEPKcRNS_7BSONObjERNS_5CurOpERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi+0x3a) [0x88df2a] /usr/sbin/mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_+0x12eb) [0x89071b] /usr/sbin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x6fa) [0x7f54fa] /usr/sbin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0xdc) [0x973c3c] /usr/sbin/mongod(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x29a) [0x60c06a] /lib64/libpthread.so.0(+0x75f0) [0x7f1841eb45f0] /lib64/libc.so.6(clone+0x6d) [0x7f184065684d] Wed Dec 21 13:31:23 [conn1] command newdb.$cmd command: { dropDatabase: 1.0 } ntoreturn:1 reslen:99 113ms When using the binary package from mongodb.org this bug is not reproducible -- 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 731320] New: server:database/mongodb: mongod does not respect --noprealloc
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

https://bugzilla.novell.com/show_bug.cgi?id=731320 https://bugzilla.novell.com/show_bug.cgi?id=731320#c0 Summary: server:database/mongodb: mongod does not respect --noprealloc Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: asn(a)cryptomilk.org ReportedBy: jmatejek(a)suse.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- to reproduce: 1. install mongodb 2. edit /etc/mongodb.conf to say "noprealloc = true" 3. optionally, run mongod manually with --noprealloc option expected result: mongo starts without preallocating journals actual result: mongo does not care. from mongodb.log: note: noprealloc may hurt performance in many applications Fri Nov 18 12:24:02 [initandlisten] MongoDB starting : pid=4902 port=27017 dbpath=/var/lib/mongodb 64-bit host=limetka.suse.cz Fri Nov 18 12:24:02 [initandlisten] db version v2.0.1, pdfile version 4.5 Fri Nov 18 12:24:02 [initandlisten] git version: nogitversion Fri Nov 18 12:24:02 [initandlisten] build info: Linux build05 2.6.37.6-0.7-xen #1 SMP 2011-07-21 02:17:24 +0200 x86_64 BOOST_LIB_VERSION=1_44 Fri Nov 18 12:24:02 [initandlisten] options: { auth: "true", bind_ip: "127.0.0.1", config: "/etc/mongodb.conf", dbpath: "/var/lib/mongodb", fork: "true", logappend: "true", logpath: "/var/log/mongodb/mongodb.log", nohttpinterface: "true", noprealloc: true, quiet: true } Fri Nov 18 12:24:02 [initandlisten] journal dir=/var/lib/mongodb/journal Fri Nov 18 12:24:02 [initandlisten] recover : no journal files present, no recovery needed Fri Nov 18 12:24:05 [initandlisten] preallocateIsFaster=true 25.86 Fri Nov 18 12:24:07 [initandlisten] preallocateIsFaster=true 25.88 Fri Nov 18 12:24:10 [initandlisten] preallocateIsFaster=true 24.26 Fri Nov 18 12:24:10 [initandlisten] preallocateIsFaster check took 8.42 secs Fri Nov 18 12:24:10 [initandlisten] preallocating a journal file /var/lib/mongodb/journal/prealloc.0 well yes, preallocate might as well be "IsFaster=true", but that still doesn't justify spending extra three minutes at startup and eating 3GB for no good reason whatsoever in a friggin development environment where performance does not matter but 3GB of storage do </frustratedRant> -- 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 928328] New: VUL-1: libnettle: off-by-one in the test suite
by bugzilla_noreply＠novell.com 03 Feb '19

03 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=928328 Bug ID: 928328 Summary: VUL-1: libnettle: off-by-one in the test suite Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: vpereira(a)novell.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Address Sanitizer found a problem in the des-compat-test.c the line: for (i=0; i<(NUM_TESTS-1); i++) should be: for (i=0; i<(NUM_TESTS-2); i++) we found a simila problem, in the 13.2, however in Factory it was already fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1015478] New: printing an a4 pdf from okular comes out scaled down to apprx a5
by bugzilla_noreply＠novell.com 30 Jan '19

30 Jan '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1015478 Bug ID: 1015478 Summary: printing an a4 pdf from okular comes out scaled down to apprx a5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: per(a)computer.org QA Contact: jsmeix(a)suse.com Found By: --- Blocker: --- Printing an A4 size PDF from okular comes out scaled down to what looks like A5, but with about 2cm truncated on the right. Printing to this printer via our local printserver works fine from other systems - Windows, openSUSE 10/12/13 and Leap421. The Leap422 installation is vanilla, not much changed. Printer is a Kyocera C5015N. -- You are receiving this mail because: You are on the CC list for the bug.

1 24