F

[Venecia Peñaloza]

Enviado desde mi iPhone

texdoctk: how to set Button colours ?

[Jerome BENOIT]

Hello Forum,

whenever I launch texdoctk(1), I get the message:

NOTE: Button colours not set in /etc/texmf/texdoctk/texdocrc.defaults; 
using defaults.

Any hint on how to fix this ?

Thanks in advance,
Jerome

Re: Atualização para o Kernel 4.7.1

[Thiago Canuto]

Ok Daniel. Mais uma vez obrigado pela info.

Seria interessante atualizar o distro upgrade? Neste caso instalara a
versao estável Debian 8.6, por exemplo?

Thiago

Em 16h41 sex, 19/08/2016, Gustavo S. L.  escreveu:

> Em 19 de agosto de 2016 17:03, Thiago Canuto Ferreira
>  escreveu:
> > Olá Gustavo. Obrigado pela info.
> >
> > Aproveitando a oportunidade sobre a atualização do Kernel, como eu faço
> > para fazer atualizações de segurança?
>
> Se tiver "deb http://security.debian.org/ jessie/updates main":
> # apt-get upgrade
>
> > Estou usando o Debian com interface GNOME. Ele nos avisa de novas
> > atualizações de segurança como o Ubuntu faz?
> >
> > Instalei o Debian com interface gráfica LXDE no notebook de meu pai. O
> > LXDE nos avisa de novas atualizações?
>
> No diretório /var/log nos arquivos "aptitude" e "dpkg.log" há
> informações sobre os pacotes instalados.
>
> No mesmo diretório se quiser fazer uma busca por mensagens de erro e
> warning dada sua preocupação de segurança pode fazer:
>
> # cat /var/log/syslog | grep -iE '(errors?|warnings?)' --color
>
> > É possível fazer atualizações através do Synaptic?
>
> Sim, usando a seção "Origin" e selecionando o repositório relativo a
> segurança
>
> >
> > Thiago
> >
>
> --
> Gustavo Soares de Lima
> Logicus Tecnologia de Informação e Comunicação
>
>

Re: install debian depuis écran secondaire

[Marc]

Le 20/08/2016 à 16:26, alpha bravo a écrit :

Quelqu'un saurait-il comment procéder pour dire à l'installeur debian
d'utiliser l'écran secondaire et non pas l'écran principal ?

Existe-t-il d'autres manières de s'en sortir ?

Option 3 : faire une installation par ssh avec network-console
Faut automatiser le début de l'installation avec un fichier preseed.cfg 
contenant quelque chose comme


d-i debian-installer/locale string fr_FR
d-i debconf/priority select critical
d-i keyboard-configuration/xkb-keymap select fr
d-i auto-install/enabled boolean true
#  d-i iso-scan/ask_second_pass boolean true
#  d-i iso-scan/filename string ${Isofile}
d-i netcfg/choose_interface select eth0
d-i netcfg/disable_dhcpboolean true
d-i netcfg/get_nameservers string ${Nameserver}
d-i netcfg/get_ipaddress string ${Ip}
d-i netcfg/get_netmask string ${Subnet}
d-i netcfg/get_gateway string ${Gateway}
d-i netcfg/confirm_static boolean true
d-i netcfg/get_hostname string ${Hostname}
d-i netcfg/get_domain string ${Domain}
d-i anna/choose_modules string network-console
d-i network-console/password password ${Password}
d-i network-console/password-again password ${Password}

Bien entendu, faut remplacer les variables par les valeurs appropriées

Il faut ensuite ajouter ce fichier (et aussi les drivers spéciaux) là où 
ça va bien, faut prévoir un peu de mise au point... cf 
https://d-i.debian.org/manual/fr.amd64/apb.html


Quelqu'un a une solution plus complexe ?

Re: Can't install new driver

[Maureen L Thomas]

On 08/20/2016 05:12 PM, deloptes wrote:

Maureen L Thomas wrote:


[ 19.214674] r8169 :03:00.0: firmware: agent aborted loading
rtl_nic/rtl8168e-2.fw (not found?)

Which kernel is this, besides in your original post you were talking about
rtl8168g-2.fw not rtl8168e-2.fw.

To make it simple: The firmware version is used by specific kernel line.
Which kernel are you using? I asked but you did not answer.

rtl8168e-2.fw is part of the wheezy-backports. install as instructed before.

Perhaps the wheezy kernel version would work with it or may be there is also
some newer kernel in the backports. Use this if so. I also found this
thread http://forums.debian.net/viewtopic.php?f=17=72645

