On Sat, Jun 06, 2009 at 07:09:56PM +0400, Andrew Gaydenko wrote
On Saturday 06 June 2009 18:07:53 Alex Schuster wrote:
Alt-SysRq-R will allow you to switch to a text console with Ctrl-Alt-Fn.
Wonko
Unfortunately didn't help - still black screen during switching attempts.
It may be
Hi,
After upgrading avidemux the resulting executable fails to start with:
avidemux2: error while loading shared libraries: libfaad.so.1: cannot open
shared object file: No such file or directory
qsearch only knows libffad2...
Am I lost ?
Kind regards,
Meino Cramer
--
Please don't send
-video:kaffeine-0.8.6:20090607-120807.log'. * The
ebuild environment file is located at
'/home/mccramer/data/portagetmp/portage/media-video/kaffeine-0.8.6/temp/env
ironment'. *
* QA Notice: Unrecognized configure options:
*
* configure: WARNING: unrecognized options: --with-x,
--enable
, and the call stack if
relevant. * A complete build log is located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-120807.log'. * The
ebuild environment file is located at
'/home/mccramer/data/portagetmp/portage/media-video/kaffeine-0.8.6/temp/env
ironment'. *
* QA Notice: Unrecognized
failed
*
* If you need support, post the topmost build error, and the call
stack if relevant. * A complete build log is located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-120807.log'. *
The ebuild environment file is located at
'/home/mccramer/data/portagetmp/portage
} || die fixing
mo files failed; * The die message:
* fixing mo files failed
*
* If you need support, post the topmost build error, and the call
stack if relevant. * A complete build log is located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-120807.log
is located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-120807.log'.
* The ebuild environment file is located at
'/home/mccramer/data/portagetmp/portage/media-video/kaffeine-0.8.6/
temp /env ironment'. *
* QA Notice: Unrecognized configure options
the topmost build error, and the call
stack if relevant. * A complete build log is located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-120807.log'.
* The ebuild environment file is located at
'/home/mccramer/data/portagetmp/portage/media-video/kaffeine-0.8.6
:
* fixing mo files failed
*
* If you need support, post the topmost build error, and the
call stack if relevant. * A complete build log is located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-120807.lo
g'. * The ebuild environment file is located
the topmost build error, and the
call stack if relevant. * A complete build log is located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-120807.log'
. * The ebuild environment file is located at
'/home/mccramer/data/portagetmp/portage/media-video/kaffeine-0.8.
6/ temp
On Sunday 07 June 2009 13:30:30 meino.cra...@gmx.de wrote:
Hi,
After upgrading avidemux the resulting executable fails to start with:
avidemux2: error while loading shared libraries: libfaad.so.1: cannot open
shared object file: No such file or directory
qsearch only knows libffad2...
Am
On Sunday 07 June 2009 03:28:21 William Kenworthy wrote:
As for the OP, I can only guess what might be causing this. Let's start
with obvious stuff:
1. Is portage the latest version for your arch?
2. What does revdep-rebuild return?
3. What is your arch, and is it a mixture of stable
:
* fixing mo files failed
*
* If you need support, post the topmost build error, and the
call stack if relevant. * A complete build log is located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-120807.lo
g' . * The ebuild environment file is located
-video:kaffeine-0.8.6:20090607-120807.
lo g' . * The ebuild environment file is located at
'/home/mccramer/data/portagetmp/portage/media-video/kaffeine-
0. 8. 6/ temp /env ironment'. *
* QA Notice: Unrecognized configure options:
*
* configure
Alan McKinnon wrote:
...
I'm also not sure anymore about which portage version was first to support
sets. What I did was blow my top at the forced downgrade of portage at Zac's
whim, and unmasked portage. Lots of troubles immediately and at once went away
when I did this...
Maybe that's why I
On Sunday 07 June 2009 17:21:20 walt wrote:
Alan McKinnon wrote:
...
I'm also not sure anymore about which portage version was first to
support sets. What I did was blow my top at the forced downgrade of
portage at Zac's whim, and unmasked portage. Lots of troubles immediately
and at
if relevant. * A complete build log is located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-120807.
lo g' . * The ebuild environment file is located at
'/home/mccramer/data/portagetmp/portage/media-video/kaffeine-
0. 8. 6/ temp /env ironment
On 6/7/09, meino.cra...@gmx.de meino.cra...@gmx.de wrote:
Meanwhile I compiled kaffeine ... but now it does not find
xine_part.desktop ... on the other hand:
ls /usr/share/services/xine_part.desktop
/usr/share/services/xine_part.desktop
Could you try copying it over to
On 6/7/09, Arttu V. arttu...@gmail.com wrote:
Could you try copying it over to /usr/kde/3.5/share/services/ and see
if the problem persists?
image # find . -iname 'xine*.desktop'
./usr/kde/3.5/share/services/xine_part.desktop
Naturally meant if it is *there* and you copy it to the other
On Sun, 07 Jun 2009 09:28:21 +0800, William Kenworthy wrote:
* sys-apps/portage
Latest version available: 2.1.6.13
Latest version installed: 2.2_rc15
If you're going to run release candidate versions, at least run the
latest release candidate. rc15 hasn't been in portage for a
Arttu V. arttu...@gmail.com [09-06-07 18:01]:
On 6/7/09, Arttu V. arttu...@gmail.com wrote:
Could you try copying it over to /usr/kde/3.5/share/services/ and see
if the problem persists?
image # find . -iname 'xine*.desktop'
./usr/kde/3.5/share/services/xine_part.desktop
Naturally
Alan McKinnon alan.mckin...@gmail.com writes:
The only reason it's masked is to force as many users as possible to use an
earlier version so that it can receive more testing and get better bug
reports, and that was done by Zac himself. There is not a single technical
or
code quality
if relevant. * A complete build log is
located at
'/var/log/portage/media-video:kaffeine-0.8.6:20090607-12080
7. lo g' . * The ebuild environment file is located at
'/home/mccramer/data/portagetmp/portage/media-video/kaffein
e- 0. 8. 6/ temp /env ironment
Good Day;
ati-drivers fails to emerge; foolowed the somewhat out of date doc's online.
emerge ati-drivers
Calculating dependencies... done!
Verifying ebuild manifests
Emerging (1 of 1) x11-drivers/ati-drivers-8.552-r2
* ati-driver-installer-8-11-x86.x86_64.run RMD160 SHA1 SHA256 size ;-)
On Sonntag 07 Juni 2009, Hazen Valliant-Saunders wrote:
Good Day;
ati-drivers fails to emerge; foolowed the somewhat out of date doc's
online.
emerge ati-drivers
Calculating dependencies... done!
Verifying ebuild manifests
Emerging (1 of 1) x11-drivers/ati-drivers-8.552-r2
*
Who is maintaining this?
On Sun, Jun 7, 2009 at 1:00 PM, Volker Armin Hemmann
volkerar...@googlemail.com wrote:
On Sonntag 07 Juni 2009, Hazen Valliant-Saunders wrote:
Good Day;
ati-drivers fails to emerge; foolowed the somewhat out of date doc's
online.
emerge ati-drivers
On Sonntag 07 Juni 2009, Hazen Valliant-Saunders wrote:
Good Day;
ati-drivers fails to emerge; foolowed the somewhat out of date doc's
online.
emerge ati-drivers
Calculating dependencies... done!
Verifying ebuild manifests
Emerging (1 of 1) x11-drivers/ati-drivers-8.552-r2
*
On Sonntag 07 Juni 2009, Hazen Valliant-Saunders wrote:
Who is maintaining this?
cat /var/portage/x11-drivers/ati-drivers/metadata.xml
?xml version=1.0 encoding=UTF-8?
!DOCTYPE pkgmetadata SYSTEM http://www.gentoo.org/dtd/metadata.dtd;
pkgmetadata
herdx11-drivers/herd
maintainer
1. This is a fresh install from 2008.0 with no previous drivers.
2. How can i get access to fix this in Portage? (Since that's the
underlying issue).
3. Do we know who maintains this (ATI has a member but are they on this
list?).
On Sun, Jun 7, 2009 at 1:20 PM, Volker Armin Hemmann
Abviously,
Since they are both busy then this needs attention.
On Sun, Jun 7, 2009 at 1:22 PM, Volker Armin Hemmann
volkerar...@googlemail.com wrote:
On Sonntag 07 Juni 2009, Hazen Valliant-Saunders wrote:
Who is maintaining this?
cat /var/portage/x11-drivers/ati-drivers/metadata.xml
Hazen Valliant-Saunders wrote:
Good Day;
ati-drivers fails to emerge; foolowed the somewhat out of date doc's
online.
There doesn't exist a Catalyst for Linux release yet that support kernel
2.6.29. Even if you install the latest version (9.5), it won't work.
On Sonntag 07 Juni 2009, Hazen Valliant-Saunders wrote:
1. This is a fresh install from 2008.0 with no previous drivers.
2. How can i get access to fix this in Portage? (Since that's the
underlying issue).
3. Do we know who maintains this (ATI has a member but are they on this
list?).
1.
On Sonntag 07 Juni 2009, Nikos Chantziaras wrote:
Hazen Valliant-Saunders wrote:
Good Day;
ati-drivers fails to emerge; foolowed the somewhat out of date doc's
online.
There doesn't exist a Catalyst for Linux release yet that support kernel
2.6.29. Even if you install the latest
Volker Armin Hemmann wrote:
On Sonntag 07 Juni 2009, Nikos Chantziaras wrote:
Hazen Valliant-Saunders wrote:
Good Day;
ati-drivers fails to emerge; foolowed the somewhat out of date doc's
online.
There doesn't exist a Catalyst for Linux release yet that support kernel
2.6.29. Even if you
On Sonntag 07 Juni 2009, Nikos Chantziaras wrote:
Volker Armin Hemmann wrote:
On Sonntag 07 Juni 2009, Nikos Chantziaras wrote:
Hazen Valliant-Saunders wrote:
Good Day;
ati-drivers fails to emerge; foolowed the somewhat out of date doc's
online.
There doesn't exist a Catalyst for
35 matches
Mail list logo
