Re: Jessie : plus de session X sur un HP2133

2015-04-29 Thread Adrien
Le 28/04/2015 17:49, Bernard Schoenacker a écrit :
 bonjour,

 le serveur xorg est compilé pour un noyau 3.2 et voici la preuve :

 [   286.735] X Protocol Version 11, Revision 0
 [   286.735] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
 [   286.736] Current Operating System: Linux little-hat
 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) i686
 [   286.736] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-686-pae
 root=UUID=fb6f90f3-70b5-4f82-af42-ed655eb33496 ro quiet [   286.737]
 Build Date: 11 February 2015  01:14:26AM


 télécharger le noyau 3.2 amd64 :
 https://packages.debian.org/fr/wheezy/linux-image-3.2.0-4-amd64

Bonjour Bernard et merci de ta réponse,

La machine ne fonctionne pas sous amd64, c'est un système 32 bits. Le
processeur est un VIA C7-M Processor 1600MHz
Par contre, il se trouve que j'avais déjà un noyau 3.2.0-4-686-pae
installé, et ensuite ça fait pareil.
Voici dans ce cas le /var/log/Xorg.0.log :

https://framabin.org/?88f28072f494b757#VzS8dKQvUmRq/mObCSvaAJYCKmwI115pxpqUQPvmu/k=

Merci !

--
Adrien.



signature.asc
Description: OpenPGP digital signature


Re: documentation en français sur Systemd

2015-04-29 Thread Sylvain L. Sauvage
Le mercredi 29 avril 2015, 12:52:42 
frederique.marecai...@numericable.fr a écrit :
 Merci pour cette doc.
 
 Je vois que pour gérer les services, on peut utiliser la
 commande systemctl start|stop|disable|enable|status.
 
 Cela remplace donc le #/ /etc/init.d/services
 start|stop|disable|enable|status?

  Oui.

  Mais il était déjà recommandé d’utiliser 'invoke-rc.d' (sysV ; 
gère les niveaux d’exécution) ou 'service' (sysV, upstart, 
openrc ou systemd).

  Tu peux quand même continuer à utiliser /etc/init.d/toto, il 
va utiliser systemctl un sous-main.
  Évidemment ça ne fonctionnera pas pour les services purement 
systemd. Donc tu devras quand même connaître et utiliser 
systemctl et, en plus, savoir sur quels services il doit être 
utilisé directement. Donc autant n’utiliser que systemctl ou 
service, ça en fait moins à connaître…

-- 
 Sylvain Sauvage

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/1721627.rmuq0fQcCG@earendil



Re: documentation en français sur Systemd

2015-04-29 Thread frederique . marecaille
Merci pour cette doc.

Je vois que pour gérer les services, on peut utiliser la commande systemctl 
start|stop|disable|enable|status.

Cela remplace donc le #/ /etc/init.d/services start|stop|disable|enable|status?


 Message d'origine 
De : maderios mader...@gmail.com
À : debian-user-french@lists.debian.org
Objet : documentation en français sur Systemd
Date : 29/04/2015 11:20:10 CEST

Bonjour
L'excellent et vénérable site lea-linux.org propose une documentation en 
français sur Systemd
http://lea-linux.org/documentations/Systemd
-- 
Maderios

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/5540a24a.9060...@gmail.com




Re: jessie x86_64: Rosegarden unusable (possible bug in qt-at-spi?)

2015-04-29 Thread Alexis


Ric Moore wayward4...@gmail.com writes:


On 04/28/2015 11:33 PM, Alexis wrote:


I have to wonder if you installed another DE like XFCE would you 
still  have the problem?


i'd already tried under KDE with the same result, but hadn't tried 
other DEs (of which i have several installed, for software testing 
purposes). i've now also tried XFCE and LXDE with the same result.



I love musical stuff, but the heavy depend on jack put me off.


Well, i don't use Rosegarden seriously enough to have set up jack; 
i just run QSynth and use its PulseAudio output. (i use Hydrogen 
similarly.)



Alexis.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/87sibjmabn@gmail.com



Re: initramfs broken on Jessie upgrade

2015-04-29 Thread Bernhard Schmidt
Bernhard Schmidt be...@birkenwald.de wrote:

Hi,

 Since I could not find anything secret in the initrd I have uploaded
 both images

 http://users.birkenwald.de/~berni/volatile/783620_initrd_ok
 http://users.birkenwald.de/~berni/volatile/783620_initrd_broken

 It is _not_ caused by the initrd per se, I have just rebooted the system
 and edited the grub commands to load the .broken initrd, and it came up
 fine.

 I will make a snapshot in the broken state the next time it happens,
 maybe something else is broken. Except for update-initramfs I did not
 run any command, but the system was fully booted on the Wheezy kernel,
 maybe something else triggered a fix.

 I hope to upgrade a few more systems today, maybe I can reproduce it.

Got another system with the symptoms and managed to get a snapshot.

It is really extremely weird. The kernel output is

List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)

This is reproducible. To fix it it is enough to boot into the Wheezy
kernel (even with init=/bin/sh), then reboot. It apparently does
something to the root-fs (fsck?) which allows the Jessie kernel to boot.

I have asked our Windows guys to make a screencast, it is uploaded here.

http://users.birkenwald.de/~berni/volatile/783620.mkv

We still have the snapshot available, if you have an idea please drop me
a note.

Bernhard


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mhqdo5$37k$1...@ger.gmane.org



Re: Jessie : plus de session X sur un HP2133

2015-04-29 Thread Sébastien NOBILI
Le mercredi 29 avril 2015 à 11:57, Adrien a écrit :
 La machine ne fonctionne pas sous amd64, c'est un système 32 bits. Le
 processeur est un VIA C7-M Processor 1600MHz
 Par contre, il se trouve que j'avais déjà un noyau 3.2.0-4-686-pae
 installé, et ensuite ça fait pareil.

Est-ce que tu trouves des traces de plantage (segfault ou autre) dans les logs
système (« /var/log/syslog », « /var/log/kern.log ») ?

As-tu essayé de forcer l'utilisation du driver VESA ?

Il te suffit de créer un fichier « /etc/X11/xorg.conf » comme indiqué là :

http://ubuntuforums.org/showthread.php?t=1228082p=7711766#post7711766

Sébastien

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150429113640.gc14...@sebian.nob900.homeip.net



Re: variable globale d'environnement [RÉSOLU]

2015-04-29 Thread humbert . olivier . 1
Merci à vous pour les réponses qui m'ont un peu éclairé sur la notion 
d'environnement et de variables d'environnement.

Avec Jessie/lightdm/mate, j'ai trouvé une solution qui fonctionne et qui 
consiste à mettre un fichier dans /etc/X11/Xsession.d/

qui contient:
  TOTO=tata
  export TOTO

Cordialement,
Olivier

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: 
https://lists.debian.org/2131640852.1021726016.1430308321165.javamail.r...@zimbra61-e11.priv.proxad.net



Re: [Jessie] Anomalie

2015-04-29 Thread Alain Rpnpif
Le 27 avril 2015, Sébastien NOBILI a écrit :

 Bonjour,
 
 Le jeudi 23 avril 2015 à  9:17, Alain Rpnpif a écrit :
  Alors avec de GRANDES précautions (!!!) à coup de chmod -R
  utilisateur.utilisateur * sur le home (surtout pas sur / !!!), on peut
  réparer ces permissions.
 
 Sûrement une faute de frappe, « chown » plutôt que « chmod ».

Oups, oui. merci.

-- 
Alain Rpnpif

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429081756.97575500...@chro.home



Re: Bluetooth mouse problems on Jessie

2015-04-29 Thread Lisi Reisz
On Wednesday 29 April 2015 08:10:25 Johann Spies wrote:
 This is happened on two different laptops so I do not think it is a
 hardware problem.

The mouse is hardware.  This test does not exclude the possibility that it is 
the mouse that is faulty.  It merely suggests (not proves) that the laptops 
are not.  

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201504291020.46976.lisi.re...@gmail.com



Re: Bluetooth mouse problems on Jessie

2015-04-29 Thread Brad Rogers
On Wed, 29 Apr 2015 09:10:25 +0200
Johann Spies johann.sp...@gmail.com wrote:

Hello Johann,

mouse which I have been using for years.  I get the message
successfully added but failed to connect.

As Lisi says, you've not eliminated the mouse as the problem (in fact,
you've probably done the opposite).

Try the simple things first;  Batteries failing, perhaps?

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent
Bet you thought you knew what I was about
Problem - Sex Pistols


pgpV3voA6aKxg.pgp
Description: OpenPGP digital signature


Re: No HDMI-Sound anymore with onboard sound chip Intel CougarPoint HDMI after upgrading from Wheezy to Jessie

2015-04-29 Thread Lisi Reisz
On Wednesday 29 April 2015 06:05:06 Juha Heinanen wrote:
 Lisi Reisz writes:
   Any suggestions how I can try to get the HDMI sound working again?
 
  My eyes are playing up tonight, so I haven't beeen able to read your
  email carefully, but I got HDMI sound working on Jessie by :
 
  Checking that I had pulseaudio (I can't remember whether I had it or had
  to install it after checking).
 
  Installing pavucontrol.
 
  Turning on HDMI, which was off by default.

 i have hdmi audio (HDA Intel HDMI) working fine on my chromebook just
 with alsa, i.e., no pulseaudio.

Yes, but on my Jessie it didn't.  And with pulseaudio and pavucontrol it did.

Depends on your priorities.  Being right all along or getting it working.  

Go on doing the same until it gives in, says Sorry, guv, you're right and 
works after all.  Or try a few different things and see if they work.  You 
can always uninstall things if they don't work.

I was offering a potential practical solution to a problem.  As I said, I also 
use supermarkets.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201504290829.29753.lisi.re...@gmail.com



Re: Fwd: Drivers ATI Debian Jessie 64 Bits

2015-04-29 Thread Fernando Mordi Guerrieri
Creo, entonces, que lo mejor será instalar el driver no privativo.

¿Cómo instalo el AMDGPU?

Mordi

El 29 de abril de 2015, 1:05, Jose Maldonado josemal...@gmail.com
escribió:

 On 28/04/15 16:23, Fernando Mordi Guerrieri wrote:

 El 28 de abril de 2015, 17:42, metalhead b93 b93onli...@gmail.com
 escribió:

  me corrijo
 lo siento me he equivocado, no instalé KDE fué KDM (Session manager),

 y no, no soy Fernando.

 El día 28 de abril de 2015, 10:29, metalhead b93
 b93onli...@gmail.com escribió:

 El día 28 de abril de 2015, 9:39, Camaleón noela...@gmail.com

 escribió:

 El Tue, 28 Apr 2015 16:03:18 +0200, Fernando Mordi Guerrieri escribió:

 Hum... a ver que me estoy liando... ¿fernando = metalhead? :-???



  jaja yo ando igual, le chico apareció de pronto y sin más empezó a
 hablar pero bnn
 prosigamos

  El 28 de abril de 2015, 15:35, Camaleón noela...@gmail.com escribió:

  El Mon, 27 Apr 2015 13:35:23 -0500, metalhead b93 escribió:


 (...)

  Te recomiendo que uses mientras tanto el driver libre (radeon) hasta
 que lo arreglen por lo que convendría que siguieras de cerca ese
 informe de fallo para ver si hay algún cambio.

  6-ALT+F1 para logear y lego starx, inicia el entorno gráfico pero
 arroja el mismo mensaje

   Oh no! Something has gone wrong
   A problem has occurred and the system cant't recover. All

 extension

 have been disabled as a precaution.

 hice una copia de Xorg.0.log http://pastebin.com/1QTxjgei


 Perfecto. Sí, en el log se ven varios errores pero que la pantalla se
 vaya a negro indica un problema más grave. Revisa los mensajes del
 bug
 por si vieras algo que te interesara y si te animas, añade tu
 problema
 para que vean que hay más gente afectada.

  Una pregunta muy básica:

 ¿cómo vuelvo al driver libre radeon? La única que me queda es usar
 el
 modo consola. ¿qué comandos debo ejecutar?


 Si tienes instalado el driver propietario antes de eliminarendolo
 prueba
 añadiendo el módulo fglxr en la lista negra y activa el radeon. Eso lo
 tendrás en /etc/modprobe.d/radeon-kms.conf y para habilitarlo tendrás
 que dejarlo así:

 options radeon modeset=1

 Si eso no funciona, seguramente tendrás que eliminar los paquetes del
 driver propietario :-(


  Fernando, si has hecho  aptitude install fglrx-driver  creo que
 bastaría con aptitude remove fglrx-driver
 desconozco si hay que hacer algo más, prueba también con lo de la lista

 negra

 pero sigue leyendo que os traigo una noticia.





  esto va para todos

 resulta que tuve la idea de intentar con otros entornos gráficos,
 así que cómo la pantalla iniciaba en negro y no dejaba iniciar sesión,
 decidí instalar el gestor de inicio de sesión KDE
 aptitude install kde

 reinicié la pc y, vualá! KDE funciona, pero cuando inicio sesión con
 Gnome, otra ves el mismo error

 entonces decidí seguir probando, y también instalé el entorno de
 escritorio MATE aptitude install mate-desktop-environment-core(eso
 me instala mate básico)

 ahora reinicio la pc selecciono entorno de escritorio MATE con KDE y
 que sorpresa me llevo, MATE también funciona a la perfección,  e
 incluso veo habilitada una gran variedad de resoluciones para la
 pantalla (el problema es que yo quiero Gnome)

 también he comprobado la aceleración 3D y funciona perfecto

 metalheadb93@B93-Desktop:~$ glxinfo | grep direct
 direct rendering: Yes
  GL_AMD_multi_draw_indirect, GL_AMD_name_gen_delete,
  GL_ARB_draw_indirect, GL_ARB_draw_instanced,
 GL_ARB_enhanced_layouts,
  GL_ARB_multi_draw_indirect, GL_ARB_multisample,
 GL_ARB_multitexture,
  GL_EXT_direct_state_access, GL_EXT_draw_buffers2,

 GL_EXT_draw_instanced,

  GL_AMD_multi_draw_indirect, GL_AMD_name_gen_delete,
  GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect,
  GL_ARB_multi_draw_indirect, GL_ARB_multisample,
 GL_ARB_multitexture,
  GL_EXT_direct_state_access, GL_EXT_draw_buffers2,

 GL_EXT_draw_instanced,

 metalheadb93@B93-Desktop:~$ glxgears
 33376 frames in 5.0 seconds = 6675.199 FPS
 33721 frames in 5.0 seconds = 6744.189 FPS
 33724 frames in 5.0 seconds = 6744.715 FPS
 30181 frames in 5.0 seconds = 6035.950 FPS
 27798 frames in 5.0 seconds = 5559.473 FPS
 27544 frames in 5.0 seconds = 5508.700 FPS



 eso me lleva a creer que no hay problema con los drivers,

 quizás aun faltan librerías para que el nuevo Gnome corra sobre los

 drivers ati;

 no lo se, díganme ustedes, habra alguna posibilidad de solucionar el
 lío de ati con Gnome?



 Y yo no soy Metalhead :-)

 Perdonen por la aparición tan intempestiva. No quería hablar de cosas
 personales para no quedar fuera de tema.
 ¿es costumbre hacer una presentación personal cuando se es nuevo en la
 lista?

 A modo de presentación tardía:
 Me llamo Fernando, me dicen Mordi.
 Soy argentino y vivo en Francia. Soy biólogo, así que con el carbono me
 entiendo mucho mejor que con el silicio.
 Uso Debian desde 2008.
 Hace poco compré una nueva PC, por piezas. Le pedí consejo a los usuarios
 de soft libre locales (Ciudad 

Re: Problem with name resolution - IPv6 queries are sent before IPv4.

2015-04-29 Thread Darac Marjal
On Wed, Apr 29, 2015 at 10:10:26AM +0200, Rafał Radecki wrote:
Hi Everyone :)
I have a quite annoying problem on several ubuntu 12.04 servers. I know
that I should use ubuntu mailing list but I tried that with no success :)
Maybe someone here will be able to help.
When I force a dns query using:
time wget --waitretry=1 [1]http://xxx.yyy -O -
I get (tcpdump  wireshark) the info that an  IPv6 query is first send
to a DNS server from /etc/resolv.conf. The server is only serving IPv4

Are you saying that xxx.yyy has both a A and an  record, but is only
listening on IPv4? If so, then the server is misconfigured. This is
effectively the same has having two A records and not listening to
requests on one of them.

queries so it responds with an error. Then an IPv4 query is sent. Overall
the process takes ~10 seconds every time so its painful.
[cut]
Any clues? :D
BR,
Rafal.
 
 References
 
Visible links
1. http://xxx.yyy/


signature.asc
Description: Digital signature


Bluetooth mouse problems on Jessie

2015-04-29 Thread Johann Spies
Since the weekend (and Jessie becoming Stable) I could not use my bluetooth
mouse which I have been using for years.  I get the message successfully
added but failed to connect.

When I delete the device in the bluetooth setup and try to set it up again,
the device seems to be detected, then it disappears and reappears about
every second.

This is happened on two different laptops so I do not think it is a
hardware problem.

Anyone else having similar problems?

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)


Re: Contribuciones de Debian al mundo

