September 2007 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Grub Problem
by Sid Boyce 06 Sep '07

06 Sep '07

I had a failing IDE HD as /dev/sda, so I installed 10.3 on a new SATA drive /dev/sdb and was booting from it until I removed /dev/sda. The SATA drive is now /dev/sda, but it won't boot, just the cursor on the top of the screen. Booted from DVD to rescue, altered fstab and menu.lst was changed from (hd1,0) to (hd0,0), still won't boot and grub commands give unrecognised device string errors. menu.lst now says gfxmenu (hd0,0)/boot/message No luck. Thnks and Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 8

[opensuse-factory] bugzilla
by Peter Czanik 06 Sep '07

06 Sep '07

Hello, Is bugzilla down? Or just I can't reach it? Wanted to report an ugly installation bug for beta3... Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] Frequent rpmdb crashes in opensuse 10.3 beta 2
by Juan Erbes 06 Sep '07

06 Sep '07

The last days I got more than 5 crashes with the rpmdb, and must rebuild it with "rpm --rebuilddb", and in one case, after rebuilding, in the first case I woluld to install a rpm package. The last case was installing a package compiled in the system and created by checkinstall: rpmdb: PANIC: Argumento inválido rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) storing record libc.so.6 into Requirename rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.1)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.1.3)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.2)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libdl.so.2" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libdl.so.2(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libdl.so.2(GLIBC_2.1)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgcc_s.so.1" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgcc_s.so.1(GCC_3.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgcc_s.so.1(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libm.so.6" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libm.so.6(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libpthread.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libpthread.so.0(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libpthread.so.0(GLIBC_2.2)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6(CXXABI_1.3)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6(CXXABI_1.3.1)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6(GLIBCXX_3.4)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6(GLIBCXX_3.4.9)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_baseu-2.8.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_baseu-2.8.so.0(WXU_2.8)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_baseu_net-2.8.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_baseu_net-2.8.so.0(WXU_2.8)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_gtk2u_adv-2.8.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_gtk2u_adv-2.8.so.0(WXU_2.8)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_gtk2u_core-2.8.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_gtk2u_core-2.8.so.0(WXU_2.8)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libz.so.1" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Providename index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Dirnames index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Requireversion index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Provideversion index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Installtid index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Sigmd5 index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Sha1header index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Filemd5s index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery With package from the opensuse I got: error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 7

[opensuse-factory] BulletProofX - a critical feature request for openSUSE
by Alexey Eremenko 05 Sep '07

05 Sep '07

Hi Susers ! Ubuntu team have just developed an excellent technology, that existed in Windows for many years before. More specifically, the ability to recover from Graphics Adapter misconfigurations. It is called: BulletProofX ! I would like to see this included into openSUSE (11.0 ?), and available as an addon for openSUSE 10.3. Home Page: https://wiki.ubuntu.com/BulletProofX -- -Alexey Eremenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

15 29

[opensuse-factory] Bug 305195
by Frank-Michael Fischer 05 Sep '07

05 Sep '07

Is there someone who does not experience this bug with Beta2? If not, I should raise it to "Blocker". FMF --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 6

[opensuse-factory] High number of serious bugs in GNOME
by Alberto Passalacqua 05 Sep '07

05 Sep '07

Hello everyone, during a discussion on IRC it emerged that GNOME still has a very high number of blockers and critical bugs. As it can be seen here: https://bugzilla.novell.com/report.cgi?x_axis_field=&y_axis_field=component… GNOME + Evolution has 26 of them. Plus, from bugzilla it appears that GNOME + GNOME Admin/Platform + Evolution have 201 bugs: https://bugzilla.novell.com/report.cgi?x_axis_field=&y_axis_field=component… Considering the short time before the final release (~1 month), I think it would be helpful to know the actual situation of the fixes, and if there's enough time to solve all these issues before the release date. With kind regards, Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

14 25

[opensuse-factory] [status report] openSUSE distribution, week 36
by Christoph Thiel 05 Sep '07

05 Sep '07

Preface: ... a bit late and short due to Beta3 preparations, but still on time (it's still Tuesday ;)) status report: openSUSE distribution, week 36 --------------------------------------------------------------------------- - 10.3 Beta3: first internal test build from today looks promising. Will hopefully only need minor tweaks tomorrow. Public release is scheduled for Thursday (2007-09-06). - autobuild status: 8 failing packages on i386, 7 on x86_64, 25 on ppc. - bug count down from last week: 14 blockers, 90 critical. * bug review pending after Beta3 is out * if there is anything <critical that needs attention, make sure to set NEEDINFO to cthiel or coolo, to get it onto our radar. - the team made very good progress on libzypp / package management last week! - bundle-lang situation improved -- not completly solved for Beta3 (check out #302270 for details) - current focus for Beta3: * bundle-lang and friends * patterns / media layout * LiveCD * libzypp Is there anything missing? Please let us know, if we are ignoring any hot spots? Best, Christoph -- Christoph Thiel, Tech. Project Management, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 5

[opensuse-factory] Default package request
by Alex Lau 04 Sep '07

04 Sep '07

Dear all Is that possible to install pin by default? So we can create the next great thing call pin-install ... meaning base on the pin info after locating the package which is missing and trigger the install ? Thanks Alex ----------------------------------- 刘俊贤 Alex Lau PRC Beijing Linux R&D Engineer Mainland-Mobile (8610) 13910181404 HongKong-Mobile (852) 91621631 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 4

[opensuse-factory] GNOME: Pidgin, sane defaults
by Magnus Boman 04 Sep '07

04 Sep '07

Hello all, I've been talking to some people about the Pidgin defaults and we agreed that the upstream defaults are not really sane. We have an opportunity to get this patched with sane settings. Apart from https://bugzilla.novell.com/show_bug.cgi?id=304635, does anyone have any other suggestions on what defaults we should have? Thanks, Magnus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] Can't add Full-Qualified-Hostname to hosts file using yast2
by James PEARSON 04 Sep '07

04 Sep '07

Hello In the "/etc/hosts" file on opensuse 10.2, I have the "Full-Qualified-Hostname" on my machine in like this: # IP-Address Full-Qualified-Hostname Short-Hostname 127.0.0.2 my_hostname.my_dns my_hostname This was not the case with 10.3 after I installed it - so I tried to add it (for reasons I won't go into here). I can add a Full-Qualified-Hostname (in the form of the line above) manually via the command line but I can't using yast2 by running "DNS and Hostname" with the "Change Hostname via DHCP" and "Write to Hostname to /etc/hosts" options selected. This procedure works on 10.2 Is this a bug or am I doing something wrong here? TIA Regards James --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2