Debian installer not finding free space

[David DLC]

Hello again everyone!

I wanted to thank everyone for the help on the "Debian Installation Issues"
thread. I got the installer to start up through some fiddling around with
settings that were discussed. I am actually not 100% sure which solution
solved the problem, but I am glad it worked out!

I have encountered a new problem, and decided to start a new thread due to
the large amount of messages already present on the previous thread.

I have 40 gb unallocated on my C drive currently. When I start up the
installer and get to the disk partitioning section, it cannot find the free
space in the "guided" section. Am I doing something wrong with the disk
management?

I took a screenshot of my disk management program to show you guys:
http://imgur.com/a/qUoE0

Re: Re: Please help me resize my ext4 file system to size > 16TB

[R. Ramesh]

You implied you don't even have a backup of that data, which means you
have exactly one chance of getting it right.  This is a non-starter.

First: you are warned to NEVER proceed with a filesystem resize before
you have a valid, current, and *tested* backup.

You are also warned that the ext4 *conversion* to 64-bit block numbers
so as to be able to span more than 16TB is NOT your typical filesystem
resize operation in the first place.  It touches a *lot more* of the
filesystem and the risks are much higher than just adding an extent.
Even if it works flawlessly, it is not going to result in an optimal
filesystem.

The recommended procedure is to create a *new* filesystem and restore
from backup (or copy from the legacy filesystem if you find a way to
have both at the same time).  And for such large filesystems, the use of
"xfs" instead of "ext4" should be seriously considered.

Second: whatever reasons you had, or excuses you gave yourself, nothing
is going to get your data back if the filesystem ends up damaged beyond
repair and you don't have a backup.

"it would require updates that I am not ready do to yet"? Then DON'T.
Find another way to solve your immediate problem, and postpone the
larger filesystem for when you update everything.

You *have* been warned.


Now, you did not give us any idea of what is in that filesystem and what
you use it for, but as an alternative to resizing it, maybe you could
create several extra filesystems instead of enlarging the one you have
and attaching these extra ones to wherever you need more space?  Any
subdirectory can be made an entirely separate filesystem...

This wouldn't work for everything (e.g. you can't hardlink or
fast-rename across filesystems), but maybe it would work for whatever
you use that big filesystem for?

--
   Henrique Holschuh

Henrique,

  Let us not worry about backup. The data is just videos and not worth 
the effort. They are all recreatable with some effort. So, it is ok to 
try resize2fs and if that dies, I will simply get the data from my 
DVDs/Blurays.


  I don't think there is in place ext4 to xfs conversion. So, 
converting to xfs is less possible that resize2fs.


  I am just looking for path of least resistance. That is why I asked 
if it possible to resize without any upgrade. I will eventually upgrade 
and eventually figure out something. I just need to hear that there 
isn't a simple solution I have overlooked *today*. That is all.


Ramesh

Re: Re: How to delay resume after suspend to get disks ready, using kernel command line switch?

[R. Ramesh]

> Problem:
>
> I am having a problem with ubuntu 14.04 resume from suspend. I suspect a
> race condition in boot process. I have a mpt2sas (LSISAS2008:
> FWVersion(20.00.07.00)) host adapter to which several of my disks are
> attached. On occasions, there is a delay before these devices become
> available. However, kernel tries to assemble RAID6 that includes these
> disks before they become available. As a result the array gets assembled
> in a degraded mode.
>
> My question:
>
> I like to tell kernel to delay resume until LSI card finishes its card
> identifying devices. Can I use resumedelay/rootdelay switches in
> grub.cfg to accomplish this? If so, which one I should use?
>
> Ramesh

I also have mpt2sas and it is slow in disk initialization but I never use
suspend/resume. I only use shutdown/reboot. I use rootdelay=15.
Interesting. I did not have to use rootdelay for reboots. This is 
because I don't get to grub screen until mpt2sas finishes its thing.
So, disks are ready. This is not true in suspend because normal bios 
sequence is not run for resume, I think.


Ramesh

Re: e2fsck automatique au boot

[Pierre L.]

Salut,

Il me semble effectivement que le disque a besoin d'être automatiquement
monté via fstab au boot pour qu'il soit automatiquement "scanné" par
e2fsck. Si tu le montes à la main, le système ne devrait logiquement pas
y avoir accès, et ca râle ?

Ca peut valoir le coup de voir ce que ca donne avec ce disque
automatiquement monté au boot ? ;)
Au passage, j'utilise généralement pour mes disques de stockage ta même
config pour ton autre disque

defaults0   2 

et tout se passe pénard ;)

J'ai souvenir qu'il existait une commande (à l'époque Ubuntesque...)
pour connaître le nombre de reboots restants avant un scan auto... à
voir si ca fonctionne encore !




Le 13/06/2017 à 00:26, list a écrit :
> Bonjour.
>
> Ah forcément il fallait que j'oublie quelque chose dans ma
> description...
>
> Alors effectivement ce disque apparaît dans le fstab.
>
> UUID="d845-2f8x-40xx-88xx-630b4891819" /mnt/Ledisqueext3
> rw,users,noauto 0   2
>
> Mais je le monte uniquement «à la main» quand nécessaire
> (mount /mnt/Ledisque) 
>
> Le problème viendrait de là ? 
> Un autre disque, qui ne présente pas le «problème»,  est quant à lui
> avec les options suivantes dans le fstab : 
>
> defaults0   2 
>
>
> Une piste à explorer ? 
>
>
> Cordialement.
>
>
>
>
>
>  Le Mon, 12 Jun 2017 22:04:11 +0200 (CEST),
> l...@worldonline.fr a écrit :
>
>> Bonsoir
>>
>> C'est un disque monté avec fstab ?
>>
>  
>




signature.asc
Description: OpenPGP digital signature

Re: %2%F Buscas amiga discreta ?

[javier frf]

2017-06-12 19:44 GMT-04:00 ignacio eusebio hernandez hernandez
:
> Eso espero
>
> Tengo un amigo que me recomendó esta pagina para contactar amigas
>
> Estoy en la correcto con tu página??*
>
> O estoy equivocado en la dirección???
>

Estas en lo correcto, solo debe mandar un scanner de tu tarjeta de
crédito por ambos lados, y podrás hablar con las mejores chicas de
Mexico.
> Enviado desde Yahoo Mail para Android
>
> El lun., 12 de jun. de 2017 a la(s) 6:37 PM, Andres Pv
>  escribió:
>
> Espero estes consciente de lo que acabas de hacer.
>
>
>
>
>
> De: ignacio eusebio hernandez hernandez
> Enviado: lunes, 12 de junio de 2017 17:54
> Para: conta...@intimosamigos.net
> CC: debian-user-spanish@lists.debian.org
> Asunto: Re: %2%F Buscas amiga discreta ?
>
>
>
> Busco amiga discreta
>
>
>
> Mi cel es 5585564337
>
>
>
> Slds
>
> Enviado desde Yahoo Mail para Android
>
>

Re: slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)

[Joel Rees]

On Tue, Jun 13, 2017 at 9:30 AM, Dan Ritter  wrote:
> On Mon, Jun 12, 2017 at 11:50:00AM +0900, Joel Rees wrote:
>> (famous last words)
>>
>> On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees  wrote:
>> > I now have connection for both the wireless and the netbook that is acting
>> > as the AP. I took out the bridge entirely, quit trying to play with
>> > port forwarding,
>> > just used dead simple setup. dnsmasq was the only missing piece, if I had
>> > not been focusing on bridging.  Bridging is probably for the other 
>> > direction.
>> >
>> > But the wireless is pretty slow, so I'm not sure I'm finished.
>> >
>> > I have to go take care of some family business, when I'm done I'll
>> > post the details.
>> >
>> > But it's really pretty simply. I was just working too hard.
>>
>> But it's too slow to maintain a connection.
>>
>> After mucking around a bit, I haven't really come up with anything. So
>> I'll post my
>> configurations (names changed as usual):
>>
>
>
> You have an eth0 network, a non-overlapping wlan0 network -- can
> you characterize "too slow"?

Actually, now that I dig in, it only seems to be routing dns traffic.

That is, I tried to ping the wireless interface from my daughter's computer
and got a network not reachable or down result of some sort. (I didn't
write the exact message down, and my daughter's at school so I can't
use her computer.)

But my logs on the netbook that is running hostapd and dnsmasq show
quite a bit of dns traffic, lots of queries returning successful results.

> Things to check:
>
> - ping from your netbook to the outside world

No problem there.

> - ping from a wifi client through the netbook to the outside
>   world

That also got network not reachable or down or something.

> if those work,
>
> - wget -O /dev/null http://speed.hetzner.de/100MB.bin
> - and on a wifi client

I tried that in bridge configuration just now and I'm only getting one
percent every twenty to thirty seconds. The non-bridged configuration
doesn't even read the mail to look at the url.

-- 
Joel Rees

One of these days I'll get someone to pay me
to design a language that combines the best of Forth and C.
Then I'll be able to leap wide instruction sets with a single #ifdef,
run faster than a speeding infinite loop with a #define,
and stop all integer size bugs with my bare cast.
http://defining-computers.blogspot.com/2017/06/reinventing-computers.html

More of my delusions:
http://reiisi.blogspot.com/2017/05/do-not-pay-modern-danegeld-ransomware.html
http://reiisi.blogspot.jp/p/novels-i-am-writing.html

Re: slow connections to non-bridged hostapd/dnsmasq wireless access point (was pointers to material...)

[Dan Ritter]