regards



My kernel is 3.2.81-1.  This was the last one I did with an update from 
debian.  When I installed the rtl-nic I installed the whole package that 
included the one 8168e-2.fw.


I am wondering if it would be ok to just upgrade to jessie.  I have the 
dvd's downloaded.

Maureen

Re: Can't install new driver

[deloptes]

Maureen L Thomas wrote:

> [ 19.214674] r8169 :03:00.0: firmware: agent aborted loading
> rtl_nic/rtl8168e-2.fw (not found?)

Which kernel is this, besides in your original post you were talking about
rtl8168g-2.fw not rtl8168e-2.fw.

To make it simple: The firmware version is used by specific kernel line.
Which kernel are you using? I asked but you did not answer.

rtl8168e-2.fw is part of the wheezy-backports. install as instructed before.

Perhaps the wheezy kernel version would work with it or may be there is also
some newer kernel in the backports. Use this if so. I also found this
thread http://forums.debian.net/viewtopic.php?f=17=72645

regards

Re: Can't install new driver

[Maureen L Thomas]

On 08/20/2016 02:52 AM, deloptes wrote:

Maureen L Thomas wrote:


It appeared to have been installed with the above information but I
still cannot connect to the net.  I have tried to send my log file and
dmseg file but apparently it will not go through.  Thank you Charlie
though that did appear to work with no error messages.
Maureen

Perhaps you need the kernel from the wheezy-backports as well.

Just paste here the lines from dmesg after modprobe



[ 19.214674] r8169 :03:00.0: firmware: agent aborted loading 
rtl_nic/rtl8168e-2.fw (not found?)


[ 19.214977] r8169 :03:00.0: eth1: unable to load firmware patch 
rtl_nic/rtl8168e-2.fw (-2)


[ 19.231534] r8169 :03:00.0: eth1: link down

[ 19.231900] ADDRCONF(NETDEV_UP): eth1: link is not ready

[ 19.591414] apm: BIOS not found.

I also found the following:

Aug 19 17:48:07 debian NetworkManager[2216]:  caught signal 15, 
shutting down normally.


Aug 19 17:48:07 debian NetworkManager[2216]:  quit request 
received, terminating...


Aug 19 17:48:07 debian NetworkManager[2216]:  (eth1): now unmanaged

Aug 19 17:48:07 debian NetworkManager[2216]:  (eth1): device state 
change: unavailable -> unmanaged (reason 'removed') [20 10 36]


Aug 19 17:48:07 debian NetworkManager[2216]:  (eth1): cleaning up...

Aug 19 17:48:07 debian NetworkManager[2216]:  (eth1): taking down 
device.


Aug 19 17:48:07 debian NetworkManager[2216]:  exiting (success)


And this:

Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: init!

Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: 
update_system_hostname


Aug 19 17:48:49 debian NetworkManager[2191]: SCPluginIfupdown: guessed 
connection type (eth0) = 802-3-ethernet


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: 
update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, 
id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: adding 
eth0 to iface_connections


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: adding 
iface eth0 to well_known_interfaces


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: autoconnect

Aug 19 17:48:49 debian NetworkManager[2191]: SCPluginIfupdown: 
management mode: unmanaged


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: devices 
added (path: /sys/devices/pci:00/:00:07.0/net/eth0, iface: eth0)


Aug 19 17:48:49 debian NetworkManager[2191]: SCPluginIfupdown: locking 
wired connection setting


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: devices 
added (path: /sys/devices/pci:00/:00:0b.0/:03:00.0/net/eth1, 
iface: eth1)


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: device 
added (path: /sys/devices/pci:00/:00:0b.0/:03:00.0/net/eth1, 
iface: eth1): no ifupdown configuration found.


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: devices 
added (path: /sys/devices/virtual/net/lo, iface: lo)


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: device 
added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown 
configuration found.


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: end _init.

Aug 19 17:48:49 debian NetworkManager[2191]:  Loaded plugin 
ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the 
NetworkManager mailing list.


Aug 19 17:48:49 debian NetworkManager[2191]:  Loaded plugin 
keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the 
NetworkManager mailing list.


Aug 19 17:48:49 debian NetworkManager[2191]: Ifupdown: get unmanaged 
devices count: 1


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: 
(168559344) ... get_connections.


Aug 19 17:48:49 debian NetworkManager[2191]: SCPlugin-Ifupdown: 
(168559344) ... get_connections (managed=false): return empty list.