2015-04-29 Thread Cristian Mitchell
El 28 de abril de 2015, 7:20 p. m., Esteban Mongeestebanmo...@riseup.net
escribió:

 El 2015-04-28 15:20, Carlos Manuel Escalona Villeda escribió:

 Para muestra un botón:

 http://futurist.se/gldt/wp-content/uploads/subtrees/debian1007.png

 Debian es El sistema operativo universal, su objetivo no es ser el más
 innovador, su objetivo es estar allí para todo y para todos.

 Lo principal que tiene Debian es contar con la mayor cantidad de
 colaboradores del planeta, la forma de organizarse para dar forma a un
 sistema que sea eficiente, seguro y estable.

 Para explicar las cosas siempre me gusta recurrir a la historia. En la
 India se inventó el sistema numérico que usamos, una tribu nómada en el
 desierto inventó los libros, los turcos inventaron gran cantidad de
 textiles y en egipto se inventó el cristal. Como logras que todos esos
 inventos creados por pueblos tan remotos se junten para formar parte de
 una
 civilización??? Como consigues que una cultura comparta sus logros con
 otras culturas y que estas reciban estos descubrimientos e inventos de
 buena gana

 Lo que sucedió en la edad media fue que el islamismo se extendió por toda
 esa parte del mundo y les impuso una regla: Cada persona estaba obligada
 (de hecho creo que aun lo están) a viajar al menos una vez en la vida
 hacia
 la ciudad de La Meca.

 Esto provocó que en ese lugar se juntaran personas provenientes de cada
 pueblo musulmán, y estas personas llevaban consigo conocimientos,
 inventos,
 historias. Al entrar en contacto con personas de otros pueblos aprendían,
 se maravillaban y volvían a sus pueblos llevando todo lo que habían
 aprendido.

 Debido a esto fue que hasta el invento más pequeño de esos pueblos formara
 la civilización que hoy tenemos, si miras a tu alrededor verás tecnologías
 creadas por esos pueblos insignificantes, desde el cristal de tu ventana
 hasta la escoba y el azulejo de tu baño.

 Eso es lo que hace Debian. Mira cuantos proyectos existen en Github, en
 sourceforge, en googleCode y en tantos lugares. La mayoría de ellos son
 basura. Como tomas toda esa tecnología y la integras a nuestra
 civilización
 para formar parte de ella, separando lo bueno de lo malo y organizando los
 millones y millones de proyectos existentes en el planeta???

 Debian es la Meca del desarrollo informático. Todo desarrollo va hacia
 Debian, si logra ser lo bastante bueno para soportar las rudas pruebas
 para
 llegar a Stable entonces es una buena tecnología y, desde Debian, se
 propaga al resto del mundo y se integra a nuevos proyectos que cambian
 nuestra forma de vida.

 Ejemplos??? Mira a Apache, metido en casi todos los servidores web, no
 inició con Debian pero ha pasado por todas sus pruebas y se ha convertido
 en un demonio http tan eficiente que estará soportando nuestras
 comunicaciones durante los próximos siglos.

 Pregunta a los asesores de Oracle Cuantos betatesters y desarrolladores
 tienen? , y en cuanto te lo digan muéstrales esta tabla:

 https://bugs.mysql.com/bugstats.php?limit=all



 Quiero hacer una discusión sana... y voy a hacer comentarios del tipo
 abogado del diablo ninguno de esos comentarios representa lo que yo
 pienso, yo soy fiel a Debian y conozco sus ventajas y desventajas, las
 cuales son muy pocas, pero a nivel empresarial importantes.

 Es muy interesante... pero... quedamos en el mismo tema, eso mismo que me
 has dicho... yo se lo he dicho a ellos, te voy a dar algunas de las
 respuestas:

 -Si Debian es el sistema operativo universal... ¿porque no tiene soporte?
 ¿porque los productos de IBM, Oracle, SAP no tienen soporte?
 -¿Porque usar una fábula o parábola para defender a Debian? ¿No hay nada
 meramente técnico?
 -¿En donde están las contribuciones de Debian? En la página de RedHat,
 Oracle, IBM y SuSE sale en que colaboran.
 -Ese link no es de Debian, es de otro proyecto del que Debian solo se
 beneficia.
 -Puede ser que existan mas beta tester en la comunidad, pero ¿de que me
 sirven si cuando tengo un error no les puedo pagar para que me lo
 solucionen? Eso es soporte por mejor esfuerzo y si yo quiero pagar, no
 puedo...

 Este último para mi es el mas fácil de desarmar... yo tengo reportes de
 fallos en software libre que hemos resuelto en menos de dos días, ahora
 Debian tiene LTS y se puede pagar soporte... ¿pero los demás puntos?

 Para mi es muy importante que las empresas apoyen el software libre... les
 voy a comentar algo que me pasó:

 Resulta de que necesitaba que dokuwiki pudiera imprimir PDFs, la wiki la
 tenía en redhat 5 mientras que la migramos a un power con RedHat7... pues
 resulta que no me imprime los PDFs, porque requiere el paquete
 php-mbstring. Fácil... lo instalo... a pues resulta de que está en un
 repositorio especial de paquetes sólo para subscriptores (1).

 Es de mi conocimiento que el código fuente de CentOS es el mismo que el de
 RedHat, mas aún con la unión de ambos, simple... bajo el paquete fuente de
 php-mbstring... oh sorpresa... no está, resulta 

Problem with name resolution - IPv6 queries are sent before IPv4.

2015-04-29 Thread Rafał Radecki
Hi Everyone :)

I have a quite annoying problem on several ubuntu 12.04 servers. I know
that I should use ubuntu mailing list but I tried that with no success :)
Maybe someone here will be able to help.

When I force a dns query using:

time wget --waitretry=1 http://xxx.yyy -O -

I get (tcpdump  wireshark) the info that an  IPv6 query is first send
to a DNS server from /etc/resolv.conf. The server is only serving IPv4
queries so it responds with an error. Then an IPv4 query is sent. Overall
the process takes ~10 seconds every time so its painful.

I tried to disable IPv6 by:
- adding to sysctl.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
- adding to /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=ipv6.disable=1
- adding to /etc/modprobe.d/blacklist.conf
blacklist ipv6
and then I run update-grub an performed a restart. The server is not using
IPv6 anymore BUT the IPv6 queries are still performed before IPv4 queries
for each dns lookup which I perform with wget/curl or from inside my
node.js application. From my point of view it is quite strange :D I
disabled IPv6 and still see IPv6 queries :D

I also tried to:
- add to /etc/gai.conf
precedence :::0:0/96  100
- add to /etc/resolv.conf
options single-request
- update all packages and kernel (and performed a reboot afterwards).
but it did not help.

I know that I can use wget -4 to force IPv6 but we are running some node.js
apps and for them the problem is the same

Any clues? :D

BR,
Rafal.


Re: Cron

2015-04-29 Thread Alain Rpnpif
Le 28 avril 2015, maderios a écrit :

 Pour Cron, il faut aller dans la boite de dialogue Profile/Schedule/add/ 
 et là tous est paramétrable à coups de clics: date, reboot, délai, 
 console mode, vue du crontab,  etc... C'est archi-simple.

Je comprends mieux le lien avec cron.
Merci.
-- 
Alain Rpnpif

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429082015.43f87500...@chro.home



Debian jessie: DHCP v6 in interfaces does not start dhclient

2015-04-29 Thread Stefan Pietsch
Dear list,

a fresh installation of Debian jessie does not start dhclient for IPv6
at boot.

This is the interfaces file:

~

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
iface eth0 inet6 dhcp

~


Doing a manual ifup eth0 after boot starts dhclient -6.

Can anyone confirm this behaviour?


Regards,
Stefan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150429104502.pl6k0xp4cnob0qnfiwz...@consulting.lsexperts.de



documentation en français sur Systemd

2015-04-29 Thread maderios

Bonjour
L'excellent et vénérable site lea-linux.org propose une documentation en 
français sur Systemd

http://lea-linux.org/documentations/Systemd
--
Maderios

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/5540a24a.9060...@gmail.com



Unable to set LAN Internet connection on Debian Server

2015-04-29 Thread Binod Yadav
Dear all,
We are unable to set LAN Connection in the server and so we are unable to
get online service through Teamviewer for Koha and Dspace software.
Please guide us to solve the problems.
Thanks

-- 
Binod Kumar Yadav
Senior Librarian
B. P. Koirala Institute of Health Sciences
Dharan, Nepal
Phone: +9772552
E-mail: binod.ya...@bpkihs.edu
Mobile:+977-9804060641


Jessie: XFCE4 Desktop background stopped working

2015-04-29 Thread Johann Spies
Since Jessie became stable, there is a flat gray background on the XFCE4
desktop and I cannot change it.  My normal configuration is that XFCE4
should use a list of pictures and change the background regularly
(something that I don't think the other systems can do).  This is not
working anymore.

Even Wallpapoz (my second choice) which in the past could work with XFCE4
would not do it's job.

Now I am using cinnamon + wallpapoz.  I would prefer however to use XFCE4.

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)


Re: Réponse positive d'un cobaye

2015-04-29 Thread Sébastien NOBILI
Le mardi 28 avril 2015 à 21:15, andre_deb...@numericable.fr a écrit :
 Upgrade de Wheezy, c'est pas brillant de mon côté.
 
 Supprimer systemd pour sysvinit ne change rien :
 
 1] Impossible de lancer le bureau TDE.
 Il commence à s'ouvrir avec les icônes clignotantes,
 puis se bloquent... CTRL-ALT-F1 pour revenir au mode console.

Tu aurais dû essayer de démarrer un des bureaux fournis par Debian. TDE n'est
pas dans Debian, le fait qu'il ne fonctionne pas après ta mise-à-jour n'indique
donc pas un problème de Jessie.

 3] Si je remets systemd, j'ai ce message :
 systemd-login failed to start user service : 
 unknow unit.user@0.service

Quel DM utilises-tu ? Est-ce qu'il provient de Debian ou bien d'une autre
source ?

Sébastien

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150429082052.ga14...@sebian.nob900.homeip.net



Re: Réponse positive d'un cobaye

2015-04-29 Thread maderios

On 04/29/2015 12:27 AM, Charles Plessy wrote:

Le Tue, Apr 28, 2015 at 09:15:11PM +0200, andre_deb...@numericable.fr a écrit :


2] Au boot, j'ai ce message :
Super Block write time is in the future dev/sda2
Mon horloge BIOS est à la bonne date  + heure.
# hwclock --systohc
# hwclock --localtime
n'y changent rien et j'ai droit à la vérif de la partition
à chaque boot.


Bonjour,

ce problème est décrit dans les « notes de publication », qu'il est très
fortement conseillé de lire avant de mettre à jour.

https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.fr.html#initramfs-tools-issues

Bonjour
Merci pour ce lien officiel. Tout est dit et cela concerne 
particulièrement Systemd: Lors de la mise à niveau de Wheezy vers 
Jessie, purger les anciens paquets avant le premier redémarrage peut 
être une bonne idée. En particulier, les scripts de démarrage obsolètes 
peuvent causer des problèmes.


--
Maderios

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/5540954c.20...@gmail.com



Re: Fwd: Drivers ATI Debian Jessie 64 Bits

2015-04-29 Thread Fernando Mordi Guerrieri
Muchas gracias, José.

Intenté instalar Mate y KDE siguiendo las instrucciones de Metalhead.

El problema que me queda es que

aptitude install kde

me indica que no encuentra el paquete kde.

Perdonen si les parece una tontería lo que les comento, pero hace ya mucho
tiempo de que no instalo cosas tan importantes en una computadora.

Para probar qué pasaría con mate, lo instalé (sin kde, debido al problema
mencionado más arriba), utilizando:

aptitude install mate-desktop-environment-core

No pasó nada. La pantalla siguió negra :-(


Puse apt-get purge fglrx-driver para probar si el driver libre se
activaría. En ese caso, se inicia el sistema en mode terminal (login:).

¿El paquete con el driver libre se llama simplemente radeon? Si es así,
la cosa es peor, porque con apt-get install radeon, el sistema no lo
encontró en los repositorios.


Mordi



El 28 de abril de 2015, 23:26, Jose Maldonado josemal...@gmail.com
escribió:

 On 28/04/15 14:25, metalhead b93 wrote:

 El día 28 de abril de 2015, 12:53, Jose Maldonado
 josemal...@gmail.com escribió:


 Sobre los mensajes del Xorg son muy claros, el primero es que al parecer
 hacen faltan librerias para que el DRI funcione (lo que te permite
 Direct Rendering y aceleración 3D) no están instaladas o no se
 instalaron por alguna razón (esto me huele a que hiciste la instalación
 con el driver fglrx desde la Web y luego pusiste sin desinstalar el
 fglrx de los repositorios).


  en un principio instalé los drivers que proporciona AMD en ss web,
 como no funcionaron,
 los des instalé y probé con los privados que proporciona Debian en su
 web https://packages.debian.org/jessie/fglrx-driver,
 pero tampoco funcionó.

 se que suelen quedar restos de una aplicación luego de hacer varios
 intentos,
 por lo que hice nuevamente una instalación limpia del sistema para
 eliminar definitivamente cualquier rastro de los drivers
 e instalé nuevamente los drivers pero esta ves de los repositorios con
 aptitude install fglrx-driver,

 es la instalación que tengo actualmente y de las anteriores ya no queda
 nada


 El segundo mensaje es que efectivamente la tarjeta usando el driver que
 tienes reconoce la resolución de tu monitor, por eso aparece esto:

 [16.152] (II) fglrx(0): Modeline 1440x900x60.0  106.50 1440 1520
 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)

 La pregunta del millon que tengo yo es si efectivamente radeon está
 redirigiendo la salida de pantalla a tu monitor. Suena raro pero sucede,
 al menos en mi caso tuve que hacer la redirección porque no funcionaba
 de otra manera.

  eso podría explicar el por qué, GDM daba pantalla en negro,
 pero, por qué no sucede lo mismo al hacer startx deste terminal (la
 pantalla da imagen pero con alerta de error)?
 y por qué no pasa lo mismo con KDM? y por qué todo funciona
 aparentemente bien con MATE
 y  todas las aplicaciones que he iniciado desde MATE?


 Si lei tu msj sobre lo de KDM, y el arranque de MATE y demas entornos.

 Lo que seguramente esta pasando, es que el driver no tiene soporte para
 ciertas operaciones de aceleracion que son necesarias para el entorno de
 GNOME y por ello crashea. ¿Puedes probar Gnome Classic y ver si este
 arranca usando GDM3? Si arranca, ya tendrás tu respuesta.

 Por otro lado son bien conocidos los problemas de ATI + Gnome asi que
 puede que algunos de esos bugs te este causando problemas.

 --
 Dios en su Cielo, todo bien en la Tierra
 -


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: https://lists.debian.org/553ffafd.40...@gmail.com




Re: Is anyone else having trouble sending mail from Jessie?

2015-04-29 Thread Lisi Reisz
On Wednesday 29 April 2015 01:04:47 Bob Holtzman wrote:
 On Tue, Apr 28, 2015 at 09:09:03AM +0100, Lisi Reisz wrote:
  On Tuesday 28 April 2015 01:23:41 John J. Boyer wrote:
   I did not have this problem with Ubuntu.
 
  Ubuntu, of course, is the solution to all ills.
 
  What I don't understand, is why people who think so, don't just use
  Ubuntu.

 How about Marvelous Mark's dictatorial attitude? That's reason enough
 for me.

Yes, but you're not claiming that Ubuntu is marvellous, wonderful and the 
solution to all ills!  Or are you?

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201504290831.06397.lisi.re...@gmail.com



Re: issue with systemd-udev-settle

2015-04-29 Thread Christian Seiler

Am 2015-04-29 07:15, schrieb Matthias Bodenbinder:

systemd-analyze blame:
 56.397s systemd-udev-settle.service


Yeah, that shouldn't happen.


But I am not really happy with the log since I find the following
statement when doing a journalctl -b:

 start of log
Apr 29 06:51:55 xxx systemd-journal[164]: Runtime journal is using
8.0M (max allowed 79.2M, trying to leave 118.8M free of 784.2M
available → current limit 79.2M).



Apr 29 06:52:19 xxx systemd-journal[164]: Forwarding to syslog missed
3819 messages.
Apr 29 06:52:25 xxx systemd-journal[164]: Suppressed 2818 messages
from /system.slice/systemd-udevd.service




Looks like I am missing plenty of udev log messages during the
critical phase of the boot process. Any idea what to do about it?


Ok, so basically you are running into a pathological case of Bug
#762700 [1]. A bit of explanation: journald forwards messages to
syslog by queuing them in the socket for syslog. However, syslog is
only started later in boot (after remote-fs.target, because /var
could be on network filesystems or so) - and thus messages will
only be queued until the kernel reaches a limit, further messages
will be dropped until syslog can actually start and process these
messages. The solution to the aforementioned bug was to increase
the limit from 11 to 513, which covers most cases. However, if at
early boot an uncharacteristic number of messages is generated,
even that limit will be reached.

In this case, because you activated udev debugging, udev will
generate a LOT of messages - and this will exceed the limit, since
udev is early-boot and udevadm-settle.service will have to be done
before syslog is started. (Typically, early-boot shouldn't log
even remotely as much.) Increasing the limit could help here, but
sine this is only for debugging, don't bother, because there's a
much simpler way:

Just use journalctl (without -b) to see all messages (they are
still in RAM in the journal - as per the log you posted, journald
will use up to 80 MiB [2] which is more than enough to keep all
3000 or so messages). Just look through them (there are going to
be a lot of debug messages from udev) and look at the timestamps.
There you'll be able to see where the delay happens - and maybe
you'll have a chance of figuring out, what the problem is. If
it's nothing obvious, just post the last 20 or so udev messages
before the large gap in the timestamps and every udev message
afterwards. If there is no gap and udev is constantly doing
something, take a look at what it's actually doing.

Christian

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762700
[2] The limit depends on the amount of RAM you have, so this is
true on your computer, but not necessarily in general.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/c0e09974329c8f049d64f034faea6...@iwakd.de



Re: apt vs aptitude (was ... Re: non-stable packages infestation)

2015-04-29 Thread Liam O'Toole
On 2015-04-29, Doug dmcgarr...@optonline.net wrote:


 On 04/28/2015 09:51 PM, Marco Segura wrote:
 I think use aptitude or apt is more a personal decision than any other
 thing, however I believe aptitude is more powerful.
 --
 Marco T. Segura M.


 «Cuando naciste, todos reían y solo tu llorabas, asegurate que al
 morir, todos lloren y solo tu rías.»



 Confucio


   Confucius spoke Spanish?

 --doug

To the same extent that he spoke English. :-)

-- 

Liam



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmk174l.jvf.liam.p.otoole@dipsy.tubbynet



Re: jessie x86_64: Rosegarden unusable (possible bug in qt-at-spi?)