On Mon, Jun 12, 2017 at 11:50:00AM +0900, Joel Rees wrote:
> (famous last words)
> 
> On Sat, Jun 10, 2017 at 3:53 PM, Joel Rees  wrote:
> > I now have connection for both the wireless and the netbook that is acting
> > as the AP. I took out the bridge entirely, quit trying to play with
> > port forwarding,
> > just used dead simple setup. dnsmasq was the only missing piece, if I had
> > not been focusing on bridging.  Bridging is probably for the other 
> > direction.
> >
> > But the wireless is pretty slow, so I'm not sure I'm finished.
> >
> > I have to go take care of some family business, when I'm done I'll
> > post the details.
> >
> > But it's really pretty simply. I was just working too hard.
> 
> But it's too slow to maintain a connection.
> 
> After mucking around a bit, I haven't really come up with anything. So
> I'll post my
> configurations (names changed as usual):
> 


You have an eth0 network, a non-overlapping wlan0 network -- can 
you characterize "too slow"?

Things to check:

- ping from your netbook to the outside world
- ping from a wifi client through the netbook to the outside
  world

if those work,

- wget -O /dev/null http://speed.hetzner.de/100MB.bin 
- and on a wifi client

RE: %2%F Buscas amiga discreta ?

[ignacio eusebio hernandez hernandez]

Eso espero
Tengo un amigo que me recomendó esta pagina para contactar amigas 
Estoy en la correcto con tu página??*
O estoy equivocado en la dirección???
Enviado desde Yahoo Mail para Android 
 
  El lun., 12 de jun. de 2017 a la(s) 6:37 PM, Andres Pv 
escribió:   #yiv1836463651 #yiv1836463651 -- _filtered #yiv1836463651 
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv1836463651 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv1836463651 
#yiv1836463651 p.yiv1836463651MsoNormal, #yiv1836463651 
li.yiv1836463651MsoNormal, #yiv1836463651 div.yiv1836463651MsoNormal 
{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;}#yiv1836463651 a:link, 
#yiv1836463651 span.yiv1836463651MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv1836463651 a:visited, #yiv1836463651 
span.yiv1836463651MsoHyperlinkFollowed 
{color:#954F72;text-decoration:underline;}#yiv1836463651 
.yiv1836463651MsoChpDefault {} _filtered #yiv1836463651 {margin:70.85pt 3.0cm 
70.85pt 3.0cm;}#yiv1836463651 div.yiv1836463651WordSection1 {}#yiv1836463651 
Espero estes consciente de lo que acabas de hacer.

  

  

De: ignacio eusebio hernandez hernandez
Enviado: lunes, 12 de junio de 2017 17:54
Para: conta...@intimosamigos.net
CC: debian-user-spanish@lists.debian.org
Asunto: Re: %2%F Buscas amiga discreta ?

  

Busco amiga discreta

  

Mi cel es 5585564337

  

Slds

Enviado desde Yahoo Mail para Android

  
  

RE: %2%F Buscas amiga discreta ?

[Andres Pv]

Espero estes consciente de lo que acabas de hacer.


De: ignacio eusebio hernandez hernandez
Enviado: lunes, 12 de junio de 2017 17:54
Para: conta...@intimosamigos.net
CC: debian-user-spanish@lists.debian.org
Asunto: Re: %2%F Buscas amiga discreta ?

Busco amiga discreta

Mi cel es 5585564337

Slds
Enviado desde Yahoo Mail para Android

Re: %2%F Buscas amiga discreta ?

[Paynalton]

El lun., 12 de jun. de 2017 a la(s) 17:54, ignacio eusebio hernandez
hernandez  escribió:

> Busco amiga discreta
>
> Mi cel es 5585564337
>
> Slds
>
> Enviado desde Yahoo Mail para Android
> 
>

Ya buscaste en eBay??? acá venden una:

http://www.ebay.com/itm/SEALED-BOXED-COMMODORE-AMIGA-1200-A1200-RARE-500-600-RARE-CDTV-4000-3000-2000-/222542364864?hash=item33d08f00c0:g:OCAAAOSwstJZPUND

Re: ntfsprogs den debian jessie?

[Paynalton]

El lun., 12 de jun. de 2017 a la(s) 15:38, Ariel Alvarez 
escribió:

> hola lista recien me tope con un problema que ya tengo solucion para este
> pero leyendo algunas soluciones recorde la utilidad (*ntfsfix*)  la cual
> se encarga de arreglar errores en el sistema de archivos, esta utilidad
> viene implicita en el paquete ntfsprogs, pero parar sorpresa ese paquete no
> esta disponible en jessie, alguien sabe algo al respecto?
>
> les argumento el problemilla que tuve por si le sirve a alguien, tengo
> algunos colegas que me llevan discos fisicos con particiones NTFS los
> cuales los puedo gestionar con NTFS-3G sin problemas pero al parecer desde
> windows 8 y versiones superiores a este incorporan el reinicio rapido, y
> esto causa que al tratar de montar un disco en NTFS que estuvo puesto en
> algun sistema windows 8 o superior de un error similar al siguiente:
>
> The disk contains an unclean file system (0, 0).
> Metadata kept in Windows cache, refused to mount.
> Failed to mount '/dev/sdb5': Operación no permitida
> The NTFS partition is in an unsafe state. Please resume and shutdown
> Windows fully (no hibernation or fast restarting), or mount the volume
> read-only with the 'ro' mount option.
>
> la solucion desde windows es desactivar el reinicio rapido, pero recorde
> que la utilidad (*ntfsfix*) me permite arreglar esto desde el mismo
> debian, en fin lo demas se los puse al inicio.
>
> cualquier aclaracion bienvenida sea.
> gracias de antemano
>
> - Consejo
> Nacional de Casas de Cultura http://www.casasdecultura.cult.cu
>

El programa ntfsfix está incluido dentro del paquete ntfs-3g

https://packages.debian.org/jessie/amd64/ntfs-3g/filelist

Re: Please help me resize my ext4 file system to size > 16TB

[Henrique de Moraes Holschuh]

On Mon, 12 Jun 2017, Ramasubramanian Ramesh wrote:
> >I think you ran into this problem:
> >http://blog.ronnyegner-consulting.de/2011/08/18/ext4-and-the-16-tb-limit-now-solved/
> >
> >I know of no way to get resize2fs to work with partitions larger than
> >16 TB, however in the blog post it's explained how to make mke2fs
> >work with such sizes by editing /etc/mke2fs.conf. Not sure if this is
> >an option for you though.
> 
> I have no way of backing up 16TB to use mke2fs. There is a solution (
> https://askubuntu.com/questions/779754/how-do-i-resize-an-ext4-partition-beyond-the-16tb-limit),
> but needs updates that I am not ready to do yet. So, I am checking if
> there is something that I missed that will allow me to resize without
> having to upgrade release/kernel/e2fsprogs and all of its friends.

You implied you don't even have a backup of that data, which means you
have exactly one chance of getting it right.  This is a non-starter.

First: you are warned to NEVER proceed with a filesystem resize before
you have a valid, current, and *tested* backup.

You are also warned that the ext4 *conversion* to 64-bit block numbers
so as to be able to span more than 16TB is NOT your typical filesystem
resize operation in the first place.  It touches a *lot more* of the
filesystem and the risks are much higher than just adding an extent.
Even if it works flawlessly, it is not going to result in an optimal
filesystem.

The recommended procedure is to create a *new* filesystem and restore
from backup (or copy from the legacy filesystem if you find a way to
have both at the same time).  And for such large filesystems, the use of
"xfs" instead of "ext4" should be seriously considered.

Second: whatever reasons you had, or excuses you gave yourself, nothing
is going to get your data back if the filesystem ends up damaged beyond
repair and you don't have a backup.

"it would require updates that I am not ready do to yet"? Then DON'T.
Find another way to solve your immediate problem, and postpone the
larger filesystem for when you update everything.

You *have* been warned.


Now, you did not give us any idea of what is in that filesystem and what
you use it for, but as an alternative to resizing it, maybe you could
create several extra filesystems instead of enlarging the one you have
and attaching these extra ones to wherever you need more space?  Any
subdirectory can be made an entirely separate filesystem...

This wouldn't work for everything (e.g. you can't hardlink or
fast-rename across filesystems), but maybe it would work for whatever
you use that big filesystem for?

-- 
  Henrique Holschuh

Re: Printer Setup Problem

[Brian]

On Mon 12 Jun 2017 at 10:36:56 -0400, Thomas George wrote:

> Two computers, an old pc with Debian Stretch and a new Raspberry Pi with the
> raspbian jessie operating system.
> 
> The old pc prints to a lan printer with no problem. The lpstat -t shows the
> identical set up on the Raspberry Pi but a command lp test.txt results in no
> printer output although the cups log shows the job as completed.

What do you mean by "cups log"?
 
> I have attached a script of the output of lpstat -t on the Raspberry Pi. The
> output of this command on the old pc is absolutely identical except for the
> dates and times.

lpstat shows the status of cups. It says nothing about how the job
progressed through the filtering system.
 
> Where should I look to fix this? 

[Snip]

The wiki explains how to get the smallest possible error_log. Obtain
one for each of the "old" and "new" machines using

  lp /etc/nsswitch

They will compress to a tenth of their sizes with gzip or xz. Post the
two compressed logs here.

-- 
Brian.

Re: %2%F Buscas amiga discreta ?

[ignacio eusebio hernandez hernandez]

Busco amiga discreta
Mi cel es 5585564337
Slds

Enviado desde Yahoo Mail para Android

Re: e2fsck automatique au boot