Aug 19 17:48:49 debian NetworkManager[2191]: keyfile: parsing Wired 
connection 2 ...


Aug 19 17:48:49 debian NetworkManager[2191]: keyfile: read connection 
'Wired connection 2'


Aug 19 17:48:49 debian NetworkManager[2191]: keyfile: parsing DSL 
connection 1 ...


Aug 19 17:48:49 debian NetworkManager[2191]: keyfile: read connection 
'DSL connection 1'


Aug 19 17:48:49 debian NetworkManager[2191]: keyfile: parsing Wireless 
connection 1 ...


Aug 19 17:48:49 debian NetworkManager[2191]: keyfile: read connection 
'Wireless connection 1'


Aug 19 17:48:49 debian NetworkManager[2191]: Ifupdown: get unmanaged 
devices count: 1


Aug 19 17:48:49 debian NetworkManager[2191]:  trying to start the 
modem manager...


Aug 19 17:48:49 debian dbus[2141]: [system] Activating service 
name='org.freedesktop.ModemManager' (using servicehelper)


Aug 19 17:48:49 debian NetworkManager[2191]:  monitoring kernel 
firmware directory '/lib/firmware'.


Aug 19 17:48:49 debian NetworkManager[2191]:  monitoring ifupdown 
state file '/run/network/ifstate'.


Aug 19 17:48:49 debian 

Re: A minimalist network

[Andy Smith]

Hi Richard,

On Fri, Aug 19, 2016 at 07:41:56AM -0500, Richard Owlett wrote:
> As I had said in last paragraph of
> https://lists.debian.org/debian-user/2016/08/msg00609.html :
> "Why would I be interested in ssh as both machines are sitting on my
> desk and _neither_ will be connected to the internet when ethernet
> connection is live?"

If you ever have a need to administer the Linux machine while not being
in front of it then you will probably find this easiest over ssh.
Yes, you could argue that you do not need the encryption features of
ssh since the data only goes over this short cable inside your home,
but really, ssh is so ubiquitous that it's probably not worth using
any different solution.

If remote (and remote may include things like, over wifi from
another room in your house) administration is never going to be
something you do, as you'll be doing all work from the physical
keyboard of the machine, then maybe ssh is something you don't need
to run. Running ssh also allows file transfer with scp or sftp.

>From what I can tell you haven't actually got IP connectivity going
yet though, so perhaps talk of ssh is premature. Perhaps get
networking working before you consider which networking applications
you're going to install.

Cheers,
Andy

-- 
http://bitfolk.com/ -- No-nonsense VPS hosting

"The electric guitar - like making love - is much improved by a little
 feedback, completely ruined by too much." — The League Against Tedium

Re: OT - Software/servicio para video conferencias.

[Camaleón]

El Sat, 20 Aug 2016 13:18:21 -0300, divagante escribió:

> Hola gente!
> 
>   Deseaba consultarles por un software para realizar video conferencias.

Supongo que hablas de la parte servidora y no de clientes ¿no?

> El requisito es que sea software libre, ya que se esta usando un
> servicio de pago y que brinda software privativo -vamos! calcadito a
> skype digamos-.
>   Por el momento, se me ocurre a mi nomas, se podría usar localmente el
> ancho de banda para realizar la transmisión a no mas de 10 o 15
> personas, intentando así prescindir de contratar un servicio externo.

Más que la aplicación tendrás que tener en cuenta el hardware del que 
dispones y el servicio que quieres dar porque la transmisión de vídeo en 
tiempo real no sólo requiere buen ancho de banda y baja latencia sino 
mucho micro.

>   P.D.: he pensado en firefox 'hello', pero habiendolo utilizado entre
> tres personas me ha parecido lento y por demas pasado (supongo que es el
> codec utilizado). Quizas alguien tenga mas experiencia con esta
> utilizdad de mozilla.

Pero Hello es una aplicación cliente ¿buscas un cliente o un servidor 
para gestionar tus propias videoconferencias?

Como cliente probaría con Jitsi (java) y como servidor le daría un 
vistazo a la tabla de la wikipedia:

https://en.wikipedia.org/wiki/Comparison_of_web_conferencing_software

Saludos,

-- 
Camaleón

Re: OT - Software/servicio para video conferencias.

[Ricardo Adolfo Sánchez Arboleda]

http://openmeetings.apache.org/



*Saludes;*

rasa.

El 20 de agosto de 2016, 11:29, Walter Falla 
escribió:

