Mailinglist Archive: opensuse (4570 mails)

[Erik Jakobsen <eja@xxxxxxxxxxx>]

Ken Schneider wrote:
> On Mon, 2005-11-07 at 12:58 +0100, Erik Jakobsen wrote:
>   
>> Hi.
>>
>> On my SuSE 10.0, I have just tested with the Smart Package Mange.
>>
>> At finish, I could see this problems ?.
>> How is that tackled ?
>>
>> Output from amarok-1.3.5-2.guru.suse100.kde34@i686:
>> rpmdb: PANIC: Ugyldigt argument
>> rpmdb: PANIC: fatal region error detected; run recovery
>> error: db4 error(-30978) from dbcursor->c_put: DB_RUNRECOVERY: Fatal
>> error, run database recovery
>>     
> <snip>
>
> Are you using the cli or the menu version and are you running this as
> root?
>
>   
I use the menu version, and yes as root:

smart --gui

What is the cli ?.

Here I show what is been shown in the terminal after a try with smar
--gui, and after it has shown all the errors:

smart --gui
/usr/lib/python2.4/site-packages/smart/interfaces/gtk/packageview.py:93:
DeprecationWarning: Class PixbufCellRenderer is already
GObject-registered; Please note that classes containing any of the
attributes __gtype_name__, __gproperties__, or __gsignals__ are now
automatically registered.
  gobject.type_register(PixbufCellRenderer)
/usr/lib/python2.4/site-packages/smart/interfaces/gtk/packageview.py:413:
DeprecationWarning: Class GtkPackageView is already GObject-registered;
Please note that classes containing any of the attributes
__gtype_name__, __gproperties__, or __gsignals__ are now automatically
registered.
  gobject.type_register(GtkPackageView)
/usr/lib/python2.4/site-packages/smart/interfaces/gtk/progress.py:281:
DeprecationWarning: Class ProgressCellRenderer is already
GObject-registered; Please note that classes containing any of the
attributes __gtype_name__, __gproperties__, or __gsignals__ are now
automatically registered.
  gobject.type_register(ProgressCellRenderer)

lajka3:~ # smart --gui
/usr/lib/python2.4/site-packages/smart/interfaces/gtk/packageview.py:93:
DeprecationWarning: Class PixbufCellRenderer is already
GObject-registered; Please note that classes containing any of the
attributes __gtype_name__, __gproperties__, or __gsignals__ are now
automatically registered.
  gobject.type_register(PixbufCellRenderer)
/usr/lib/python2.4/site-packages/smart/interfaces/gtk/packageview.py:413:
DeprecationWarning: Class GtkPackageView is already GObject-registered;
Please note that classes containing any of the attributes
__gtype_name__, __gproperties__, or __gsignals__ are now automatically
registered.
  gobject.type_register(GtkPackageView)
/usr/lib/python2.4/site-packages/smart/interfaces/gtk/progress.py:281:
DeprecationWarning: Class ProgressCellRenderer is already
GObject-registered; Please note that classes containing any of the
attributes __gtype_name__, __gproperties__, or __gsignals__ are now
automatically registered.
  gobject.type_register(ProgressCellRenderer)
/usr/lib/python2.4/site-packages/smart/interfaces/gtk/log.py:90:
GtkWarning: gtk_text_buffer_emit_insert: assertion `g_utf8_validate
(text, len, NULL)' failed
  buffer.insert(iter, msg)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from dbenv->close: DB_RUNRECOVERY: Fatal error,
run database recovery