2015-04-29 Thread Rusi Mody
On Wednesday, April 29, 2015 at 10:50:03 AM UTC+5:30, Ric Moore wrote:
 On 04/28/2015 11:33 PM, Alexis wrote:
 
  Hi all,
 
  i've just upgraded from wheezy to jessie, and the process was
  impressively trouble-free - thanks to all involved in preparing the
  jessie release!
 
  Now that i'm running jessie, i've encountered a few problems (one of
  which was easily solved, and which i'll mention in a separate message).
 
  One of the most significant is that Rosegarden is unusable due to the
  entire application crashing whenever one tries to use its menu bar. More
  specifically, the crash results in error messages in a terminal such as:
 
  QSpiAccessible::accessibleEvent not handled
 
  Searching the Web for similar messages, this seems to be an issue going
  back a few years, related to qt-at-spi. The usual 'solution' provided
  seems to be to uninstall that package; and whilst removing qt-at-spi
  certainly stops Rosegarden crashing, qt-at-spi is a dependency of the
  gnome metapackage (via gnome-core - gnome-orca - python3-pyatspi).
 
  My question is: Should i report a bug against the rosegarden package, or
  against qt-at-spi?
 
 I have to wonder if you installed another DE like XFCE would you still 
 have the problem? I love musical stuff, but the heavy depend on jack put 
 me off.

Jack is an upfront onetime not very large investment.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/89563b51-bccf-4422-ad5e-bd45ff343...@googlegroups.com



Re: initramfs broken on Jessie upgrade

2015-04-29 Thread Bernhard Schmidt
Don Armstrong d...@debian.org wrote:

Hi Don,

 has anyone observed something similar to
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783620 on their
 Upgrade from Wheezy to Jessie? I'm still trying to figure out what's
 happening, and I don't really know where to look.
 
 I was unable to attach the screenshot so far (mail is accepted but
 never makes it to the BTS), I've put the screenshot here:
 
 http://users.birkenwald.de/~berni/volatile/783620.png

 Could you run something like this on the initrds?

 diff -u ( zcat workinginitrd) ( zcat brokeninitrd);

 It's possible that something has corrupted the initrds in some subtle
 way, or some part of the cpio archive has been truncated which causes as
 issue for the kernel but is ignored by cpio.

lxmhs63:/boot$ diff -u ( zcat initrd.img-3.16.0-4-amd64 ) (
zcat initrd.img-3.16.0-4-amd64.broken )
Binary files /dev/fd/63 and /dev/fd/62 differ

with -a it outputs a lot of difference in binary, I can't figure out
anything there.

Since I could not find anything secret in the initrd I have uploaded
both images

http://users.birkenwald.de/~berni/volatile/783620_initrd_ok
http://users.birkenwald.de/~berni/volatile/783620_initrd_broken

Bernhard


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mhpsrl$11l$2...@ger.gmane.org



Re: initramfs broken on Jessie upgrade

2015-04-29 Thread Bernhard Schmidt
Bernhard Schmidt be...@birkenwald.de wrote:
 Don Armstrong d...@debian.org wrote:

 Hi Don,

 has anyone observed something similar to
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783620 on their
 Upgrade from Wheezy to Jessie? I'm still trying to figure out what's
 happening, and I don't really know where to look.
 
 I was unable to attach the screenshot so far (mail is accepted but
 never makes it to the BTS), I've put the screenshot here:
 
 http://users.birkenwald.de/~berni/volatile/783620.png

 Could you run something like this on the initrds?

 diff -u ( zcat workinginitrd) ( zcat brokeninitrd);

 It's possible that something has corrupted the initrds in some subtle
 way, or some part of the cpio archive has been truncated which causes as
 issue for the kernel but is ignored by cpio.

 lxmhs63:/boot$ diff -u ( zcat initrd.img-3.16.0-4-amd64 ) (
 zcat initrd.img-3.16.0-4-amd64.broken )
 Binary files /dev/fd/63 and /dev/fd/62 differ

 with -a it outputs a lot of difference in binary, I can't figure out
 anything there.

 Since I could not find anything secret in the initrd I have uploaded
 both images

 http://users.birkenwald.de/~berni/volatile/783620_initrd_ok
 http://users.birkenwald.de/~berni/volatile/783620_initrd_broken

It is _not_ caused by the initrd per se, I have just rebooted the system
and edited the grub commands to load the .broken initrd, and it came up
fine.

I will make a snapshot in the broken state the next time it happens,
maybe something else is broken. Except for update-initramfs I did not
run any command, but the system was fully booted on the Wheezy kernel,
maybe something else triggered a fix.

I hope to upgrade a few more systems today, maybe I can reproduce it.

Best Regards,
Bernhard


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mhptd4$g21$1...@ger.gmane.org



Re: Konstigt meddelande från Cron

2015-04-29 Thread Tobias Carlsson
Hej Anders,

Jag har testat med purge också, men som sagt, det är något som fortfarande
spökar.

Mvh
Tobias

Den 29 april 2015 02:03 skrev Anders Jackson anders.jack...@gmail.com:


 Den 28 apr 2015 21:58 skrev Tobias Carlsson janerlingtob...@gmail.com:
 
  Hej!

 Hej

  Jag får ett mejl varje dag från crontab som lyder så här:
 
  Ämnesraden är: Cron root@voyager test -x /usr/sbin/anacron || ( cd /
  run-parts --report /etc/cron.daily )
 
 
  /etc/cron.daily/logrotate:
  error: policyd:14 unknown user 'amavis'
  error: found error in /var/log/amavisd.log , skipping
  error: stat of /var/log/amavisd.log failed: Filen eller katalogen finns
 inte
  run-parts: /etc/cron.daily/logrotate exited with return code 1
 
 
  Till saken hör att jag testade ett paket med program för några månader
 sedan, det la till diverse skräp och jag förstod direkt att jag inte
 ville ha det så. Jag lyckades rensa det mesta, men får alltså detta mejl
 fortfarande.
 
  Amavis förstår jag är ett virusprogram för att kolla mejl till och från
 datorn, jag tror jag avinstallerade amavis korrekt.
 
  Till frågan, jag begriper inte hur jag ska plocka bort den schemalagda
 händelsen. Jag kan inte tyda i vilken fil jag ska kolla. Finns det någon
 vänlig själ som kan ge mig råd?

 Har du rensat bort konfigurationsfilerna med?  Det gör man med operationen
 purge till aptitude.  Du kan även söka i interktiva aptitude ( sök efter
 paketet med /amavis ) och sedan ta bort med kommandot _.

  Kör Debian 7.8.

  Mvh
 
  Tobias
 /Anders



Re: initramfs broken on Jessie upgrade

2015-04-29 Thread Bernhard Schmidt
Michael Biebl bi...@debian.org wrote:

Hi Michael,

 has anyone observed something similar to
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D783620 on their
 Upgrade from Wheezy to Jessie? I'm still trying to figure out what's
 happening, and I don't really know where to look.
=20
 I was unable to attach the screenshot so far (mail is accepted but
 never makes it to the BTS), I've put the screenshot here:
=20
 http://users.birkenwald.de/~berni/volatile/783620.png
=20
 ---snip---
 Dear Maintainer,
=20
 I have a hard time wrapping my head around this bug, feel free to assig=
 n
 somewhere else.
=20
 We have started upgrading some of our production VMs to Jessie. The
 testsystems worked fine, but I have hit the following bug for the secon=
 d
 time on a production VM now.
=20
 - dist-upgrade works flawlessly
 - on first boot into Jessie I get an immediate (1s) kernel-panic (see
   attached screenshot) about being unable to find the root fs.

 Did you run into
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D783297 maybe?

No, no cryptsetup on that box and BUSYBOX=y is set anyway.

Bernhard


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mhpsfo$11l$1...@ger.gmane.org



Re: documentation en français sur Systemd

2015-04-29 Thread Sébastien NOBILI
Le mercredi 29 avril 2015 à 13:21, Sylvain L. Sauvage a écrit :
   Mais il était déjà recommandé d’utiliser 'invoke-rc.d' (sysV ; 
 gère les niveaux d’exécution) ou 'service' (sysV, upstart, 
 openrc ou systemd).

Merci d'aborder ce sujet, c'est justement une des questions que je me pose quant
à mon utilisation à venir de Jessie avec Systemd (actuellement je n'ai migré que
des conteneurs LXC qui sont sur un hôte qui est encore en Wheezy, j'ai donc dû
conserver SysV en attendant la mise-à-jour de l'hôte).

Ma question donc… Est-ce que ces commandes (« invoke-rc.d » et « service »)
existent toujours dans Jessie et permettent une gestion transparente des
services, que SysV ou Systemd soit utilisé dessous ?

Je crois comprendre que oui, je crois aussi comprendre qu'il vaut mieux préférer
« service » à « invoke-rc.d », ce dernier étant plus à destination des systèmes
utilisant SysV.

Si tu (ou quelqu'un d'autre) pouvais confirmer tout ça, sinon je m'en rendrai
compte par moi-même une fois que j'aurai migré ma première machine physique…

Sébastien

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150429115057.gd14...@sebian.nob900.homeip.net



Re: construction d'un .deb pour un noyau avec une config locale

2015-04-29 Thread Erwan David
On Wed, Apr 29, 2015 at 02:11:53PM CEST, humbert.olivie...@free.fr said:
 Bonjour,

[...]

 
 Que me conseillez-vous de faire ?
 
 Remarque annexe : ma méthode de construction est basée sur l'idée de coller 
 le plus possible au noyau Debian et de produire des .deb proprement 
 installables et dés-installables avec les outils apt*. Ceci dit, si il y a 
 une meilleure méthode que celle-là, je veux bien la connaître.
 
 Cordialement,
 Olivier

Ça fait longtemps que je n'ai pas compilé de noyau, mais as-tu regardé 
make-kpkg ?
http://www.parinux.org/content/debian-compiler-son-kernel-sous-debian-avec-make-kpkg


-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429121930.gb21...@rail.eu.org



Re: Contribuciones de Debian al mundo

2015-04-29 Thread Camaleón
El Tue, 28 Apr 2015 13:58:35 -0600, Esteban Monge escribió:

 Hola gente...
 
 Resulta de que he tenido muchas conversaciones sobre lo increíblemente
 maravilloso que es Debian GNU/Linux, del contrato social, de las normas
 para sólo usar software libre y siempre obtengo la misma respuesta:
 ¿Y eso de que me sirve?
 ¿Eso corre Oracle? ¿Si lo hace tiene soporte?

Comprensible, pero cuando alguien hace esa pregunta demuestra su 
ignorancia. Un buen administrador/técnico de sistemas no busca 
aplicaciones con nombre sino solucionar problemas con herramientas (al 
fin y al cabo son ingenieros), se llamen como se llamen esas herramientas 
y tengan el soporte que tengan.

 Y otra gran cantidad de burradas... perdón por la palabra, en parte
 tienen razón, yo trabajo para una empresa grande donde hablar de MySQL o
 PostgresQL es como hablar del chiquito pequeño de Oracle... de un
 juguete... en parte tienen razón, las grandes empresas desean tener
 soporte por parte de un tercero para sus servicios críticos... una
 especie de seguro a quien trasladarle el riesgo. RedHat y SuSE suenan en
 el ambiente... y corriendo riesgos CentOS porque es de RedHat, tal vez
 Oracle Linux porque los vendedores de Oracle son muy necios.

Creo que a menudo se confunde calidad con soporte y ambos conceptos 
pueden ir parejos pero no siempre es así. Es decir, que una aplicación 
tenga un buen soporte detrás no implica que su diseño sea óptimo (véase 
Windows/Microsoft u Oracle DB/Oracle) ni que sea siempre la opción más 
indicada, ya que entran en juego otros factores a tener en cuenta.

 Pero hay una pregunta que siempre hiere mi orgullo porque actualmente no
 tengo el conocimiento o los argumentos para decirles: Ah si es X porque
 A B C D.
 
 La pregunta es:
 ¿Que ha hecho Debian a nivel técnico que sea revolucionario
 últimamente?

¿Y por qué tendría que hacerlo? :-)

De todas formas, ¿te parece poca revolución técnica desarrollar un 
sistema operativo sin apenas recursos? Yo creo que es todo un hito.

 O la afirmación:
 Debian es tecnología de hace 20 años

A lo que habría que responder: que es la que nunca falla.

Pero tampoco estoy de acuerdo con esa afirmación, aunque sí acepto que 
los paquetes de la rama estable siguen una línea conservadora porque eso 
es precisamente lo que se espera de esa versión.
 
 Y acá no se vale responder con que si que los paquetes, que se aporta a
 la seguridad, fallos, etc, la gente quiere escuchar algo cool... como
 systemd, openstack, alguna otra burrada. Alguien una vez me recetó el
 siguiente vídeo: https://www.youtube.com/watch?v=Lqi_RG60ovY

Si la gente quiere algo cool que instale AIX y se lo pasarán genial :-)

 Yo se que esto no es así... día a día yo trabajo con Debian GNU/Linux y
 es un orgullo... una dicha, un placer, pero a nivel empresarial... no
 tengo armas, no tengo argumentos. Es frustrante.
 
 Buscando con el orgullo entre las patas algo me encontré que el mismo
 líder de Debian se encontró en la misma situación, en su momento Zack, y
 posteó esto:
 http://upsilon.cc/~zack/blog/posts/2012/03/
debian_contributions_to_the_linux_kernel/
 
 Pero que diablos todavía queda el sin sabor... yo quiero algo como esto:
 http://community.redhat.com/software/
 
 Para aplicar la del tipo: Tome mae(1) lease ese link... y dejarlos
 callados.
 
 ¿Existe algún recurso que tenga algunas de las grandes contribuciones
 que la gente que hace posible el proyecto Debian realiza?

https://www.debian.org/partners/index.en.html

Pero vaya, creo que el mayor orgullo es poder usar Debian y colaborar, 
algo que no se puede decir de Redhat sin pasar por caja ($$$).

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2015.04.29.13.10...@gmail.com



Re: Jessie : plus de session X sur un HP2133

2015-04-29 Thread Adrien Poupin
Le 28/04/2015 17:49, Bernard Schoenacker a écrit :
 bonjour,

 le serveur xorg est compilé pour un noyau 3.2 et voici la preuve :

 [   286.735] X Protocol Version 11, Revision 0
 [   286.735] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
 [   286.736] Current Operating System: Linux little-hat
 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) i686
 [   286.736] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-686-pae
 root=UUID=fb6f90f3-70b5-4f82-af42-ed655eb33496 ro quiet [   286.737]
 Build Date: 11 February 2015  01:14:26AM


 télécharger le noyau 3.2 amd64 :
 https://packages.debian.org/fr/wheezy/linux-image-3.2.0-4-amd64


 les erreurs et warning :

 grep WW  xorg.log

 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
 [   286.746] (WW) The directory /usr/share/fonts/X11/cyrillic does not 
 exist. 
 [   286.782] (WW) Falling back to old probe method for modesetting 
 [   286.783] (WW) Falling back to old probe method for fbdev 
 [   286.787] (WW) Falling back to old probe method for vesa
 [   287.324] (WW) CHROME(0): [XvMC] XvMC is not supported on this chipset. 

 grep EE  xorg.log

 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
 [   286.783] (EE) open /dev/dri/card0: No such file or directory
 [   286.787] (EE) open /dev/fb0: No such file or directory
 [   286.938] (EE) CHROME(0): [drm] Failed to open DRM device for
  pci::01:00.0: No such file or directory 
 [   287.355] (EE) AIGLX: reverting to software rendering 
 [   287.813] (EE) Server terminated successfully (0). 
   Closing log file.

 slt
 bernard