[list]

Bonjour.

Ah forcément il fallait que j'oublie quelque chose dans ma
description...

Alors effectivement ce disque apparaît dans le fstab.

UUID="d845-2f8x-40xx-88xx-630b4891819" /mnt/Ledisqueext3
rw,users,noauto 0   2

Mais je le monte uniquement «à la main» quand nécessaire
(mount /mnt/Ledisque) 

Le problème viendrait de là ? 
Un autre disque, qui ne présente pas le «problème»,  est quant à lui
avec les options suivantes dans le fstab : 

defaults0   2 


Une piste à explorer ? 


Cordialement.





 Le Mon, 12 Jun 2017 22:04:11 +0200 (CEST),
l...@worldonline.fr a écrit :

> Bonsoir
> 
> C'est un disque monté avec fstab ?
> 
 

Re: Printer Setup Problem

[Ric Moore]

On 06/12/2017 11:08 AM, Jan-Peter Rühmann wrote:

Did the same command work with the Debian PC?
Nonetheless have you choose the right driver?


For the love of $DEITY$, must you top post?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

To the OP, make sure samba is not installed. Get the printer working and 
then re-install samba, if you must. It took the entire customer support 
team at RedHat two days to discover samba messing with my wife's 
computer and printer. Jobs were sent yet never got printed. Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: Re: Please help me resize my ext4 file system to size > 16TB

[Ramasubramanian Ramesh]

> Hi,
>
>   I have kernel 3.13 and e2fsprog 1.42.9 (as part of mybuntu 14.04.5 LTS).
> With this, is it possible to resize2fs my ext4 RAID6 /dev/md0 to 24TB (ie
> >16TB)? If so, please help me get there. If not, please recommend the
> upgrades needed to the setup before this can be done. So, far, my google
> says I need to do "tune2fs -O extents,uninit_bg,dir_index /dev/md0" which I
> already did and I still get the dreaded message "resize2fs: New size too
> large to be expressed in 32 bits."
>
> There are mentions of a 64bit option for the ext4 file system. I can see how
> this relates to the error message from resize2fs, but I do not know what I
> should do to get that update done for my /dev/md0. Also all of the message
> that I come across relating to 64bit option, only talk about  how to
> *create* a brand new file system with 64bit. None of them tell me how to
> convert existing one. In fact, many of them scare me saying that it will be
> unsupported in older kernels. I am not really sure if my kernel is too old
> or not. Also, they talk about a switch -b for resize2fs that is not
> supported in the version installed currently on my system/release.
>
> Pleas help me figure out the correct sequence of steps. What packages need
> update, if current kernel/release is ok? Or, do I need to upgrade to a newer
> release before this is possible?
>
> Thanks
> Ramesh
>

I think you ran into this problem:
http://blog.ronnyegner-consulting.de/2011/08/18/ext4-and-the-16-tb-limit-now-solved/

I know of no way to get resize2fs to work with partitions larger than 16 TB,
however in the blog post it's explained how to make mke2fs work with such
sizes by editing /etc/mke2fs.conf. Not sure if this is an option for you
though.


I have no way of backing up 16TB to use mke2fs. There is a solution ( 
https://askubuntu.com/questions/779754/how-do-i-resize-an-ext4-partition-beyond-the-16tb-limit 
), but needs updates that I am not
ready to do yet. So, I am checking if there is something that I missed 
that will allow me to resize without having to upgrade 
release/kernel/e2fsprogs and all of its friends.


Ramesh

Re: Debian startup/booting help

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Jun 12, 2017 at 04:29:27PM -0400, DJ VIN Lom wrote:
> Is there a way to edit a script so when my raspberry pi2 running raspian
> jessie can automaticly go into a set directory so when it auto logs in its
> in a certain directory

Hm. I'm not sure I understand. The "raspberry pi2" "being in a directory"
doesn't make sense like that. A running process has a current directory,
e.g. a shell, or something like that. But there are many running processes
in an operating system running on the pi.

What exactly are you trying to achieve? Please describe a bit more, so
we can get an idea.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlk/AT8ACgkQBcgs9XrR2kZsbQCfUXlHpDC81R6Q5AUKrfR4TIpZ
Y8cAn38yhL4yL5Kjftl7G85KKR2+dAos
=TRvp
-END PGP SIGNATURE-

Debian startup/booting help

[DJ VIN Lom]

Is there a way to edit a script so when my raspberry pi2 running raspian
jessie can automaticly go into a set directory so when it auto logs in its
in a certain directory

ntfsprogs den debian jessie?

[Ariel Alvarez]

hola lista recien me tope con un problema que ya tengo solucion para 
este pero leyendo algunas soluciones recorde la utilidad (*ntfsfix*) la 
cual se encarga de arreglar errores en el sistema de archivos, esta 
utilidad viene implicita en el paquete ntfsprogs, pero parar sorpresa 
ese paquete no esta disponible en jessie, alguien sabe algo al respecto?


les argumento el problemilla que tuve por si le sirve a alguien, tengo 
algunos colegas que me llevan discos fisicos con particiones NTFS los 
cuales los puedo gestionar con NTFS-3G sin problemas pero al parecer 
desde windows 8 y versiones superiores a este incorporan el reinicio 
rapido, y esto causa que al tratar de montar un disco en NTFS que estuvo 
puesto en algun sistema windows 8 o superior de un error similar al 
siguiente:


The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sdb5': Operación no permitida
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.

la solucion desde windows es desactivar el reinicio rapido, pero recorde 
que la utilidad (*ntfsfix*) me permite arreglar esto desde el mismo 
debian, en fin lo demas se los puse al inicio.


cualquier aclaracion bienvenida sea.
gracias de antemano


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu

Re: e2fsck automatique au boot

[lann]

Bonsoir

C'est un disque monté avec fstab ?

- Mail original -
De: "list" 
À: debian-user-french@lists.debian.org
Envoyé: Dimanche 11 Juin 2017 00:44:51
Objet: e2fsck automatique au boot

Salut la liste.

Debian 8.7 
En regardant les logs je tombe sur un : 

kernel: EXT4-fs (sdc7): warning: maximal mount count reached, running
e2fsck is recommended

Un petit : systemctl status
systemd-fsck@dev-disk-by\x2duuid-d845dba2\x2d2f87\x2d40b7\x2d881c\x2d630f47931810.service

me donne : 
 Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static)
   Active: inactive (dead)
 Docs: man:systemd-fsck@.service(8)

J'ai tenté un : 

systemctl start
systemd-fsck@dev-disk-by\x2duuid-d845dba2\x2d2f87\x2d40b7\x2d881c\x2d630f47931810.service

Ça bloque et je me fais insulter dans les logs : 

systemd[1]: Dependency failed for File System Check
on /dev/disk/byx2duuid/d845dba2x2d2f87x2d40b7x2d881cx2d630f47931810

Bien sûr, je réponds avec fierté à l'insulte : 

 systemctl list-dependencies
 
systemd-fsck@dev-disk-by\x2duuid-d845dba2\x2d2f87\x2d40b7\x2d881c\x2d630f47931810.service

systemd-fsck@dev-disk-byx2duuid-d845dba2x2d2f87x2d40b7x2d881cx2d630f47931810.service
● └─system-systemd\x2dfsck.slice

Mais j'en reste là...piteusement battu...


Donc, un de mes disques durs  n'est plus vérifié après un certain nombre
de «montage» comme avant systemd (pas de critique ici, simplement un
comportement différent que je ne maîtrise pas ni ne comprend, pour le
moment) 

Un peu de lumière dans cette obscurité ? 

Avant le crash... 


Amicalement.

Adminer/SQLite3/Stretch: comment se connecter ?

[Olivier]

Bonjour,

J'ai installé Adminer sur un PC sous Stretch.
Avec Adminer, je n'arrive pas çà me connecter à une base de données locale
SQLite3.

1.Sur l'écran d'accueil, j'ai 4 champs Server/Username/Password/Database et
une liste déroulante.
Quand je sélectionne SQLite 3, je saisi le nom du fichier de base de donnée
(exemple /home/toto/foo.db) et je clique sur le bouton Login, j'ai un
message d'erreur Implement login() method to use SQLite.

2. Sur Jessie, il n'y a pas que 3 champs Server/Username/Password qui
disparaissent quand on sélectionne SQLite 3. Quand, je clique sur le bouton
Login, je peux saisir le nom du fichier de base de données SQLite.