> Utiliza Hangouts
>
> El sáb., 20 de ago. de 2016 11:19 AM, divagante 
> escribió:
>
>> Hola gente!
>>
>>   Deseaba consultarles por un software para realizar video conferencias.
>> El requisito es que sea software libre, ya que se esta usando un
>> servicio de pago y que brinda software privativo -vamos! calcadito a
>> skype digamos-.
>>   Por el momento, se me ocurre a mi nomas, se podría usar localmente el
>> ancho de banda para realizar la transmisión a no mas de 10 o 15
>> personas, intentando así prescindir de contratar un servicio externo.
>>
>>   P.D.: he pensado en firefox 'hello', pero habiendolo utilizado entre
>> tres personas me ha parecido lento y por demas pasado (supongo que es el
>> codec utilizado). Quizas alguien tenga mas experiencia con esta
>> utilizdad de mozilla.
>>
>>   Saludos y muchas gracias.
>>
> --
>
> [image: https://walterfalla.odoo.com/] 
> *Walter Falla Morales  **Gerencia de Proyectos ERP Odoo V9*
>
> Cel: *+584166022604 <%2B584166022604>  **Proyectos de Desarrollo
> de Software *
> Web:walterfalla.odoo.com *Proyectos de
> Domotica & Iluminación LED *
> Skype:walterfalla   *Community
> Manager*
>    
>
> 
>
>
>
>
>

Re: OT - Software/servicio para video conferencias.

[Walter Falla]

Utiliza Hangouts

El sáb., 20 de ago. de 2016 11:19 AM, divagante 
escribió:

> Hola gente!
>
>   Deseaba consultarles por un software para realizar video conferencias.
> El requisito es que sea software libre, ya que se esta usando un
> servicio de pago y que brinda software privativo -vamos! calcadito a
> skype digamos-.
>   Por el momento, se me ocurre a mi nomas, se podría usar localmente el
> ancho de banda para realizar la transmisión a no mas de 10 o 15
> personas, intentando así prescindir de contratar un servicio externo.
>
>   P.D.: he pensado en firefox 'hello', pero habiendolo utilizado entre
> tres personas me ha parecido lento y por demas pasado (supongo que es el
> codec utilizado). Quizas alguien tenga mas experiencia con esta
> utilizdad de mozilla.
>
>   Saludos y muchas gracias.
>
-- 

[image: https://walterfalla.odoo.com/] 
*Walter Falla Morales  **Gerencia de Proyectos ERP Odoo V9*
Cel: *+584166022604 <%2B584166022604>  **Proyectos de Desarrollo de
Software *
Web:walterfalla.odoo.com *Proyectos de Domotica
& Iluminación LED *
Skype:walterfalla   *Community
Manager*
   

   

OT - Software/servicio para video conferencias.

[divagante]

Hola gente!

 Deseaba consultarles por un software para realizar video conferencias. 
El requisito es que sea software libre, ya que se esta usando un 
servicio de pago y que brinda software privativo -vamos! calcadito a 
skype digamos-.
 Por el momento, se me ocurre a mi nomas, se podría usar localmente el 
ancho de banda para realizar la transmisión a no mas de 10 o 15 
personas, intentando así prescindir de contratar un servicio externo.


 P.D.: he pensado en firefox 'hello', pero habiendolo utilizado entre 
tres personas me ha parecido lento y por demas pasado (supongo que es el 
codec utilizado). Quizas alguien tenga mas experiencia con esta 
utilizdad de mozilla.


 Saludos y muchas gracias.
<>

Re: maxima, draw3d, and vtk

[Thomas E. Vaughan]

On Sat, Aug 20, 2016 at 04:54:09PM +0200, Nicolas George wrote:
>
> Le quartidi 4 fructidor, an CCXXIV, Thomas Vaughan a ?crit?:
> >
> > Using 'dpkg -S libvtkCommonCoreTCL', I find
> > libvtk6.3: /usr/lib/x86_64-linux-gnu/libvtkCommonCoreTCL-6.3.so.6.3.0
> > libvtk6.3: /usr/lib/x86_64-linux-gnu/libvtkCommonCoreTCL-6.3.so.6.3
> > 
> > It looks to me as though there is something at least a bit broken about the
> > names of the libraries installed by the libvtk6.3 Debian package, but I'm
> > not an expert in library naming.
> 
> A library normally exists as three files:
> 
> First, the actual library file, with a full version after the .so extension.
> The other files will be symlinks to it.
> 
> Second, a symlink with just a major version mark after the .so extension.
> This is called the SONAME, it can be queried with "objdump -p". This is the
> name programs must use to access the library. It therefore must be changed
> each time an incompatible change in the library ABI is made, for example
> changing the type of a function argument.

Thanks for your excellent and clear response!  I see that the actual library
file and the SONAME link (which has the major version) are included in the vtk
packages that I have installed.

> Third, a symlink with just .so: this is accessed to support linking libraries
> using the "-lsomething" linker options.

It seems that maxima is trying to access a file that is ordinarily present only
when one might want to build an executable (or other library) and then link
against vtk.  Linking via '-lfoo' would also, in general, require header files,
which declare the symbols that are resolved by linking.  So I see why the link
ending in '.so' would be supplied by the '-dev' package.

> The .so file comes with the -dev package.

Right.

> Still, the only acceptable way of accessing a library for a program (not
> part of the library package) is though the SONAME. The maxima package is
> definitely at fault.

You seem to mean that the only acceptable way of accessing a library via
dlopen() is through the SONAME.  I presume that maxima is using dlopen(), but I
don't really know.  Clearly, one may access a library by linking to it (as with
'-lfoo') via the file that ends with '.so'.

> Still, there may be a case for another explanation: sometimes, the upstream
> of a library does not understand the SONAME logic and just produces a library
> file ending as .so, and the distribution maintainers add the SONAME to make
> it a proper library. If that happens, programs that expect that will not work
> without the -dev package. You can check that by compiling the upstream libvtk
> and checking if it includes the SONAME.

You seem to suggest that the Debian vtk developers might have made changes to
the build system to make the names of the library and the links be right,
though a bit different from upstream vtk, and that the Debian maxima developers
might not have caught a broken dependency on upstream naming when incorporating
the draw package into maxima.

Re: install debian depuis écran secondaire

[err404]

On 08/20/2016 04:26 PM, alpha bravo wrote:
> Bonjour,
> 
> 
> mon pc portable a un grave problème d'écran ou de carte graphique ; je
> l'utilise sans aucun problème avec un écran secondaire.
> 
> Je veux le réinstaller pour mettre à jour la distribution (passage sous
> stretch) et je ne veux pas de dist-upgrade.
> 
> Quelqu'un saurait-il comment procéder pour dire à l'installeur debian
> d'utiliser l'écran secondaire et non pas l'écran principal ?
> 
> Existe-t-il d'autres manières de s'en sortir ?
> 
> 
> Merci.
> 
option 1: Tu peux toujours sortir le disque dur et faire une install minimale 
depuis un autre ordinateur sur lequel tu aura mis le disque dur.

option 2: Pour certains ordinateurs portable, il y a une combinaison de touches 
pour activer l'une des sorties video, ou les deux, ou aucune.
Le résultat est très variable suivant les constructeurs.



signature.asc
Description: OpenPGP digital signature

install debian depuis écran secondaire

[alpha bravo]

Bonjour,


mon pc portable a un grave problème d'écran ou de carte graphique ; je
l'utilise sans aucun problème avec un écran secondaire.

Je veux le réinstaller pour mettre à jour la distribution (passage sous
stretch) et je ne veux pas de dist-upgrade.

Quelqu'un saurait-il comment procéder pour dire à l'installeur debian
d'utiliser l'écran secondaire et non pas l'écran principal ?

Existe-t-il d'autres manières de s'en sortir ?


Merci.

Re: maxima, draw3d, and vtk

[Nicolas George]

Le quartidi 4 fructidor, an CCXXIV, Thomas Vaughan a écrit :
> Using 'dpkg -S libvtkCommonCoreTCL', I find
> libvtk6.3: /usr/lib/x86_64-linux-gnu/libvtkCommonCoreTCL-6.3.so.6.3.0
> libvtk6.3: /usr/lib/x86_64-linux-gnu/libvtkCommonCoreTCL-6.3.so.6.3
> 
> It looks to me as though there is something at least a bit broken about the
> names of the libraries installed by the libvtk6.3 Debian package, but I'm
> not an expert in library naming.

A library normally exists as three files:

First, the actual library file, with a full version after the .so extension.
The other files will be symlinks to it.

Second, a symlink with just a major version mark after the .so extension.
This is called the SONAME, it can be queried with "objdump -p". This is the
name programs must use to access the library. It therefore must be changed
each time an incompatible change in the library ABI is made, for example
changing the type of a function argument.

Third, a symlink with just .so: this is accessed to support linking
libraries using the "-lsomething" linker options.

The actual file, of course, comes in the library package. The SONAME symlink
comes with it too, but it is really not necessary since ldconfig will
recreate them if necessary.

The .so file comes with the -dev package.

The SONAME symlink exists to allow several versions of the same library to
be present on the system at the same time. Otherwise, you would have to
rebuild all the packages that depends on it at the same time.

On the other hand, incompatible API changes are considered rare enough: no
provisions exist to allow the development files for several versions of the
same library to be present on the system at the same time. If it is
necessary, it either requires the developer to play with -L and -I paths, or
the name of the library needs to be changed, for example from gtk-2.0 to
gtk-3.0 (which are respectively at version 2.32.2 and 3.21.4; I wonder what
they were on when they decided to include the .0 in the name for the 3
branch).


Now, what can we tell about vtk? Well, you can see that the version number,
"6.3" is included both in the library name and as a suffix for the SONAME.
That tells us that the vtk people have decided not to care more about ABI
stability than API stability. Fine.

Still, the only acceptable way of accessing a library for a program (not
part of the library package) is though the SONAME. The maxima package is
definitely at fault.

The blame likely lies with the maxima people.

Still, there may be a case for another explanation: sometimes, the upstream
of a library does not understand the SONAME logic and just produces a
library file ending as .so, and the distribution maintainers add the SONAME
to make it a proper library. If that happens, programs that expect that will
not work without the -dev package. You can check that by compiling the
upstream libvtk and checking if it includes the SONAME.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

maxima, draw3d, and vtk

[Thomas Vaughan]

The 'draw3d' function defined in the 'draw' package for maxima is failing.
Before I file a bug report, I'd like to find out what package has the bug.
(Or find out if the bug be user error. :-)

I am running Debian unstable with maxima, vtk6, and tcl-vtk6 installed,
according to documentation here: http://riotorto.users.sourceforge.net/vtk/

The error output (pasted below) refers to a file that does not exist:
/usr/lib/x86_64-linux-gnu/libvtkCommonCoreTCL-6.3.so

Using 'dpkg -S libvtkCommonCoreTCL', I find
libvtk6.3: /usr/lib/x86_64-linux-gnu/libvtkCommonCoreTCL-6.3.so.6.3.0
libvtk6.3: /usr/lib/x86_64-linux-gnu/libvtkCommonCoreTCL-6.3.so.6.3

It looks to me as though there is something at least a bit broken about the
names of the libraries installed by the libvtk6.3 Debian package, but I'm
not an expert in library naming.

If you have an idea of what I might do to rectify the situation, then
please respond to all, because I am not a subscriber to the list.

Anyway, here is the error that I saw inside maxima:

(%i8) draw3d(color=white,elevation_grid(m,0,0,10,10));
(%o8)done
(%i9) couldn't load file "/usr/lib/x86_64-linux-gnu/
libvtkCommonCoreTCL-6.3.so": /usr/lib/x86_64-linux-gnu/
libvtkCommonCoreTCL-6.3.so: cannot open shared object file: No such file or
directory
attempt to provide package vtkCommonCoreTCL 6.3 failed: no version of
package vtkCommonCoreTCL provided
attempt to provide package vtkcommoncore 6.3 failed: no version of package
vtkcommoncore provided
Error in startup script: attempt to provide package vtk 6.3 failed: no
version of package vtk provided
("package ifneeded vtk 6.3" script)
invoked from within
"package.orig require vtk"
("eval" body line 1)
invoked from within
"eval package.orig $args"
(procedure "package" line 2)
invoked from within
"package require vtk"

-- 
Thomas E. Vaughan

Re: Ayuda

[Camaleón]

El Fri, 19 Aug 2016 16:30:49 -0500, Paynalton escribió:

> cunchunfleale el batango y luego dale vuelta al durmbuele hasta que diga
> "Sistema enchinflado", ya que te salga eso sólo cancheale y listo.

:-)
   :-D
   X-D

