Re: [Slackbuilds-users] libev source downloaded by web browser cannot be extracted by tar

2016-02-29 Thread Andrzej Telszewski
On 29/02/16 21:11, Didier Spaier wrote: On 29/02/2016 20:57, Andrzej Telszewski wrote: $ md5sum libev-4.15.tar.gz_seamonkey bd3fe50a18a86f977f91cfc46783f52d libev-4.15.tar.gz_seamonkey $ md5sum libev-4.15.tar.gz_wget 3a73f247e790e2590c01f3492136ed31 libev-4.15.tar.gz_wget $ tar -xf

Re: [Slackbuilds-users] libev source downloaded by web browser cannot be extracted by tar

2016-02-29 Thread Didier Spaier
On 29/02/2016 20:57, Andrzej Telszewski wrote: > $ md5sum libev-4.15.tar.gz_seamonkey > bd3fe50a18a86f977f91cfc46783f52d libev-4.15.tar.gz_seamonkey > > $ md5sum libev-4.15.tar.gz_wget > 3a73f247e790e2590c01f3492136ed31 libev-4.15.tar.gz_wget > > $ tar -xf libev-4.15.tar.gz_seamonkey > tar:

[Slackbuilds-users] libev source downloaded by web browser cannot be extracted by tar

2016-02-29 Thread Andrzej Telszewski
Hi, Just for your information: $ md5sum libev-4.15.tar.gz_seamonkey bd3fe50a18a86f977f91cfc46783f52d libev-4.15.tar.gz_seamonkey $ md5sum libev-4.15.tar.gz_wget 3a73f247e790e2590c01f3492136ed31 libev-4.15.tar.gz_wget $ tar -xf libev-4.15.tar.gz_seamonkey tar: This does not look like a tar

Re: [Slackbuilds-users] Possible issue with "nvidia-kernel"

2016-02-29 Thread King Beowulf
On 02/28/2016 12:24 PM, Chip Widmer wrote: > It appears I forgot the attachment. > > On Sun, Feb 28, 2016 at 3:20 PM, Chip Widmer wrote: >> Hello, >> >> My apologies if I'm just overlooking something, but there seems to be an >> issue with the "nvidia-kernel" Slackbuild,

Re: [Slackbuilds-users] adobe-reader error

2016-02-29 Thread Didier Spaier
On 29/02/2016 18:08, Didier Spaier wrote: > Blind guess: you installed it on x86_64 aka 65-bit Slackwaren but Sorry for the typos. 65-bit architecture is yet to be invented... Dider ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] adobe-reader error

2016-02-29 Thread Luís Fernando Carvalho Cavalheiro
What can you find in /opt/Adobe in your machine? Em 29 de 02 de 2016 às 18:04:29T+0100, Jostein Berntsen escreveu: > Running acroread after installing adobe-reader gives this error: > > /usr/bin/acroread: line 22: > /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: No

Re: [Slackbuilds-users] adobe-reader error

2016-02-29 Thread Didier Spaier
On 29/02/2016 18:04, Jostein Berntsen wrote: > Running acroread after installing adobe-reader gives this error: > > /usr/bin/acroread: line 22: > /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: No such file or > directory > > Looking in the referenced directory a binary acroread file exists

[Slackbuilds-users] adobe-reader error

2016-02-29 Thread Jostein Berntsen
Running acroread after installing adobe-reader gives this error: /usr/bin/acroread: line 22: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: No such file or directory Looking in the referenced directory a binary acroread file exists there. Anything to check here? Jostein