Re,
Mais du coup c'est bizarre : quand je tape `apt-cache madison
xserver-xorg`, j'obtiens qu'il n'y a que deux versions possibles,
celle-ci et la source. Pourtant, sur une autre machine, j'ai bien ceci :

[ 5.682] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 5.682] Current Operating System: Linux Machine-fixe-bureau
3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64

Et pourtant, toutes deux sont sous Jessie...

--
Adrien.




signature.asc
Description: OpenPGP digital signature


construction d'un .deb pour un noyau avec une config locale

2015-04-29 Thread humbert . olivier . 1
Bonjour,

j'ai l'habitude de reconstruire mon noyau afin d'y intégrer une ou deux options 
non-activées par le noyau de base Debian.

Pour cela, la méthode que j'utilise est la suivante :

0) Préparation
==

  (kernel-package, fakeroot et build-essential sont installés)

  cd '/home/monuser/Bureau/oli/Librazik/04-Constructions 
propres/Reconstructions propres'
  mkdir 'monnoyau/'
  cd 'monnoyau'


1) Récupération des sources avec rustines Debian et déballage
=

  apt-get source linux-source-3.16


2) Mise en place


  cd linux-3.16[TAB]
  cp /boot/config-`uname -r` .config #pour récupérer la config' Debian actuelle
  make oldconfig


3) Sélection des options


  make menuconfig
  pour une configuration en mode ncurses (avec le paquet libncurses5-dev 
installé)

  Je personnalise les 2 options dont j'ai besoin.

  Je donne un nom à ce noyau pour m'y retrouver
- General setup - Local version - append to kernel release - mettre 
-monnoyau
- Puis je sors en enregistrant la configuration

4) Compilation
==

  make -j `nproc` LOCALVERSION= deb-pkg
  qui me crée un beau .deb facilement manipulable avec les outils apt*



Mon problème est que cette méthode fonctionnait jusqu'à la dernière mis à jour 
du noyau (Jessie) mais que maintenant, j'ai une erreur pendant la compilation :

  ...
  ... (zap)...
  ...
  LD [M]  sound/usb/usx2y/snd-usb-usx2y.ko
  BUILDDEB
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
ln: la cible « ./debian/tmp/lib/modules/3.16.7-ckt9-monnoyau/source » n'est pas 
un répertoire
Makefile:1094: recipe for target '_modinst_' failed
make[2]: *** [_modinst_] Error 1
scripts/package/Makefile:90: recipe for target 'deb-pkg' failed
make[1]: *** [deb-pkg] Error 2
Makefile:1203: recipe for target 'deb-pkg' failed
make: *** [deb-pkg] Error 2


si je regarde dans ./debian/tmp/lib/modules/3.16.7-ckt9-monnoyau/ , je n'ai 
effectivement pas de répertoire nommé source, uniquement un répertoire nommé 
kernel et c'est donc certainement pour cela que la construction plante.

Je ne suis pas trop certain de par où il me faut chercher. J'ai utiliser les 
moteurs de recherche avec des morceaux de ce message d'erreur ci-dessus, mais 
n'y comprend pas grand chose et mon intuition me dit qu'il manque simplement 
une règle de création de ce répertoire dans le processus de construction (cad: 
debian/rules) ou quelque chose du genre.

Que me conseillez-vous de faire ?

Remarque annexe : ma méthode de construction est basée sur l'idée de coller 
le plus possible au noyau Debian et de produire des .deb proprement 
installables et dés-installables avec les outils apt*. Ceci dit, si il y a une 
meilleure méthode que celle-là, je veux bien la connaître.

Cordialement,
Olivier

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: 
https://lists.debian.org/177297312.1021806712.1430309513324.javamail.r...@zimbra61-e11.priv.proxad.net



Re: construction d'un .deb pour un noyau avec une config locale

2015-04-29 Thread maderios

On 04/29/2015 02:11 PM, humbert.olivie...@free.fr wrote:

Bonjour,

j'ai l'habitude de reconstruire mon noyau afin d'y intégrer une ou deux options 
non-activées par le noyau de base Debian.

Pour cela, la méthode que j'utilise est la suivante :

0) Préparation
==

   (kernel-package, fakeroot et build-essential sont installés)

   cd '/home/monuser/Bureau/oli/Librazik/04-Constructions 
propres/Reconstructions propres'
   mkdir 'monnoyau/'
   cd 'monnoyau'


1) Récupération des sources avec rustines Debian et déballage
=

   apt-get source linux-source-3.16


2) Mise en place


   cd linux-3.16[TAB]
   cp /boot/config-`uname -r` .config #pour récupérer la config' Debian actuelle
   make oldconfig


3) Sélection des options


   make menuconfig
   pour une configuration en mode ncurses (avec le paquet libncurses5-dev 
installé)

   Je personnalise les 2 options dont j'ai besoin.

   Je donne un nom à ce noyau pour m'y retrouver
 - General setup - Local version - append to kernel release - mettre 
-monnoyau
 - Puis je sors en enregistrant la configuration

4) Compilation
==

   make -j `nproc` LOCALVERSION= deb-pkg
   qui me crée un beau .deb facilement manipulable avec les outils apt*



Mon problème est que cette méthode fonctionnait jusqu'à la dernière mis à jour 
du noyau (Jessie) mais que maintenant, j'ai une erreur pendant la compilation :

   ...
   ... (zap)...
   ...
   LD [M]  sound/usb/usx2y/snd-usb-usx2y.ko
   BUILDDEB
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
ln: la cible « ./debian/tmp/lib/modules/3.16.7-ckt9-monnoyau/source » n'est pas 
un répertoire
Makefile:1094: recipe for target '_modinst_' failed
make[2]: *** [_modinst_] Error 1
scripts/package/Makefile:90: recipe for target 'deb-pkg' failed
make[1]: *** [deb-pkg] Error 2
Makefile:1203: recipe for target 'deb-pkg' failed
make: *** [deb-pkg] Error 2


si je regarde dans ./debian/tmp/lib/modules/3.16.7-ckt9-monnoyau/ , je n'ai effectivement pas de 
répertoire nommé source, uniquement un répertoire nommé kernel et c'est 
donc certainement pour cela que la construction plante.

Je ne suis pas trop certain de par où il me faut chercher. J'ai utiliser les 
moteurs de recherche avec des morceaux de ce message d'erreur ci-dessus, mais 
n'y comprend pas grand chose et mon intuition me dit qu'il manque simplement 
une règle de création de ce répertoire dans le processus de construction (cad: 
debian/rules) ou quelque chose du genre.

Que me conseillez-vous de faire ?

Remarque annexe : ma méthode de construction est basée sur l'idée de coller 
le plus possible au noyau Debian et de produire des .deb proprement installables et 
dés-installables avec les outils apt*. Ceci dit, si il y a une meilleure méthode que 
celle-là, je veux bien la connaître.


Bonjour
Tes commandes me semblent bien compliquées...
Je compile tous mes noyaux de la façon suivante sur Jessie et Sid.
Raison principale: désactiver tout ce qui est inutile et obtenir un vrai 
noyau patché 'real-time' (l'outil 'ketchup' pour télécharger et patcher 
est d'ailleurs génial)

Décompression du paquet source dans /usr/src
Configuration avec make menuconfig
Puis par exemple dans  /usr/src/linux-3.14.38-rt36/ je lance:

make-kpkg --jobs 9  kernel_image --initrd

C'est tout, et le paquet .deb est disponible à la fin dans /usr/src

--
Maderios

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/5540d30e.9080...@gmail.com



Re: Fwd: Drivers ATI Debian Jessie 64 Bits

2015-04-29 Thread Camaleón
El Tue, 28 Apr 2015 13:36:09 -0500, metalhead b93 escribió:

 El día 28 de abril de 2015, 13:07, Camaleón noela...@gmail.com
 escribió:

 ¿Has probado a iniciar gnome-shell o gnome-classical desde KDM?


 si, lo he intentado pero me salta el mismo error, Gnome y Gdm no
 funcioan con los drivers

Pues entonces te tocará esperar a que lo arreglen. 

Pero oye, hay algo que no me cuadra. KDM es sólo un gestor de sesiones, 
dices que funciona pero ¿qué entorno de escritorio cargas cuando 
inicias la sesión con KDM?

 lo siento Camaleon, se fué a tu privado XD

No lo he visto... lo habrá atrapado mi filtro ;-)

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2015.04.29.12.52...@gmail.com



Re: Unable to set LAN Internet connection on Debian Server

2015-04-29 Thread Stephan Seitz

On Wed, Apr 29, 2015 at 10:57:30AM +0100, Darac Marjal wrote:

I think you're going to have to give us more information than it
doesn't work. By default, Debian comes configured to perform a DHCP
request on eth0. This should work for the majority of people, but some


Well, he was speaking of a server, so DHCP may not work. And if it is 
really server hardware then the problem may be missing non-free firmware 
for the NIC.


So we can add the output of dmesg to your list.

Shade and sweet water!

Stephan

--
| Stephan Seitz  E-Mail: s...@fsing.rootsland.net |
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |


signature.asc
Description: Digital signature


Re: documentation en français sur Systemd

2015-04-29 Thread maderios

On 04/29/2015 01:50 PM, Sébastien NOBILI wrote:

Le mercredi 29 avril 2015 à 13:21, Sylvain L. Sauvage a écrit :

   Mais il était déjà recommandé d’utiliser 'invoke-rc.d' (sysV ;
gère les niveaux d’exécution) ou 'service' (sysV, upstart,
openrc ou systemd).


Merci d'aborder ce sujet, c'est justement une des questions que je me pose quant
à mon utilisation à venir de Jessie avec Systemd (actuellement je n'ai migré que
des conteneurs LXC qui sont sur un hôte qui est encore en Wheezy, j'ai donc dû
conserver SysV en attendant la mise-à-jour de l'hôte).

Ma question donc… Est-ce que ces commandes (« invoke-rc.d » et « service »)
existent toujours dans Jessie et permettent une gestion transparente des
services, que SysV ou Systemd soit utilisé dessous ?

Je crois comprendre que oui, je crois aussi comprendre qu'il vaut mieux préférer
« service » à « invoke-rc.d », ce dernier étant plus à destination des systèmes
utilisant SysV.

Bonjour
'invoke-rc.d' et 'service' font partie de sysv-rc et non de systemd. Il 
sont toujours obligatoires dans Jessie. Ensuite, je ne vois pas trop 
leur utilité quand on a choisi systemd. Bizarre que Debian ait conservé 
des morceaux de Sysv, peut-être pour assurer la compatibilité avec le 
choix Sysv par l'utilisateur. J'ai deux serveurs nginx et lighttpd, des 
services dont nfs et mysql, je n'ai jamais utilisé 'invoke-rc.d' et 
'service'. Avec Systemd, c'est Systemctl qui fait tout le travail, même 
si on tape à l'ancienne /etc/init.d/machintruc start

--
Maderios

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/5540cf78.9020...@gmail.com



Re: Help with TestDisk

2015-04-29 Thread German
On Tue, 28 Apr 2015 22:24:50 -0700
Seeker seeker5...@comcast.net wrote:

 
 
 On 4/28/2015 8:03 PM, German wrote:
  On Tue, 28 Apr 2015 19:06:29 -0700
  Seeker seeker5...@comcast.net wrote:
 
 
  On 4/28/2015 6:09 PM, German wrote:
  My USB drive won't mount. I tried TestDisk, but I am not sure what to do 
  and how to procede. Are there any experts out there with TestDisk 
  knowledge? Also, if there are, could anyone tell me what is good site to 
  attach screenshots? Thanks
 
  The testdisk web site has a pretty good sample session so you can see
  what it should look like.
 
  http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step
 
  Later, Seeker
 
  It is still confusing. Here where I got stucked. Maybe someone can chime 
  in. Thanks.
 
  http://forum.cgsecurity.org/phpBB3/help-with-restoring-usb-drive-t4953.html
 
 Right from the beginning this sounds bad
 
 /Input/output error//
 //Failed to read of MFT, mft=17625 count=1 br=-1: Input/output error//
 //Inode is corrupt (5): Input/output error//
 //Index root attribute missing in directory inode 5: Input/output error//
 //Failed to mount '/dev/sdc1': Input/output error/
 
 MFT tables are low level indexes in the NTFS file system, if they can't 
 be read
 that's a big issue.
 
 The screenshot here
 
 http://forum.cgsecurity.org/phpBB3/help-with-restoring-usb-drive-t4953.html#p15748
 
 looks like you already got the partition list and hit 'P' to see a list 
 of files.
 You should be seeing a list of files and directories at that point, none 
 are visible
 in the screenshot, another bad sign.

As you can see, there are two directories, but how to view contents of them I 
have no clue. Enter, P, Right does nothing.
 
 Was this after a deep scan?

After deep scan I got one FAT partition 32 MB in size, what is it and what it 
has to do with NTFS I also have no clue.

 
 Was the partition listed more than once, and if so did you try to view 
 the files in all
 listings for the partition?
 
 If the cradle for the goflex has SATA connectors that plug into the HDD 
 like the one
 shown here...
 
 http://www.amazon.com/Seagate-GoFlex-Desktop-Adapter-PCI-Express/dp/B00HWZ6OYC
 
 My next step, would be to plug the goflex in to the SATA power and data 
 cable in a
 desktop system. When plugged in on USB more is done in software, the 
 SATA controller
 on the motherboard is better able to recover from errors if there is 
 more going on than
   just filesystem corruption.

Unfortunately I don't have now any desktop computer and I am not sure if that's 
possible re-assamble this GoFlex drive.
 
 I've dealt with a few of the goflex drives and had to shave the plastic 
 on the SATA power
 and data cable with a razor blade to get them to fit into the connectors 
 on the drive without
   taking the enclosure apart.
 
 Typically at this point I would run the Gnome disk utility, and do a 
 full smart test on the
 hard drive. If the drive already has errors recorded that the disk 
 utility doesn't like it may
   give you an indication of this when you run it. You can also view a 
 list of Smart data in the
 disk utility. Pending remaps and uncorrectable errors are a couple of 
 the more significant
 things to look at.
 
 Sector remaps only happen on a write, so a handful of pending I would 
 not consider an
 automatic failure, if you are getting into the neighborhood of ten or 
 more I would question
 the reliability of the drive.
 
 This could be done from the command line with smartmon tools, but I'm 
 not familiar with
 it's usage.
 
 If the disk physically looks good, then I would try testdisk again.
 
 If you can get access to the files, you want to have another drive ready 
 to copy the files
 to or enough free space on the drive you are running from to hold the files.
 

As I said before, I got two directories shown. What they are and how to view 
the content of them I have no clue. Please enlighten me.


 If you get an indication that the disk is failing, then the question of 
 how important the data
 is to you comes into play, poking at a disk that is physically failing 
 could reduce the chance
 of a professional data recovery service being able to recover the files.

I think that physically ok. I just was installing Lubuntu to my computer and 
forgot to unplug this USB drive and installer probed it and done to it 
something nasty.

 
 If testdisk still doesn't show you and files and directories, then I 
 would try photorec.
 
 Photorec doesn't do well with files that are fragmented, and if it can 
 recognize files may give
 you numbers for names, instead of the actual file names, it does have a 
 brute force option
 that will try to piece the file chains together and match the files to 
 names. The brute force
 option has to be enabled before doing the scan.
 
 http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step
 
 If you use the brute force option be prepared for it to take days to 
 analyze the partition.
 
 Later, Seeker
 
 
 
 
Thank you for the effort 

Re: ttty , donde?

2015-04-29 Thread Camaleón
El Tue, 28 Apr 2015 16:05:48 -0300, walter escribió:

 Buenas
   estoy intentando adaptar Debian 8.0 , a mi uso personal y en la
 empresa en la que trabajo...
 bien entre esas cosas. esta:
   en debian 6  y 7   si queria modificar los ttyX  entraba en
 /etc/inittab...
 editaba y perfecto...
 pero ahora... no encuentro. asumo que sera por  lo del Systemd
 alguno me puede orientar??

Ah amijo... ahora ya no usas Debian sino systemd 453.26.32.15.12.a ;-PP

systemd for Administrators, Part XVI
http://0pointer.de/blog/projects/serial-console.html

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2015.04.29.12.54...@gmail.com



Re: Fwd: Drivers ATI Debian Jessie 64 Bits

2015-04-29 Thread metalhead b93
El día 29 de abril de 2015, 7:52, Camaleón noela...@gmail.com escribió:
 El Tue, 28 Apr 2015 13:36:09 -0500, metalhead b93 escribió:

 El día 28 de abril de 2015, 13:07, Camaleón noela...@gmail.com
 escribió:

 ¿Has probado a iniciar gnome-shell o gnome-classical desde KDM?


 si, lo he intentado pero me salta el mismo error, Gnome y Gdm no
 funcioan con los drivers

 Pues entonces te tocará esperar a que lo arreglen.


si, tocará esperar, por ahora seguiré usando los drivers libres

tienes alguna idea de cómo poner una resolución  de pantalla decente
usando los drivers libres?



 Pero oye, hay algo que no me cuadra. KDM es sólo un gestor de sesiones,
 dices que funciona pero ¿qué entorno de escritorio cargas cuando
 inicias la sesión con KDM?

con los drivers privados solo se puede iniciar sesión con Mate

lo de los gestores de sesión tambien me tiene confundido
KDM y GDM solo son gestores de sesión, no entiendo por qué GDM es
afectado negativamente por los drivers y KDM no

algo que tampoco me cuadra es que Gnome Classic al igual que Gnome
Shell tampoco funciona con los drivers pero MATE si funciona

la nueva versión de Gnome funciona bien con los drivers en otras
distribuciones Gnu/Linux

parece que el problema se limita a Debian
ya que tiene completamente liada la aceleración 3D,
no solo con los drivers privados, si no también con los drivers libres
pues aunque con drivers privado se puede trabajar en Mate con con
algunas aplicaciones basicas que requieren aceleración 3D, lo cierto
es que al intentar usar todo el rendimiento con aplicaciones más
exigentes, estas aplicaciones fallan


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAMFJo=XZvxV6Tpepz-Osh_nAeFcQmiyGxnRRZs0bXEO=ncc...@mail.gmail.com



rss2email upgrade woes

2015-04-29 Thread Reco
Dear list.

I've upgraded one of my VPS to Jessie recently. The upgrade itself
went smoothly, more-or-less (disregarding inability to boot
xz-compressed kernel due to ancient pvgrub).

Yet there's that rss2mail package I used for years that's troubling me
now.

First, the packaging quality. The rss2email package now depends on both
python2.7 and python3.4 at the same time, which is kind of… strange. Not
that I cannot tolerate multiple versions of python installed, but still.

Second (but not last), is that rss2email has the ability to send
plain-text e-mails, which I find invaluable. rss2email in Jessie
retained that ability, but now it applies horrible text wrapping, which
renders text nearly unreadable *and* breaks urls.


First problem is easily solved as I rebuild rss2email package anyway
(upstream has a braindead idea of sending e-mails with UTC timezone).
After all, replacing python-xdg → python3-xdg in Depends field is not that
hard.

It's the second problem that I need to be advised on. I played with
'body-width' configuration setting, and it does not seem to do anything
useful at all. And rss2email does not seem to have another don't format
the text dammit knob :(


As for the alternatives I tried feed2imap and I cannot view it as a
suitable replacement - it seems to be able to send html e-mails only.

Anything else they give in Debian main archive does not seem to be able
to cope with a simple task of transforming RSS feeds to plain-text
e-mails.

Reco


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429102304.ga22...@d1696.int.rdtex.ru



Re: Unable to set LAN Internet connection on Debian Server

2015-04-29 Thread Darac Marjal
On Wed, Apr 29, 2015 at 03:12:44PM +0545, Binod Yadav wrote:
Dear all,
We are unable to set LAN Connection in the server and so we are unable to
get online service through Teamviewer for Koha and Dspace software.
Please guide us to solve the problems.

Hello,

I think you're going to have to give us more information than it
doesn't work. By default, Debian comes configured to perform a DHCP
request on eth0. This should work for the majority of people, but some
people have more complex requirements so the above may not work. In
fact, I seem to remember that if the installer doesn't receive a DHCP
response, it will prompt for manual configuration. Might you have got
that wrong?

So, in order for us to help you, I think we'll want the following:

 * What model of network card(s) are installed?
 * What is the topology of your network (e.g. is this a home computer
   connected to an ISPs router, is it an institutional computer
   connected to a network that you don't control (in which case you
   should tell us how the network administrator has told you to
   connect), is it an air-gapped network between a few computers which
   you control, etc etc)
 * What is the content of /etc/network/interfaces?
 * What is the output of (as root) 'ifdown eth0 ; ifup -v eth0'
   (assuming that eth0 is your network interface - on a computer with
   one ethernet port, it will be)?

The above may lead to further questions, though.

Thanks
--
Binod Kumar Yadav
Senior Librarian
B. P. Koirala Institute of Health Sciences
Dharan, Nepal
Phone: +9772552
E-mail: [1]binod.ya...@bpkihs.edu
Mobile:+977-9804060641
 
 References
 
Visible links
1. mailto:binod.ya...@bpkihs.edu


signature.asc
Description: Digital signature


Re: Is anyone else having trouble sending mail from Jessie?

2015-04-29 Thread Richard Hector
On 29/04/15 19:31, Lisi Reisz wrote:
 On Wednesday 29 April 2015 01:04:47 Bob Holtzman wrote:
 On Tue, Apr 28, 2015 at 09:09:03AM +0100, Lisi Reisz wrote:
 On Tuesday 28 April 2015 01:23:41 John J. Boyer wrote:
 I did not have this problem with Ubuntu.
 
 Ubuntu, of course, is the solution to all ills.
 
 What I don't understand, is why people who think so, don't just
 use Ubuntu.
 
 How about Marvelous Mark's dictatorial attitude? That's reason
 enough for me.
 
 Yes, but you're not claiming that Ubuntu is marvellous, wonderful
 and the solution to all ills!  Or are you?

I don't think the OP did either. He just provided a point of comparison.

Richard


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5540b016.80...@walnut.gen.nz



Re: J'ai besoin d'aide pour choisir l'architecture de Debian Jessie !

2015-04-29 Thread Johnny B

Cédric le plus simple est de passer ces commandes :

uname -a

et

ioreg -l -p IODeviceTree -l |grep firmware-abi

qui vont te donner les infos précises sur quel archi tu tournes

@+



--
Je top post désolé mais on s'égare, il faut que Cédric check d'abord sa 
conf OS et son modèle de CPU ensuite on pourra spéculer ;)




On 04/29/2015 05:24 PM, Samy Mezani wrote:

Bonjour,

Le 29/04/2015 15:51, Cédric Cola a écrit :

il me répond i386

Mémoire : 16 Go 1600 MHz DDR3


Comment pourrais-tu exploiter tes 16 Go de RAM avec un système 32 bits ?
Vérifie sur ton système, ça me paraît bizarre qu'à notre époque un tel
ordinateur soit en i386. Ou alors c'est une révolution... ;-)

Samy



--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/5540fad2.1070...@gmail.com



Re: testing or stable

2015-04-29 Thread Chris Bannister
On Mon, Apr 27, 2015 at 02:37:43PM -0400, The Wanderer wrote:
 The experimental repository has no codename, at least not that I know
 of. It is used entirely for packages that developers want to make

My understanding is that it is affectionally referred to as 'rc-buggy'

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429153817.GE28736@tal



Re: Fwd: Drivers ATI Debian Jessie 64 Bits

2015-04-29 Thread metalhead b93
El día 29 de abril de 2015, 9:18, Camaleón noela...@gmail.com escribió:
 El Wed, 29 Apr 2015 09:00:59 -0500, metalhead b93 escribió:

 El día 29 de abril de 2015, 8:39, Camaleón noela...@gmail.com
 escribió:

 (...)

 tienes alguna idea de cómo poner una resolución  de pantalla decente
 usando los drivers libres?

 Sí, tienes varias opciones pero antes manda de nuevo el archivo
 /var/log/
 Xorg.0.log para que veamos qué resoluciones nativas reconoce el driver
 radeon.


 este es el xorg.0.log de los drivers libres
 http://pastebin.com/rnqXJubB;

 Veamos, no está cargando el driver libre (radeon) sino el
 patatero (VESA), no me extraña que notes lento el entorno.

 [15.021] (II) [KMS] drm report modesetting isn't supported.
 [15.021] (EE) open /dev/dri/card0: No such file or directory
 [15.021] (WW) Falling back to old probe method for modesetting
 [15.021] (EE) open /dev/dri/card0: No such file or directory

 Seguramente se deba a que has instalado ya varios drivers (el de ATI, el
 fglxr de Debian y ahora has habilitado el radeon) y se habrá hecho un
 lío. Verifica que tienes activado el KMS porque sin el KMS el radeon NO
 se carga:

 https://wiki.debian.org/KernelModesetting#AMD.2FATI_GfxCards

no loc creo
justo no me gusta ese tipo de problemas
por lo que hice una instalación limpia del sistema para evitarlos

no queda rastro de los drivers anteriores
actualmente tengo solo los libres que instala Debian por defecto


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAMFJo=W0Sxm=ape1zaxd2aamq0pfuj0ss3dpnihzlhowjxi...@mail.gmail.com



Re: instalacion de debian8 con wifi

2015-04-29 Thread Aradenatorix Veckhom Vacelaevus
El 29 de abril de 2015, 11:50 a. m., Juan Fco Guil Vazquez
erj...@gmail.com escribió:
 Hola
 Estoy pensando instalar Debian8 con xfce  en mi portátil.
 La cuestión es:
 En el asistente de configuración te detecta el Wifi?

¿por que no descargas un live cd y lo averiguas por ti mismo? Digo,
que digas que lo quieres instalar en tu portatil no nos dice gran
cosa. No sabemos que modelo es, que hardware usa para wifi o si has
tenido problemas con el controlador o algo que sea de utilidad.
Anímate a probar y si falla nos cuentas.

Suerte


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caacnk7yaot19w+0msfdyi7acbzvgjwfptvqzjcoy163kgjf...@mail.gmail.com



Re: passage de ce soir de wheezy à jessie

2015-04-29 Thread Nicolas

Le 29-04-2015 18:40, maderios a écrit :

On 04/29/2015 05:36 PM, Nicolas wrote:

Bon ben j'ai passé mon serveur dédié en jessie hier soir. Tout est ok,
zéro soucis (sauf spammassassin qui n'avait pas redémarré mais un coup
de systemctl start spamassassin et c'est reparti. Passage à systemd 
en

douceur et sans accroc.

Cela ne suffit pas, il faut faire
systemctl enable spamassassin
sinon il ne démarrera pas au prochain boot
--
Maderios


J'ai vérifié avant reboot : il était déjà dans l'état enable...

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/22ef5a82953677632272570fd0150...@tycho.fr



Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso

2015-04-29 Thread Avinash Sonawane
A new development:

Now I have managed to create a separate FAT partition using fdisk
which is holding the
 firmware files. The reason why earlier I couldn't is because I used
default block values from fdisk.

Start partition at block more that size of iso - #debian IRC

Now installer to begins smoothly but it says no firmware was found
though I can see the damn firmware directory in newly created FAT
partition.

Any pointers?
-- 
Avinash Sonawane (RootKea)
PICT, Pune
http://www.rootkea.wordpress.com


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caj9bsw_fqpj41lwpkps0wvyjfcnaxo08s2xk7sdutn-o+dk...@mail.gmail.com



Question: Why do you dist-upgrade?

2015-04-29 Thread Tim K
For me, and I think anyone with a sensibly laid out system, it's so much
less trouble and time to reinstall. I can only really think of one reason
to dist-upgrade, and that's if the system is remote (and a very good reason
it is). I'm wondering why some of you dist-upgrade ... do you just like it
that way? A habit?

I keep my /home and my data (/share) and /var on a separate disk and only
the system goes on / (an ssd). Still have to painfully deal with outdated
configuration wrt the desktop environments, so I just make a new (fake)
user to see what the new layout is.

The cons are that firstly, it's very time consuming and much more
complicated. Second, and perhaps most importantly, you're going to be left
with older versions of things when a paradigm has changed. I dist-upgraded
for the longest time and was hence completely unaware of grub2 for several
years, since the maintainers of it wisely did not upgrade me to it! I can
see the same happening with init systems being switched about. I guess if
you care and read the release notes carefully this won't happen though. But
Debian was so reliable (I found) that it was pretty much a fire and forget
operation with each stable release.

What's your reason?


Tim Kelley


Re: Fwd: Drivers ATI Debian Jessie 64 Bits

2015-04-29 Thread Camaleón
El Wed, 29 Apr 2015 11:17:12 -0500, metalhead b93 escribió:

 El día 29 de abril de 2015, 9:18, Camaleón noela...@gmail.com
 escribió:

(...)

 Veamos, no está cargando el driver libre (radeon) sino el patatero
 (VESA), no me extraña que notes lento el entorno.

 [15.021] (II) [KMS] drm report modesetting isn't supported.
 [15.021] (EE) open /dev/dri/card0: No such file or directory [   
 15.021] (WW) Falling back to old probe method for modesetting [   
 15.021] (EE) open /dev/dri/card0: No such file or directory

 Seguramente se deba a que has instalado ya varios drivers (el de ATI,
 el fglxr de Debian y ahora has habilitado el radeon) y se habrá hecho
 un lío. Verifica que tienes activado el KMS porque sin el KMS el radeon
 NO se carga:

 https://wiki.debian.org/KernelModesetting#AMD.2FATI_GfxCards

 no loc creo justo no me gusta ese tipo de problemas por lo que hice una
 instalación limpia del sistema para evitarlos

Oye, que los registros no mienten ;-)

[15.049] (EE) Screen 0 deleted because of no matching config section.
[15.049] (II) UnloadModule: radeon
[15.049] (EE) Screen 0 deleted because of no matching config section.
[15.049] (II) UnloadModule: modesetting
[15.049] (EE) Screen 0 deleted because of no matching config section.
 
 no queda rastro de los drivers anteriores actualmente tengo solo los
 libres que instala Debian por defecto

No importa, a veces pensamos que algo debe suceder porque sí cuando no es 
así, así que mejor comprueba que el KMS esté activado como te dije antes. 
Ah, y renombra cualquier archivo de configuración que tengas xorg.conf 
para que no entre en conflicto con el driver radeon.

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2015.04.29.16.30...@gmail.com



Re: passage de ce soir de wheezy à jessie

2015-04-29 Thread maderios

On 04/29/2015 05:36 PM, Nicolas wrote:

Bon ben j'ai passé mon serveur dédié en jessie hier soir. Tout est ok,
zéro soucis (sauf spammassassin qui n'avait pas redémarré mais un coup
de systemctl start spamassassin et c'est reparti. Passage à systemd en
douceur et sans accroc.

Cela ne suffit pas, il faut faire
systemctl enable spamassassin
sinon il ne démarrera pas au prochain boot
--
Maderios

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/55410987.4070...@gmail.com



Re: Question: Why do you dist-upgrade?

2015-04-29 Thread Reco
 Hi.

On Wed, 29 Apr 2015 11:11:52 -0500
Tim K kelle...@gmail.com wrote:

 For me, and I think anyone with a sensibly laid out system, it's so much
 less trouble and time to reinstall. 

While the amount of trouble is subjective, the install/upgrade time is
objective. And it's the last one that you estimated wrong.

An debian-installer, being a complex frontend to debootstrap, install
packages and configures them. It also does disks partitioning, and the
whole process requires two reboots (to installer and to a new system).

An upgrade process installs the packages, configures them, but does not
do partitioning. Also requires a single reboot that can be postponed
indefinitely.

An upgrade is simply faster.


 I can only really think of one reason
 to dist-upgrade, and that's if the system is remote (and a very good reason
 it is). I'm wondering why some of you dist-upgrade ... do you just like it
 that way? A habit?

Upgrade can be done via SSH. Upgrade retains all my packages installed.
The most important thing is - upgrade does its best in handling all
those customizations in /etc.

Re-install *can* be done via SSH (although not by default), but that's
it.


 I keep my /home and my data (/share) and /var on a separate disk and only
 the system goes on / (an ssd). 

/var contents will do you little good without /etc in most server
environments.


 Still have to painfully deal with outdated
 configuration wrt the desktop environments, so I just make a new (fake)
 user to see what the new layout is.

I stopped using DEs back in 2007, so I can not comment on this.


 The cons are that firstly, it's very time consuming and much more
 complicated.

See above.


 Second, and perhaps most importantly, you're going to be left
 with older versions of things when a paradigm has changed. 

If software works *and* is supported by Debian - it's good software,
and there's nothing to worry about.

If software works *but* is no longer supported by Debian - it's
obsolete software, and replacing it with something is a part of
post-upgrade process.

If software does not work after the upgrade - it's a bug.

So if upgrade leaves you with old familiar software - it's a good thing.


 I dist-upgraded
 for the longest time and was hence completely unaware of grub2 for several
 years, since the maintainers of it wisely did not upgrade me to it!

And that's a perfect example of good software as all those years your
system booted successfully.

I mean - grub was able to boot your system.
Grub2 is able to boot your system.
What's the key difference?


 I can
 see the same happening with init systems being switched about. 

You'll get systemd as a result of 'apt-get dist-upgrade' so there's
nothing to worry about.


 I guess if
 you care and read the release notes carefully this won't happen though.

And reading release notes *before* the upgrade is considered essential
regardless of whenever you're re-installing or upgrading :)

Reco


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150429201310.1e1c982f125ac98cf1a9d...@gmail.com



Re: J'ai besoin d'aide pour choisir l'architecture de Debian Jessie !

2015-04-29 Thread Samy Mezani

Bonjour,

Le 29/04/2015 15:51, Cédric Cola a écrit :

il me répond i386

Mémoire : 16 Go 1600 MHz DDR3


Comment pourrais-tu exploiter tes 16 Go de RAM avec un système 32 bits ?
Vérifie sur ton système, ça me paraît bizarre qu'à notre époque un tel 
ordinateur soit en i386. Ou alors c'est une révolution... ;-)


Samy

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/5540f7b0.6030...@wanadoo.fr



Re: passage de ce soir de wheezy à jessie

2015-04-29 Thread Charles Plessy
Le Wed, Apr 29, 2015 at 05:36:40PM +0200, Nicolas a écrit :
 
 Le seul truc un peu bizarre fut que mes fichiers de conf des virtualhosts
 (apache2) ne se terminant pas par .conf, apache refusait de les prendre en
 compte (alors que tout fonctionnait jusque là). J'ai donc ajouté l'extension
 .conf et toc...

[tousse...] [tousse...] notes de publication...

https://www.debian.org/releases/stable/amd64/release-notes/ch-information.fr.html#apache-httpd-incomat

  « La gestion des fichiers de configuration a également changé dans le paquet
Debian. En particulier, tous les fichiers de configuration et les sites 
doivent
maintenant se terminer par « .conf » pour être interprétés par défaut. Cette
modification remplace également l'usage actuel de /etc/apache2/conf.d/. »

Amicalement,

--
Charles Plessy
Tsurumi, Kanagawa, Japon

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429155536.gg20...@falafel.plessy.net



Re: Screen resolution in Jessie

2015-04-29 Thread Michael Biebl
Am 29.04.2015 um 18:28 schrieb Gary Roach:
 I just upgraded to Jessie with no problems. I use a 24 16x9 monitor.
 With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
 ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
 mode. All of my circles are now elipses. Is there a solution to this
 problem. Is there a different driver out there. I'm using the on board
 video card  on my Intel DP55KG mother board. I am certain that I didn't
 have this problem with Wheezy.

Does /var/log/Xorg.0.log contain any warnings or errors?
I assume you use the intel driver? Is xserver-xorg-video-intel
correctly installed?

What does xrandr -q say?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Re: documentation en français sur Systemd

2015-04-29 Thread Sylvain L. Sauvage
Le mercredi 29 avril 2015, 14:32:56 maderios a écrit :
[…]
 Ensuite, je ne vois pas trop leur utilité quand on a choisi
 systemd.

  service fonctionne avec *tous* les systèmes d’init : sysV, 
systemd, upstart ou openrc.
  C’est toujours une bonne idée d’avoir une commande générique, 
au moins pour les actions de base.

  Vendredi est férié, donc demain, c’est trolldi : sur Debian, 
service est © successivement de Red Hat, Canonical et 
M. Stapelberg (Debian), qui veut se lancer sur « c’est la faute 
à Red Hat » ou « Ubuntu, c’est rien que des voleurs » ou « tout 
ça c’est le syndrome NIH (Red Hat → systemd, Canonical → 
upstart) » ?

-- 
 Sylvain Sauvage

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/1669239.UZEpPll5Uh@earendil



[Debian 8.0 Installation] Synaptics touchpad not working in Graphical Install

2015-04-29 Thread Avinash Sonawane
3 Days back when I tried to install debian 7.8.0 on my laptop, at the
time of install my mouse touchpad was working just fine. But when I
tried to install Debian 8.0 in graphical way touchpad isn't working at
all.

Does that mean Jessie lacks the Synaptics driver in default install?
Will I be able to make the touchpad work after installing Debian?

-- 
Avinash Sonawane (RootKea)
PICT, Pune
http://www.rootkea.wordpress.com


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caj9bsw8n4xuas6hlebarx3++7voypsjmwdgebtxwyjrsrra...@mail.gmail.com



Re: Bluetooth mouse problems on Jessie

2015-04-29 Thread Brad Rogers
On Wed, 29 Apr 2015 17:23:08 +0200
Johann Spies johann.sp...@gmail.com wrote:

Hello Johann,

On 29 April 2015 at 11:40, Brad Rogers b...@fineby.me.uk wrote:
 As Lisi says, you've not eliminated the mouse as the problem (in fact,
 you've probably done the opposite).
Correct!  Thanks for opening my eyes for that  possibility.

You're welcome.

Yes, I have tested it with other batteries also.

Do you have access to another mouse you could try?

BTW;  No need to Cc me, as I'm subbed to the list and will see your
replies.

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent
Keep your drink just give em the money
U  Ur Hand - P!nk


pgpLFyjE6i3s8.pgp
Description: OpenPGP digital signature


Re: passage de ce soir de wheezy à jessie

2015-04-29 Thread Nicolas

Le 29-04-2015 17:55, Charles Plessy a écrit :

Le Wed, Apr 29, 2015 at 05:36:40PM +0200, Nicolas a écrit :


Le seul truc un peu bizarre fut que mes fichiers de conf des 
virtualhosts
(apache2) ne se terminant pas par .conf, apache refusait de les 
prendre en
compte (alors que tout fonctionnait jusque là). J'ai donc ajouté 
l'extension

.conf et toc...


[tousse...] [tousse...] notes de publication...

https://www.debian.org/releases/stable/amd64/release-notes/ch-information.fr.html#apache-httpd-incomat

  « La gestion des fichiers de configuration a également changé dans le 
paquet

Debian. En particulier, tous les fichiers de configuration et les
sites doivent
maintenant se terminer par « .conf » pour être interprétés par 
défaut. Cette
modification remplace également l'usage actuel de 
/etc/apache2/conf.d/. »


Et hop, j'avais sauté des sections. Ça m'apprendra à lire en 
diagonale...

Merci en tout cas.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/266fa3d72da2614ae1f736ea8d622...@tycho.fr



Re: instalacion de debian8 con wifi

2015-04-29 Thread Miguel Matos
El día 29 de abril de 2015, 12:20, Juan Fco Guil Vazquez
erj...@gmail.com escribió:
 Hola
 Estoy pensando instalar Debian8 con xfce  en mi portatil.
 La cuestión es:
 En el asistente de configuración te detecta el Wifi?

 Gracias!


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: https://lists.debian.org/55410bcf.2070...@gmail.com


Por los poquitos datos que nos das, la probabilidad de que sí es
cercana al 20%. Si tu wifi es una Atheros o compatible, puede ser 99%
eficaz. Yo lo hice con Debian/Ubuntu, y sí las reconoce.
Prueba pasar lo que dice el comando lshw -C network con root y te
podemos dar más pistas.


-- 
Ayuda para hacer preguntas inteligentes: http://is.gd/NJIwRz


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CALEvJmSBqMEsUekm27yENsM=elxvntcr_++uxoc5hytqorf...@mail.gmail.com



Re: instalacion de debian8 con wifi

2015-04-29 Thread Camaleón
El Wed, 29 Apr 2015 18:50:23 +0200, Juan Fco Guil Vazquez escribió:

 Hola Estoy pensando instalar Debian8 con xfce  en mi portatil.
 La cuestión es:
 En el asistente de configuración te detecta el Wifi?

Sí, esa opción ya debería estar disponible.

Funcionará bien si la tarjeta wifi no necesita drivers o firmware 
adicional, en cuyo caso tendrás que instalarlo para que el instalador la 
pueda usar y configurar.

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2015.04.29.17.06...@gmail.com



Re: passage de ce soir de wheezy à jessie

2015-04-29 Thread Nicolas

Le 26-04-2015 11:08, maderios a écrit :

On 04/26/2015 10:43 AM, Jean-Marc wrote:


Rectification :
https://bits.debian.org/2015/04/jessie-released.html

Salut
L'annonce de la  publication en français
https://www.debian.org/News/2015/20150426
détails
https://identi.ca/debian
--
Maderios


Bon ben j'ai passé mon serveur dédié en jessie hier soir. Tout est ok, 
zéro soucis (sauf spammassassin qui n'avait pas redémarré mais un coup 
de systemctl start spamassassin et c'est reparti. Passage à systemd en 
douceur et sans accroc.


Le seul truc un peu bizarre fut que mes fichiers de conf des 
virtualhosts (apache2) ne se terminant pas par .conf, apache refusait de 
les prendre en compte (alors que tout fonctionnait jusque là). J'ai donc 
ajouté l'extension .conf et toc...


Vive Jessie et systemd donc.

PS : je viens aussi de remplacer sysvinit par systemd sur mon portable 
et ça fonctionne impec. D'où ma question : peut-on virer sans souci 
toute trace de sysvinit ? Si oui comment procéderiez-vous ?


N. Roudninski

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/d351682da2b985babd007d8fd5898...@tycho.fr



Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso

2015-04-29 Thread Avinash Sonawane
On Wed, Apr 29, 2015 at 9:50 PM, David Wright deb...@lionunicorn.co.uk wrote:

 But my workaround (to reduce bandwidth as much as I could) would be to
 install with firmware-netinst as far as the first reboot and then use
 the DVD you've got from then on.

But then won't Debian will be downloading all the packages from
internet while installing from netinst image? Can I use the existing
amd64 dvd1 iso then? (instead of downloading packages extract from the
dvd1 iso)

But then just to have a single 10MB firmware file is it really cool to
download the whole netinst image?

-- 
Avinash Sonawane (RootKea)
PICT, Pune
http://www.rootkea.wordpress.com


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caj9bsw-1qwxbjqhnnyvwbg9lxct05zgwoyzwadx92a0hdkd...@mail.gmail.com



Screen resolution in Jessie

2015-04-29 Thread Gary Roach
I just upgraded to Jessie with no problems. I use a 24 16x9 monitor. 
With wheezy, there was a 1920 x 1080? mode that gave the correct aspect 
ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200 
mode. All of my circles are now elipses. Is there a solution to this 
problem. Is there a different driver out there. I'm using the on board 
video card  on my Intel DP55KG mother board. I am certain that I didn't 
have this problem with Wheezy.


Gary R.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/554106b6.10...@verizon.net



Re: Screen resolution in Jessie

2015-04-29 Thread Frank Miles
On Wed, 29 Apr 2015 18:30:03 +0200, Gary Roach wrote:

 I just upgraded to Jessie with no problems. I use a 24 16x9 monitor. 
 With wheezy, there was a 1920 x 1080? mode that gave the correct aspect 
 ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200 
 mode. All of my circles are now elipses. Is there a solution to this 
 problem. Is there a different driver out there. I'm using the on board 
 video card  on my Intel DP55KG mother board. I am certain that I didn't 
 have this problem with Wheezy.
 
 Gary R.

My 1920 x 1200 is working fine using the on-chip Intel video system and Jessie.
Never tried the x1080.

Can you alter the configuration using xrandr ?

HTH..


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mhr2dg$spg$1...@dont-email.me



Re: J'ai besoin d'aide pour choisir l'architecture de Debian Jessie !

2015-04-29 Thread Johnny B
Je top post désolé mais on s'égare, il faut que Cédric check d'abord sa 
conf OS et son modèle de CPU ensuite on pourra spéculer ;)




On 04/29/2015 05:24 PM, Samy Mezani wrote:

Bonjour,

Le 29/04/2015 15:51, Cédric Cola a écrit :

il me répond i386

Mémoire : 16 Go 1600 MHz DDR3


Comment pourrais-tu exploiter tes 16 Go de RAM avec un système 32 bits ?
Vérifie sur ton système, ça me paraît bizarre qu'à notre époque un tel 
ordinateur soit en i386. Ou alors c'est une révolution... ;-)


Samy



--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/5540f844.7020...@gmail.com



Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso

2015-04-29 Thread Avinash Sonawane
On Wed, Apr 29, 2015 at 9:18 PM, Curt cu...@free.fr wrote:
 On 2015-04-29, Avinash Sonawane root...@gmail.com wrote:

 I'm not sure which iso you downloaded. If it was the netinst version
 from https://www.debian.org/releases/jessie/debian-installer/
 take a look further down the page where there's a panel with a red
 cross. Here you can get the netinst iso with firmware included within
 it. bcm43xx-0.fw 96224 Jun 15  2014 is in there.

 I downloaded 
 http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-dvd/debian-8.0.0-amd64-DVD-1.iso
 whose integrity I checked using sha512sum, sha256sum and md5sum. I
 also verifies gpg signatures for the same. So I am pretty sure I have
 the official Debian 8.0 dvd1 iso.

 I am stuck at how to create a separate partition to hold the firmware
 files as mentioned in Debian Installation guide.


 Yes, you have the official iso, but in order to obviate the difficulties
 you're encountering, David is saying you have the option of downloading the
 unofficial iso with the firmware included (that way you're off and
 running to the races without further ado).

 http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.0.0/amd64/iso-cd/firmware-8.0.0-amd64-netinst.iso

 I am sorry if I came as rude.

Yes. I am aware of the debian images with firmware included. The
reason why I don't want to use that I think they are netinstall images
only. And being a student in developing country I am afraid I can't
manage the internet needed for the installation. So I would be
thankful if you could suggest away to have a firmware work with amd64
dvd1 iso (which I got from a friend)

Thank you.

Avinash Sonawane (RootKea)
PICT, Pune
http://www.rootkea.wordpress.com


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caj9bsw-g+uhqvzu8x873unas7zl4z2qe1w7xpmcdzvzvuyq...@mail.gmail.com



Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso

2015-04-29 Thread David Wright
Quoting Avinash Sonawane (root...@gmail.com):
 On Wed, Apr 29, 2015 at 9:18 PM, Curt cu...@free.fr wrote:
  On 2015-04-29, Avinash Sonawane root...@gmail.com wrote:
 
  I'm not sure which iso you downloaded. If it was the netinst version
  from https://www.debian.org/releases/jessie/debian-installer/
  take a look further down the page where there's a panel with a red
  cross. Here you can get the netinst iso with firmware included within
  it. bcm43xx-0.fw 96224 Jun 15  2014 is in there.
 
  I downloaded 
  http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-dvd/debian-8.0.0-amd64-DVD-1.iso
  whose integrity I checked using sha512sum, sha256sum and md5sum. I
  also verifies gpg signatures for the same. So I am pretty sure I have
  the official Debian 8.0 dvd1 iso.
 
  I am stuck at how to create a separate partition to hold the firmware
  files as mentioned in Debian Installation guide.
 
 
  Yes, you have the official iso, but in order to obviate the difficulties
  you're encountering, David is saying you have the option of downloading the
  unofficial iso with the firmware included (that way you're off and
  running to the races without further ado).
 
  http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.0.0/amd64/iso-cd/firmware-8.0.0-amd64-netinst.iso
 
  I am sorry if I came as rude.

Not in the slightest rude.

I'm sorry I can't help you get the firmware onto the stick; it's
something I will need to do in the future but just haven't had time to
figure it out (so I was going to watch for replies to this thread).

But my workaround (to reduce bandwidth as much as I could) would be to
install with firmware-netinst as far as the first reboot and then use
the DVD you've got from then on.

I quite understand if even that amount of bandwidth is too much for you.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429162021.GA9838@alum



Re: issue with systemd-udev-settle

2015-04-29 Thread Matthias Bodenbinder

Am 29.04.2015 um 10:32 schrieb Christian Seiler:

Just use journalctl (without -b) to see all messages (they are
still in RAM in the journal - as per the log you posted, journald
will use up to 80 MiB [2] which is more than enough to keep all
3000 or so messages). Just look through them (there are going to
be a lot of debug messages from udev) and look at the timestamps.
There you'll be able to see where the delay happens - and maybe
you'll have a chance of figuring out, what the problem is. If
it's nothing obvious, just post the last 20 or so udev messages
before the large gap in the timestamps and every udev message
afterwards. If there is no gap and udev is constantly doing
something, take a look at what it's actually doing.


No way. Just using journalctl makes no difference:

Apr 29 18:45:08 xxx systemd-journal[170]: Forwarding to syslog missed 
3819 messages.
Apr 29 18:45:14 xxx systemd-journal[170]: Suppressed 2818 messages from 
/system.slice/systemd-udevd.service


And this is exactly the time period where I would expect the issue to 
pop up.


Any other idea?
Matthias



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/mhr2a3$vu4$1...@ger.gmane.org



Re: Jessie and screensaver on lid-close

2015-04-29 Thread Gary Roach

On 04/28/2015 05:27 AM, Francesco Ariis wrote:

Hello,
 I recently upgraded my laptop from wheezy to jessie, and everything
is going smoothly. I run a very simple system, with X but no DE.

I would like to lock the screen when the lid of my laptop is closed
(by running xscreensaver, which I currently have installed, if possible,
but any other method will do).

How to do it? After searching a bit I suspect I have to mess with systemd
configuration files, but I am not sure which one to edit.


This doesn't answer you question exactly but I would like to point out 
that screen savers are useless with lcd / led screens. They were 
originally meant to protect CRT's from burn in when the electron beam 
stayed in the same place too long. I don't use them anymore. So unless 
you just like the pretty pictures, turn them off.


Gary R


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55410209.7030...@verizon.net



Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso

2015-04-29 Thread Curt
On 2015-04-29, Avinash Sonawane root...@gmail.com wrote:

 I'm not sure which iso you downloaded. If it was the netinst version
 from https://www.debian.org/releases/jessie/debian-installer/
 take a look further down the page where there's a panel with a red
 cross. Here you can get the netinst iso with firmware included within
 it. bcm43xx-0.fw 96224 Jun 15  2014 is in there.

 I downloaded 
 http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-dvd/debian-8.0.0-amd64-DVD-1.iso
 whose integrity I checked using sha512sum, sha256sum and md5sum. I
 also verifies gpg signatures for the same. So I am pretty sure I have
 the official Debian 8.0 dvd1 iso.

 I am stuck at how to create a separate partition to hold the firmware
 files as mentioned in Debian Installation guide.


Yes, you have the official iso, but in order to obviate the difficulties
you're encountering, David is saying you have the option of downloading the
unofficial iso with the firmware included (that way you're off and
running to the races without further ado).

http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.0.0/amd64/iso-cd/firmware-8.0.0-amd64-netinst.iso




-- 



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmk1vag.2bf.cu...@einstein.electron.org



Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso

2015-04-29 Thread Curt
On 2015-04-29, Curt cu...@free.fr wrote:


 Yes, you have the official iso, but in order to obviate the difficulties
 you're encountering, David is saying you have the option of downloading the
 unofficial iso with the firmware included (that way you're off and
 running to the races without further ado).

 http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.0.0/amd64/iso-cd/firmware-8.0.0-amd64-netinst.iso


Is it just me or is the option to install an alternative desktop
environment missing from the advanced options of both amd64 netinstall
isos ( official and firmware-unofficial)?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmk20r3.2bf.cu...@einstein.electron.org



Re: issue with systemd-udev-settle

2015-04-29 Thread Matthias Bodenbinder

Am 29.04.2015 um 15:28 schrieb Michael Biebl:

Am 29.04.2015 um 10:32 schrieb Christian Seiler:

Am 2015-04-29 07:15, schrieb Matthias Bodenbinder:

systemd-analyze blame:
  56.397s systemd-udev-settle.service


Yeah, that shouldn't happen.


Matthias, do you have any custom udev rules in /etc/udev/rules.d/?
Is this an upgraded or freshly installed system?





This is a clean install. I tried to upgrade from wheezy but could not 
boot afterwards. boot eror init not found and I was left with and 
initramd shell. I could not fix that so I made a clean install.


/etc/udev/rules.d/ has only one file:

xxx - root - /etc/udev/rules.d
17# cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, 
ATTR{address}==00:24:1d:d6:df:5f, ATTR{dev_id}==0x0, 
ATTR{type}==1, KERNEL==eth*, NAME=eth0


Matthias


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/mhr1i8$f41$1...@ger.gmane.org



Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso

2015-04-29 Thread Curt
On 2015-04-29, Avinash Sonawane root...@gmail.com wrote:
 On Wed, Apr 29, 2015 at 9:50 PM, David Wright deb...@lionunicorn.co.uk 
 wrote:

 But then won't Debian will be downloading all the packages from
 internet while installing from netinst image? Can I use the existing
 amd64 dvd1 iso then? (instead of downloading packages extract from the
 dvd1 iso)

Won't the dvd1 iso install to your usb stick without the firmware for your
wireless card?  Then, let's say, if you've another usb stick with the
firmware on it, you'd copy that firmware to the correct location 

/lib/firmware/brcm/bcm43xx-0.fw
/lib/firmware/brcm/bcm43xx_hdr-0.fw
/usr/share/bug/firmware-brcm80211/presubj
/usr/share/doc/firmware-brcm80211/changelog.gz
/usr/share/doc/firmware-brcm80211/copyright

At which point you'd be able to install via a package manager the relevant 
package
so that the package manager knows about it and updates it normally.

 But then just to have a single 10MB firmware file is it really cool to
 download the whole netinst image?



-- 



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmk23a8.2bf.cu...@einstein.electron.org



Re: documentation en français sur Systemd

2015-04-29 Thread Sylvain L. Sauvage
Le mercredi 29 avril 2015, 13:50:57 Sébastien NOBILI a écrit :
Mais il était déjà recommandé d’utiliser 'invoke-rc.d'
  (sysV ; gère les niveaux d’exécution) ou 'service' (sysV,
  upstart, openrc ou systemd).
[…]
 je crois aussi comprendre qu'il
 vaut mieux préférer « service » à « invoke-rc.d », ce dernier
 étant plus à destination des systèmes utilisant SysV.

  C’est écrit dans le texte que tu citais :
— invoke-rc.d : sysV et obéit aux contraintes (« gère ») des 
niveaux d’exécution ;
— service : fonctionne avec sysV, upstart, openrc ou systemd.

  Donc, oui, 'service' est plus générique et fonctionne très 
bien avec systemd (et upstart et openrc et sysV).
  Il est donc préférable de l’utiliser, surtout si on risque de 
tomber sur une machine avec un autre système d’init que le sien.
En plus, c’est plus facile à taper que invoke-rc.d (dont, 
franchement, personne ne se sert jamais, à part les DD dans les 
scripts d’installation).
  Et il a évidemment moins de possibilités que sysctl puisqu’il 
n’a que l’option '--status-all' et que toutes les actions 
individuelles standard (start / stop / reload / …) sont 
repassées au script init.d ou à systemctl.

-- 
 Sylvain Sauvage

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/2677709.hsszMuPIWg@earendil



Re: Bluetooth mouse problems on Jessie

2015-04-29 Thread Lisi Reisz
On Wednesday 29 April 2015 16:23:08 Johann Spies wrote:
 On 29 April 2015 at 11:40, Brad Rogers b...@fineby.me.uk wrote:
  On Wed, 29 Apr 2015 09:10:25 +0200
  Johann Spies johann.sp...@gmail.com wrote:
 
  Hello Johann,
 
  mouse which I have been using for years.  I get the message
  successfully added but failed to connect.
 
  As Lisi says, you've not eliminated the mouse as the problem (in fact,
  you've probably done the opposite).

 Correct!  Thanks for opening my eyes for that  possibility.

  Try the simple things first;  Batteries failing, perhaps?

 Yes, I have tested it with other batteries also.

Can you use the mouse with another operating system or distro?  Can it be made 
to work anywhere?  Presumably bluetooth mice die sometimes as do other 
rodents.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201504291718.18747.lisi.re...@gmail.com



Re: [Debian 8.0 Installation] Synaptics touchpad not working in Graphical Install

2015-04-29 Thread German
On Wed, 29 Apr 2015 21:53:52 +0530
Avinash Sonawane root...@gmail.com wrote:

 3 Days back when I tried to install debian 7.8.0 on my laptop, at the
 time of install my mouse touchpad was working just fine. But when I
 tried to install Debian 8.0 in graphical way touchpad isn't working at
 all.
 
 Does that mean Jessie lacks the Synaptics driver in default install?
 Will I be able to make the touchpad work after installing Debian?
 

Yes, mine wasn't working either in graphical mode. I did text install
and after rebooting my touchpad was working. Go ahead and install in
text mode.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429122728.5f667...@asterius.asterius.net



Jessie: Problem switching from graphical to text-based login

2015-04-29 Thread Reiner Bühl

Hi,

I have installed a new system with Debian Jessie and Xfce. When I try
to disable lightdm via systemctl, X11 is stopped as expected, but
after the next restart, the graphical login is back. I do not want to
uninstall lightdm, but just disable the automatic start of X11 and
lightdm. What is the way to do this with systemd?

systemctl disable lightdm.service seems to not do it.

Best regards,
Reiner


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: 
https://lists.debian.org/ae4bf034ab4efc27cc318cb89c2cd...@mail.buehl.net



Re: ATA resets with Intel 8/C220 and HGST drive

2015-04-29 Thread Selim T . Erdoğan
On Mon, Apr 27, 2015 at 03:03:58PM +0200, Nicolas George wrote:
 Summary: I had annoying resets of the SATA bus with a 8 Series/C220 Series
 Chipset controller and a HGST Travelstar 7K1000 drive. I recently managed to
 stop them and as far as I currently know I am satisfied; I write this mail
 in the hope that it may be useful for anyone having similar issues. If you
 do not have that issue and you are not a developer interested in fixing the
 issue more permanently, you can stop reading right now.
 
 Here are the details. The computer is a Zotac ZBox ID91 nettop with a
 proprietary motherboard, and, as stated above, a Travelstar 7K1000 hard
 drive (a 7200 RPM 2.5, an unusual beast). It was installed around June
 2014, and I noticed the problems some time later, they probably started
 right away.
 
 The distribution was a Debian Jessie (testing) with the packaged kernel,
 probably linux-image-3.14-1-amd64:amd64 at the time; the issue was not fixed
 by upgrades.
 
 The possibly relevant hardware information are these:
 
 CPU: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz
 
 CPU:
 product: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz
 
 description: SATA controller
 product: 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI 
 mode]
 vendor: Intel Corporation
 physical id: 1f.2
 bus info: pci@:00:1f.2
 version: 05
 width: 32 bits
 clock: 66MHz
 capabilities: storage msi pm ahci_1.0 bus_master cap_list
 configuration: driver=ahci latency=0
 resources: irq:42 ioport:f0b0(size=8) ioport:f0a0(size=4) ioport:f090(size=8) 
 ioport:f080(size=4) ioport:f060(size=32) memory:f7d1a000-f7d1a7ff
 
 description: ATA Disk
 product: HGST HTS721010A9
 physical id: 0.0.0
 bus info: scsi@1:0.0.0
 logical name: /dev/sda
 version: A3J0
 serial: [REMOVED]
 size: 931GiB (1TB)
 capabilities: partitioned partitioned:dos
 configuration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 
 signature=d3079a6d
 
 The resets happened a few times a day (this computer was is kept on for more
 than a day and suspend is not used), mostly when the disk was in heavy use,
 sometimes as early as during the boot; there was a few good days when they
 did not happen. They were annoying because they caused a few seconds freeze
 of anything reading from disk; AFAIK they never resulted in data corruption.
 
 The corresponding kernel messages look like this:
 
 [  337.466498] ata2: EH complete
 [  367.251032] ata2.00: exception Emask 0x10 SAct 0x8 SErr 0x400100 
 action 0x6 frozen
 [  367.251041] ata2.00: irq_stat 0x0800, interface fatal error
 [  367.251046] ata2: SError: { UnrecovData Handshk }
 [  367.251053] ata2.00: failed command: WRITE FPDMA QUEUED
 [  367.251063] ata2.00: cmd 61/08:98:68:3b:40/00:00:6b:00:00/40 tag 19 ncq 
 4096 out
 [  367.251063]  res 50/00:08:68:3b:40/00:00:6b:00:00/40 Emask 0x10 
 (ATA bus error)
 [  367.251068] ata2.00: status: { DRDY }
 [  367.251075] ata2: hard resetting link
 [  367.571128] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
 [  367.577660] ata2.00: configured for UDMA/133
 [  367.577676] ata2: EH complete
 [  409.772730] ata2: limiting SATA link speed to 3.0 Gbps
 [  409.772735] ata2.00: exception Emask 0x10 SAct 0x3fe00 SErr 0x400100 
 action 0x6 frozen
 [  409.772736] ata2.00: irq_stat 0x0800, interface fatal error
 [  409.772737] ata2: SError: { UnrecovData Handshk }
 [  409.772739] ata2.00: failed command: READ FPDMA QUEUED
 [  409.772742] ata2.00: cmd 60/08:48:78:09:41/00:00:01:00:00/40 tag 9 ncq 
 4096 in
 [  409.772742]  res 50/00:28:e0:a3:04/00:00:02:00:00/40 Emask 0x10 
 (ATA bus error)
 [  409.772743] ata2.00: status: { DRDY }
 snip seven similar failed command...DRDY blocks
 [  409.772773] ata2.00: failed command: WRITE FPDMA QUEUED
 [  409.772776] ata2.00: cmd 61/28:88:e0:a3:04/00:00:02:00:00/40 tag 17 ncq 
 20480 out
 [  409.772776]  res 50/00:28:e0:a3:04/00:00:02:00:00/40 Emask 0x10 
 (ATA bus error)
 [  409.772777] ata2.00: status: { DRDY }
 [  409.772779] ata2: hard resetting link
 [  410.092732] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
 [  410.097670] ata2.00: configured for UDMA/133
 
 Last week, hinted by the penultimate line, I tried to lower the speed of the
 SATA link permanently, and it worked. I did this by adding
 libata.force=2:3.0Gbps to the kernel command line (configured using
 /etc/default/grub).
 
 Since then, no reset happened; I am confident that seven days without them
 are not a coincidence.

I had a similar experience with a Sony Vaio VGN-NS140 laptop (from 2008)
when its hard drive died a few years ago.  

The replacement drives (new or used) that I tried would work for a 
little while, usually long enough to install Debian, but would get 
corrupted within a few hours.  I would see messages like yours above, 
about going to a lower SATA speed.  From 3.0Gbps to 1.5 Gbps in my case.  
But that wouldn't keep the drive from getting corrupted.  (Maybe it 
was trying to auto-negotiate back to a higher 

Synaptic package?

2015-04-29 Thread German
I just installed new Jessie on my new laptop. I assume it is Synaptic
touchpad, but can be wrong. How at all to tell by whom touchpad was
made? Anyway, I think it is possible to make my touchpad more
responsive. Firmware? Drivers? Clue me in. Thanks. 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429133950.57f51...@asterius.asterius.net



Debian 8 Display corruption and previous desktop revelation during login (nouveau)

2015-04-29 Thread Nick Booker
Hi.

I'm getting display corruption during login on the latest Debian 8
(Jessie), installed from scratch on an emptied hard disk.

I have the MATE desktop environment, and am using the nouveau graphics
driver.

This didn't happen with my previous OSes (Debian Wheezy, Linux Mint 17.1
or Parabola GNU/Linux bleeding edge).

If I boot my machine from cold, having just plugged in:

Boot messages progress to lightdm fine
All looks normal while interacting with lightdm
After entering my login details, before showing the usual MATE desktop
elements and wallpaper, the screen is corrupted for a couple of seconds.
During that period it is green with various coloured (mostly purple)
dots in seemingly-random places.

If I then reboot or shut down and start back up without unplugging and
waiting for the motherboard to power down, during my next login, rather
than the green with purple dots, I get a collage of bits of my previous
session's windows (even some long closed before shutdown) displayed.

Please can anyone help me to debug and fix this issue?

I haven't filed a bug because I don't know where the issue lies at the
moment (kernel/systemd/xf86-video-nouveau/...?)

I don't mind poking around source code if necessary with a bit of
hand-holding.

Selected details from lspci, glxinfo and dmesg in the following paste:

http://paste.debian.net/169967/

Thanks,

Nick

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: semi-OT: Problemas varios con ubuntu

2015-04-29 Thread Jose Maldonado

On 28/04/15 18:50, Miguel Matos wrote:

saludos al grupo. Tengo instalado el ubuntu versión 14.04 LTS, pero,
presento 2 problemas: vamos por partes...
1) Quiero instalarme el nuevo entorno de escritorio LXQT, pero, cuando
escojo instalarlo por synaptic, me dice que tiene muchas dependencias
que no va a instalar, ¡y se 'rompe'! ¿qué proponen que haga?
y 2)no puedo hacer que muestre la imagen con el cable HDMI, aunque
parece reconocer la conexión. Incluso, instalando arandr, no hace
nada. ¿Qué tendré de malo?
Quiero acotar que ya presenté esto a la lista de usuarios de Ubuntu
Venezuela; pero, estoy en espera a la aprobación del moderador desde
hace 6 días, y si espero, yo creo que sale antes la versión 17.04 y me
tocará actualizar sin poder usarlo. Por ello recurro a ustedes. Y
quizás, saber cómo hacerlo en la versión 8 de Debian (aún no la
instalo, pero, quiero estar preparado).



Tengo que decir algunas cosas:

1.- Me entero que esta es la nueva lista de Ubuntu.

2.- De las listas de Ubuntu, la de Venezuela no es la única, ni la mejor 
tampoco, eso ya lo estás viviendo (y yo tambien lo vivi en su momento), 
pero recuerda qe hay una española (o para quienes hablen el español), 
foros y demas para hacer la pregunta en el lugar apropiado.


3.- Tu firma dice:

--
Ayuda para hacer preguntas inteligentes: http://is.gd/NJIwRz

Comienza a poner en practica lo que dice.


Lo de Synaptic es mas que claro. Y sobre el HDMI, no se porque me suena 
a ATI. :/


--
Dios en su Cielo, todo bien en la Tierra
-


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55413296.80...@gmail.com



Re: semi-OT: Problemas varios con ubuntu

2015-04-29 Thread Camaleón
El Wed, 29 Apr 2015 14:27:27 -0430, Miguel Matos escribió:

 El día 29 de abril de 2015, 9:02, Camaleón noela...@gmail.com
 escribió:

(...)

 Synaptic no siempre es la mejor opción. Usa apt o aptitude y manda la
 salida del comando. Las dependencias están ahí por algo, no las
 subestimes.

 y 2)no puedo hacer que muestre la imagen con el cable HDMI, aunque
 parece reconocer la conexión. Incluso, instalando arandr, no hace
 nada. ¿Qué tendré de malo?

 Que usas aplicaciones gráficas :-)

 Usa xrandr para ver si te reconoce la saluda digital e intenta forzar
 que la use y por cierto ¿qué drivers gráficos has instalado?

(...)

 y yo ya imaginaba que me pediría esa opción, por eso me preparé para
 eso:
 
 Para lo 1ro:
 root@miguel-LT:/home/miguel# add-apt-repository
 ppa:lubuntu-dev/lubuntu-daily
  Daily builds for LXDE and others components of Lubuntu Más información:
 https://launchpad.net/~lubuntu-dev/+archive/ubuntu/lubuntu-daily Pulse
 [Intro] para continuar o ctrl-c para cancelar
 
 OK root@miguel-LT:/home/miguel# add-apt-repository ppa:gilir/q-project
  Q!
  Más información: https://launchpad.net/~gilir/+archive/ubuntu/q-project
 Pulse [Intro] para continuar o ctrl-c para cancelar

Algo me dice que esos repositorios no son oficiales de Ubuntu, ten mucho 
cuidado siempre que añadas paquetería de terceros.

Por cierto, por si te sirve:

Install LXQt on Ubuntu 14.04 
http://linuxhalwa.blogspot.com.es/2014/05/install-lxqt-on-ubuntu-1404.html

How to install LXQt DE in Ubuntu 14.04 LTS?
http://askubuntu.com/questions/464741/how-to-install-lxqt-de-in-
ubuntu-14-04-lts

Dicen que no es muy estable, pero bueno...

 OK root@miguel-LT:/home/miguel# apt-get update
 
 ...
 Pero, al momento de hacer  esto: apt-get install lxqt-metapackage
 lxqt-panel openbox

(...)

 Los siguientes paquetes tienen dependencias incumplidas:
  lxqt-metapackage : Depende: lxqt-session pero no va a instalarse

(...)

El paquete importante (la dependencia fuerte) es lxqt-session. Puedes 
investigar con más detalle por qué no se va a instalar (aptitude why-not 
lxqt-session) o intentar instalarlo manualmente (si salta alguna otra 
dependencia, para).

  lxqt-panel : Depende: libkf5guiaddons5 (= 4.96.0) pero no va a
  instalarse
   Depende: libkf5windowsystem5 (= 4.100.0) pero no va a
   instalarse Depende: liblxqt0 pero no va a instalarse
   Depende: lxqt-globalkeys pero no va a instalarse

(...)

Y aquí lo mismo, hay 4 dependencias fuertes que tendrás que ver por qué 
no se instalan automáticamente (aptitude why-not...) y en su caso 
intentar hacerlo manualmente  (si salta alguna otra dependencia, para).

 Para lo 2do:

¿Tarjeta gráfica y driver en uso?

 miguel@miguel-LT:~$ xrandr 
 Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis
 y axis) 331mm x 207mm
1280x800   60.0 +   50.0 1024x768   60.0*
800x60060.3 56.2 640x48059.9
(...)
 HDMI1 connected 1024x768+0+0 (normal left inverted right x axis y axis)
 747mm x 420mm
1360x768   60.0 +
1920x1080  60.0 50.0 59.9 24.0 24.0 1920x1080i   
 60.1 50.0 60.0 1280x720   60.0 50.0 59.9
1440x576i  50.1 1024x768   75.1 70.1 60.0*
1440x480i  60.1 60.1 800x60072.2 75.0 60.3   
 56.2 720x57650.0 720x48060.0 59.9 640x480   
75.0 72.8 60.0 59.9 720x40070.1

(...)

Detecta dos pantallas conectadas: la interna del portátil 
(predeterminada) y la HDMI. Bien, puedes intentar lo siguiente:

1/ Forzar la salida HDMI desde las teclas de función del portátil para 
conmutar entre una pantalla u otra (algunos ordenadores no permiten tener 
las dos activadas al tiempo).

2/ Forzar la salida HDMI con xrandr, por ejemplo:

xrandr --output LVDS1 --off --output HDMI1 --auto

(ojo, prepárate para perder el entorno gráfico porque con xrandr pasan 
cosas... inesperadas :-))

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2015.04.29.19.52...@gmail.com



Re: instalacion de debian8 con wifi

2015-04-29 Thread Camaleón
El Wed, 29 Apr 2015 21:22:31 +0200, Juan Fco Guil Vazquez escribió:

 El 29/04/15 a las 19:06, Camaleón escribió:
 El Wed, 29 Apr 2015 18:50:23 +0200, Juan Fco Guil Vazquez escribió:

 Hola Estoy pensando instalar Debian8 con xfce  en mi portatil.
 La cuestión es:
 En el asistente de configuración te detecta el Wifi?
 Sí, esa opción ya debería estar disponible.

 Funcionará bien si la tarjeta wifi no necesita drivers o firmware
 adicional, en cuyo caso tendrás que instalarlo para que el instalador
 la pueda usar y configurar.


 Hola Gracias por las contestaciones. Es eso exactamente que quería
 saber. Es que esta tarde he instalado en una maquina virtual con
 debian8, y no he visto tal opción wifi.
 Por eso lo preguntaba.

¿Una máquina virtual? 

Dependiendo del tipo sistema de virtualización que uses los adaptadores 
de red wifi se tratan como adaptadores de tipo puente (p. ej. en 
VirtualBox), quizá sea eso, que no lo haya detectado o se haya 
configurado en el host correctamente.

 Por cierto, me ha dado muy buena impresión
 
 Hay que retocarlo poco el aspecto, pero tiene muy buena pinta sobre todo
 porque veo que no necesita muchos recursos y la estabilidad.
 
 Gracias por las respuestas!!

Me alegra que te guste el ratoncito :-)

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2015.04.29.19.59...@gmail.com



Re: Jessie and screensaver on lid-close

2015-04-29 Thread Gary Roach

On 04/29/2015 10:30 AM, Frederic Marchal wrote:

On Wednesday 29 April 2015 09:08:41 Gary Roach wrote:

On 04/28/2015 05:27 AM, Francesco Ariis wrote:

Hello,

  I recently upgraded my laptop from wheezy to jessie, and everything

is going smoothly. I run a very simple system, with X but no DE.

I would like to lock the screen when the lid of my laptop is closed
(by running xscreensaver, which I currently have installed, if possible,
but any other method will do).

How to do it? After searching a bit I suspect I have to mess with systemd
configuration files, but I am not sure which one to edit.

This doesn't answer you question exactly but I would like to point out
that screen savers are useless with lcd / led screens. They were
originally meant to protect CRT's from burn in when the electron beam
stayed in the same place too long. I don't use them anymore. So unless
you just like the pretty pictures, turn them off.

Not quite right. I have seen LCD screens where the login screen was burned in
the screen leaving a clearly visible and annoying shadow at all time.

So, it isn't a good idea to leave the same display on the screen for a long
period of time even if LCD screens are more robust than CRT monitors and some
people claim it is possible to get rid of the shadow.

Moreover, it makes sense to have a screen saver to turn the display and
backlight off. It saves a lot of energy on a laptop.

Frederic


I bow to your experience but, for the life of me, I can't see how this 
could happen with the physics that is involved. I suppose that the 
liquid crystal material could deteriorate with time but I thought that 
the stuff was pretty indestructible.


As follow on: Getting rid of the screen saver turns the screen power off 
sooner.


Gary R.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55412615.7040...@verizon.net



Re: Screen resolution in Jessie

2015-04-29 Thread Gary Roach

On 04/29/2015 09:47 AM, Michael Biebl wrote:

Am 29.04.2015 um 18:28 schrieb Gary Roach:

I just upgraded to Jessie with no problems. I use a 24 16x9 monitor.
With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
mode. All of my circles are now elipses. Is there a solution to this
problem. Is there a different driver out there. I'm using the on board
video card  on my Intel DP55KG mother board. I am certain that I didn't
have this problem with Wheezy.

Does /var/log/Xorg.0.log contain any warnings or errors?
I assume you use the intel driver? Is xserver-xorg-video-intel
correctly installed?

What does xrandr -q say?



OK xrandr -v -q gives:

xrandr program version   1.4.2
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
   1600x1200  0.00*
   1280x1024  0.00
   1280x960   0.00
   1024x768   0.00
   800x6000.00
   640x4800.00

No 1920 x ? shows up. I re-installed xserver-xorg-video-intel using 
Aptitude. Nothing changed.


There were no warnings or errors in the Xorg.0.log but I did find the 
following:

//(I noticed that it got the screen size right, 520, 320 mm)

[27.140] (II) VESA(0): Total Memory: 256 64KB banks (16384kB)
[27.140] (II) VESA(0): default monitor: Using hsync range of 
30.00-83.00 kHz
[27.140] (II) VESA(0): default monitor: Using vrefresh range of 
50.00-61.00 Hz
[27.140] (II) VESA(0): default monitor: Using maximum pixel clock 
of 175.00 MHz

[27.140] (WW) VESA(0): Unable to estimate virtual size
[27.140] (II) VESA(0): Not using built-in mode 1920x1440 (no mode 
of this name)
[27.140] (II) VESA(0): Not using built-in mode 1856x1392 (no mode 
of this name)
[27.140] (II) VESA(0): Not using built-in mode 1792x1344 (no mode 
of this name)
[27.140] (II) VESA(0): Not using built-in mode 1400x1050 (no mode 
of this name)
[27.141] (II) VESA(0): Not using built-in mode 1152x864 (no mode 
of this name)
[27.141] (II) VESA(0): Not using built-in mode 720x400 (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode 640x350 (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode 512x384 (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode 320x240 (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode 320x200 (no mode of 
this name)

[27.141] (--) VESA(0): Virtual size is 1600x1200 (pitch 1600)
[27.141] (**) VESA(0): *Built-in mode 1600x1200
[27.141] (**) VESA(0): *Built-in mode 1280x1024
[27.141] (**) VESA(0): *Built-in mode 1280x960
[27.141] (**) VESA(0): *Built-in mode 1024x768
[27.141] (**) VESA(0): *Built-in mode 800x600
[27.141] (**) VESA(0): *Built-in mode 640x480
*[27.141] (**) VESA(0): Display dimensions: (520, 320) mm*
[27.141] (**) VESA(0): DPI set to (78, 95)
[27.141] (**) VESA(0): Using Shadow Framebuffer
[27.141] (II) Loading sub module shadow
[27.141] (II) LoadModule: shadow
[27.141] (II) Loading /usr/lib/xorg/modules/libshadow.so
[27.247] (II) Module shadow: vendor=X.Org Foundation
[27.247]compiled for 1.16.4, module version = 1.1.0
[27.247]ABI class: X.Org ANSI C Emulation, version 0.4
[27.247] (II) Loading sub module fb
[27.247] (II) LoadModule: fb
[27.247] (II) Loading /usr/lib/xorg/modules/libfb.so
[27.324] (II) Module fb: vendor=X.Org Foundation
[27.324]compiled for 1.16.4, module version = 1.0.0
[27.324]ABI class: X.Org ANSI C Emulation, version 0.4
[27.324] (==) Depth 24 pixmap format is 32 bpp
[27.324] (II) Loading sub module int10
[27.324] (II) LoadModule: int10
[27.324] (II) Loading /usr/lib/xorg/modules/libint10.so
[27.324] (II) Module int10: vendor=X.Org Foundation
[27.324]compiled for 1.16.4, module version = 1.0.0
[27.324]ABI class: X.Org Video Driver, version 18.0
[27.324] (II) VESA(0): initializing int10
[27.324] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[27.324] (II) VESA(0): VESA BIOS detected
[27.324] (II) VESA(0): VESA VBE Version 3.0
[27.324] (II) VESA(0): VESA VBE Total Mem: 16384 kB
[27.324] (II) VESA(0): VESA VBE OEM: ATI ATOMBIOS
[27.324] (II) VESA(0): VESA VBE OEM Software Rev: 12.16
[27.324] (II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI 
Technologies Inc.

[27.324] (II) VESA(0): VESA VBE OEM Product: CEDAR
[27.324] (II) VESA(0): VESA VBE OEM Product Rev: 01.00
[27.324] (II) VESA(0): virtual address = 0x7f66a9821000,
physical address = 0xe000, size = 16777216
[27.337] (II) VESA(0): Setting up VESA Mode 0x176 (1600x1200)
[27.337] (II) VESA(0): VBESetVBEMode failed, mode set without 
customized refresh.

[27.451] (==) VESA(0): Default visual is TrueColor
[27.516] (==) VESA(0): 

Re: semi-OT: Problemas varios con ubuntu

2015-04-29 Thread alexlikerock-Gmail

El 28/04/15 a las 17:20, Miguel Matos escribió:

saludos al grupo. Tengo instalado el ubuntu versión 14.04 LTS, pero,
presento 2 problemas: vamos por partes...
1) Quiero instalarme el nuevo entorno de escritorio LXQT, pero, cuando
escojo instalarlo por synaptic, me dice que tiene muchas dependencias
que no va a instalar, ¡y se 'rompe'! ¿qué proponen que haga?
y 2)no puedo hacer que muestre la imagen con el cable HDMI, aunque
parece reconocer la conexión. Incluso, instalando arandr, no hace
nada. ¿Qué tendré de malo?
Quiero acotar que ya presenté esto a la lista de usuarios de Ubuntu
Venezuela; pero, estoy en espera a la aprobación del moderador desde
hace 6 días, y si espero, yo creo que sale antes la versión 17.04 y me
tocará actualizar sin poder usarlo. Por ello recurro a ustedes. Y
quizás, saber cómo hacerlo en la versión 8 de Debian (aún no la
instalo, pero, quiero estar preparado).





ESTO NO ES MUGRU-BUNTU 

parece q  tu propia  firma , no te ayuda de mucho:

 Ayuda para hacer preguntas inteligentes: http://is.gd/NJIwRz  

al parecer nesesitas agregar  la pregunta :

si tengo MUGRU-BUNTU ¿devo de ir a  a lista de Debian o  MUGRU-BUNTU?

por que parece q la logica no te  funciona  bien Miguel.


ESTO NO ES MUGRU-BUNTU 


entiende si no te  ayudan en MUGRU-BUNTU-Venezuela pues sigue buscando 
en MUGRU-BUNTU-ingles  o MUGRU-BUNTU-japon,


pero no preguntes en Debian  hasta q tengas un Debian instalado.

deverias de  agregar la siguiente pregunta  inteligente:

si MUGRU-BUNTU esta basado en Debian , pero tiene sus propios paquetes 
modificados, ¿significa que son iguales  o estan modificados con cambios 
q  no lo hacen iguales ?



y por cierto no essemi-OT  por que no tiene q ver con DEBIAN. asi q es 
un completo OT



--
**
software libre no significa gratis: richard m. stallman
http://wiki.debian.org/es/NormasLista#resumen
http://wiki.debian.org/es/NormasLista/Gmail
http://es.wikipedia.org/wiki/Top-posting


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/554136b4.1070...@gmail.com



Jessie with ATI Radeon HD 4250 boots black screen after installing drivers...

2015-04-29 Thread Gábor Hársfalvi
Hello,

I have a big problem - I use the official tutorial -
https://wiki.debian.org/ATIProprietary#Debian_8_.22Jessie.22 - but when I
reboot it always give me a black screen. :(

Why? And why gives me aticonfig --initial No supported adapters
detected?

Thanks


Re: instalacion de debian8 con wifi

2015-04-29 Thread Juan Fco Guil Vazquez



El 29/04/15 a las 19:06, Camaleón escribió:

El Wed, 29 Apr 2015 18:50:23 +0200, Juan Fco Guil Vazquez escribió:


Hola Estoy pensando instalar Debian8 con xfce  en mi portatil.
La cuestión es:
En el asistente de configuración te detecta el Wifi?

Sí, esa opción ya debería estar disponible.

Funcionará bien si la tarjeta wifi no necesita drivers o firmware
adicional, en cuyo caso tendrás que instalarlo para que el instalador la
pueda usar y configurar.

Saludos,


Hola
Gracias por las contestaciones. Es eso exactamente que quería saber.
Es que esta tarde he instalado en una maquina virtual con debian8, y no 
he visto tal opción wifi.

Por eso lo preguntaba.

Por cierto, me ha dado muy buena impresión

Hay que retocarlo poco el aspecto, pero tiene muy buena pinta sobre todo 
porque veo que no necesita muchos recursos y la estabilidad.


Gracias por las respuestas!!

Un saludo


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55412f77.7090...@gmail.com



Re: Power completely drained in hibernate mode?

2015-04-29 Thread Patrick Wiseman
On Wed, Apr 29, 2015 at 10:17 AM, Darac Marjal mailingl...@darac.org.uk wrote:
 On Wed, Apr 29, 2015 at 09:50:18AM -0400, Patrick Wiseman wrote:
 Hello:

 To hibernate, I use 'sudo pm-hibernate' (because the hibernate button
 on my Xfce power manager tells me 'Sleep verb not supported'). I
 thought hibernate mode was not supposed to use any power, but after 4
 days, my laptop was powerless (it wasn't when I hibernated).

 It should.  Hibernate and Off should use almost the same amount of power
 (there might be a trickle of usage for monitoring the lid opening).


I Googled the 'sleep verb not supported' and found that at least one
person experienced the same problem when Chrome was open with a bunch
of open tabs, which is _always_ the case on my laptop. I closed
Chrome, and the hibernate button worked. I'll see when next I open
that laptop whether hibernate really worked this time. (Could it be
Chrome that was draining power even when the machine was hibernated?)

 Any thoughts about how to diagnose what's going on? (It's also
 painfully slow to get back up to speed coming out of hibernation, but
 that's another story.)

 First off, see if you have any lights on on the machine while it's
 hibernated. If there is a sleep light, or if the power light pulses,
 for example, then the machine hasn't hibernated.

No lights were on or blinking. It _looks_ to be shut down.

 Next, see if your system is configured for hybrid sleep. Hybrid Sleep
 is like sleep, but the system is additionally saved to disk. That way,
 if the battery dies, a resume-from-hibernation can be performed. Check
 /etc/systemd/login.conf in case any of the Handle* options are set to
 hybrid-sleep.

The options in logind.conf (which I take it you meant) were all
commented out, and none defaults to hybrid sleep.

Thanks for your insights.

Patrick


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cajvvksormcezcuzjcacknahxdlfnajax5_d2jqfvb-ocjjv...@mail.gmail.com



Re: Question: Why do you dist-upgrade?

2015-04-29 Thread Reco
 Hi.

On Wed, 29 Apr 2015 13:52:07 -0500
Tim Kelley tim.kelley.n...@gmail.com wrote:

 Tim Kelley
 
 
 On Wed, Apr 29, 2015 at 12:13 PM, Reco recovery...@gmail.com wrote:
 
   Hi.
 
  On Wed, 29 Apr 2015 11:11:52 -0500
  Tim K kelle...@gmail.com wrote:
 
   For me, and I think anyone with a sensibly laid out system, it's so much
   less trouble and time to reinstall.
 
  While the amount of trouble is subjective, the install/upgrade time is
  objective. And it's the last one that you estimated wrong.
 
  An debian-installer, being a complex frontend to debootstrap, install
  packages and configures them. It also does disks partitioning, and the
  whole process requires two reboots (to installer and to a new system).
 
  An upgrade process installs the packages, configures them, but does not
  do partitioning. Also requires a single reboot that can be postponed
  indefinitely.
 
  An upgrade is simply faster.
 
 
 ​Hm. Not for me, ​anyway. None of those reboots matter to me much.

Get yourself a server hardware. Every reboot equals to 20-30 minutes on
hardware self-tests alone. Every reinstall requires that *magic*
firmware of very specific version (non-free, of course, so it's not
included in Debian CD).

Don't like server hardware? Get yourself a VPS, where every reinstall
requires you to communicate with those friendly overseas support guys.
And you'll be lucky if they don't charge you extra for console access.

Don't need a VPS? Get yourself an ARM board where every $DEITY-damn
*model* requires its' own street magic special trickery to run the
installer.

*Grumble* x86 desktop users. So many things are taken for granted.
No offense meant.


  I can only really think of one reason
   to dist-upgrade, and that's if the system is remote (and a very good
  reason
   it is). I'm wondering why some of you dist-upgrade ... do you just like
  it
   that way? A habit?
 
  Upgrade can be done via SSH. Upgrade retains all my packages installed.
  The most important thing is - upgrade does its best in handling all
  those customizations in /etc.
 
  ​Oh absolutely. ​But it can make /etc cruftier over time.

# du -sxh /etc
40M
# du -sxh /etc/.git
32M
# tune2fs -l /dev/root | grep creat
Filesystem created:   Fri Jan 27 23:41:53 2008

I can live with that cruft :)


 Being able to
 upgrade a distribution remotely is a very nice feature of Debian indeed.

Debian is not the only one in this regard.
Unless I'm mistaken, the only major distribution which does not
support major version upgrade is RHEL.


  /var contents will do you little good without /etc in most server
  environments
 
 ​/var's only separate because of the SSD (trying to activity on it, but I'm
 not sure that's really even an issue any more)
 In my case, I use the same SCMS at home as I do at work (salt) and that's
 where I configure most everything, and that is backed by remote git, and
 backed up remotely in addition to that, so, I think I'm covered there.​

If you have a backup - it's not an issue. Provided, of course, that
such backup is tested on a regular basis.


 You're right though, the new install would be very painful without that,
 since you'd have to change a hundred little things, from /etc/papersize to
 all the shell settings (which I have a lot of). And I admit it's very
 uncommon for a home user to back their configuration up with an SCMS.

:)


   The cons are that firstly, it's very time consuming and much more
   complicated.
 
  See above.
 
 
 ​You have to admit, there is much more to go wrong on an upgrade than a
 reinstall. 

Yes, indeed. For example, a power outage in a middle of upgrade may
result in unbootable system.
Re-install will end the same, of course, but another re-install will
fix it.


 Unless you were super-careful with your backports and software
 from outside the release in general that will cause problems, and while you
 might say you should always be careful about that it's also true that
 most people just aren't.

That's exactly why they suggest disabling third-party apt sources
before the upgrade :)

And users who install proprietary software should suffer anyway.
Especially the ones who use so-called installers.


 But yes if you do it right, use /usr/local or /opt
 and /etc/local and /etc/opt, /var/opt and /var/local you should be fine,
 but I've never personally met anyone who does that.​ Or if you kept your
 stable plain vanilla - never met anyone who does that either.

I did. Basically, it's like this:

'apt-get install' = 'sudo make install'
'apt-get remove' = 'rm -rf'
'apt-get upgrade' = 'um. I'll think of something'

IMO if one is using Debian and tries to 'make install' their way - one
might as well use Slackware :)


  And that's a perfect example of good software as all those years your
  system booted successfully.
 
 
 ​Well, yes, it is. I'm not dissing upgrading. I'd just rather re-install.​

There are times then re-install is necessary. For example - unauthorized
access that turned the host 

Re: Jessie with ATI Radeon HD 4250 boots black screen after installing drivers...

2015-04-29 Thread The Wanderer
On 04/29/2015 at 04:11 PM, Gábor Hársfalvi wrote:

 Hello,
 
 I have a big problem - I use the official tutorial -
 https://wiki.debian.org/ATIProprietary#Debian_8_.22Jessie.22 - but
 when I reboot it always give me a black screen. :(

Those directions state that they are only for specific models of AMD
GPUs:

For support of Radeon R9 200, Radeon R7 200, Radeon HD 8000, Radeon HD
7000, Radeon HD 6000 and Radeon HD 5000 series GPUs

The Radeon HD 4250 is part of the Radeon HD 4000-series, which is not in
that supported list.


In wheezy, there was a separate fglrx-legacy-driver package, which
included support for older graphics cards - including the Radeon HD 4000
series. It was available from the wheezy-backports repository.

Although this package is still mentioned in the description of the
fglrx-driver package, it does not seem to be available anymore - at
least not as far as I can tell at a glance.


I have a laptop which also has a 4000-series Radeon GPU, and I run it
with the non-proprietary driver from the xserver-xorg-video-radeon
package instead. It's not as performant as the proprietary FGLRX
equivalent would probably be, if one were available, but it does work;
the proprietary driver went away in testing some time last year, and I
haven't had any particular problems with the free alternative.


The directions on that Wiki page should probably explicitly state that
other models are not supported by the available proprietary drivers, and
suggest the free driver instead. It may not work ideally well, but it
should still work.

Alternatively, it _should_ be possible to install the most recent FGLRX
legacy driver from AMD's upstream site - but that would lose the
advantages of the Debian packaging and the integration which it
provides, and the directions for accomplishing it with certainty would
be considerably more complicated than what's already on that Wiki page.

 Why? And why gives me aticonfig --initial No supported adapters 
 detected?

Most likely because the 4250 graphics adapter is not supported by the
installed driver.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature


Re: Fwd: Drivers ATI Debian Jessie 64 Bits

2015-04-29 Thread Jose Maldonado
El 29/04/15 a las 04:11, Fernando Mordi Guerrieri escribió:
 Creo, entonces, que lo mejor será instalar el driver no privativo.
 
 ¿Cómo instalo el AMDGPU?
 
 Mordi
 
 El 29 de abril de 2015, 1:05, Jose Maldonado josemal...@gmail.com
 escribió:
 
 On 28/04/15 16:23, Fernando Mordi Guerrieri wrote:

 El 28 de abril de 2015, 17:42, metalhead b93 b93onli...@gmail.com
 escribió:

  me corrijo
 lo siento me he equivocado, no instalé KDE fué KDM (Session manager),

 y no, no soy Fernando.

 El día 28 de abril de 2015, 10:29, metalhead b93
 b93onli...@gmail.com escribió:

 El día 28 de abril de 2015, 9:39, Camaleón noela...@gmail.com

 escribió:

 El Tue, 28 Apr 2015 16:03:18 +0200, Fernando Mordi Guerrieri escribió:

 Hum... a ver que me estoy liando... ¿fernando = metalhead? :-???



  jaja yo ando igual, le chico apareció de pronto y sin más empezó a
 hablar pero bnn
 prosigamos

  El 28 de abril de 2015, 15:35, Camaleón noela...@gmail.com escribió:

  El Mon, 27 Apr 2015 13:35:23 -0500, metalhead b93 escribió:


 (...)

  Te recomiendo que uses mientras tanto el driver libre (radeon) hasta
 que lo arreglen por lo que convendría que siguieras de cerca ese
 informe de fallo para ver si hay algún cambio.

  6-ALT+F1 para logear y lego starx, inicia el entorno gráfico pero
 arroja el mismo mensaje

   Oh no! Something has gone wrong
   A problem has occurred and the system cant't recover. All

 extension

 have been disabled as a precaution.

 hice una copia de Xorg.0.log http://pastebin.com/1QTxjgei


 Perfecto. Sí, en el log se ven varios errores pero que la pantalla se
 vaya a negro indica un problema más grave. Revisa los mensajes del
 bug
 por si vieras algo que te interesara y si te animas, añade tu
 problema
 para que vean que hay más gente afectada.

  Una pregunta muy básica:

 ¿cómo vuelvo al driver libre radeon? La única que me queda es usar
 el
 modo consola. ¿qué comandos debo ejecutar?


 Si tienes instalado el driver propietario antes de eliminarendolo
 prueba
 añadiendo el módulo fglxr en la lista negra y activa el radeon. Eso lo
 tendrás en /etc/modprobe.d/radeon-kms.conf y para habilitarlo tendrás
 que dejarlo así:

 options radeon modeset=1

 Si eso no funciona, seguramente tendrás que eliminar los paquetes del
 driver propietario :-(


  Fernando, si has hecho  aptitude install fglrx-driver  creo que
 bastaría con aptitude remove fglrx-driver
 desconozco si hay que hacer algo más, prueba también con lo de la lista

 negra

 pero sigue leyendo que os traigo una noticia.





  esto va para todos

 resulta que tuve la idea de intentar con otros entornos gráficos,
 así que cómo la pantalla iniciaba en negro y no dejaba iniciar sesión,
 decidí instalar el gestor de inicio de sesión KDE
 aptitude install kde

 reinicié la pc y, vualá! KDE funciona, pero cuando inicio sesión con
 Gnome, otra ves el mismo error

 entonces decidí seguir probando, y también instalé el entorno de
 escritorio MATE aptitude install mate-desktop-environment-core(eso
 me instala mate básico)

 ahora reinicio la pc selecciono entorno de escritorio MATE con KDE y
 que sorpresa me llevo, MATE también funciona a la perfección,  e
 incluso veo habilitada una gran variedad de resoluciones para la
 pantalla (el problema es que yo quiero Gnome)

 también he comprobado la aceleración 3D y funciona perfecto

 metalheadb93@B93-Desktop:~$ glxinfo | grep direct
 direct rendering: Yes
  GL_AMD_multi_draw_indirect, GL_AMD_name_gen_delete,
  GL_ARB_draw_indirect, GL_ARB_draw_instanced,
 GL_ARB_enhanced_layouts,
  GL_ARB_multi_draw_indirect, GL_ARB_multisample,
 GL_ARB_multitexture,
  GL_EXT_direct_state_access, GL_EXT_draw_buffers2,

 GL_EXT_draw_instanced,

  GL_AMD_multi_draw_indirect, GL_AMD_name_gen_delete,
  GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect,
  GL_ARB_multi_draw_indirect, GL_ARB_multisample,
 GL_ARB_multitexture,
  GL_EXT_direct_state_access, GL_EXT_draw_buffers2,

 GL_EXT_draw_instanced,

 metalheadb93@B93-Desktop:~$ glxgears
 33376 frames in 5.0 seconds = 6675.199 FPS
 33721 frames in 5.0 seconds = 6744.189 FPS
 33724 frames in 5.0 seconds = 6744.715 FPS
 30181 frames in 5.0 seconds = 6035.950 FPS
 27798 frames in 5.0 seconds = 5559.473 FPS
 27544 frames in 5.0 seconds = 5508.700 FPS



 eso me lleva a creer que no hay problema con los drivers,

 quizás aun faltan librerías para que el nuevo Gnome corra sobre los

 drivers ati;

 no lo se, díganme ustedes, habra alguna posibilidad de solucionar el
 lío de ati con Gnome?



 Y yo no soy Metalhead :-)

 Perdonen por la aparición tan intempestiva. No quería hablar de cosas
 personales para no quedar fuera de tema.
 ¿es costumbre hacer una presentación personal cuando se es nuevo en la
 lista?

 A modo de presentación tardía:
 Me llamo Fernando, me dicen Mordi.
 Soy argentino y vivo en Francia. Soy biólogo, así que con el carbono me
 entiendo mucho mejor que con el silicio.
 Uso Debian desde 2008.
 Hace poco compré una nueva PC, por 

Re: issue with systemd-udev-settle

2015-04-29 Thread Christian Seiler
On 04/29/2015 06:53 PM, Matthias Bodenbinder wrote:
 Am 29.04.2015 um 10:32 schrieb Christian Seiler:
 Just use journalctl (without -b) to see all messages (they are
 still in RAM in the journal - as per the log you posted, journald
 will use up to 80 MiB [2] which is more than enough to keep all
 3000 or so messages). Just look through them (there are going to
 be a lot of debug messages from udev) and look at the timestamps.
 There you'll be able to see where the delay happens - and maybe
 you'll have a chance of figuring out, what the problem is. If
 it's nothing obvious, just post the last 20 or so udev messages
 before the large gap in the timestamps and every udev message
 afterwards. If there is no gap and udev is constantly doing
 something, take a look at what it's actually doing.
 
 No way. Just using journalctl makes no difference:
 
 Apr 29 18:45:08 xxx systemd-journal[170]: Forwarding to syslog missed
 3819 messages.
 Apr 29 18:45:14 xxx systemd-journal[170]: Suppressed 2818 messages from
 /system.slice/systemd-udevd.service
 
 And this is exactly the time period where I would expect the issue to
 pop up.

Ah, I only noticed the first message about syslog forwarding. The second
message tells us that rate limiting has kicked in, because udev just
generates a TON of messages in a short time.

Just for the purpose of debugging, could you increase RateLimitBurst to
1 or so (i.e. 10x the default value) in /etc/systemd/journald.conf
and reboot? (Set it back again after you're done deubgging, else your
logs might get flooded.)

Christian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55411381.7060...@iwakd.de



Re: Jessie and screensaver on lid-close

2015-04-29 Thread Ron
On Wed, 29 Apr 2015 19:30:19 +0200
Frederic Marchal frederic.marc...@wowtechnology.com wrote:

 Moreover, it makes sense to have a screen saver to turn the display and 
 backlight off. It saves a lot of energy on a laptop.

Not to mention that some, who make grunting noises in the backwoods, are still 
using CRT monitors...
 
Cheers,
 
Ron.
-- 
   So many beautiful women,
 and so little time.
-- John Barrymore

   -- http://www.olgiati-in-paraguay.org --
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150429134938.29842...@ron.cerrocora.org



  1   2   3   >