Saludos,

-- 
Camaleón

Re: Can't install new driver

[Charlie]

On Fri, 19 Aug 2016 23:03:40 -0400 Maureen L Thomas sent:

> On 08/19/2016 07:15 PM, Charlie wrote:
> > On Fri, 19 Aug 2016 17:59:06 -0400 Maureen L Thomas sent:
> >  
> >> Ok, so I got rid of the windows machine and found a card that fit
> >> the old machine.  It needs the rtl_nic driver to work.  Fine I
> >> have that firmware and the needed driver on a USB stick and on an
> >> iso disk for stretch.  The USB is just the firmware for these type
> >> of cards.  I must be losing my mind because I cannot remember how
> >> to get the driver to install off of the USB to my existing weezy
> >> system.  Thank you for even reading this but I need help.  I did
> >> try apt-get install but it didn't find the file on the USB>
> >> Maureen
> >>  
> >
> > After contemplation, my reply is:
> >
> > I'm not certain I understand the question. If there is enough
> > detail?
> >
> > If the Debian Wheezy? system is installed do: dpkg
> > -i /yourUSBstick/thefile-name.deb
> >
> > I think that should install it, unless you get any errors.
> >
> > If you are installing Wheezy? and have a netinstall or DVD/CD just
> > install the system for now. Bypass the network card search. Then do
> > as above and after that do all the network search and find things
> > and apply the packages.
> >
> > Hope that helps somewhat if not completely.
> > Charlie
> >  
> It appeared to have been installed with the above information but I 
> still cannot connect to the net.  I have tried to send my log file
> and dmseg file but apparently it will not go through.  Thank you
> Charlie though that did appear to work with no error messages.
> Maureen