1. Observez-vous le même comportement sous Stretch.
2. Si oui, quel contournement ?
3. Si non, j'ai lu [1].
Avez-vous installé le plugin login-sqlite ? Si oui, comment exactement
(j'ai procédé comme en [2])



Slts

[1] https://github.com/skydiver/october-plugin-adminer/issues/7
[2] Sauver le contenu du lien
https://raw.github.com/vrana/adminer/master/plugins/login-sqlite.php
dans le fichier /usr/share/adminer/plugins/login-sqlite.php (droits 644
root:root)
Modifier le fichier /usr/share/adminer/adminer/plugin.php pour y ajouter
une ligne "new AdminerLoginSqlite,"

Re: Peculiar problem with root login

[Dejan Jocic]

On 12-06-17, Erik Karlin wrote:
> On Mon, Jun 12, 2017 at 08:06:21PM +0200, Dejan Jocic wrote:
> > On 12-06-17, Felix Miata wrote:
> > > Jan-Peter Rühmann composed on 2017-06-12 17:15 (UTC+0200):
> > > .
> > > > Normally you can´t login via Root, because there is no entry in the 
> > > > passwd file.
> > > .
> > > That is false for every Debian installation (Squeeze, Wheezy, Jessie, 
> > > Stretch at
> > > least) I have ever done (unless maybe I'm misremembering all the way back 
> > > to Etch).
> > > -- 
> > > "The wise are known for their understanding, and pleasant
> > > words are persuasive." Proverbs 16:21 (New Living Translation)
> > > 
> > >  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> > > 
> > > Felix Miata  ***  http://fm.no-ip.com/
> > > 
> > 
> > dejan@ddeb:~$ cat /etc/passwd | grep root
> > root:x:0:0:root:/root:/bin/bash
> > 
> > Perhaps it is true if you choose not to create root account during
> > installation process.
> > 
> > 
> man 5 shadow

And? 

p.s. Please, reply to the list, not to me. There is no need to reply to
me, I'm subscribed. Thank you :)

Re: Peculiar problem with root login

[David Christensen]

On 06/12/2017 06:39 AM, Harry Putnam wrote:

Running debian jesse in a vbox vm on a Solaris host

I have what seems like an unusual problem with root login on this
host.

I've done the normal things one does to allow root login; that is, add

   PermitRootLogin yes

to /etc/ssh/sshd_config

Restart ssh, and in fact this host has been rebooted a few times since
adding that Permit line.

I set sudo up to work with no passwd for a certain user long ago and
so I was able to redo root passwd just to make sure there wasn't some
error there.

Still, I cannot login as root user  I don't mean at the main login
screen one gets on bootup, but from an xterm in a running session.

Of course, checked to see if Caps lock was on...

I've checked output of ssh -vvv root@localhost, and see nothing very
exciting.. just asking for password and rejecting it repeatedly:

debug1: Next authentication method: password
  root@localhost's password:
  debug2: we sent a password packet, wait for reply
  debug1: Authentications that can continue: publickey,password
  Permission denied, please try again.

This password has been in use for many years on vm hosts behind
firewall etc etc. So, there is literally NO chance I'm just getting it
wrong.  Not to mention as I said above that I redid the passwd in this
most recent attempt to get it working.

I'm fresh out of ideas as to what else to do here.

The auth log shows:

  Jun 11 14:50:55 d2 sshd[2830]: pam_unix(sshd:auth): authentication
  failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d.local.lan
  user=root

  Jun 11 14:50:57 d2 sshd[2830]: Failed password for root from
  127.0.0.1 port 54522 ssh2


Please run the following commands from the console of the jesse vm as 
root and paste your console session (prompts, commands entered, output 
obtained).  If you redact anything, substitute the phrase '':


# cat /etc/debian_version

# uname -a

# dpkg-query --show openssh-server

# dpkg-query --show openssh-client

# ls -1 /etc/ssh/*ssh*

# ls -1 /root/.ssh

# egrep -v '^.*#' /etc/ssh/sshd_config | grep .

# ssh localhost

# tail /var/log/auth.log


David

Package on which Bug must be reported ? (bluetooth)

[Kaartic Sivaraam]

Hello all,

This is a continuation of the thread that has a similar subject. Seems
the previous thread didn't grab much attention. 

For more information you may refer to the earliest thread that has a
similar subject prefix.

Issue 3:

My laptop came with a Broadcom bluetooth adapter. When I try to enable
it gets enabled but doesn't show any nearby devices. 

I once tried to fix specified in [1]. It worked for some time and after
some upgrade it stopped working again. I have re-installed the
operating system since then (not for this reason).

I am currently unable to use it to transfer files (or) connect devices.
The only thing I could do is t-o watch it trying detect devices. What
could be the issue and on which package should this be filed ?

Device Information:

Laptop Vendor : DELL
Laptop Model : 3542
Debian version : 4.9.25-1 (2017-05-02)
Kernel version : 4.9.0-3-amd64
Display Manager : GNOME
Display server : X


Links
-
[1] : https://www.gnebehay.com/blog/lenovo-flexpad-bluetooth-debian

-- 
Regards,
Kaartic Sivaraam 

Re: Peculiar problem with root login

[Dejan Jocic]

On 12-06-17, Felix Miata wrote:
> Jan-Peter Rühmann composed on 2017-06-12 17:15 (UTC+0200):
> .
> > Normally you can´t login via Root, because there is no entry in the passwd 
> > file.
> .
> That is false for every Debian installation (Squeeze, Wheezy, Jessie, Stretch 
> at
> least) I have ever done (unless maybe I'm misremembering all the way back to 
> Etch).
> -- 
> "The wise are known for their understanding, and pleasant
> words are persuasive." Proverbs 16:21 (New Living Translation)
> 
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> 
> Felix Miata  ***  http://fm.no-ip.com/
> 

dejan@ddeb:~$ cat /etc/passwd | grep root
root:x:0:0:root:/root:/bin/bash

Perhaps it is true if you choose not to create root account during
installation process.

Re: Peculiar problem with root login

[Felix Miata]

Jan-Peter Rühmann composed on 2017-06-12 17:15 (UTC+0200):
.
> Normally you can´t login via Root, because there is no entry in the passwd 
> file.
.
That is false for every Debian installation (Squeeze, Wheezy, Jessie, Stretch at
least) I have ever done (unless maybe I'm misremembering all the way back to 
Etch).
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Peculiar problem with root login

[Jan-Peter Rühmann]

Normally you can´t login via Root, because there is no entry in the passwd file.
That is because it is no good Idea to work as root.
the best way for SSH is by public key, without the need for Passwords.
There are a lot of Howto´s in the net.
Hope that helps a little.

Am 12.06.2017 um 15:50 schrieb Harry Putnam:
> Running debian jesse in a vbox vm on a Solaris host
>
> I have what seems like an unusual problem with root login on this
> host.
>
> I've done the normal things one does to allow root login; that is, add
>
>PermitRootLogin yes
>
> to /etc/ssh/sshd_config
>
> Restart ssh, and in fact this host has been rebooted a few times since
> adding that Permit line.
>
> I set sudo up to work with no passwd for a certain user long ago and
> so I was able to redo root passwd just to make sure there wasn't some
> error there.
>
> Still, I cannot login as root user  I don't mean at the main login
> screen one gets on bootup, but from an xterm in a running session.
>
> Of course, checked to see if Caps lock was on... 
>
> I've checked output of ssh -vvv root@localhost, and see nothing very
> exciting.. just asking for password and rejecting it repeatedly:
>
> debug1: Next authentication method: password
>   root@localhost's password: 
>   debug2: we sent a password packet, wait for reply
>   debug1: Authentications that can continue: publickey,password
>   Permission denied, please try again.
>
> This password has been in use for many years on vm hosts behind
> firewall etc etc. So, there is literally NO chance I'm just getting it
> wrong.  Not to mention as I said above that I redid the passwd in this
> most recent attempt to get it working.
>
> I'm fresh out of ideas as to what else to do here.
>
> The auth log shows:
>
>   Jun 11 14:50:55 d2 sshd[2830]: pam_unix(sshd:auth): authentication
>   failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d.local.lan
>   user=root
>
>   Jun 11 14:50:57 d2 sshd[2830]: Failed password for root from
>   127.0.0.1 port 54522 ssh2
Good luck,
-- 
Signatur
--
FOTO  
Jan-Peter Rühmann & Kuma

QR-Code (ME-Card) 
Gubkower Str. 7 
TELEFON:   +49 (38205) 65484
18195 Prangendorf   
FAX:   +49 (38205) 65212
Deutschland / MVP   
MOBILE:   +49 (162) 1316054
PIRATENPARTEI  VER.DI  
EUROPA
DEUTSCHLAND MECKLENBURG-VORPOMMERN ROSTOCK
EMAIL:   jan-pe...@ruehmann.name 
  ICQ:    288192920
   Sprechen
   Hinzuf�gen

  Twitter Profil @JPRuehmann   
  WhatsApp 491621316054   
WEB:   http://www.ruehmann.name 

--
Die Verwendung der Daten zu Werbezwecken ist verboten.

Re: Printer Setup Problem

[Jan-Peter Rühmann]

Did the same command work with the Debian PC?
Nonetheless have you choose the right driver?
It is possible that your printer can´t emulate the old Matrix Printers and so 
it can´t
Print Text directly the same goes for GDI Printers.
Hope that helps a little pointing out the Problem.

Am 12.06.2017 um 16:50 schrieb Thomas George:
> Two computers, an old pc with Debian Stretch and a new Raspberry Pi with the 
> raspbian
> jessie operating system.
>
> The old pc prints to a lan printer with no problem. The lpstat -t shows the 
> identical
> set up on the Raspberry Pi but a command lp test.txt results in no printer 
> output
> although the cups log shows the job as completed.
>
> I have attached a script of the output of lpstat -t on the Raspberry Pi. The 
> output of
> this command on the old pc is absolutely identical except for the dates and 
> times.
>
> Where should I look to fix this?
>
>
> PrinterPrintsNothing.txt
>
>
> Script started on Sun 11 Jun 2017 11:36:43 AM EDT
> raspberrypi:/home/pi# lpstat -t
> scheduler is running
> system default destination: Samsung_CLP-320_Series
> device for Samsung_CLP-320_Series: socket://192.168.1.139
> Samsung_CLP-320_Series accepting requests since Fri 09 Jun 2017 04:21:01 PM 
> EDT
> printer Samsung_CLP-320_Series is idle.  enabled since Fri 09 Jun 2017 
> 04:21:01 PM EDT
> raspberrypi:/home/pi# systemcytl enable cups
> Synchronizing state for cups.service with sysvinit using update-rc.d...
> Executing /usr/sbin/update-rc.d cups defaults
> Executing /usr/sbin/update-rc.d cups enable
> raspberrypi:/home/pi# exit
>
> Script done on Sun 11 Jun 2017 11:37:49 AM EDT
Good luck,
-- 

-=== Jan-Peter Rühmann & Kuma 
===-
 Gubkower Str.7   [  Tel.:  +49 (38205) 65484  ]   
jan-pe...@ruehmann.name
 18195 Prangendorf[  FAX:   +49 (38205) 65212  ]  
http://www.ruehmann.name
  [  Tel.:  +49 (38205) 65215  ]
  [  Mobil: +49 (162) 1316054  ]   
IT-Servicetechniker
ICQ: 288192920WhatsApp: 491621316054  Twitter: 
@JPRuehmann
--
  Die Verwendung der Daten zu Werbezwecken ist verboten.

Printer Setup Problem

[Thomas George]

Two computers, an old pc with Debian Stretch and a new Raspberry Pi with 
the raspbian jessie operating system.


The old pc prints to a lan printer with no problem. The lpstat -t shows 
the identical set up on the Raspberry Pi but a command lp test.txt 
results in no printer output although the cups log shows the job as 
completed.


I have attached a script of the output of lpstat -t on the Raspberry Pi. 
The output of this command on the old pc is absolutely identical except 
for the dates and times.


Where should I look to fix this?


PrinterPrintsNothing.txt


Script started on Sun 11 Jun 2017 11:36:43 AM EDT
raspberrypi:/home/pi# lpstat -t
scheduler is running
system default destination: Samsung_CLP-320_Series
device for Samsung_CLP-320_Series: socket://192.168.1.139
Samsung_CLP-320_Series accepting requests since Fri 09 Jun 2017 04:21:01 PM EDT
printer Samsung_CLP-320_Series is idle.  enabled since Fri 09 Jun 2017 04:21:01 
PM EDT
raspberrypi:/home/pi# systemcytl enable cups
Synchronizing state for cups.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d cups defaults
Executing /usr/sbin/update-rc.d cups enable
raspberrypi:/home/pi# exit

Script done on Sun 11 Jun 2017 11:37:49 AM EDT

Re: Primera versio d'un paquet

[Narcis Garcia]

__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 12/06/17 a les 13:51, Alex Muntada ha escrit:
> Narcis Garcia:
> 
>> Si per exemple faig:
>>
>> $ LANG=en apt-cache show x11vnc | grep -ie '^Version:'
>>
>> veig les versions disponibles al repositori per un paquet, però no estic
>> segur de si estan ordenades de nova a antiga o només segons es recorden
>> a la memòria cau d'APT.
> 
> Jo només veig una versió:
> 
> $ LANG=en apt-cache show x11vnc | grep -ie '^Version:'
> Version: 0.9.13-1.2+b2
> 
>> Temo que si aplico |sort per ordenar-les alfabèticament, se'm pugui
>> colar una versió 9 com a més nova que una 10.
> 
> Pots utilitzar «|sort -n» per indicar que vols que ordeni números
> però això no funciona amb les versions: la versió 0.10 és més gran
> que la 0.9 però numèricament 0.9 és més gran que 0.10.
> 
> El millor que pots fer és utilitzar alguna llibreria que faci
> les comparacions de versió de Debian, per exemple Dpkg::Version
> per a Perl té la funció «version_compare» (imagino que hi deu
> haver llibreries similars per d'altres llenguatges). Et caldrà
> instal·lar el paquet libdpkg-perl (potser ja el tens si havies
> instal·lat dpkg-dev abans).
> 
> Per exemple, donada una llista de versions desordenades, aquesta
> ordre retorna la versió més petita (posició 0 dels arguments
> ordenats amb version_compare):
> 
> $ perl -MDpkg::Version -lE 'say((sort version_compare @ARGV)[0])' 0.10 0.9 
> 0.5 0.100
> 0.5
> 
> Salut,
> Alex
> 

Gràcies; provaré aquest mètode.

Re: Mijn Canon EOS 700D wordt niet gemount

[Cecil Westerhof]

On Monday 12 Jun 2017 15:59 CEST, Diederik de Haas wrote:

> On maandag 12 juni 2017 15:12:01 CEST Cecil Westerhof wrote:
>> colord-sane[7123]: io/hpmud/musb.c 2101: Invalid usb_open:
>> Permission denied
>>
>> Wat zou hier aan de hand kunnen zijn?
>
> Zit je in de plugdev groep?

Ja.

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

Re: Fwd: xorg.conf dos pantallas

[marcelo]

El 12/06/17 a las 03:59, Antonio Trujillo Carmona escribió:

El 09/06/17 a las 15:36, marcelo escribió:

El 09/06/17 a las 03:36, Antonio Trujillo Carmona escribió:

El 09/06/17 a las 02:16, marcelo escribió:


 Mensaje reenviado 
Asunto: xorg.conf dos pantallas
Fecha: Thu, 8 Jun 2017 21:12:10 -0300
De: marcelo
A:debian-user-spanish@lists.debian.org



Hola amigos.

El problema que tengo con mi Debian 8 xfce es el siguiente. Cuando
inicio no me reconoce la resolución del monitor y lo tengo que hacer a
mano cada vez que inicio sesión con la aplicación "ArandR".

Estuve investigando pero no me animé a tocar. Copio el resultado de
xrandr

Screen 0: minimum 320 x 200, current 1280 x 768, maximum 16384 x 16384
LVDS connected 1280x768+0+0 (normal left inverted right x axis y axis)
344mm x 194mm
1366x768  60.01 +
1280x768  60.01*
1280x720  60.01
1024x768  60.01
800x600   60.01
640x480   60.01
DFP1 connected 1280x768+0+0 (normal left inverted right x axis y axis)
510mm x 290mm
1920x1080 60.00 +  50.0059.9450.0060.00 59.94
1776x1000 50.0059.9450.0059.94
1680x1050 59.95
1400x1050 59.95
1600x900  59.95
1280x1024 60.02
1440x900  59.95
1280x960  60.00
1152x864  59.96
1280x768  60.00*
1280x720  50.0060.0059.94
1024x768  60.00
1152x648  50.0059.94
800x600   60.32
720x480   60.0059.94
640x480   60.0059.94
CRT1 disconnected (normal left inverted right x axis y axis)

y ahora copio mi Xorg.conf

Section "ServerLayout"
 Identifier "aticonfig Layout"
 Screen  0  "aticonfig-Screen[0]-0" 0 0
EndSection

Section "Module"
EndSection

Section "Monitor"
 Identifier   "aticonfig-Monitor[0]-0"
 Option  "VendorName" "ATI Proprietary Driver"
 Option  "ModelName" "Generic Autodetecting Monitor"
 Option  "DPMS" "true"
EndSection

Section "Device"
 Identifier  "aticonfig-Device[0]-0"
 Driver  "fglrx"
 BusID   "PCI:0:1:0"
EndSection

Section "Screen"
 Identifier "aticonfig-Screen[0]-0"
 Device "aticonfig-Device[0]-0"
 Monitor"aticonfig-Monitor[0]-0"
 DefaultDepth 24
 SubSection "Display"
 Viewport   0 0
 Depth 24
 EndSubSection
EndSection

Si me pueden ayudar se los voy a agradecer mucho

Me olvidé de poner lo mas importante. El monitor que tiene probelmas
es el DFP1, cuya resolución es de 1920x1080.
Disculpen estos errores de novato



Para configurar en modo gráfico existe un programa llamado xrandr.
Si no ves muy claro como va la cosa instálate el "lxrandr" (una
versión para lxde), veras la opción de guardar, lo que guardes lo
pondrá en un directorio escondido
"~/.config/autostart/lxrandr-autostart.desktop", si no se te ejecuta
(por que no usas el lxde), puedes ver el contenido con "cat" y copiar
lo que hay en la linea Exec=sh -c'[lo que tienes que copiar]' al
fichero "~/.xinitrc".
--


Uso xfce. Hay algun programa como lxrandr para xfce?
También tengo el archivo xinitrc ahí tendría que poner la
linea correspondiente de xrandr?


Perdona pero no se que tal funciona la configuración automatica de
lxrandr en xfce (no lo uso), lo que te dije es que lo usaras, despues de
darle a guardar pueden ocurrir 2 cosas, a que funcione, pues eso, B que
no funcione, entonces es cuando debes de copiar la linea que te dije a
tu .xinitrc

-- *Antonio Trujillo Carmona* *Técnico de redes y sistemas.* 
*Subdirección de Tecnologías de la Información y Comunicaciones* 
Servicio Andaluz de Salud. Consejería de Salud de la Junta de 
Andalucía _antonio.trujillo.sspa@juntadeandalucia.es_ Tel. +34 
670947670 747670)

Apenas lo pruebe te aviso. Gracias

Re: kernel 4.9 cuelgue en el inicio

[marcelo]

El 10/06/17 a las 15:50, Felix Perez escribió:

El día 9 de junio de 2017, 11:29, marcelo  escribió:


El 09/06/17 a las 12:03, Felix Perez escribió:

El día 9 de junio de 2017, 9:33, marcelo 
escribió:

El 08/06/17 a las 23:52, Felix Perez escribió:

El día 8 de junio de 2017, 20:01, marcelo 
escribió:

El 08/06/17 a las 20:38, Felix Perez escribió:

El día 8 de junio de 2017, 19:33, Paynalton 
escribió:

si estás usando gdm para iniciar sesión necesitas instalar los modulos
para
tu tarjeta gráfica.

Estimado por favor no haga top posting, así se lleva un hilo ordenado
y no contestes al privado siempre a la lista.

Gracias.

El jue., 8 de jun. de 2017 a la(s) 18:15, marcelo
 escribió:

Amigos:

Tomé la decisión de volver a instalar debian 8 y me llamó la atención
que después de instalar no podía loguearme con mi usuario y contraseña
porque la computadora se "congelaba". Pensé que era un error de
instalación asi que volví a instalarlo dos veces mas con idéntico
resultado.

Desesperado se me ocurrió probar distintas alternativas y llegué a la
conclusión que el problema es el kernel 4.9, ya que iniciando en
opciones con kernel 3.16 no tengo ningún problema.

En el inicio me sale un error "module microcode not found in
modules.dep" buscando en internet deducí que ese no es un problema. Es
así

Espero sus comentario.

Muy agradecido

Estoy usando lightdm.
Que debería hacer?
prometo no hacer mas top-posting. Perdón

No Marcelo tú no has echo top posting, quien lo hizo es quién te
contesto anteriormente la idea tampoco es contestar al final sino que
debajo de lo que estás contestando, como yo ahora mismo que contesto
bajo tu comentario.

Jessie usa de serie el kernel 3.1 y Stretch 4.9 ¿Que versión estás
intentando instalar?  ¿Activaste los repos Contrib / Non free?

Estoy intentando instalar Debian 8.
Efectivamente tengo los repos contrib y non-free

A ver, si instalas debian 8, Jessie, instalas el kernel 3.16 no
entiendo porqué dices que instalas debian 8 y tienes problemas con el
kernel 4.9 el cual en una instalación viene con Debian 9 Stretch.  No
queda claro qué y cómo instalas.

Intenta entrar en modo rescate y revisa los logs, tal vez por ahí
encontremos algo, pero me parece que puede ser y tal como comentan
anteriormente unos problemas derivados de la tarjeta gráfica.


Gracias

Yo bajé una versión netinstall de debian (ayer). Digamos que el kernel 4.9
se instaló solo. Yo no hice nada para que se instalara. Es mas, tampoco se
como se hace.

Ahhh entonces debes haber instalado un testing stretch, y lo más
probable que te falten los módulos de la gráfica.


Mañana pruebo de entrar en modo rescate y les cuento como me fue

envía la salida de un:
uname -a
lspci
lsusb

Suerte.


Esto lo hago desde la consola del 3.16 no es cierto? Porque el 4.9 no lo 
puedo arrancar. Perdón por la ignorancia

Re: Mijn Canon EOS 700D wordt niet gemount

[Diederik de Haas]

On maandag 12 juni 2017 15:12:01 CEST Cecil Westerhof wrote:
> colord-sane[7123]: io/hpmud/musb.c 2101: Invalid usb_open: Permission
> denied 
> 
> Wat zou hier aan de hand kunnen zijn?

Zit je in de plugdev groep?

signature.asc
Description: This is a digitally signed message part.

Peculiar problem with root login

[Harry Putnam]

Running debian jesse in a vbox vm on a Solaris host

I have what seems like an unusual problem with root login on this
host.

I've done the normal things one does to allow root login; that is, add

   PermitRootLogin yes

to /etc/ssh/sshd_config

Restart ssh, and in fact this host has been rebooted a few times since
adding that Permit line.

I set sudo up to work with no passwd for a certain user long ago and
so I was able to redo root passwd just to make sure there wasn't some
error there.

Still, I cannot login as root user  I don't mean at the main login
screen one gets on bootup, but from an xterm in a running session.

Of course, checked to see if Caps lock was on... 

I've checked output of ssh -vvv root@localhost, and see nothing very
exciting.. just asking for password and rejecting it repeatedly:

debug1: Next authentication method: password
  root@localhost's password: 
  debug2: we sent a password packet, wait for reply
  debug1: Authentications that can continue: publickey,password
  Permission denied, please try again.

This password has been in use for many years on vm hosts behind
firewall etc etc. So, there is literally NO chance I'm just getting it
wrong.  Not to mention as I said above that I redid the passwd in this
most recent attempt to get it working.

I'm fresh out of ideas as to what else to do here.

The auth log shows:

  Jun 11 14:50:55 d2 sshd[2830]: pam_unix(sshd:auth): authentication
  failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d.local.lan
  user=root

  Jun 11 14:50:57 d2 sshd[2830]: Failed password for root from
  127.0.0.1 port 54522 ssh2

Mijn Canon EOS 700D wordt niet gemount

[Cecil Westerhof]

Ik ben overgegaan naar Debian. Op mijn oude (openSUSE) systeem kon ik
gewoon mijn Canon EOS 700D inpluggen en werd deze gemount. Als ik dit
echter op mijn Debian systeem doe, dan krijg ik:
kernel: usb 6-1: new high-speed USB device number 7 using xhci_hcd
kernel: usb 6-1: New USB device found, idVendor=04a9, idProduct=3272
kernel: usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 6-1: Product: Canon Digital Camera
kernel: usb 6-1: Manufacturer: Canon Inc.
mtp-probe[7076]: checking bus 6, device 7: 
"/sys/devices/pci:00/:00:15.2/:04:00.0/usb6/6-1"
mtp-probe[7076]: bus: 6, device: 7 was not an MTP device
colord-sane[7089]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
colord-sane[7089]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
colord-sane[7089]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
colord-sane[7089]: io/hpmud/pp.c 627: unable to read device-id ret=-1
kernel: usb 6-1: USB disconnect, device number 7
colord-sane[7123]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
colord-sane[7123]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
colord-sane[7123]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
colord-sane[7123]: io/hpmud/pp.c 627: unable to read device-id ret=-1

Wat zou hier aan de hand kunnen zijn?

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

Cinnamon DE Frequent Crash

[Ashok Inder]

Greetings,

For past few days, Cinnamon DE is constantly crashing and I'm unable to
understand the reason for this.

Here I have attached log file of Xorg.0.log and output of cinnamon
--replace.

What could be issue?

Currently have MATE installed as backup DE.

System is updated.

*Do I need to share further any other log files as well?

Regards,
ashok@localhost:~$ grep -i module /var/log/Xorg.0.log
[27.707] (==) ModulePath set to "/usr/lib/xorg/modules"
[27.707] (II) Module ABI versions:
[27.710] (II) LoadModule: "glx"
[27.710] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[28.988] (II) Module glx: vendor="X.Org Foundation"
[28.988]compiled for 1.16.4, module version = 1.0.0
[28.988] (II) LoadModule: "intel"
[29.168] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[29.676] (II) Module intel: vendor="X.Org Foundation"
[29.676]compiled for 1.15.99.904, module version = 2.21.15
[29.676]Module class: X.Org Video Driver
[29.676] (II) LoadModule: "modesetting"
[29.871] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[30.245] (II) Module modesetting: vendor="X.Org Foundation"
[30.245]compiled for 1.16.4, module version = 0.9.0
[30.245]Module class: X.Org Video Driver
[30.245] (II) LoadModule: "fbdev"
[30.245] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[30.468] (II) Module fbdev: vendor="X.Org Foundation"
[30.468]compiled for 1.15.99.904, module version = 0.4.4
[30.468]Module class: X.Org Video Driver
[30.468] (II) LoadModule: "vesa"
[30.891] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[31.117] (II) Module vesa: vendor="X.Org Foundation"
[31.117]compiled for 1.15.99.904, module version = 2.3.3
[31.117]Module class: X.Org Video Driver
[31.122] (II) Loading sub module "fbdevhw"
[31.122] (II) LoadModule: "fbdevhw"
[31.122] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[31.183] (II) Module fbdevhw: vendor="X.Org Foundation"
[31.183]compiled for 1.16.4, module version = 0.0.2
[31.621] (II) Loading sub module "fb"
[31.621] (II) LoadModule: "fb"
[31.621] (II) Loading /usr/lib/xorg/modules/libfb.so
[32.001] (II) Module fb: vendor="X.Org Foundation"
[32.001]compiled for 1.16.4, module version = 1.0.0
[32.001] (II) Loading sub module "dri2"
[32.001] (II) LoadModule: "dri2"
[32.001] (II) Module "dri2" already built-in
[32.001] (II) UnloadModule: "modesetting"
[32.001] (II) UnloadModule: "fbdev"
[32.001] (II) UnloadSubModule: "fbdevhw"
[32.001] (II) UnloadModule: "vesa"
[36.547] (II) LoadModule: "evdev"
[36.591] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[36.728] (II) Module evdev: vendor="X.Org Foundation"
[36.728]compiled for 1.16.0, module version = 2.9.0
[36.728]Module class: X.Org XInput Driver
[36.739] (II) LoadModule: "synaptics"
[36.740] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[37.190] (II) Module synaptics: vendor="X.Org Foundation"
[37.191]compiled for 1.16.0.901, module version = 1.8.99
[37.191]Module class: X.Org XInput Driver
ashok@localhost:~$ cinnamon --replace
  JS LOG: About to start Cinnamon
Window manager warning: Trying to remove non-existent custom keybinding 
"magnifier-zoom-in".
Window manager warning: Trying to remove non-existent custom keybinding 
"magnifier-zoom-out".

(cinnamon:2234): Clutter-WARNING **: Attempting to add actor of type 
'StBoxLayout' to a container of type 'StButton', but the actor has already a 
parent of type 'StButton'.

(cinnamon:2234): Clutter-WARNING **: Attempting to add actor of type 
'StBoxLayout' to a container of type 'StButton', but the actor has already a 
parent of type 'StButton'.

(cinnamon:2234): Clutter-WARNING **: Attempting to add actor of type 
'StBoxLayout' to a container of type 'StButton', but the actor has already a 
parent of type 'StButton'.

(cinnamon:2234): Clutter-WARNING **: Attempting to add actor of type 
'StBoxLayout' to a container of type 'StButton', but the actor has already a 
parent of type 'StButton'.
Window manager warning: Trying to remove non-existent custom keybinding 
"gTile-close".
Window manager warning: Trying to remove non-existent custom keybinding 
"gTile-tile1".
Window manager warning: Trying to remove non-existent custom keybinding 
"gTile-tile2".
Window manager warning: Trying to remove non-existent custom keybinding 
"gTile-k-left".
Window manager warning: Trying to remove non-existent custom keybinding 
"gTile-k-right".
Window manager warning: Trying to remove non-existent custom keybinding 
"gTile-k-up".
Window manager warning: Trying to remove non-existent custom keybinding 
"gTile-k-down".
Window manager warning: Trying to remove non-existent custom keybinding 
"gTile-k-left-meta".
Window manager warning: Trying to remove non-existent custom keybinding 

Re: Please help me resize my ext4 file system to size > 16TB

[Jonathan Marquardt]

On Sun, Jun 11, 2017 at 05:01:36PM -0500, Ram Ramesh wrote:
> Hi,
> 
>   I have kernel 3.13 and e2fsprog 1.42.9 (as part of mybuntu 14.04.5 LTS).
> With this, is it possible to resize2fs my ext4 RAID6 /dev/md0 to 24TB (ie
> >16TB)? If so, please help me get there. If not, please recommend the
> upgrades needed to the setup before this can be done. So, far, my google
> says I need to do "tune2fs -O extents,uninit_bg,dir_index /dev/md0" which I
> already did and I still get the dreaded message "resize2fs: New size too
> large to be expressed in 32 bits."
> 
> There are mentions of a 64bit option for the ext4 file system. I can see how
> this relates to the error message from resize2fs, but I do not know what I
> should do to get that update done for my /dev/md0. Also all of the message
> that I come across relating to 64bit option, only talk about  how to
> *create* a brand new file system with 64bit. None of them tell me how to
> convert existing one. In fact, many of them scare me saying that it will be
> unsupported in older kernels. I am not really sure if my kernel is too old
> or not. Also, they talk about a switch -b for resize2fs that is not
> supported in the version installed currently on my system/release.
> 
> Pleas help me figure out the correct sequence of steps. What packages need
> update, if current kernel/release is ok? Or, do I need to upgrade to a newer
> release before this is possible?
> 
> Thanks
> Ramesh
> 

I think you ran into this problem:
http://blog.ronnyegner-consulting.de/2011/08/18/ext4-and-the-16-tb-limit-now-solved/

I know of no way to get resize2fs to work with partitions larger than 16 TB,
however in the blog post it's explained how to make mke2fs work with such
sizes by editing /etc/mke2fs.conf. Not sure if this is an option for you
though.
-- 
4096R/1224DBD299A4F5F3
47BC 7DE8 3D46 2E8B ED18  AA86 1224 DBD2 99A4 F5F3


signature.asc
Description: Digital signature

Re: Oplossing voor mount-problemen (NFS en Webdav)

[Paul van der Vlis]

Op 12-06-17 om 14:06 schreef Richard Lucassen:
> On Tue, 30 May 2017 13:30:20 +0200
> Paul van der Vlis  wrote:
> 
>> Ik heb nu een oplossing waar ik blij mee ben, alhoewel het eigenlijk
>> een work-arround is. Ik zet in /etc/crontab het volgende regeltje en
>> dat lijkt te helpen:
>>
>> @reboot root /bin/sleep 10; /bin/mount -a > /tmp/mount-log 2>&1
>>
>> Als ik die sleep kort zet, bijvoorbeeld op "1", dan zie ik regelmatig
>> een melding als "hostname niet gevonden". Het lijkt er dus op dat het
>> probleem komt omdat de DNS resolving nog niet werkt.
> 
> [beetje laat]
> 
> Draait de DNS op de host zelf of draait-ie extern? Je zou als test de
> entry ook even in de hosts file kunnen opnemen.

Ook een interessante oplossing inderdaad...

Groeten,
Paul




-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: Oplossing voor mount-problemen (NFS en Webdav)

[Richard Lucassen]

On Tue, 30 May 2017 13:30:20 +0200
Paul van der Vlis  wrote:

> Ik heb nu een oplossing waar ik blij mee ben, alhoewel het eigenlijk
> een work-arround is. Ik zet in /etc/crontab het volgende regeltje en
> dat lijkt te helpen:
> 
> @reboot root /bin/sleep 10; /bin/mount -a > /tmp/mount-log 2>&1
> 
> Als ik die sleep kort zet, bijvoorbeeld op "1", dan zie ik regelmatig
> een melding als "hostname niet gevonden". Het lijkt er dus op dat het
> probleem komt omdat de DNS resolving nog niet werkt.

[beetje laat]

Draait de DNS op de host zelf of draait-ie extern? Je zou als test de
entry ook even in de hosts file kunnen opnemen.

-- 
richard lucassen
http://contact.xaq.nl/

Re: Primera versio d'un paquet

[Alex Muntada]

Narcis Garcia:

> Si per exemple faig:
> 
> $ LANG=en apt-cache show x11vnc | grep -ie '^Version:'
> 
> veig les versions disponibles al repositori per un paquet, però no estic
> segur de si estan ordenades de nova a antiga o només segons es recorden
> a la memòria cau d'APT.

Jo només veig una versió:

$ LANG=en apt-cache show x11vnc | grep -ie '^Version:'
Version: 0.9.13-1.2+b2

> Temo que si aplico |sort per ordenar-les alfabèticament, se'm pugui
> colar una versió 9 com a més nova que una 10.

Pots utilitzar «|sort -n» per indicar que vols que ordeni números
però això no funciona amb les versions: la versió 0.10 és més gran
que la 0.9 però numèricament 0.9 és més gran que 0.10.

El millor que pots fer és utilitzar alguna llibreria que faci
les comparacions de versió de Debian, per exemple Dpkg::Version
per a Perl té la funció «version_compare» (imagino que hi deu
haver llibreries similars per d'altres llenguatges). Et caldrà
instal·lar el paquet libdpkg-perl (potser ja el tens si havies
instal·lat dpkg-dev abans).

Per exemple, donada una llista de versions desordenades, aquesta
ordre retorna la versió més petita (posició 0 dels arguments
ordenats amb version_compare):

$ perl -MDpkg::Version -lE 'say((sort version_compare @ARGV)[0])' 0.10 0.9 0.5 
0.100
0.5

Salut,
Alex

Re: Celebració Debian Stretch al Tagamanent

[Alex Muntada]

Simó Albert i Beltran:

> Per tal de celebrar la sortida de la Debian Stretch us proposem
> pujar al Tagamanent.

Com ja vaig comentar, aquest dia tenim un altre compromís. Espero
que us ho passeu molt bé :)

Salut i Debian!
Alex

Re: Grave bug when playing flash videos

[Darac Marjal]

On Sun, Jun 11, 2017 at 10:50:17PM +0200, Pétùr wrote:

I have a serious bug when using flashplayer in debian sid.

This bug freezes everything and I have to do a hard reboot. It happens
with flashplugin and pepperflash when I play a video with flash (both
tested with firefox and chromium). Today I am using pepperflash,
installed by the package browser-plugin-freshplayer-pepperflash.

The bug could occur after playing 2s or 2h. When I play a flash video, I
have ~50% chances to be affected.


Have you tried switching to a VT and back when this happens? There was a
bug in... I *think* it was something like opengl ... recently, whereby a
bunch of unrelated programs (chrome/chromium included) could freeze the
display. Switching away from X and back caused the display to refresh
and things would work again (for a time).



I have some difficulties to see where it comes from. I need some help.

Here is the /var/log/debug for the time of the bug (occurred today at
21:25) :

https://hastebin.com/hupeqituji.sql

In /var/log/daemon.log I have some inconsistencies at 21:25:28
represented by:

^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@...


This is less's representation of null characters and is an artefact of
journaling file systems. Syslog has told the file system "I'm about to
write X bytes to /var/log/daemon.log" and then, at some point during the
writing of that, you've killed the power. During either fsck or mount
(depending on the file system), the journal is replayed - that is, there
is a log saying "X bytes were being writen to /var/log/daemon.log". Now,
most of those bytes never made it to the disk, but the record is still
there. So the file grows by X bytes of nothing. Now the file system is
consistent (the metadate, at least, the idea being that it's better to
have SOME of the file still there, rather than a broken filesystem)



followed by:
Jun 11 21:25:28 punda systemd-modules-load[218]: Inserted module 'lp'
Jun 11 21:25:28 punda systemd-modules-load[218]: Inserted module 'ppdev'
Jun 11 21:25:28 punda systemd[1]: Starting Flush Journal to Persistent
Storage...
Jun 11 21:25:28 punda systemd[1]: Started Load/Save Random Seed.
Jun 11 21:25:28 punda systemd[1]: Started Flush Journal to Persistent
Storage.
Jun 11 21:25:28 punda systemd[1]: Started Create Static Device Nodes in
/dev.
Jun 11 21:25:28 punda systemd[1]: Starting udev Kernel Device Manager...
Jun 11 21:25:28 punda systemd[1]: Started udev Coldplug all Devices.
Jun 11 21:25:28 punda systemd[1]: Started Set the console keyboard layout.
Jun 11 21:25:28 punda systemd[1]: Reached target Local File Systems (Pre).

The same in syslog (a bunch of ^@^@^@^@^@^@^@^@^@^@^@^@^@^@...
followed by the reboot informations).

Does someone have a idea?



--
For more information, please reread.


signature.asc
Description: PGP signature

Re: Compiler segfault when building the kernel

[Adrian Bunk]

On Fri, Jun 09, 2017 at 07:58:12AM -0400, Celejar wrote:
> Hi,
> 
> I've been building kernels (vanilla from upstream) for years with
> kernel-package (typical command line: "time make-kpkg -j2 --initrd
> --revision 1.custom kernel_image"; .kernel-pkg.conf contains just the
> line "root_cmd = fakeroot") without problem. Recently, the builds have
> begun to fail with messages like these:
> 
> *
> 
> > In file included from ./include/linux/percpu-rwsem.h:8:0,
> >  from ./include/linux/fs.h:30,
> >  from ./include/linux/pagemap.h:8,
> >  from block/partitions/check.h:1,
> >  from block/partitions/msdos.c:23:
> > ./include/linux/rcu_sync.h:29:48: internal compiler error: Segmentation 
> > fault
> >  enum rcu_sync_type { RCU_SYNC, RCU_SCHED_SYNC, RCU_BH_SYNC };
> > ^
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See  for instructions.
> >   CC  fs/posix_acl.o
> > The bug is not reproducible, so it is likely a hardware or OS problem.
> 
> *
> 
> > In file included from ./include/linux/linkage.h:6:0,
> >  from ./include/linux/kernel.h:6,
> >  from ./include/linux/list.h:8,
> >  from ./include/linux/module.h:9,
> >  from lib/fonts/font_8x16.c:8:
> > ./include/linux/export.h:63:22: internal compiler error: Segmentation fault
> >   static const struct kernel_symbol __ksymtab_##sym  \
> >   ^
> > ./include/linux/export.h:93:25: note: in expansion of macro 
> > ‘___EXPORT_SYMBOL’
> >  #define __EXPORT_SYMBOL ___EXPORT_SYMBOL
> >  ^
> > ./include/linux/export.h:97:2: note: in expansion of macro ‘__EXPORT_SYMBOL’
> >   __EXPORT_SYMBOL(sym, "")
> >   ^
> > lib/fonts/font_8x16.c:4633:1: note: in expansion of macro ‘EXPORT_SYMBOL’
> >  EXPORT_SYMBOL(font_vga_8x16);
> >  ^
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> 
> This occurred immediately following a cleaning of the source tree
> ("make-kpkg ... clean"), the first one I've done in quite some time, so
> I'm pretty sure that that's what triggered this, whatever the
> underlying problem actually is.
> 
> Googling suggests that this sort of thing can be triggered by race
> conditions caused by build systems improper handling of
> concurrency,e.g.:
> 
> https://askubuntu.com/questions/343490/the-bug-is-not-reproducible-so-it-is-likely-a-hardware-or-os-problem

That is just an incorrect answer from some random person.

Missing dependencies produce different kinds of errors,
never internal compiler errors.

> For the last year or so, I've been building with -j2, so I tried again
> without it. I still got the same error, but when I once again did a
> clean and then rebuilt without -j2, the build succeeded.
> 
> Any ideas? Is this a bug I should be filing against kernel-package (or
> anywhere else)?

Based on what you describe (the problem is not reproducible and the 
problem started recently), there is a nearly 100% chance that it is
caused by a hardware defect on your machine.

Were there any hardware changes or was there a a move of the machine recently?
Are all fans still working?
Do all temperatures look normal?
Do all capacitors on the mainboard look OK?
Does a RAM testing tool like memtest86 succeed?
...

> Celejar

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

He

[Brittany Barnard]

Sent from my iPhone

Primera versio d'un paquet

[Narcis Garcia]

Necessito automatitzar una gestió, que és la d'instal·lar la versió més
antiga d'un paquet disponible al repositori de la distribució.
Si per exemple faig:

$ LANG=en apt-cache show x11vnc | grep -ie '^Version:'

veig les versions disponibles al repositori per un paquet, però no estic
segur de si estan ordenades de nova a antiga o només segons es recorden
a la memòria cau d'APT.

Temo que si aplico |sort per ordenar-les alfabèticament, se'm pugui
colar una versió 9 com a més nova que una 10.

-- 


__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.

Re: Fwd: xorg.conf dos pantallas

[Antonio Trujillo Carmona]

El 09/06/17 a las 15:36, marcelo escribió:
>
>
> El 09/06/17 a las 03:36, Antonio Trujillo Carmona escribió:
>> El 09/06/17 a las 02:16, marcelo escribió:
>>>
>>>
>>>
>>>  Mensaje reenviado 
>>> Asunto: xorg.conf dos pantallas
>>> Fecha: Thu, 8 Jun 2017 21:12:10 -0300
>>> De: marcelo 
>>> A: debian-user-spanish@lists.debian.org
>>>
>>>
>>>
>>> Hola amigos.
>>>
>>> El problema que tengo con mi Debian 8 xfce es el siguiente. Cuando
>>> inicio no me reconoce la resolución del monitor y lo tengo que hacer a
>>> mano cada vez que inicio sesión con la aplicación "ArandR".
>>>
>>> Estuve investigando pero no me animé a tocar. Copio el resultado de
>>> xrandr
>>>
>>> Screen 0: minimum 320 x 200, current 1280 x 768, maximum 16384 x 16384
>>> LVDS connected 1280x768+0+0 (normal left inverted right x axis y axis)
>>> 344mm x 194mm
>>>1366x768  60.01 +
>>>1280x768  60.01*
>>>1280x720  60.01
>>>1024x768  60.01
>>>800x600   60.01
>>>640x480   60.01
>>> DFP1 connected 1280x768+0+0 (normal left inverted right x axis y axis)
>>> 510mm x 290mm
>>>1920x1080 60.00 +  50.0059.9450.0060.00 59.94
>>>1776x1000 50.0059.9450.0059.94
>>>1680x1050 59.95
>>>1400x1050 59.95
>>>1600x900  59.95
>>>1280x1024 60.02
>>>1440x900  59.95
>>>1280x960  60.00
>>>1152x864  59.96
>>>1280x768  60.00*
>>>1280x720  50.0060.0059.94
>>>1024x768  60.00
>>>1152x648  50.0059.94
>>>800x600   60.32
>>>720x480   60.0059.94
>>>640x480   60.0059.94
>>> CRT1 disconnected (normal left inverted right x axis y axis)
>>>
>>> y ahora copio mi Xorg.conf
>>>
>>> Section "ServerLayout"
>>> Identifier "aticonfig Layout"
>>> Screen  0  "aticonfig-Screen[0]-0" 0 0
>>> EndSection
>>>
>>> Section "Module"
>>> EndSection
>>>
>>> Section "Monitor"
>>> Identifier   "aticonfig-Monitor[0]-0"
>>> Option  "VendorName" "ATI Proprietary Driver"
>>> Option  "ModelName" "Generic Autodetecting Monitor"
>>> Option  "DPMS" "true"
>>> EndSection
>>>
>>> Section "Device"
>>> Identifier  "aticonfig-Device[0]-0"
>>> Driver  "fglrx"
>>> BusID   "PCI:0:1:0"
>>> EndSection
>>>
>>> Section "Screen"
>>> Identifier "aticonfig-Screen[0]-0"
>>> Device "aticonfig-Device[0]-0"
>>> Monitor"aticonfig-Monitor[0]-0"
>>> DefaultDepth 24
>>> SubSection "Display"
>>> Viewport   0 0
>>> Depth 24
>>> EndSubSection
>>> EndSection
>>>
>>> Si me pueden ayudar se los voy a agradecer mucho
>>>
>>> Me olvidé de poner lo mas importante. El monitor que tiene probelmas
>>> es el DFP1, cuya resolución es de 1920x1080.
>>> Disculpen estos errores de novato
>>>
>>>
>>
>> Para configurar en modo gráfico existe un programa llamado xrandr.
>> Si no ves muy claro como va la cosa instálate el "lxrandr" (una
>> versión para lxde), veras la opción de guardar, lo que guardes lo
>> pondrá en un directorio escondido
>> "~/.config/autostart/lxrandr-autostart.desktop", si no se te ejecuta
>> (por que no usas el lxde), puedes ver el contenido con "cat" y copiar
>> lo que hay en la linea Exec=sh -c'[lo que tienes que copiar]' al
>> fichero "~/.xinitrc".
>> -- 
>>
> Uso xfce. Hay algun programa como lxrandr para xfce?
> También tengo el archivo xinitrc ahí tendría que poner la
> linea correspondiente de xrandr?
>

Perdona pero no se que tal funciona la configuración automatica de
lxrandr en xfce (no lo uso), lo que te dije es que lo usaras, despues de
darle a guardar pueden ocurrir 2 cosas, a que funcione, pues eso, B que
no funcione, entonces es cuando debes de copiar la linea que te dije a
tu .xinitrc

-- 

*Antonio Trujillo Carmona*

*Técnico de redes y sistemas.*

*Subdirección de Tecnologías de la Información y Comunicaciones*

Servicio Andaluz de Salud. Consejería de Salud de la Junta de Andalucía

_antonio.trujillo.sspa@juntadeandalucia.es_

Tel. +34 670947670 747670)