Le samedi 5 septembre 2015, 17:11:48 François Boisson a écrit :
>[… CONFIG_RTC_SYSTOHC …]
> > Sauf que cette option a été ajoutée au noyau 3.10 et
> > n’existe pas dans le 2.6…
>
> Mince je pensais que cela existait déjà sur le 2.6. C'était
> mon explication...
Vérifie quand même sur ton
Le Sat, 05 Sep 2015 11:31:29 +0200
"Sylvain L. Sauvage" a écrit:
> Et aussi : Pourquoi le serveur NTP voit le décalage quand il
> apparaît mais pas quand il disparaît ?
dans le deuxième cas le décalage est trop grand et ans ce cas, NTP ne rattrape
pas l'heure. Ce
Le Sun, 26 Jul 2015 14:38:08 +0200
Vincent Lefevre vinc...@vinc17.net a écrit:
On 2015-07-20 22:10:52 +0200, François Boisson wrote:
Autre chose qui m'incite à penser à des interruptions non traitées:
Mais pourquoi toutes les 2^22 secondes, et pourquoi pendant
89,06 secondes?
Si je le
El día 19 de agosto de 2015, 10:28, Camaleón noela...@gmail.com escribió:
El Tue, 18 Aug 2015 15:31:54 -0300, Javier ArgentinaBBAR escribió:
El día 18 de agosto de 2015, 14:24, Camaleón noela...@gmail.com
escribió:
(...)
Pero veo que por fin (!) lo han arreglado, pero vamos, que no son
El Tue, 18 Aug 2015 15:31:54 -0300, Javier ArgentinaBBAR escribió:
El día 18 de agosto de 2015, 14:24, Camaleón noela...@gmail.com
escribió:
(...)
Pero veo que por fin (!) lo han arreglado, pero vamos, que no son
errores graves sino simplemente mensajes molestos. Paciencia.
Es lo que nos
El Tue, 18 Aug 2015 14:04:48 -0300, Javier ArgentinaBBAR escribió:
Buenas tardes.
Pregunta a la lista: ¿alguno pudo solucionare el inconveniente?
Pues como no edites el script de configuración para que no se cargue ese
módulo y regeneres la imagen initrd no veo otra forma de hacer... salvo
El día 18 de agosto de 2015, 14:24, Camaleón noela...@gmail.com escribió:
El Tue, 18 Aug 2015 14:04:48 -0300, Javier ArgentinaBBAR escribió:
Buenas tardes.
Pregunta a la lista: ¿alguno pudo solucionare el inconveniente?
Pues como no edites el script de configuración para que no se cargue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Aug 16, 2015 at 04:16:33AM +0800, Nafiez wrote:
Hi,
I wanted to ask on what is the process to submit bug via e-mail. Can you
help?
I assume you are talking about reporting a bug against a Debian package:
there's a comand for that called
On Sun, Aug 16, 2015 at 04:16:33AM +0800, Nafiez wrote:
Hi,
I wanted to ask on what is the process to submit bug via e-mail. Can you
help?
Thank you,
Nafiez
Hello Nafiez,
you usually report bugs via reportbug (open a terminal, type
`reportbug enter` and follow the instructions).
On 2015-07-20 22:10:52 +0200, François Boisson wrote:
Autre chose qui m'incite à penser à des interruptions non traitées:
Mais pourquoi toutes les 2^22 secondes, et pourquoi pendant
89,06 secondes?
En clair donc, il y eu pour la machine 314s d'interruption horloge
entre chaque ligne,
Le Sun, 19 Jul 2015 17:54:21 +0200
Vincent Lefevre vinc...@vinc17.net a écrit:
Il y a un autre bug: c'était 89,06s dans ton premier message, et c'est
maintenant 86,06s!
Celui là je le connais bien, c'est l'interface clavier chaise. Lire 89,06s.
[...]
Pour le 2^22, je ne vois pas, à part
On Mon, Jul 20, 2015 at 07:27:35AM +0200, François Boisson wrote:
* Je vais regarder si il y a une dérive de l'horloge RTC, je me demande si
ces 89,06s ne viendrait pas de là (mais théoriquement l'horloge RTC est mise
à jour toutes les 11 minutes)
Pour autant qu'il m'en souvienne, l'horloge
Bonsoir,
Et en te fiant à ta première impression du souci matériel, ne serait-ce pas une
interférence horloge rtc pile du bios ?
Cordialement,
Christophe De Natale
Le 20 juil. 2015 à 22:10, François Boisson
user.anti-s...@maison.homelinux.net a écrit :
Le Mon, 20 Jul 2015 10:08:07
Le Mon, 20 Jul 2015 10:08:07 +0200
François Boisson user.anti-s...@maison.homelinux.net a écrit:
L'heure matérielle est censée se mettre à jour toutes les 11 minutes. En fait
tout ce passe comme si la machine s'était gelée pendant ces 89,06s. On
pourrait peut être imaginer que pour une raison
On Sat, Jul 18, 2015 at 02:28:46PM +0200, François Boisson wrote:
Cette période de 2^22 et le délai de 86,06s disent ils quelque chose à
quelqu'un?
Pas spécifiquement, mais la description me rappelle un très
vieux bug que j'avais eu, où l'on ne masquait pas les
interruptions dans le traitement
Le 19 juil. 2015 à 17:54, Vincent Lefevre vinc...@vinc17.net a écrit :
On 2015-07-18 14:28:46 +0200, François Boisson wrote:
Essaie de faire une recherche sur Google avec ces valeurs sous
diverses écritures. Mais j'ai l'impression que tu est le seul à avoir
ce problème, sinon il aurait été
On 2015-07-18 14:28:46 +0200, François Boisson wrote:
[precisions]
Toutes les 2^22 secondes soit en gros 1 mois 20 jours, le serveur, prend
89,06s d'avance (et est ejecté du pool donc). Les bugs se
sont produit à ces dates (et peut être avant):
12/08/2014 13:44:02
30/09/2014 02:56:06
Le Sun, 19 Jul 2015 12:50:16 +0200
Yves Rutschle debian.anti-s...@rutschle.net a écrit:
On Sat, Jul 18, 2015 at 02:28:46PM +0200, François Boisson wrote:
Cette période de 2^22 et le délai de 86,06s disent ils quelque chose à
quelqu'un?
Pas spécifiquement, mais la description me rappelle
[precisions]
Toutes les 2^22 secondes soit en gros 1 mois 20 jours, le serveur, prend
89,06s d'avance (et est ejecté du pool donc). Les bugs se
sont produit à ces dates (et peut être avant):
12/08/2014 13:44:02
30/09/2014 02:56:06 17/11/2014 15:02:38 05/01/2015 04:14:12
22/02/2015 17:21:55
Le Sat, 18 Jul 2015 14:37:54 +0200
Bernard Schoenacker bernard.schoenac...@free.fr a écrit:
bonjour,
serait il possible de voir du côté de adjtimex ?
Plus précisemment? Voilà ce que donne un dump de adjtimex:
francois@cerbere:~$ ./adjtimex
code retour: 0
modes : 0
offset (time offset ns ou
Le Sat, 18 Jul 2015 14:28:46 +0200,
François Boisson user.anti-s...@maison.homelinux.net a écrit :
[precisions]
Toutes les 2^22 secondes soit en gros 1 mois 20 jours, le serveur,
prend 89,06s d'avance (et est ejecté du pool donc). Les bugs se
sont produit à ces dates (et peut être avant):
Sounds like usb-autosuspend, at a glance.
I noticed that the commented line listing usb-autosuspend as a valid
option for one of the settings in /etc/laptop-mode/laptop-mode.conf
disappeared with the most recent update to that package, but I didn't
notice anything in the changelogs that would
On 07/11/2015 at 09:04 AM, Hans wrote:
Dear list,
I accidently had to reinstall laptop-mode-tools. I had to purge and
reinstall the package.
After this, I noticed, that my usb-mouse (cable), turns off after 3s
of inactivity. This behaviour was already deccribed here in older
forums:
On Fri, 2015-06-19 at 20:43 +0200, Christoph Martens wrote:
Hey guys,
I wanted to report a bug, but reportbug is completely broken on
Ubuntu.
So, I have the following issue with xdg-open, which is not the fault
of
xdg-utils, but an issue with gvfs:
El Mon, 01 Jun 2015 12:33:21 -0400, Ariel escribió:
(...)
Bug in Mailman version 2.1.18
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited,
but the webmaster can find this
El Mon, 01 Jun 2015 15:04:08 -0400, Ariel escribió:
(mando de nuevo porque el otro mensaje se coló dentro de otro hilo)
(...)
Bug in Mailman version 2.1.18
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system
On Fri, 2015-05-22 at 18:16 +0200, jake.pers...@riseup.net wrote:
Hi Guys
Very odd bug this. Caja opens fine without qmmp installed. But when qmmp
is installed and you want to browse with caja, the qmmp player launches
instead.
Where do I post this?
Hi,
I poked around the qmmp
Nader wrote:
hi, I need to report a bug in the debian installation system. I do not
know the name of the package that reportbug needs. Please let me know
how to proceed.
Browse the bugs in installation-reports and see if it has been
reported already.
could be debian-installer package?
2015-05-06 11:13 GMT+08:00 Nader nad...@gmail.com:
hi, I need to report a bug in the debian installation system. I do not
know the name of the package that reportbug needs. Please let me know
how to proceed.
--
To UNSUBSCRIBE, email to
Traduzindo, o usuário operador adicionado ao grupo www-data nao
consegue criar subdiretorios de um diretorio do grupo www-data com
permissão rwx.
Em 26 de março de 2015 10:54, Rodrigo Cunha rodrigo.root...@gmail.com
escreveu:
Fala pessoal, olha o que eu peguei no lubuntu.
http://ubuntuforum-br.org/
Em 26/03/15, Rodrigo Cunharodrigo.root...@gmail.com escreveu:
Fala pessoal, olha o que eu peguei no lubuntu.
operador@lab:/var/www/www.loja.meudominio.intranet$ pwd
/var/www/www.loja.meudominio.intranet
operador@lab:/var/www/www.loja.meudominio.intranet$ ls -l ../
quem tem servidor web com cgi-bin publico precisa atualizar o seu sistema .
tem esse script que você pode usa-lo
https://shellshocker.net/
On 22-03-2015 13:28, Rodrigo Cunha wrote:
Solução,
adicione os repositorios :
deb http://ftp.br.debian.org/debian/ wheezy main
deb-src
O bash 4.1 Tinha essa vulnerabilidade, fiz o upgrade para o 4.2.37 e
agora não tem mais a vulnerabilidade.
Fiquei curioso de como eu poderia explorar esta vulnerabilidade em meu
ambiente de laboratorio para fins academicos, isso poderia render um bom
artigo para a comunidade de SLivre,
Olha isso
# bash --version
GNU bash, version 4.1.5(1)-release (i486-pc-linux-gnu)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software; you are free to
Obrigado ao Antonio Terceiro por lembrar que o Debian LTS existe. Estou
com gNewSense e com algumas dúvidas
Coloquei no terminal:
root@root# env x='() { :;}; echo vulneravel' bash -c 'true'
vulneravel
root@root# env x='() { :;}; echo unvulneravel' bash -c 'false'
unvulneravel
root@root# env x='()
Que mistureba...
Mas com relação ao bug veja qual versão do bash é a vulnerável e qual
está instalada na sua máquina... assimo como os pacotes do referentes
ao SSL... procure no google, sites com CVE's por exemplo, ou na parte
de segurança do debian no seu site...
[ ] 's
Em 22/03/15, Thiago
Solução,
adicione os repositorios :
deb http://ftp.br.debian.org/debian/ wheezy main
deb-src http://ftp.br.debian.org/debian/ wheezy main
Executei:
sudo apt-get update
sudo apt-get install --only-upgrade bash gcc-4.4
Em 22 de março de 2015 13:26, P. J. pjotam...@gmail.com escreveu:
Que
* Retirei linhas duplicadas que acabei colocando no sources.list quando
copiei o que estava nas páginas do Debian-LTS;
* Apliquei # apt-get update apt-get install bash (gcc-4.4 já estava
instalado)
* Agora o comando que o Rodrigo Cunha apresentou não retorna mais a
resposta de 'vulneravel' nem
Valeu por mais esta dica do site shelshocker.net
Se não tiver o curl instalado, como foi aqui, é só instalar
# apt-get install curl
Teste:
# curl https://shellshocker.net/shellshock_test.sh | bash
% Total% Received % Xferd Average Speed TimeTime Time
Current
On Sun, Mar 22, 2015 at 01:04:40PM -0300, Thiago Zoroastro wrote:
Obrigado ao Antonio Terceiro por lembrar que o Debian LTS existe. Estou
com gNewSense e com algumas dúvidas
Coloquei no terminal:
root@root# env x='() { :;}; echo vulneravel' bash -c 'true'
vulneravel
root@root# env x='() {
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sir,
É claro que bugaria. Às vezes coloco algumas linhas diferentes da
família Debian e coloco # apt-get upgrade para ver quais pacotes
precisariam ser atualizados. Na maioria das vezes nem é possível ou não
faço. Como neste que uso é gNewSense,
On Sun, Mar 22, 2015 at 09:23:34PM -0300, Thiago Zoroastro wrote:
Sir,
É claro que bugaria. Às vezes coloco algumas linhas diferentes da
família Debian e coloco # apt-get upgrade para ver quais pacotes
precisariam ser atualizados. Na maioria das vezes nem é possível ou não
faço. Como
Aviso: (...) "The mail server responded: 4.7.1 deb...
Não foi possível enviar pelo Icedove.
Em meus computadores eu faço testes. No momento estou usando um Kaiana beta em dois notebooks (pessoal e um somente de testes). Já tive experiências falhas com pacotes, estou habituado a instalar o que
Bonjour à tous les utilisateurs et développeurs de Debian :
Le jeudi 12 mars 2015 à 13:27, Philippe Gras ph.g...@worldonline.fr a écrit
:
Listmaster me remonte les bretelles parce que mon fournisseur
a rejeté 1 de ses messages sur un total de 199, sur une période
de 7 jours (voir plus bas
Le 12/03/2015 14:27, Philippe Gras a écrit :
Listmaster me remonte les bretelles parce que mon fournisseur
C'est un envoi automatique, donc pas la peine de trop paniquer. Ce qui
est desolant c'est de voir tant de projets libres(ou pas) ne pas
utiliser Sympa, qui ecrase tous les autres
On 3/10/15, Bret Busby bret.bu...@gmail.com wrote:
-- Forwarded message --
From: Bret Busby bret.bu...@gmail.com
Date: Tue, 10 Mar 2015 22:54:42 +0800
Subject: Re: Bug#780201: new codename needed for oldstable (due to
squeeze-lts) when stable becomes oldstable
To: debian
*Hello*
*Kindly acknowledge that the problem is partially resolved.*
*I managed to run top for a while and found that mount and systemd were
consuming the cpu, so tried to delete some packages like lightdm and
schroot.*
*After removal of schroot the system has now become usable.*
*I have not
On 02/03/2015 06:32 AM, Ian Scheehan wrote:
Sometimes (random moment), my debian freeze, stop working.
I don't know which package or kernel part cause that debian jessie freeze.
How can get data/info of my computer and error which happen and send
report bug to you?
Can you help?
best
On 02/03/2015 06:32 AM, Ian Scheehan wrote:
Sometimes (random moment), my debian freeze, stop working.
I don't know which package or kernel part cause that debian jessie freeze.
How can get data/info of my computer and error which happen and send
report bug to you?
Can you help?
best
Den 30 januari 2015 17:47 skrev Sven Arvidsson s...@whiz.se:
Bug: #681315
Det är tyvärr inte så ovanligt, men du kan ju göra ändringen själv, så
funkar det åtminstone på ditt system.
Hmmm.. du menar alltså att det är vanligt att kända buggar kan finnas
kvar i flera år i Debian ? Ok.
Den 30 januari 2015 17:41 skrev Anders Jackson anders.jack...@gmail.com:
Det är tyvärr inte så ovanligt, men du kan ju göra ändringen själv, så
funkar det åtminstone på ditt system.
Eller så skickar man in en patch själv, om det inte redan finns någon.
Det brukar göra att det går lite fortare
Hej
Den 30 januari 2015 16:00 skrev Sven Arvidsson s...@whiz.se:
On Fri, 2015-01-30 at 05:59 +0100, Rolf Edlund wrote:
Tydligen finns buggen fortfarande kvar i GUfw, som gör att programmet
enbart visas i menyn under Unity. Fast den varit känd i många år.
Bug: #681315
Det är tyvärr inte så
Den 30 januari 2015 16:00 skrev Sven Arvidsson s...@whiz.se:
Bug: #681315
Det är tyvärr inte så ovanligt, men du kan ju göra ändringen själv, så
funkar det åtminstone på ditt system.
Hmmm.. du menar alltså att det är vanligt att kända buggar kan finnas
kvar i flera år i Debian ? Ok.
--
On Fri, 2015-01-30 at 17:35 +0100, Rolf Edlund wrote:
Den 30 januari 2015 16:00 skrev Sven Arvidsson s...@whiz.se:
Bug: #681315
Det är tyvärr inte så ovanligt, men du kan ju göra ändringen själv, så
funkar det åtminstone på ditt system.
Hmmm.. du menar alltså att det är vanligt att
On Fri, 2015-01-30 at 05:59 +0100, Rolf Edlund wrote:
Tydligen finns buggen fortfarande kvar i GUfw, som gör att programmet
enbart visas i menyn under Unity. Fast den varit känd i många år.
Bug: #681315
Det är tyvärr inte så ovanligt, men du kan ju göra ändringen själv, så
funkar det
Yes, why not?
flemming
On 18-11-2014 22:32, Per Andersson wrote:
Package: lists.debian.org
Severity: normal
Hi!
Please create a debian-nordic mailing list, for the Nordic Debian
Community.
At FSCONS 2014 in Göteborg, Sweden, almost a dozen Debian people
attended the Debian room. During a
Hi Flemming,
Quoting Flemming Bjerke (2014-11-21 10:35:46)
Yes, why not?
Bedre hvis du sender din kommentar til 770...@bugs.debian.org.
Helt fint at kommentere på denne liste (på dansk, endda), men processen
med at oprette nye lister i Debian kræver at der påvises et behov, som
bl.a. kan ske
2014-11-21 12:19 GMT+01:00 Jonas Smedegaard d...@jones.dk:
Hi Flemming,
Quoting Flemming Bjerke (2014-11-21 10:35:46)
Yes, why not?
Bedre hvis du sender din kommentar til 770...@bugs.debian.org.
Helt fint at kommentere på denne liste (på dansk, endda), men processen
med at oprette nye
2014-11-21 13:37 GMT+01:00 Jonas Smedegaard d...@jones.dk:
Quoting Per Andersson (2014-11-21 12:49:14)
2014-11-21 12:19 GMT+01:00 Jonas Smedegaard d...@jones.dk:
Quoting Flemming Bjerke (2014-11-21 10:35:46)
Yes, why not?
Bedre hvis du sender din kommentar til 770...@bugs.debian.org.
Helt
Hi Georges,
On Thu, Nov 13, 2014 at 08:53:19PM -0600, Georges Jamieson wrote:
I was trying to install jasper on a Raspbery Pi.
The installation failed and requested that I send in a bug report thus my
email.
I can not understand the instructions for doing so but I did see this email
El día 1 de septiembre de 2014, 16:03, Camaleón noela...@gmail.com escribió:
El Mon, 01 Sep 2014 10:09:40 +0200, Maykel Franco escribió:
El día 19 de agosto de 2014, 16:12, Camaleón noela...@gmail.com
escribió:
(...)
Voy a probar a reiniciar haber si con el cambio que he realizado en
grub
El día 2 de septiembre de 2014, 10:09, Maykel Franco
maykeldeb...@gmail.com escribió:
El día 1 de septiembre de 2014, 16:03, Camaleón noela...@gmail.com escribió:
El Mon, 01 Sep 2014 10:09:40 +0200, Maykel Franco escribió:
El día 19 de agosto de 2014, 16:12, Camaleón noela...@gmail.com
El Tue, 02 Sep 2014 10:09:13 +0200, Maykel Franco escribió:
El día 1 de septiembre de 2014, 16:03, Camaleón noela...@gmail.com
escribió:
(...)
Ejecuta ifconfig -a cuando el equipo haya iniciado a ver qué
interfaces detecta. Otra cosa que podrías probar es a renombrar el
archivo /etc/
El día 19 de agosto de 2014, 16:12, Camaleón noela...@gmail.com escribió:
El Tue, 19 Aug 2014 09:46:52 +0200, Maykel Franco escribió:
El día 18 de agosto de 2014, 16:22, Camaleón noela...@gmail.com
escribió:
(...)
¿Has pensado en abrir un informe de fallo contra udev?
Sí lo he pensado,
El Mon, 01 Sep 2014 10:09:40 +0200, Maykel Franco escribió:
El día 19 de agosto de 2014, 16:12, Camaleón noela...@gmail.com
escribió:
(...)
Voy a probar a reiniciar haber si con el cambio que he realizado en
grub se solventa.
¿Y qué pasó tras el reinicio?
Lo que me extraña es que sin
El día 18 de agosto de 2014, 16:22, Camaleón noela...@gmail.com escribió:
El Mon, 18 Aug 2014 10:04:50 +0200, Maykel Franco escribió:
Hola buenas, tenía configurado un bonding con 2 tarjetas de red, eth0 y
eth1. He reiniciado varias veces esa máquina y nunca he tenido problema.
Hará unos 2
El Tue, 19 Aug 2014 09:46:52 +0200, Maykel Franco escribió:
El día 18 de agosto de 2014, 16:22, Camaleón noela...@gmail.com
escribió:
(...)
¿Has pensado en abrir un informe de fallo contra udev?
Sí lo he pensado, pero si te soy sincero he pensado solucionarlo antes
de reportarlo.
Voy
El Mon, 18 Aug 2014 10:04:50 +0200, Maykel Franco escribió:
Hola buenas, tenía configurado un bonding con 2 tarjetas de red, eth0 y
eth1. He reiniciado varias veces esa máquina y nunca he tenido problema.
Hará unos 2 meses, actualicé el sistema y hoy que he reiniciado me
encuentro con que
Sorry about the delay in responding.
Henrique de Moraes Holschuh h...@debian.org writes:
Large time outs can cause bad side-efects on surprising ways. If the
socket is down, you get an immediate connection refused reply, which
short-circuits the time out.
As this is a generic feature, we
On Sun, 10 Aug 2014, Russ Allbery wrote:
To take a step back, I think this is a fair summary of the discussion.
Please let me know if you disagree:
...
I agree to all points. It is a fair summary.
I think you've convinced me that the approach of stopping a socket by the
same name when
On Sat, Aug 2, 2014 at 8:53 PM, Chris Bannister
cbannis...@slingshot.co.nz wrote:
[snip]
Is there a reason debian-user is subscribed to this bug report?
Please don't top-post.
Probably because it's a debian-user@ thread that resulted in the the
bug report and we were added to the cc as a
Jonathan de Boyne Pollard j.deboynepollard-newsgro...@ntlworld.com
writes:
And bugs #734766 and #734848 tell one the answer, which is that in order
to preserve its existing conceptual model that there is just the one
thing (named simply acpid) invoke-rc.d should pull out the socket
from the
On Sat, 02 Aug 2014, Russ Allbery wrote:
Jonathan de Boyne Pollard j.deboynepollard-newsgro...@ntlworld.com
writes:
And bugs #734766 and #734848 tell one the answer, which is that in order
to preserve its existing conceptual model that there is just the one
thing (named simply acpid)
Henrique de Moraes Holschuh h...@debian.org writes:
Services being subject to a package update can be down for extended
amounts of time (think package update that requires manual intervention,
or even a full manual reconfiguration, etc), or may actually involve an
ABI break. In both cases,
On Sat, 02 Aug 2014, Russ Allbery wrote:
Henrique de Moraes Holschuh h...@debian.org writes:
Services being subject to a package update can be down for extended
amounts of time (think package update that requires manual intervention,
or even a full manual reconfiguration, etc), or may
Is there a reason debian-user is subscribed to this bug report?
On Sat, Aug 02, 2014 at 10:42:38AM -0700, Russ Allbery wrote:
Jonathan de Boyne Pollard j.deboynepollard-newsgro...@ntlworld.com
writes:
[snip]
--
If you're not careful, the newspapers will have you hating the people
who are
On Wed, Jul 02, 2014 at 10:29:35PM +0200, Hans wrote:
strace -f dpkg --print-architecture
execve(/usr/bin/dpkg, [dpkg, --print-architecture], [/* 46 vars */]) =
-1 EACCES (Permission denied)
Ouch. This means that user cannot execute dpkg itself.
ls -la /usr/bin/dpkg
-rwxr-x--- 1 root root
Hi Reo!
And this proves it. This is definitely wrong, anyone should be able to
execute dpkg.
Yeah, I already that this was the problem. I downloaded the package dpkg
again and looked into. So I saw the wrong permissions.
BTW, to check 'stock' file permissions that should be set on a
Hi.
On Wed, 02 Jul 2014 20:06:05 +0200
Hans hans.ullr...@loop.de wrote:
LANG=C mediathekview
/usr/lib/java-wrappers/jvm-list.sh: line 25: /usr/bin/dpkg: Permission denied
And the line 25 of this script reads:
__arch=$(dpkg --print-architecture)
Can you run 'dpkg --print-architecture' as
Hi Reco!
And the line 25 of this script reads:
__arch=$(dpkg --print-architecture)
Can you run 'dpkg --print-architecture' as non-root?
No.
Are there any files at /etc/dpkg/dpkg.cfg.d that aren't readable by non-
root?
No.
What are the permissions to /etc/dpkg/dpkg.cfg (should be 644)?
On Wed, 02 Jul 2014 21:44:29 +0200
Hans hans.ullr...@loop.de wrote:
Hi Reco!
And the line 25 of this script reads:
__arch=$(dpkg --print-architecture)
Can you run 'dpkg --print-architecture' as non-root?
No.
Aha. What about:
strace -f dpkg --print-architecture
Are there any
On Wed, 02 Jul 2014 21:44:29 +0200
Hans hans.ullr...@loop.de wrote:
Hi Reco!
And the line 25 of this script reads:
__arch=$(dpkg --print-architecture)
Can you run 'dpkg --print-architecture' as non-root?
No.
Aha. What about:
strace -f dpkg --print-architecture
Are there any
Aha. What about:
strace -f dpkg --print-architecture
Reco
See:
strace -f dpkg --print-architecture
execve(/usr/bin/dpkg, [dpkg, --print-architecture], [/* 46 vars */]) =
-1 EACCES (Permission denied)
dup(2) = 3
fcntl(3, F_GETFL) =
On Fri, Apr 25, 2014 at 10:18 PM, berenger.mo...@neutralite.org wrote:
Le 25.04.2014 14:01, berenger.mo...@neutralite.org a écrit :
Le 24.04.2014 11:53, James Collier a écrit :
Hi Berenger (and all),
Thanks very much for the replies.
My installed dconf packages and versions:
On Monday 09 June 2014 14:05:01 Paul van der Vlis wrote:
Is een e-mail sturen naar cont...@bugs.debian.org met als inhoud:
'reassign 751002 libldap-2.4-2' de correct manier?
Ja, maar altijd netjes afsluiten na de control commando's met 'thanks' (zonder
aanhalingstekens).
--
GPG:
op 09-06-14 14:27, Diederik de Haas schreef:
On Monday 09 June 2014 14:05:01 Paul van der Vlis wrote:
Is een e-mail sturen naar cont...@bugs.debian.org met als inhoud:
'reassign 751002 libldap-2.4-2' de correct manier?
Ja, maar altijd netjes afsluiten na de control commando's met 'thanks'
El día 4 de junio de 2014, 10:39, Mauro Antivero
mauro.antiv...@gmail.com escribió:
Estimados, estoy buscando información sobre el bug reciente en libgnutls
(detallo el mismo más abajo), más precisamente que versiones son las
afectadas y a partir de que versión está resuelto el problema.
El Wed, 04 Jun 2014 10:39:11 -0300, Mauro Antivero escribió:
Estimados, estoy buscando información sobre el bug reciente en
libgnutls (detallo el mismo más abajo), más precisamente que versiones
son las afectadas y a partir de que versión está resuelto el problema.
(...)
Mi pregunta en
El 04/06/14 11:11, Camaleón escribió:
El Wed, 04 Jun 2014 10:39:11 -0300, Mauro Antivero escribió:
Estimados, estoy buscando información sobre el bug reciente en
libgnutls (detallo el mismo más abajo), más precisamente que versiones
son las afectadas y a partir de que versión está resuelto el
El 04/06/14 11:09, Guido Ignacio escribió:
El día 4 de junio de 2014, 10:39, Mauro Antivero
mauro.antiv...@gmail.com escribió:
Estimados, estoy buscando información sobre el bug reciente en libgnutls
(detallo el mismo más abajo), más precisamente que versiones son las
afectadas y a partir de
El Wed, 04 Jun 2014 13:10:49 -0300, Mauro Antivero escribió:
El 04/06/14 11:11, Camaleón escribió:
El Wed, 04 Jun 2014 10:39:11 -0300, Mauro Antivero escribió:
Estimados, estoy buscando información sobre el bug reciente en
libgnutls (detallo el mismo más abajo), más precisamente que
El 04/06/14 13:25, Mauro Antivero escribió:
El 04/06/14 11:09, Guido Ignacio escribió:
El día 4 de junio de 2014, 10:39, Mauro Antivero
mauro.antiv...@gmail.com escribió:
Estimados, estoy buscando información sobre el bug reciente en
libgnutls
(detallo el mismo más abajo), más precisamente
El Wed, 04 Jun 2014 13:33:46 -0300, Mauro Antivero escribió:
El 04/06/14 13:25, Mauro Antivero escribió:
El 04/06/14 11:09, Guido Ignacio escribió:
(...)
Mauro el cve es el CVE-2014-3466 y la info y solución la tenés acá [1]
Más info [2]
Pido mis disculpas, el mail que acabo de mandar
Le 24.04.2014 11:53, James Collier a écrit :
Hi Berenger (and all),
Thanks very much for the replies.
My installed dconf packages and versions:
james@james-turing:~$ apt-cache search dconf | grep dconf
dconf-cli - simple configuration storage system - utilities
dconf-editor - simple
Le 25.04.2014 14:01, berenger.mo...@neutralite.org a écrit :
Le 24.04.2014 11:53, James Collier a écrit :
Hi Berenger (and all),
Thanks very much for the replies.
My installed dconf packages and versions:
james@james-turing:~$ apt-cache search dconf | grep dconf
dconf-cli - simple
Hi Berenger (and all),
Thanks very much for the replies.
My installed dconf packages and versions:
james@james-turing:~$ apt-cache search dconf | grep dconf
dconf-cli - simple configuration storage system - utilities
dconf-editor - simple configuration storage system - utilities
Le 23.04.2014 09:00, James Collier a écrit :
Hello everyone,
first time posting here. Yay!
I've been having trouble with this dconf bug for some time now. And
no solution on google seems to help.
To get this error all I need to do is try to change a setting. e.g.
open terminal:
$
The idea of make a configuration file a binary file is the most serious
bug of dconf. It's bad by design and when ever possible, we should avoid
using software that needs dconf. As user use an editor that is dependent
to dconf, to edit a file with root privileges and than try to use a MUA
that's
Le 23.04.2014 15:33, Ralf Mardorf a écrit :
The idea of make a configuration file a binary file is the most
serious
bug of dconf. It's bad by design and when ever possible, we should
avoid
using software that needs dconf. As user use an editor that is
dependent
to dconf, to edit a file with
On Wed, 2014-04-23 at 16:38 +0200, berenger.mo...@neutralite.org wrote:
You know, I think exactly the same [snip]
the mailing-list's discussions about bloat-wares, gnome, systemd,
etc...
:D
I was thinking to send it to the off-topic list instead, but decided to
mention that dconf is less
401 - 500 of 2012 matches
Mail list logo