After contemplation, my reply is:

I assume, probably making an ass of me, you're able to connect to the
internet through your Ethernet cable?

So you didn't use a wireless network to install, the driver for the
card is the start.

Do you have wireless packages like wpa_supplicant installed?

There are a couple of network managers in Debian. I have never used
network-manager, but years ago I used wicd for a very short time.

Or are you just creating your network connection
through /etc/network/interfaces which is the way I found best and
easiest? Once I realised that was an option.

Apologies, but I don't know the command to discover all the packages
you need for wireless networking. Someone else will be able to suggest
that.

Sorry I can't be of more help.
Charlie

-- 
Registered Linux User:- 329524
***

Appreciation is a wonderful thing: It makes what is excellent
in others belong to us as well. -Voltaire

***

Debian GNU/Linux - Magic indeed.

-

Shotwell diaporama

[Jean Bernon]

Bonjour, 

Depuis peu, lorsque je lance un diaporama dans Shtowell, il défile correctement 
mais le menu en bas du diaporama (boutons paramètres, avant, arrière, sortie du 
diaporama) ne fonctionne plus et il est donc impossible d'arrêter le diaporama 
depuis Shotwell. Un seul changement semble coïncider avec l'apparition du 
problème : j'ai déplacé la bibliothèque de photos depuis le disque interne de 
mon PC vers un disque externe relié par USB. 

