April 2013 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 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 663358] New: [zypper] can not install src rpm available on the local disk
by bugzilla_noreply＠novell.com 29 Jan '19

29 Jan '19

https://bugzilla.novell.com/show_bug.cgi?id=663358 https://bugzilla.novell.com/show_bug.cgi?id=663358#c0 Summary: [zypper] can not install src rpm available on the local disk Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal 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: --- Blocker: --- While zypper in /tmp/my.rpm works by creating a temp. repo containing my.rpm, zypper si /tmp/my.src.rpm does not work. Probably possible to use the same trick here as for ordinary rpms. -- 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

[Bug 804607] New: wrong plymouth on multimonitor (and not visible cryptohome passphrase)
by bugzilla_noreply＠novell.com 17 Jan '19

17 Jan '19

https://bugzilla.novell.com/show_bug.cgi?id=804607 https://bugzilla.novell.com/show_bug.cgi?id=804607#c0 Summary: wrong plymouth on multimonitor (and not visible cryptohome passphrase) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: noga.dany(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 When booting on two monitors, plymouth animation on second monitor is displaced. And therefore is not visible request for passphrase for accessing encrypted disk. On openSUSE 12.2 is ok. Primary monitor 1600 x 900, secondary monitor 1920 x 1080 (bug found in update in RC1, but I can't set it here in bug report options) Reproducible: Always Steps to Reproduce: 1. Start boot with connected second monitor Actual Results: Wrong plymouth animation on second monitor. Is displaced cca about 10% more left and more down. Expected Results: Good position like in openSUSE 12.2 -- 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 5

[Bug 805767] New: huge plymouth theme in initrd
by bugzilla_noreply＠novell.com 25 Nov '18

25 Nov '18

https://bugzilla.novell.com/show_bug.cgi?id=805767 https://bugzilla.novell.com/show_bug.cgi?id=805767#c0 Summary: huge plymouth theme in initrd Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: tittiatcoke(a)gmail.com ReportedBy: lnussel(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are 23MB of pylmouth theme files in the initrd. Maybe there is a way to omit some files to shrink the total size of initrd making boot even faster. -- 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 5

[Bug 629374] New: desktop-data-openSUSE contains some KDE-specific bits
by bugzilla_noreply＠novell.com 25 Nov '18

25 Nov '18

http://bugzilla.novell.com/show_bug.cgi?id=629374 http://bugzilla.novell.com/show_bug.cgi?id=629374#c0 Summary: desktop-data-openSUSE contains some KDE-specific bits Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Here are some bits in desktop-data-openSUSE that should probably live in some of the kde branding packages (or in qt): + etc/kde4/: contains kdm/backgroundrc (should live in kdm-branding-openSUSE) + etc/profile.d/desktop-data.* and usr/share/desktop-data: the scripts have a line to set QT_SYSTEM_DIR to /usr/share/desktop-data. This should really live in a qt package. I'm also wondering about everything in etc/xdg/menus/, usr/share/desktop-directories/ and usr/share/icons/: this contains the XDG menu structure, except that GNOME now uses something else since we were not happy with this structure and were unable to make any real progress on changing it. LXDE also doesn't use it. So it's now more or less KDE-specific... Finally, etc/skel/ contains public_html. Is this something you want to keep? I know it annoys me to have this directory created. -- 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 803057] New: PostgreSQL 9.2.3, 9.1.8, 9.0.12, 8.4.16 and 8.3.23 released
by bugzilla_noreply＠novell.com 23 Oct '18

23 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=803057 https://bugzilla.novell.com/show_bug.cgi?id=803057#c0 Summary: PostgreSQL 9.2.3, 9.1.8, 9.0.12, 8.4.16 and 8.3.23 released Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: lijewski.stefan(a)zabka.pl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 >From postgresql.org: The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. 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 6

[Bug 800701] New: X windows is corrupt after logging in on an AMD A10-5800K APU
by bugzilla_noreply＠novell.com 31 Jul '18

31 Jul '18

https://bugzilla.novell.com/show_bug.cgi?id=800701 https://bugzilla.novell.com/show_bug.cgi?id=800701#c0 Summary: X windows is corrupt after logging in on an AMD A10-5800K APU Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)suse.com ReportedBy: ajbiii(a)comcast.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Installed 12.3. The regular kernel and X windows works fine. Reboot to the xen kernel. The login screen is displayed correctly. After logging in, the display is corrupt. The mouse pointer is ok and I can see that the menu is active by putting the cursor in the lower left corner and clicking but the display is unusable. Just an aside: The xen kernel wouldn't even boot on the APU with 12.1 or 12.2. Reproducible: Always Steps to Reproduce: 1. Install 12.3 on an AMD Trinity APU. 2. Boot regular kernel, log in and verify X is working. 3. Reboot with the xen kernel. 4. Log in and observe the corruption Actual Results: Screen is corrupt Expected Results: Normal X windows operation -- 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 23