ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: "Vinogradov Anton" <arc13@rambler.ru>
To: community@altlinux.ru
Subject: Re: [Comm] Rambler Аудио & ALJ 2.3
Date: Wed, 13 Apr 2005 15:31:26 +0400
Message-ID: <opso54yobq0ww4iy@localhost.localdomain> (raw)
In-Reply-To: <e12fd2db05041222232a4e12bd@mail.gmail.com>

13.04.05 в 09:23 Eugene Ostapets в своём письме писал(а):

> On 4/13/05, Vinogradov Anton <arc13@rambler.ru> wrote:
>> >> более акуратному (чтоб вел себя как WMP)?
>> > mplayer очень хорошо встраиваеться... у него вообще нет интерфейса...
>> Здорово! А plug-in есть?
> Он подключался через mozplug во времена ALC 2.3
>> > :) Ну или gmplayer - он умеет прятаться...
>> Его нет для ALJ 2.3 :(
> Это символическая ссылка с mplayer, при таком имени он умеет
> подргружать графический интерфейс:)))
>
mozplug дергает MPlayer ... и тишина

MPlayer работает (через  gmplayer и так)

Однако при установке пакета синаптик ругается и ни чего не устанавливает

MPlayer-1.0-alt3.pre2:

warning: /etc/MPlayer/codecs.conf saved as /etc/MPlayer/codecs.conf.rpmorig
warning: /etc/MPlayer/dvb-menu.conf saved as  
/etc/MPlayer/dvb-menu.conf.rpmorig
warning: /etc/MPlayer/example.conf saved as  
/etc/MPlayer/example.conf.rpmorig
warning: /etc/MPlayer/input.conf saved as /etc/MPlayer/input.conf.rpmorig
warning: /etc/MPlayer/menu.conf saved as /etc/MPlayer/menu.conf.rpmorig
rpmdb: PANIC: Invalid argument
error: db4 error(-30981) from dbcursor->c_put: DB_RUNRECOVERY: Fatal  
error, run database recovery
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: db4 error(-30981) from dbcursor->c_close: DB_RUNRECOVERY: Fatal  
error, run database recovery
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: error(-30981) storing record MPlayer into Name
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: error(-30981) storing record MPlayer into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run  
database recover
..........................................................................................
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: error(-30981) storing record mencoder into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: error(-30981) storing record mplayer into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run  
database recovery
error: error(-30981) storing record libdha.so.0 into Basenames
error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run  
datab


-- 
Anton (ALJ 2.3, i686)


      reply	other threads:[~2005-04-13 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 15:58 Vinogradov Anton
2005-02-26 18:41 ` Vitaly Lipatov
2005-02-27  6:37   ` Vinogradov Anton
2005-04-12 13:46     ` Vinogradov Anton
2005-04-13  4:40       ` Eugene Ostapets
2005-04-13  5:18         ` Vinogradov Anton
2005-04-13  5:23           ` Eugene Ostapets
2005-04-13 11:31             ` Vinogradov Anton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=opso54yobq0ww4iy@localhost.localdomain \
    --to=arc13@rambler.ru \
    --cc=community@altlinux.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Community general discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
		mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
	public-inbox-index community

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git