Quelqu'un a-t-il déjà rencontré ce problème mineur ? 

Jean 

Re: A minimalist network

[Richard Owlett]

On 8/19/2016 7:42 PM, Mike McClain wrote:

Don't know if this will help but...


It will. Perhaps not in the way you would expect. Early in this 
thread I asked "What questions should I be asking?" Your post 
provides guidelines to creating for myself those questions. I 
hope that makes sense.



I have a 2 box network, Wheezy and Win2K, cable connected and able to
access directories on the Win2K box from Debian.


I have a set of Wheezy DVD's so I can avoid one possible source 
of ambiguity.



Never needed to go the other way.


I don't see that I currently have a need to go the other way.


The Linux box is named playground, the Win2K box South40.
There is a router between them but it's not necessary (belt).


Pedagogically I'd prefer {belt OR suspenders} to {belt AND 
suspenders}.



[snip details of set up]


Thank you.

Re: Can't install new driver

[Curt]

On 2016-08-19, Maureen L Thomas  wrote:
>
> I got the firmware from debian downloads.  I put a new nic card in my 
> computer so I can connect to the internet.  I need the 
> rtl_nic/rtl8168g-2.fw driver to get it to work.  I have that driver on 
> my usb stick.  I need to install it from the usb stick to the computer 
> with weezy on it.  I don't remember if there is a way to do that.  Does 
> that help.
>

You downloaded the driver from wheezy-backports?  It's a deb file (a
debian package).  Normally, you would simply transfer the deb from the
usb key to your wheezy box and install it via the following command (as
root) :'dpkg -i firmware-realtek_0.43~bpo70+1_all.deb' and you'd be
done.

Or have I missed something along the way (after inadquate
contemplation)?


-- 
 "Until the Lion learns to write, tales of the hunt shall always glorify the 
Hunter."
— African proverb

Re: [HS] Sur quoi écoute Bind ?

[Ph. Gras]

Bonjour Pascal,
Bonjour à toutes et à tous,

>> 
>>> # netstat -antp
>>> Connexions Internet actives (serveurs et établies)
>>> Proto   Recv-Q  Send-Q  Adresse locale  Adresse 
>>> distanteEtatPID/Program name
>>> tcp60   0   ::1:53  
>>> :::*LISTEN  
>>> 764/named   <=  <=
>>> 
>> 
>> Je n'ai pas compris ce qui commande cette écoute =>
> 
> Le contenu de la directive listen-on-v6 qui doit inclure ::1 ou "localhost" 
> (toutes les adresses locales).
> 

Je me suis demandé si les écoutes sur :
tcp 0   0   5.196.73.219:53 
0.0.0.0:*   LISTEN  764/named   
tcp 0   0   127.0.0.1:53
0.0.0.0:*   LISTEN  764/named   

ne suffisaient pas. Mais je n'avais pas remarqué que les unes s'effectuaient 
sur TCP, tandis que l'autre
est branchée sur TCP6 (… il faudra que je me renseigne sur leurs spécificités 
respectives, merci de ne
pas spoiler).

Par ailleurs, j'ai appris que Bind pouvait recevoir des requêtes avec UDP, ce 
que je n'ai pas vu avec la
commande netstat -antp (peut-être que -t ou -p signifient TCP ?, je vais 
vérifier -- motus).

Merci pour vos réponses,

Ph. Gras

Re: Can't install new driver

[deloptes]

Maureen L Thomas wrote:

> It appeared to have been installed with the above information but I
> still cannot connect to the net.  I have tried to send my log file and
> dmseg file but apparently it will not go through.  Thank you Charlie
> though that did appear to work with no error messages.
> Maureen

Perhaps you need the kernel from the wheezy-backports as well.

Just paste here the lines from dmesg after modprobe

Re: A minimalist network

[Mike McClain]

Don't know if this will help but...
I have a 2 box network, Wheezy and Win2K, cable connected and able to
access directories on the Win2K box from Debian.
Never needed to go the other way.
The Linux box is named playground, the Win2K box South40.
There is a router between them but it's not necessary (belt).

On the Linux side:
These packages installed:
cifs-utils
libfilesys-smbclient-perl
libsmbclient
samba-common
samba-common-bin
smbclient

/etc/hosts has these entries.
192.168.1.1 router
192.168.1.2 playground  play
192.168.1.3 south40 s40

/etc/hostname contains:
playground

/etc/network/interfaces has these lines:
# The primary network interface
allow-hotplug eth1
iface eth1 inet static
address 192.168.1.2
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255

/etc/fstab has these entries:
//south40/H$/docs /south40/docs cifs 
noauto,rw,user,credentials=/home/mike/smb.psswd,uid=1000,file_mode=0755,dir_mode=0755,nounix,noserverino
   0 0
//south40/I$/MP3s /south40/MP3s cifs 
noauto,rw,user,credentials=/home/mike/smb.psswd,uid=1000,file_mode=0755,dir_mode=0755,nounix,noserverino
   0 0
#   docs & MP3s on different partitions

/home/mike/smb.psswd has 600 permissions and contains:
username=Win2K_user
password=Win2K_password

I have a small iptables firewall that must allow traffic to/from Win2K.

To access the Win2K files:
root@/deb73:/> mount /south40/docs

On the Win2K side:
StartMenu/ControlPanel/System/NetworkID/Properties:
Computer Name = south40
Member of workgroup = WORKGROUP
StartMenu/ControlPanel/System/NetworkID/NetworkID:  launches wizard
Home use, Users must enter user name and password
StartMenu/Control Panel/Internet Options/Internet Properties/Security/Local 
Intranet/Sites/Advanced/:
192.168.1.1
192.168.1.2
StartMenu/Settings/Network and Dial-up Connections/Local Area Connection  
right click
Properties check:
Client for Microsoft Networks
File and Printer sharing
Internet Protocol(TCP/IP)
select Internet Protocol(TCP/IP)/Properties:
Use the following IP address:
IP Addr:192.168.1.3
Subnet mask:255.255.255.0
Default Gateway:192.168.1.2
Use the following DNS server addresses:
Prefered DSN:   208.67.222.222
Alternate:  208.67.220.220
select Advanced/WINS/Enable NETBIOS over TCP/IP

create C:\shared & shared it (only used with smbclient to pass files back & 
forth).

C:\WINNT\system32\drivers\etc\hosts: 192.168.1.2playground


HTH,
Mike
--
Seven deadly sins:
Anger, gluttony, envy, sloth, avarice, lust and pride.
I practice most of these so guess I'll die one day.