Is this sources.list correct?

[Fjfj109]

On Stretch, upgraded from Jessie. https://paste.debian.net/933553/

Re: Debian + vidéosurveillance

[Pierre L.]

Salut,

On peut regarder du coté de "motion" qui peut être utilisé à cette fin.
Perso, uniquement utilisé avec 1 cam/ordi.
Streaming vidéo sur le réseau, enregistrement d'images toutes les x
secondes dès qu'un mouvement est détecté... etc.
Assez simple à mettre en place, tu peux t'inspirer de ces quelques
lignes de config :
https://blueberry4pi.com/2012/10/29/video-surveillance-avec-raspberry-pi/

Mais tu recherches probablement des logiciels beaucoup plus complets,
qui doivent gérer plusieurs cams sur 1 écran final à mon avis ? Mais là
ca me dépasse :p

Good luck ;)


Le 22/05/2017 à 00:51, kaliderus a écrit :
> Le bonjour,
>
> Connaissez-vous des solutions de vidéosurveillance qui tournent avec
> notre Debian préférée ?
> Si vous avez quelques références "professionnelles" j'apprécierai...
>
>
> Merci
>




signature.asc
Description: OpenPGP digital signature

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Michael Milliman]

On 05/21/2017 07:24 PM, Anil Duggirala wrote:
> Thanks everyone for your responses. I did not expect such quick and full
> response. I also really don't believe it has anything to do with
> partitioning (Debian deleted the partitions and created exactly
> corresponding partitions with guided partitioning). 
> More info: When I installed initially with LXDE, I had horrible graphics
> and no touchpad, upon installing the Linux-image from backports (4.9),
> these problems were resolved. I have tried installing Linux-image 4.9
> from backports (using the command line) now again, the problem persists.
> However, in the debian-laptop users list, I guy who said he has the
> exact same laptop (Asus X441SA) said he is running Gnome-Classic
> (Gnome), I have tried asking him if he got this problem but have
> received no response from him.
> All commands outputs here are in a new installation (I have installed 3
> times now), with the regular kernel (3.16)
> Outputs:
> inxi commands say 'command not found'
> lspci  :
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
> [8086:22b1] (rev 35)
> Subsystem: ASUSTek Computer Inc. Device [1043:1290]
> 00:0b.0 Signa processing controller [1180]: Intel Corporation Device 
> [8086:22dc] (rev 35)
> Subsystem: ASUSTek Computer Inc. Device [1043:1290]
> 00:13.0 SATA Controller [0106]: Intel Corporation Device [8086:22a3]
> (rev 35)
> 
> I have pasted Xorg log at https://paste.debian.net/933539
> 
> Should I just try Mate or XFCE?? is it possible that works?
> 
> thanks a lot,
> 
Sorry about the side conversation on partitioning.  Clearly your problem
is not the partitioning scheme.  As Felix found, the key information in
lspci output is the device id (8086:22b1) for your graphics controller
is not supported in the stable distribution of Debian.  It is, however,
supported in the Stretch distribution.  I am running Stretch currently,
and it is a good working distribution, with the vast majority of major
bugs already worked out of it.  You should be able to run Stretch
without problems.  I concur with Felix, install Stretch and enjoy :)
> 
> On Sun, May 21, 2017, at 03:57 PM, Jimmy Johnson wrote:
>> On 05/21/2017 12:52 PM, Michael Milliman wrote:
>>>
>>>
>>> On 05/21/2017 12:23 PM, Jimmy Johnson wrote:
>>
> However, the OP's post does not mention anything of this nature.  The OP
> deleted the existing Debian partition(s) leaving the existing Windows
> partition(s) alone.  No mention was made of the ordering of the
> partitions on the drive.  The OP then re-installed Debian with the
> Debian installer, effectively starting from scratch with Debian.
> Everything seems to work, except GNOME is crashing on boot.  There are
> several things that can cause this, and I have caused some of them on my
> system before, however the fact that this is a fresh install limits the
> possible causes, the most likely of them being a missing (non-free?)
> video driver or some such required by GNOME to run properly.  The way
> the OP went about scrapping and re-installing the Debian system is valid
> and should not have caused a problem under normal circumstances.  Hence
> the suspicion of a missing driver (again probably non-free, and likely
> Radeon as well...I've had similar issues with my laptop).
>>
 I have a Lenovo laptop with the problem you describe and it's a
 kernel/video/plasma problem, works fine with the old Sid 4.7 kernel but
 not with the 4.9, first boot is ok, on restart you will not get the DM
 or x and may freeze up.  Sometimes switching back and forth on the
 consoles will get you x, alt+ctrl+F2-F1-F3-F7. Jessie back-ports are
 also 4.9 and don't work right too. The problem here is an
 Intel-965-mobile, I'm going to install the Jessie kernel and see if that
 works or maybe a Ubuntu kernel, I think they are 4.4 and 4.8, I know the
 4.4 will work, for me anyways, but I have to do something cause the 4.7
 kernel is old now and not getting security updates.
>>> Hey, its better than the 3.16 kernel I was stuck with for a long time up
>>> until just a couple of months. :)  In my case, laptop would boot, but
>>> the screen would be completely blanked out.  If I caught the boot
>>> process at just the right time with a alt+ctl+F1, I could get it to
>>> finish booting, if I missed the window, it was power-off, power-on!! :(
>>> The first-boot on 3.16  would do usually boot into software emulation
>>> mode, and then I installed the Radeon drivers, and everything was OK.  I
>>> have 4.9 running now and working fine. Video drivers and wifi drivers
>>> have been my bane for many a year!
>>
>> I had to remove all Debian firmware and installed linux-image-generic 
>> and linux-headers-generic and Ubuntu's firmware-linux, but now it's 
>> running 4.4.0-21-generic, it's booting fine and I can get updates too. 
>> So this kernel problem I've had for more than a year is fixed, I was 

Re: Error on install: Repository "couldn't be accessed"

[Matthew McKinnon]

On Mon, May 22, 2017 at 01:11:43AM +0100, Brian wrote:
> > I think it should be changed when Stretch becomes stable? Just a thought.
> 
> It could be done now. Hint, hint. :)
> 
> -- 
> Brian.
> 

Well I made my first contribution to the Debian Community. Made myself an 
account on the Wiki. It has now been updated with the new link - 
http://deb.debian.org

Thanks
Matt

Re: [ANNOUNCE] apt-offline 1.8.0 Released

[Jhoanir Torres]

Sounds great!

I'll put it in the stuff list to try out.



El 21 may. 2017 22:31, "Ritesh Raj Sarraf"  escribió:

> Hello World,
>
> It gives me immense pleasure to announce the release of apt-offline,
> version 1.8.0
>
> For a detailed release announcement, please visit:
> https://www.researchut.com/blog/apt-offline-180
>
>
> This release is a major update, porting apt-offline to Python3 and Py3Qt5.
>
>
> --
> Ritesh Raj Sarraf | http://people.debian.org/~rrs
> Debian - The Universal Operating System

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Felix Miata]

Anil Duggirala composed on 2017-05-21 19:24 (UTC-0500):

> More info: When I installed initially with LXDE, I had horrible graphics
> and no touchpad, upon installing the Linux-image from backports (4.9),
> these problems were resolved. I have tried installing Linux-image 4.9
> from backports (using the command line) now again, the problem persists.
> However, in the debian-laptop users list, I guy who said he has the
> exact same laptop (Asus X441SA) said he is running Gnome-Classic
> (Gnome), I have tried asking him if he got this problem but have
> received no response from him.
> All commands outputs here are in a new installation (I have installed 3
> times now), with the regular kernel (3.16)
> Outputs:
> inxi commands say 'command not found'

Install it, then run it:

apt-get install inxi
inxi -c0 -G

> lspci  :
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
> [8086:22b1] (rev 35)

https://wiki.debian.org/InstallingDebianOn/Intel/NUC5PPYH reports your 8086:22b1
Intel gfxchip is not supported on (standard with 3.16 kernel) Debian Jessie, but
is supported on Debian Stretch.

> I have pasted Xorg log at https://paste.debian.net/933539

from that log:

(EE) open /dev/dri/card0: No such file or directory
(II) FBDEV(1): using default device

confirms your gfxchip is not supported by the software installed and is falling
back to a generic driver that is not even minimally usable with Gnome and/or 
GDM.

> Should I just try Mate or XFCE?? is it possible that works?
You should install Stretch. Even with Mate or Xfce video performance will be
poor at best in Jessie unless you can install whatever is required from 
backports.
-- 
"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/

[ANNOUNCE] apt-offline 1.8.0 Released

[Ritesh Raj Sarraf]

Hello World,

It gives me immense pleasure to announce the release of apt-offline,
version 1.8.0

For a detailed release announcement, please visit:
https://www.researchut.com/blog/apt-offline-180


This release is a major update, porting apt-offline to Python3 and Py3Qt5.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

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

Re: error en instalacion de mysql en debian 8 jesie

[Felipe Perry]

Debes intalar:

- default-mysql-server
- default-mysql-client

Si eres nuevo te recomiendo mucho que uses Synaptic para manejar tus
paquetes, te servirá para tener una visión completa del software.

- sudo apt install synaptic

El 21 de mayo de 2017, 19:52, Oscar Martinez 
escribió:

> buenas, estoy tratando de instalar mysql-server en debian 8 jesie
>
> me dice que mysql no es un candidato para la instalacion la verdad no
> conozco bien linux estoy aprendiendo he cambiado repositorios
> instale
>
> mysql-apt-repo-quick-guide-en.html-chapter.tar
>
> y no he podido pasar de ese punto he observado que cuando hago el
>
> apt-get update y apt-get upgrade me dice fallo en los repo- mysql
>
> quien me puede ayudar o darme una guia para determinar cual es mi error o
> cual es el paso que estoy omiendo gracias
>

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Anil Duggirala]

Thanks everyone for your responses. I did not expect such quick and full
response. I also really don't believe it has anything to do with
partitioning (Debian deleted the partitions and created exactly
corresponding partitions with guided partitioning). 
More info: When I installed initially with LXDE, I had horrible graphics
and no touchpad, upon installing the Linux-image from backports (4.9),
these problems were resolved. I have tried installing Linux-image 4.9
from backports (using the command line) now again, the problem persists.
However, in the debian-laptop users list, I guy who said he has the
exact same laptop (Asus X441SA) said he is running Gnome-Classic
(Gnome), I have tried asking him if he got this problem but have
received no response from him.
All commands outputs here are in a new installation (I have installed 3
times now), with the regular kernel (3.16)
Outputs:
inxi commands say 'command not found'
lspci  :
00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:22b1] (rev 35)
Subsystem: ASUSTek Computer Inc. Device [1043:1290]
00:0b.0 Signa processing controller [1180]: Intel Corporation Device 
[8086:22dc] (rev 35)
Subsystem: ASUSTek Computer Inc. Device [1043:1290]
00:13.0 SATA Controller [0106]: Intel Corporation Device [8086:22a3]
(rev 35)

I have pasted Xorg log at https://paste.debian.net/933539

Should I just try Mate or XFCE?? is it possible that works?

thanks a lot,


On Sun, May 21, 2017, at 03:57 PM, Jimmy Johnson wrote:
> On 05/21/2017 12:52 PM, Michael Milliman wrote:
> >
> >
> > On 05/21/2017 12:23 PM, Jimmy Johnson wrote:
> 
> >>> However, the OP's post does not mention anything of this nature.  The OP
> >>> deleted the existing Debian partition(s) leaving the existing Windows
> >>> partition(s) alone.  No mention was made of the ordering of the
> >>> partitions on the drive.  The OP then re-installed Debian with the
> >>> Debian installer, effectively starting from scratch with Debian.
> >>> Everything seems to work, except GNOME is crashing on boot.  There are
> >>> several things that can cause this, and I have caused some of them on my
> >>> system before, however the fact that this is a fresh install limits the
> >>> possible causes, the most likely of them being a missing (non-free?)
> >>> video driver or some such required by GNOME to run properly.  The way
> >>> the OP went about scrapping and re-installing the Debian system is valid
> >>> and should not have caused a problem under normal circumstances.  Hence
> >>> the suspicion of a missing driver (again probably non-free, and likely
> >>> Radeon as well...I've had similar issues with my laptop).
> 
> >> I have a Lenovo laptop with the problem you describe and it's a
> >> kernel/video/plasma problem, works fine with the old Sid 4.7 kernel but
> >> not with the 4.9, first boot is ok, on restart you will not get the DM
> >> or x and may freeze up.  Sometimes switching back and forth on the
> >> consoles will get you x, alt+ctrl+F2-F1-F3-F7. Jessie back-ports are
> >> also 4.9 and don't work right too. The problem here is an
> >> Intel-965-mobile, I'm going to install the Jessie kernel and see if that
> >> works or maybe a Ubuntu kernel, I think they are 4.4 and 4.8, I know the
> >> 4.4 will work, for me anyways, but I have to do something cause the 4.7
> >> kernel is old now and not getting security updates.
> > Hey, its better than the 3.16 kernel I was stuck with for a long time up
> > until just a couple of months. :)  In my case, laptop would boot, but
> > the screen would be completely blanked out.  If I caught the boot
> > process at just the right time with a alt+ctl+F1, I could get it to
> > finish booting, if I missed the window, it was power-off, power-on!! :(
> > The first-boot on 3.16  would do usually boot into software emulation
> > mode, and then I installed the Radeon drivers, and everything was OK.  I
> > have 4.9 running now and working fine. Video drivers and wifi drivers
> > have been my bane for many a year!
> 
> I had to remove all Debian firmware and installed linux-image-generic 
> and linux-headers-generic and Ubuntu's firmware-linux, but now it's 
> running 4.4.0-21-generic, it's booting fine and I can get updates too. 
> So this kernel problem I've had for more than a year is fixed, I was 
> going to wait for Stretch to go final but I've waited long enough. This 
> was on two systems Sid/Testing and Stretch. The version I'm using is 
> Ubuntu 16.04, just in case the OP wants to try it, I used Synaptic to do 
> the work and pinned the Debian release so not to pickup any other Ubuntu 
> packages not needed and I was able to rid more than 800Mb of Debian 
> kernel's on each system.
> -- 
> Jimmy Johnson
> 
> Debian Sid/Testing - Plasma 5.8.6 - EXT4 at sda15
> Registered Linux User #380263
> 

Re: Debian Developers Have Been Listening!

[Brian]

On Mon 22 May 2017 at 08:28:31 +0900, Joel Rees wrote:

> On Mon, May 22, 2017 at 6:44 AM, Brian  wrote:
> > On Sat 20 May 2017 at 17:06:56 +0100, Michael Fothergill wrote:
> >
> >> On 20 May 2017 at 15:59, Brad Rogers  wrote:
> >>
> >> > On Sat, 20 May 2017 14:20:15 +0100
> >> > Michael Fothergill  wrote:
> >> >
> >> > Hello Michael,
> >> >
> >> > >with systemd running on it to the old sysvinit format then why is there
> >> > >all this sturm und drang and spam on this subject...??
> >> >
> >> > People complain about all sorts of things.  Changing something.  Not
> >> > changing something.  Sometimes, it's even the same people.
> >> >
> >>
> >> Now I see why the developers have their own mailing list...
> >
> > A misconception. They don't.
> >
> 
> Care to unpack that, so you won't be misunderstood?

Apart from -private, no list is for the exclusive use of Developers and
Maintainers.

Re: Error on install: Repository "couldn't be accessed"

[Brian]

On Mon 22 May 2017 at 09:53:56 +1000, Matthew McKinnon wrote:

> On Mon, May 22, 2017 at 12:19:40AM +0100, Brian wrote:
> > On Mon 22 May 2017 at 08:52:07 +1000, Matthew McKinnon wrote:
> > 
> > > On Sun, May 21, 2017 at 08:35:17AM -0400, RavenLX wrote:
> > > > On 05/18/2017 09:06 AM, Liam O'Toole wrote:
> > > > [snipped...]
> > > > >>I had that happened. I then changed all the http://ftp.* to
> > > > >>http://httpredir.debian.org. I learned of this here:
> > > > >>
> > > > >>https://wiki.debian.org/SourcesList#Example_sources.list
> > > > >>
> > > > >>Then I apt-get update and it worked fine from there.
> > > > >
> > > > >Just a FYI: the recommended redirector is now http://deb.debian.org/.
> > > > >
> > > > 
> > > > Thank you! The wiki probably either needs updating or was updated since 
> > > > I
> > > > looked last.
> > > > 
> > > 
> > > Wiki still needs updating. Still showing
> > 
> > Would you care to nominate someone to do the work of updating it. :)
> > 
> 
> As we are still in Jessie. It still shows Jessie so I would think that this 
> is correct.

Support for httpredir.debian.org has been discontinued. Versions
of aptfrom 0.7.21 onwards support http redirections. Support for
httpredir.debian.org has been discontinued.

> I think it should be changed when Stretch becomes stable? Just a thought.

It could be done now. Hint, hint. :)

-- 
Brian.

Re: Error on install: Repository "couldn't be accessed"

[Matthew McKinnon]

On Mon, May 22, 2017 at 12:19:40AM +0100, Brian wrote:
> On Mon 22 May 2017 at 08:52:07 +1000, Matthew McKinnon wrote:
> 
> > On Sun, May 21, 2017 at 08:35:17AM -0400, RavenLX wrote:
> > > On 05/18/2017 09:06 AM, Liam O'Toole wrote:
> > > [snipped...]
> > > >>I had that happened. I then changed all the http://ftp.* to
> > > >>http://httpredir.debian.org. I learned of this here:
> > > >>
> > > >>https://wiki.debian.org/SourcesList#Example_sources.list
> > > >>
> > > >>Then I apt-get update and it worked fine from there.
> > > >
> > > >Just a FYI: the recommended redirector is now http://deb.debian.org/.
> > > >
> > > 
> > > Thank you! The wiki probably either needs updating or was updated since I
> > > looked last.
> > > 
> > 
> > Wiki still needs updating. Still showing
> 
> Would you care to nominate someone to do the work of updating it. :)
> 

As we are still in Jessie. It still shows Jessie so I would think that this is 
correct.

I think it should be changed when Stretch becomes stable? Just a thought.

Thanks
Matt

error en instalacion de mysql en debian 8 jesie

[Oscar Martinez]

buenas, estoy tratando de instalar mysql-server en debian 8 jesie

me dice que mysql no es un candidato para la instalacion la verdad no
conozco bien linux estoy aprendiendo he cambiado repositorios
instale

mysql-apt-repo-quick-guide-en.html-chapter.tar

y no he podido pasar de ese punto he observado que cuando hago el

apt-get update y apt-get upgrade me dice fallo en los repo- mysql

quien me puede ayudar o darme una guia para determinar cual es mi error o
cual es el paso que estoy omiendo gracias

Re: Debian Developers Have Been Listening!

[Joel Rees]

On Fri, May 19, 2017 at 1:48 AM, Patrick Bartek  wrote:
>
> A while ago, I initiated the "If Linux Is About Choice ..." thread
> about why there is no choice of inits during an initial install.
>
> Since that time, I've tested several systemd-less distros[1] as well as
> Stretch as replacements for my aging Wheezy system.  With Stretch my
> plan was to see if I could replace systemd as the init without removing
> it just leaving its components (some or all as necessary) to meet
> dependencies without it breaking the system

???

> That way there would be no
> need for third party repos or jumping through hoops to keep a
> systemd-less working. I figured it would be a somewhat difficult, time
> consuming process. However, I made a discovery during these tests: The
> Debian developers had already done it for me.  They made switching from
> systemd as the init to sysvinit or runit easy just by issuing a couple
> commands. Here's what you do.

I thought that information came out several times in the thread you mention
having started -- that it was possible to install the base system, then
disable and remove the main systemd component, just leaving some
of the pieces that have been picked up as dependencies by other
packages.

Maybe the discussion of using more advanced techniques to keep from
ever installing systemd in the first place hid the information about the
removal approach.

If so, it would seem to be worthwhile to have this separate thread, as well.

> First, install Stretch as you normally would, systemd, et al.  I chose
> LXDE for the GUI as it has no direct systemd dependencies, and it uses
> Openbox as the window manager which I normally use in lieu of a desktop
> environment anyway.  This was quicker and easier testing-wise than
> starting with a terminal-based system as I normally would, and building
> up from there.
>
> To switch to sysvinit, as root:
>
>   apt-get install sysvinit-core
>
> and reboot.  Done!  systemd components are still on the hard drive,
> except systemd-sysv has been removed.  There is also no systemd
> supervision either as far as I can tell.
>
> To switch to runit-init is an easy 2-step process.  Do a standard
> install as before.[2]  Then add runit supervision first before
> installing runit-init. As root:
>
>   apt-get install runit-systemd
>
> reboot, then
>
>   apt-get install runit-init
>
> Reboot. Done!  The latter command removes systemd-sysv during the
> install.
>
> These new init set ups survive apt-get upgrade or dist-upgrade even if
> systemd components are upgraded.  Systemd as init does not get
> reactivated.  Tested and verified.  I can find no systemd pinning
> either.
>
> I now have two Stretch systems running in VirtualBox.  One a full LXDE
> desktop using runit for both the init and supervision, and the other
> with just Openbox and lxpanel as the GUI, and sysvinit and runit for
> supervison. No problems at all with either.
>
>
> B
>
> [1] AntiX, MX Linux, SalixOS and Void Linux.
>
> [2] With either above options, you can't go from an init other than
> systemd to another init.  apt-get install  fails due to
> systemd-sysv being missing.
>

Thanks for the report.


--
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 a bare cast.

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: Debian Developers Have Been Listening!

[Joel Rees]

On Mon, May 22, 2017 at 6:44 AM, Brian  wrote:
> On Sat 20 May 2017 at 17:06:56 +0100, Michael Fothergill wrote:
>
>> On 20 May 2017 at 15:59, Brad Rogers  wrote:
>>
>> > On Sat, 20 May 2017 14:20:15 +0100
>> > Michael Fothergill  wrote:
>> >
>> > Hello Michael,
>> >
>> > >with systemd running on it to the old sysvinit format then why is there
>> > >all this sturm und drang and spam on this subject...??
>> >
>> > People complain about all sorts of things.  Changing something.  Not
>> > changing something.  Sometimes, it's even the same people.
>> >
>>
>> Now I see why the developers have their own mailing list...
>
> A misconception. They don't.
>

Care to unpack that, so you won't be misunderstood?


--
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 a bare cast.

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: Error on install: Repository "couldn't be accessed"

[Brian]

On Mon 22 May 2017 at 08:52:07 +1000, Matthew McKinnon wrote:

> On Sun, May 21, 2017 at 08:35:17AM -0400, RavenLX wrote:
> > On 05/18/2017 09:06 AM, Liam O'Toole wrote:
> > [snipped...]
> > >>I had that happened. I then changed all the http://ftp.* to
> > >>http://httpredir.debian.org. I learned of this here:
> > >>
> > >>https://wiki.debian.org/SourcesList#Example_sources.list
> > >>
> > >>Then I apt-get update and it worked fine from there.
> > >
> > >Just a FYI: the recommended redirector is now http://deb.debian.org/.
> > >
> > 
> > Thank you! The wiki probably either needs updating or was updated since I
> > looked last.
> > 
> 
> Wiki still needs updating. Still showing

Would you care to nominate someone to do the work of updating it. :)

Re: Error on install: Repository "couldn't be accessed"

[Matthew McKinnon]

On Sun, May 21, 2017 at 08:35:17AM -0400, RavenLX wrote:
> On 05/18/2017 09:06 AM, Liam O'Toole wrote:
> [snipped...]
> >>I had that happened. I then changed all the http://ftp.* to
> >>http://httpredir.debian.org. I learned of this here:
> >>
> >>https://wiki.debian.org/SourcesList#Example_sources.list
> >>
> >>Then I apt-get update and it worked fine from there.
> >
> >Just a FYI: the recommended redirector is now http://deb.debian.org/.
> >
> 
> Thank you! The wiki probably either needs updating or was updated since I
> looked last.
> 

Wiki still needs updating. Still showing

deb http://httpredir.debian.org/debian jessie main
deb-src http://httpredir.debian.org/debian jessie main

Thanks for the tip on the new redirect :)

Matt

Debian + vidéosurveillance

[kaliderus]

Le bonjour,

Connaissez-vous des solutions de vidéosurveillance qui tournent avec
notre Debian préférée ?
Si vous avez quelques références "professionnelles" j'apprécierai...


Merci

Re: Questions after doing update and upgrade on Stretch

[David Wright]

On Sun 21 May 2017 at 22:18:11 (+0200), Dejan Jocic wrote:
> On 21-05-17, David Wright wrote:
> > -rw-r--r-- 1 root root  134839 Apr 27 16:52 config-3.2.0-4-686-pae
> > drwxr-xr-x 3 root root   12288 Apr 28 07:44 grub
> > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae
> > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae
> > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae
> > 
> > (I have to notice these upgrades myself because they overwrite
> > my edited version of /boot/grub/grub.cfg which I then replace.)
> > 
> 
> Sorry, but you are doing it wrong way. Grub 2 should not be customized
> by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and
> files in /etc/grub.d/. Reason is obvious, your customization is lost
> whenever something related to linux-image is upgraded. Just saying :)

Yes, it would be nice to use the Debian Way. But there is not enough
flexibility in their scripts to do what I want.

a) the logic of
 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to 
Linux
 #GRUB_DISABLE_LINUX_UUID=true
   is odd and, unfortunately, there's no facility for
 GRUB_ENABLE_LINUX_LABEL=true
   (I did have a shot at modifying the scripts, but it's less trivial
   than it would seem at first sight).

b) they insert entries for sysvinit and recovery but not for fsck.
   I modify the first subentry, using the ids fsck and fsck so I can use
   grub-reboot 'fsck>fsck'
   to invoke it from a script that also logs a timestamp. I refuse to
   type monstrosities like
   grub-reboot 'Advanced options for Debian 
GNU/Linux>gnulinux-advanced-7ccc1c1c-a690-418b-96c0-edcce6ebd3c1'

So it's far easier to write one python script to parse /run/udev/data,
automatically make the changes I want, and keep the original and
edited files as /boot/grub/grub.cfg-{uuids,edited}. After any upgrade,
if the former matches /boot/grub/grub.cfg, it gets overwritten by the
latter.

Cheers,
David.

Re: [RESOLU (presque)] Lire des vidéos sur Vimeo avec Firefox?

[Haricophile]

Le Sun, 21 May 2017 02:56:36 +0200,
Vincent Lefevre  a écrit :

> J'ai fini par trouver la cause du problème ici:
> 
>   https://askubuntu.com/questions/777489/vimeo-video-not-playing-in-firefox
> 
> J'avais media.autoplay.enabled à false. Le passer à true résout le
> problème... en quelque sorte, parce que ça a aussi un inconvénient
> de jouer les vidéos automatiquement sur les autres sites.

il y a des addons qui gèrent ça plus simplement que about:config que
se soit pour flash ou html5

-- 
haricoph...@aranha.fr 

Re: Questions after doing update and upgrade on Stretch

[Brian]

On Sun 21 May 2017 at 22:18:11 +0200, Dejan Jocic wrote:

> On 21-05-17, David Wright wrote:
> > On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote:
> > > > 
> > > As for number 1 can't say much about it, I do not get it either. But 2
> > > happens because you've used apt-get upgrade instead of apt-get
> > > dist-upgrade. Packages that will uninstall some packages already
> > > installed on your system and that will change some dependencies 
> > > require dist-upgrade.
> > 
> > Agreed.
> > 
> > > It happens always in case of linux-image packages. 
> > 
> > Is this¹ new with stretch? My linux-images upgrade just like any other
> > package; here's the penultimate occasion for jessie:
> > 
> > Start-Date: 2017-03-08  19:20:34
> > Commandline: apt-get upgrade
> > Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2)
> > End-Date: 2017-03-08  19:22:50
> > 
> > (The last one's log was rather larger.)
> 
> Ehh, sorry not sure if it is new with Stretch, can't remember for
> Jessie. I'm certain that it was like that on Stretch and on Ubuntu
> 16.04.

Rather than just a contrast, I was rather hoping to hear how David
Wright's observations (which I agree with)fit in with yours.

> > > It will leave your previous working linux-image on though, but will 
> > > uninstall one older than that, so you will always end up with chance to 
> > > boot in working kernel, if new one messes up some things.
> > 
> > Same question. My wheezy system has had at least 28 linux-image
> > upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1)
> > but there's still only one kernel image on the system:
> > 
> > -rw-r--r-- 1 root root  134839 Apr 27 16:52 config-3.2.0-4-686-pae
> > drwxr-xr-x 3 root root   12288 Apr 28 07:44 grub
> > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae
> > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae
> > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae
> > 
> > (I have to notice these upgrades myself because they overwrite
> > my edited version of /boot/grub/grub.cfg which I then replace.)
> > 
> > Cheers,
> > David.
> > 
> > ¹ I'm not disagreeing that something is holding back the upgrade
> > on this specific occasion, but this is unusual.
> 
> Sorry, but you are doing it wrong way. Grub 2 should not be customized
> by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and
> files in /etc/grub.d/. Reason is obvious, your customization is lost
> whenever something related to linux-image is upgraded. Just saying :)

"Wrong" isn't quite the right way to put. For most people in most
circumstances editing grub.cfg and using update-grub is a wise procedure
and to be advocated. But a hand-crafted grub.cfg can be very useful.
update-grub can be prevented from getting its hands on it with
dpkg-divert,

-- 
Brian.

Re: Debian Developers Have Been Listening!

[Brian]

On Sat 20 May 2017 at 17:06:56 +0100, Michael Fothergill wrote:

> On 20 May 2017 at 15:59, Brad Rogers  wrote:
> 
> > On Sat, 20 May 2017 14:20:15 +0100
> > Michael Fothergill  wrote:
> >
> > Hello Michael,
> >
> > >with systemd running on it to the old sysvinit format then why is there
> > >all this sturm und drang and spam on this subject...??
> >
> > People complain about all sorts of things.  Changing something.  Not
> > changing something.  Sometimes, it's even the same people.
> >
> 
> ​Now I see why the developers have their own mailing list...

A misconception. They don't.

Re: Desktop Background Bites the Dust

[David Christensen]

On 05/21/2017 05:55 AM, RavenLX wrote:

On 05/20/2017 01:00 AM, Jimmy Johnson wrote:

On 05/19/2017 07:19 PM, David Christensen wrote:

I've been having problems with Xfce wallpaper on Debian 8.8 for a month
or more.  It broke after an apt-get update/ apt-get upgrade.  I filed a
bug report, received one reply, tried the suggestions to no avail, and
replied.  I'm still waiting for a response:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860925


David if it makes any difference, recently Debian installed a Debian
Stretch Theme and the Next wallpaper or the wallpaper you where using
could have been changed or I should say probably did get changed, I
run testing and Sid so I'm used to many themes being wiped out and
replaced, it's the way of testing and not something you would expect
from a stable system which Stretch is not, yet.  As I told Cindy, you
can find the installed wallpaper in /usr/share/wallpaper.


I haven't noticed any new wallpapers (I too am running Debian 8.8 with
XFCE and have my wallpaper set to one I like which I saved in
~/Pictures/Wallpaper) I also had no problems with the wallpapers going
away and also was able to change them in the settings. I do notice that
they don't all *stay* listed in the settings (except the current one
being used) if they are located somewhere other than the default
wallpaper directory. But other than that, no problems here, so far.

I did update using apt-get dist-upgrade and not apt-get upgrade. Maybe
that made a difference?


As I understand it:

*   'apt-get upgrade' is for rolling forward to a new minor revision -- 
e.g. Debian 8.7 to Debian 8.8 -- and/or new packages -- e.g. icedove 
1:45.6.0-1~deb8u1 to thunderbird 1:45.8.0-3~deb8u1).


*   'apt-get dist-upgrade' is for rolling forward to a new major 
revision -- e.g. Debian 7 to Debian 8.



I do the former regularly -- once or more per week.


I avoid the latter, as it's caused me grief in the past (when I want to 
do a major version upgrade, I backup, move the system disk aside, do a 
fresh install, and restore).



My issue is likely tied to some software corner case due the the 
hardware -- e.g. 32-bit laptop with an off-spec 64-bit processor jammed in.



David

Re: Virtual Machines: Newbie / novice questions

[Stefan Monnier]

> "Unti recently" because there now is a way to do data retention, but:
> "bup only has experimental support for pruning old backups."

Indeed, it's a relatively new feature, but it's been working fine in
my tests.


Stefan

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Jimmy Johnson]

On 05/21/2017 12:52 PM, Michael Milliman wrote:



On 05/21/2017 12:23 PM, Jimmy Johnson wrote:



However, the OP's post does not mention anything of this nature.  The OP
deleted the existing Debian partition(s) leaving the existing Windows
partition(s) alone.  No mention was made of the ordering of the
partitions on the drive.  The OP then re-installed Debian with the
Debian installer, effectively starting from scratch with Debian.
Everything seems to work, except GNOME is crashing on boot.  There are
several things that can cause this, and I have caused some of them on my
system before, however the fact that this is a fresh install limits the
possible causes, the most likely of them being a missing (non-free?)
video driver or some such required by GNOME to run properly.  The way
the OP went about scrapping and re-installing the Debian system is valid
and should not have caused a problem under normal circumstances.  Hence
the suspicion of a missing driver (again probably non-free, and likely
Radeon as well...I've had similar issues with my laptop).



I have a Lenovo laptop with the problem you describe and it's a
kernel/video/plasma problem, works fine with the old Sid 4.7 kernel but
not with the 4.9, first boot is ok, on restart you will not get the DM
or x and may freeze up.  Sometimes switching back and forth on the
consoles will get you x, alt+ctrl+F2-F1-F3-F7. Jessie back-ports are
also 4.9 and don't work right too. The problem here is an
Intel-965-mobile, I'm going to install the Jessie kernel and see if that
works or maybe a Ubuntu kernel, I think they are 4.4 and 4.8, I know the
4.4 will work, for me anyways, but I have to do something cause the 4.7
kernel is old now and not getting security updates.

Hey, its better than the 3.16 kernel I was stuck with for a long time up
until just a couple of months. :)  In my case, laptop would boot, but
the screen would be completely blanked out.  If I caught the boot
process at just the right time with a alt+ctl+F1, I could get it to
finish booting, if I missed the window, it was power-off, power-on!! :(
The first-boot on 3.16  would do usually boot into software emulation
mode, and then I installed the Radeon drivers, and everything was OK.  I
have 4.9 running now and working fine. Video drivers and wifi drivers
have been my bane for many a year!


I had to remove all Debian firmware and installed linux-image-generic 
and linux-headers-generic and Ubuntu's firmware-linux, but now it's 
running 4.4.0-21-generic, it's booting fine and I can get updates too. 
So this kernel problem I've had for more than a year is fixed, I was 
going to wait for Stretch to go final but I've waited long enough. This 
was on two systems Sid/Testing and Stretch. The version I'm using is 
Ubuntu 16.04, just in case the OP wants to try it, I used Synaptic to do 
the work and pinned the Debian release so not to pickup any other Ubuntu 
packages not needed and I was able to rid more than 800Mb of Debian 
kernel's on each system.

--
Jimmy Johnson

Debian Sid/Testing - Plasma 5.8.6 - EXT4 at sda15
Registered Linux User #380263

Re: Virtual Machines: Newbie / novice questions

[Sven Hartge]

Stefan Monnier  wrote:

>>> However, the virtual hard disk is a pretty large size. My method
>>> compresses it further so that the size of the backup is much
>>> smaller.

>> Have a look at "borg". It is ideal to backup VMs (or anything using
>> large files with only marginal changes inside) and I have been using
>> it for my Virtualbox VMs for a very long time.

> You might also like `bup` which does the same kind of deduplication,
> so can also be used on large files that change only in small parts.

Problem with bup (until recently) is that the nature of its git-based
approach prohibits you from ever removing anything from the backup.

"Unti recently" because there now is a way to do data retention, but:
"bup only has experimental support for pruning old backups."

While bup is a nice program, borg is far more mature at this point.

S°

-- 
Sigmentation fault. Core dumped.

Re: Questions after doing update and upgrade on Stretch

[Dejan Jocic]

On 21-05-17, David Wright wrote:
> On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote:
> > On 21-05-17, Richard Owlett wrote:
> > > I had done:
> > >   apt-get update
> > >   apt-get upgrade
> > > The tail end of the output was:
> > > ...
> > > Setting up libkde3support4 (4:4.14.26-2) ...
> > > Setting up libktexteditor4 (4:4.14.26-2) ...
> > > Setting up libkdewebkit5 (4:4.14.26-2) ...
> > > Setting up libkhtml5 (4:4.14.26-2) ...
> > > Setting up libplasma3 (4:4.14.26-2) ...
> > > Setting up kdelibs5-plugins (4:4.14.26-2) ...
> > > Processing triggers for initramfs-tools (0.130) ...
> > > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> > > I: The initramfs will attempt to resume from /dev/sda5
> > > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> > > I: Set the RESUME variable to override this.
> > > Processing triggers for libc-bin (2.24-10) ...
> > > root@stretch-2nd:/home/richard#
> > > 
> > > Before asking for confirmation to do the "upgrade" it said 3 packages 
> > > would
> > > not be upgraded.
> > > If it said which packages, I didn't spot it.
> > > I then reran with following result.
> > > 
> > > root@stretch-2nd:/home/richard# apt-get upgrade
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > Calculating upgrade... Done
> > > The following packages were automatically installed and are no longer
> > > required:
> > >   dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7
> > > mate-indicator-applet
> > >   mate-indicator-applet-common python3-psutil python3-setproctitle
> > > Use 'apt autoremove' to remove them.
> > > The following packages have been kept back:
> > >   linux-image-686-pae xorg xserver-xorg
> > > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> > > root@stretch-2nd:/home/richard#
> > > 
> > > My questions:
> > > 
> > > 1. In the first run, I don't understand:
> > >  Processing triggers for initramfs-tools (0.130) ...
> > >  update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> > >  I: The initramfs will attempt to resume from /dev/sda5
> > >  I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> > >  I: Set the RESUME variable to override this.
> > >  As /dev/sda5 is my SWAP.
> > > 
> > > 2. I don't understand any implications of:
> > >  The following packages have been kept back:
> > >linux-image-686-pae xorg xserver-xorg
> > > 
> > > TIA
> > > 
> > > 
> > > 
> > > 
> > As for number 1 can't say much about it, I do not get it either. But 2
> > happens because you've used apt-get upgrade instead of apt-get
> > dist-upgrade. Packages that will uninstall some packages already
> > installed on your system and that will change some dependencies 
> > require dist-upgrade.
> 
> Agreed.
> 
> > It happens always in case of linux-image packages. 
> 
> Is this¹ new with stretch? My linux-images upgrade just like any other
> package; here's the penultimate occasion for jessie:
> 
> Start-Date: 2017-03-08  19:20:34
> Commandline: apt-get upgrade
> Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2)
> End-Date: 2017-03-08  19:22:50
> 
> (The last one's log was rather larger.)

Ehh, sorry not sure if it is new with Stretch, can't remember for
Jessie. I'm certain that it was like that on Stretch and on Ubuntu
16.04.

> 
> > It will leave your previous working linux-image on though, but will 
> > uninstall one older than that, so you will always end up with chance to 
> > boot in working kernel, if new one messes up some things.
> 
> Same question. My wheezy system has had at least 28 linux-image
> upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1)
> but there's still only one kernel image on the system:
> 
> -rw-r--r-- 1 root root  134839 Apr 27 16:52 config-3.2.0-4-686-pae
> drwxr-xr-x 3 root root   12288 Apr 28 07:44 grub
> -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae
> -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae
> -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae
> 
> (I have to notice these upgrades myself because they overwrite
> my edited version of /boot/grub/grub.cfg which I then replace.)
> 
> Cheers,
> David.
> 
> ¹ I'm not disagreeing that something is holding back the upgrade
> on this specific occasion, but this is unusual.
> 

Sorry, but you are doing it wrong way. Grub 2 should not be customized
by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and
files in /etc/grub.d/. Reason is obvious, your customization is lost
whenever something related to linux-image is 

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Michael Milliman]

On 05/21/2017 12:23 PM, Jimmy Johnson wrote:
> On 05/21/2017 08:48 AM, Michael Milliman wrote:
>>
>>
>> On 05/21/2017 05:48 AM, Jimmy Johnson wrote:
>>> On 05/21/2017 03:25 AM, Michael Milliman wrote:


 On 05/21/2017 05:09 AM, Jimmy Johnson wrote:
> On 05/21/2017 12:57 AM, Pascal Hambourg wrote:
>> Le 21/05/2017 à 09:55, Jimmy Johnson a écrit :
>
>>> No, you should NOT have deleted the partition, now your partition
>>> table
>>> is messed up.
>>
>> Bullshit. This is just a Gnome error.
>
> Unless you are deleting the last partition your partition table is
> going
> to be messed up. I hope you enjoy your B.S. You can workaround by
> using
> UUID, but personally I do not care for a messed up partition table.
 I also call B.S. on this response.  The OPs problem has absolutely
 nothing to do with the partition table or the UUIDs of the various
 partitions.  If it did, the system would not have gotten to the
 point of
 starting GNOME.  Adding, deleting and resizing partitions, using the
 appropriate tools, is relatively save in the modern era.  I have, on
 many occasions over the years deleted and re-arranged the partitions on
 my system to accommodate changing needs and have had no problems
 whatsoever.
>>>
>>> Michael what I'm saying is if you have sda1,sda2,sda3, partitions and
>>> you delete sda2 partition, sda3 becomes sda2 and if you make a new
>>> partition, even in the same unused space it will become sda3. So, in the
>>> end the drive will read sda1,sda3,sda2 and personally I can't live like
>>> that, I have to many systems to tend too. But as it's been mentioned you
>>> can use UUID if your fstab and that reminds me, if you delete or format
>>> a partition the UUID will change, #blkid will give you the UUID's.  I
>>> hear your argument, but I say back-up and start over, do it right.
>> The Debian Installer uses UUIDs in the entries in the /etc/fstab file,
>> so changing the numbering of the partitions (/dev/sda2 vs. /dev/sda3)
>> does not have an effect on the overall functioning of the system.  You
>> can also use partition labels in the fstab file as well, as I do
>> frequently, as I move data from drive to drive on occasion and simply
>> relabel the partitions to move with the data.  With that, there is no
>> need to change the fstab when I move data around.
>>
>> However, the OP's post does not mention anything of this nature.  The OP
>> deleted the existing Debian partition(s) leaving the existing Windows
>> partition(s) alone.  No mention was made of the ordering of the
>> partitions on the drive.  The OP then re-installed Debian with the
>> Debian installer, effectively starting from scratch with Debian.
>> Everything seems to work, except GNOME is crashing on boot.  There are
>> several things that can cause this, and I have caused some of them on my
>> system before, however the fact that this is a fresh install limits the
>> possible causes, the most likely of them being a missing (non-free?)
>> video driver or some such required by GNOME to run properly.  The way
>> the OP went about scrapping and re-installing the Debian system is valid
>> and should not have caused a problem under normal circumstances.  Hence
>> the suspicion of a missing driver (again probably non-free, and likely
>> Radeon as well...I've had similar issues with my laptop).
> 
> I have a Lenovo laptop with the problem you describe and it's a
> kernel/video/plasma problem, works fine with the old Sid 4.7 kernel but
> not with the 4.9, first boot is ok, on restart you will not get the DM
> or x and may freeze up.  Sometimes switching back and forth on the
> consoles will get you x, alt+ctrl+F2-F1-F3-F7. Jessie back-ports are
> also 4.9 and don't work right too. The problem here is an
> Intel-965-mobile, I'm going to install the Jessie kernel and see if that
> works or maybe a Ubuntu kernel, I think they are 4.4 and 4.8, I know the
> 4.4 will work, for me anyways, but I have to do something cause the 4.7
> kernel is old now and not getting security updates.
Hey, its better than the 3.16 kernel I was stuck with for a long time up
until just a couple of months. :)  In my case, laptop would boot, but
the screen would be completely blanked out.  If I caught the boot
process at just the right time with a alt+ctl+F1, I could get it to
finish booting, if I missed the window, it was power-off, power-on!! :(
The first-boot on 3.16  would do usually boot into software emulation
mode, and then I installed the Radeon drivers, and everything was OK.  I
have 4.9 running now and working fine. Video drivers and wifi drivers
have been my bane for many a year!
-- 
73's,
WB5VQX -- The Very Quick X-ray

Re: Questions after doing update and upgrade on Stretch

[David Wright]

On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote:
> On 21-05-17, Richard Owlett wrote:
> > I had done:
> >   apt-get update
> >   apt-get upgrade
> > The tail end of the output was:
> > ...
> > Setting up libkde3support4 (4:4.14.26-2) ...
> > Setting up libktexteditor4 (4:4.14.26-2) ...
> > Setting up libkdewebkit5 (4:4.14.26-2) ...
> > Setting up libkhtml5 (4:4.14.26-2) ...
> > Setting up libplasma3 (4:4.14.26-2) ...
> > Setting up kdelibs5-plugins (4:4.14.26-2) ...
> > Processing triggers for initramfs-tools (0.130) ...
> > update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> > I: The initramfs will attempt to resume from /dev/sda5
> > I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> > I: Set the RESUME variable to override this.
> > Processing triggers for libc-bin (2.24-10) ...
> > root@stretch-2nd:/home/richard#
> > 
> > Before asking for confirmation to do the "upgrade" it said 3 packages would
> > not be upgraded.
> > If it said which packages, I didn't spot it.
> > I then reran with following result.
> > 
> > root@stretch-2nd:/home/richard# apt-get upgrade
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Calculating upgrade... Done
> > The following packages were automatically installed and are no longer
> > required:
> >   dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7
> > mate-indicator-applet
> >   mate-indicator-applet-common python3-psutil python3-setproctitle
> > Use 'apt autoremove' to remove them.
> > The following packages have been kept back:
> >   linux-image-686-pae xorg xserver-xorg
> > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> > root@stretch-2nd:/home/richard#
> > 
> > My questions:
> > 
> > 1. In the first run, I don't understand:
> >  Processing triggers for initramfs-tools (0.130) ...
> >  update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> >  I: The initramfs will attempt to resume from /dev/sda5
> >  I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> >  I: Set the RESUME variable to override this.
> >  As /dev/sda5 is my SWAP.
> > 
> > 2. I don't understand any implications of:
> >  The following packages have been kept back:
> >linux-image-686-pae xorg xserver-xorg
> > 
> > TIA
> > 
> > 
> > 
> > 
> As for number 1 can't say much about it, I do not get it either. But 2
> happens because you've used apt-get upgrade instead of apt-get
> dist-upgrade. Packages that will uninstall some packages already
> installed on your system and that will change some dependencies 
> require dist-upgrade.

Agreed.

> It happens always in case of linux-image packages. 

Is this¹ new with stretch? My linux-images upgrade just like any other
package; here's the penultimate occasion for jessie:

Start-Date: 2017-03-08  19:20:34
Commandline: apt-get upgrade
Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2)
End-Date: 2017-03-08  19:22:50

(The last one's log was rather larger.)

> It will leave your previous working linux-image on though, but will 
> uninstall one older than that, so you will always end up with chance to 
> boot in working kernel, if new one messes up some things.

Same question. My wheezy system has had at least 28 linux-image
upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1)
but there's still only one kernel image on the system:

-rw-r--r-- 1 root root  134839 Apr 27 16:52 config-3.2.0-4-686-pae
drwxr-xr-x 3 root root   12288 Apr 28 07:44 grub
-rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae
-rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae
-rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae

(I have to notice these upgrades myself because they overwrite
my edited version of /boot/grub/grub.cfg which I then replace.)

Cheers,
David.

¹ I'm not disagreeing that something is holding back the upgrade
on this specific occasion, but this is unusual.

Re: [A bit OT] Diagnosing home network

[Gene Heskett]

On Sunday 21 May 2017 12:58:05 rhkra...@gmail.com wrote:

> On Saturday, May 20, 2017 09:38:21 AM Gene Heskett wrote:
> > You'll note no mention of wifi here as its turned off unless I have
> > children visiting with their smart phones.  wifi is slower, and
> > subject to being used by the neighbors as I found my net usage after
> > the kids had been in was up about 80 Gb a month later.
>
> You know there are security measures available for WiFi, right?  I do
> two things, I use one of the more advanced encryption protocols
> (something like WPA-2 (and maybe some more initials at the end??),
> and, I have it setup so that it doesn't announce its presence--only if
> someone knows the name can they try to enter a password and login.

As of the last time, the SSID broadcast had been turned of, WPA-2+AES was 
the effective login protocol with a 23 character password .  That didn't 
appear to much of an impediment, so I just turned the radios off.

First, they came in thru the buffalo I'm looking at, then they came in 
thru the pi's radio when it came online, which was still set at the 
default jessie on a pi settings.  I've got cat5 enough to connect 
everything I want on-line up. I assume one can buy for a winders box, 
some sort of a utility that can survey the band, and hack into the 
strongest signal it can find in a time frame thats 0.1% of 
what the cryptographers claim. So I take the ultimate hammer to it by 
turning off my radios.  Making a wifi connection work like a wired 
connection is a major PITA.  I had my lappy rigged, about 6 feet from my 
lathe, and I'd have to login fresh about every 5 minutes. 9 feet from a 
dongle plugged into the lappy to a matching dongle plugged into the 
buildings hub?  Life, remaining life anyway since I'm working on my 83rd 
trip around this star, is too short for that BS.  Screw it, its 
extremely distracting when your train of thought is on writing gcode for 
the lathes next cnc operation.  Plug it in and be done with that BS.  So 
I do.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Jimmy Johnson]

On 05/21/2017 08:48 AM, Michael Milliman wrote:



On 05/21/2017 05:48 AM, Jimmy Johnson wrote:

On 05/21/2017 03:25 AM, Michael Milliman wrote:



On 05/21/2017 05:09 AM, Jimmy Johnson wrote:

On 05/21/2017 12:57 AM, Pascal Hambourg wrote:

Le 21/05/2017 à 09:55, Jimmy Johnson a écrit :



No, you should NOT have deleted the partition, now your partition
table
is messed up.


Bullshit. This is just a Gnome error.


Unless you are deleting the last partition your partition table is going
to be messed up. I hope you enjoy your B.S. You can workaround by using
UUID, but personally I do not care for a messed up partition table.

I also call B.S. on this response.  The OPs problem has absolutely
nothing to do with the partition table or the UUIDs of the various
partitions.  If it did, the system would not have gotten to the point of
starting GNOME.  Adding, deleting and resizing partitions, using the
appropriate tools, is relatively save in the modern era.  I have, on
many occasions over the years deleted and re-arranged the partitions on
my system to accommodate changing needs and have had no problems
whatsoever.


Michael what I'm saying is if you have sda1,sda2,sda3, partitions and
you delete sda2 partition, sda3 becomes sda2 and if you make a new
partition, even in the same unused space it will become sda3. So, in the
end the drive will read sda1,sda3,sda2 and personally I can't live like
that, I have to many systems to tend too. But as it's been mentioned you
can use UUID if your fstab and that reminds me, if you delete or format
a partition the UUID will change, #blkid will give you the UUID's.  I
hear your argument, but I say back-up and start over, do it right.

The Debian Installer uses UUIDs in the entries in the /etc/fstab file,
so changing the numbering of the partitions (/dev/sda2 vs. /dev/sda3)
does not have an effect on the overall functioning of the system.  You
can also use partition labels in the fstab file as well, as I do
frequently, as I move data from drive to drive on occasion and simply
relabel the partitions to move with the data.  With that, there is no
need to change the fstab when I move data around.

However, the OP's post does not mention anything of this nature.  The OP
deleted the existing Debian partition(s) leaving the existing Windows
partition(s) alone.  No mention was made of the ordering of the
partitions on the drive.  The OP then re-installed Debian with the
Debian installer, effectively starting from scratch with Debian.
Everything seems to work, except GNOME is crashing on boot.  There are
several things that can cause this, and I have caused some of them on my
system before, however the fact that this is a fresh install limits the
possible causes, the most likely of them being a missing (non-free?)
video driver or some such required by GNOME to run properly.  The way
the OP went about scrapping and re-installing the Debian system is valid
and should not have caused a problem under normal circumstances.  Hence
the suspicion of a missing driver (again probably non-free, and likely
Radeon as well...I've had similar issues with my laptop).


I have a Lenovo laptop with the problem you describe and it's a 
kernel/video/plasma problem, works fine with the old Sid 4.7 kernel but 
not with the 4.9, first boot is ok, on restart you will not get the DM 
or x and may freeze up.  Sometimes switching back and forth on the 
consoles will get you x, alt+ctrl+F2-F1-F3-F7. Jessie back-ports are 
also 4.9 and don't work right too. The problem here is an 
Intel-965-mobile, I'm going to install the Jessie kernel and see if that 
works or maybe a Ubuntu kernel, I think they are 4.4 and 4.8, I know the 
4.4 will work, for me anyways, but I have to do something cause the 4.7 
kernel is old now and not getting security updates.

--
Jimmy Johnson

Debian Sid/Testing - Plasma 5.8.6 - EXT4 at sda15
Registered Linux User #380263

Re: Virtual Machines: Newbie / novice questions

[Stefan Monnier]

>> However, the virtual hard disk is a pretty large size. My method
>> compresses it further so that the size of the backup is much smaller.
> Have a look at "borg". It is ideal to backup VMs (or anything using
> large files with only marginal changes inside) and I have been using it
> for my Virtualbox VMs for a very long time.

You might also like `bup` which does the same kind of deduplication, so
can also be used on large files that change only in small parts.


Stefan

Re: [A bit OT] Diagnosing home network

[rhkramer]

On Saturday, May 20, 2017 09:38:21 AM Gene Heskett wrote:
> You'll note no mention of wifi here as its turned off unless I have
> children visiting with their smart phones.  wifi is slower, and subject
> to being used by the neighbors as I found my net usage after the kids
> had been in was up about 80 Gb a month later. 

You know there are security measures available for WiFi, right?  I do two 
things, I use one of the more advanced encryption protocols (something like 
WPA-2 (and maybe some more initials at the end??), and, I have it setup so 
that it doesn't announce its presence--only if someone knows the name can they 
try to enter a password and login.

Re: Virtual Machines: Newbie / novice questions

[Sven Hartge]

RavenLX  wrote:

> However, the virtual hard disk is a pretty large size. My method
> compresses it further so that the size of the backup is much smaller.

Have a look at "borg". It is ideal to backup VMs (or anything using
large files with only marginal changes inside) and I have been using it
for my Virtualbox VMs for a very long time.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Desktop Background Bites the Dust

[Fungi4All]

 Original Message 
Subject: Re: Desktop Background Bites the Dust
UTC Time: May 21, 2017 12:55 PM
From: rave...@sitesplace.net

I haven't noticed any new wallpapers (I too am running Debian 8.8 with
XFCE and have my wallpaper set to one I like which I saved in
~/Pictures/Wallpaper) I also had no problems with the wallpapers going
away and also was able to change them in the settings. I do notice that
they don't all *stay* listed in the settings (except the current one
being used) if they are located somewhere other than the default
wallpaper directory. But other than that, no problems here, so far.

I did update using apt-get dist-upgrade and not apt-get upgrade. Maybe
that made a difference?

I had something similar happened once when I had moved the ../share/ folder 
into another partition and it was not mounted at the time it vanished. After 
the mount you either relog or attempt to change it and it is there.
But since the picture is still in the same folder and exists and you point to 
it and it will not display, then FEH does not have access rights to it, which 
is why the share folder with default accesses is best for things not needing 
security. I like to keep sensitibe information secure and everything else out 
in the open.
So, tell us what the rights of the actual picture show. Maybe removing feh 
completely and then reinstalling it will reset its access rights or something 
has made the shared picture more private.
By the way, that linux-PAE I understand is for 32bit systems which can't handle 
"too much" ram. If you don't have one of those systems it is safe to throw away 
unnecessary junk. Kernle files and images are bulky things and will 
unnecessaraly accumulate and slow down your updates. Either you need it and 
dump the non-PAE images or dump all the -PAE stuff. In a year or so you may 
have 6 or 8 linux kernels as the older ones are by default kept in case you run 
into trouble with newer packages braking. Instead of 2-3 you have double what 
is necessary.
If you have not ever used LXDE but are using X I suggest you give the racy 
desktop a try. One of the reasons that is nearing the end of development is 
because it is so damn perfect. It is like an old bmw M3-E30 with no upholstery, 
single seat and roll bars. No heat, no AC no stereo.
X is an eternal bulky pain

(AK)

Re: Desktop Background Bites the Dust

[Michael Milliman]

On 05/20/2017 09:31 PM, Michael Milliman wrote:
> 
> 
> On 05/20/2017 06:33 PM, Michael Milliman wrote:
>>
>>
>> On 05/20/2017 01:56 PM, Mike Kupfer wrote:
>>> Michael Milliman wrote:
>>>
 I have no clue what happened, but the desktop background picture has
 ceased to be displayed.
>>> [...]
 I have attempted to re-set the desktop
 background via both system settings and via right-click->set desktop
 background on the desktop to no effect.
>>>
>>> I don't know what caused your old wallpaper to go away, but the
>>> inability to set it is tracked by
>>>
>>>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862355
>>>
>> This appears to be the same problem.  I will be watching this bug report
>> with interest!!  It also seems to have been reported around the same
>> time my system went belly-up, so it is probably an update that was
>> installed.  Thanks for the info, at least I know it isn't something that
>> I botched up! :)
>>
>>> The bug report also lists a workaround (which I haven't tried).
>>>
> The workaround is using the feh package to manually set the background
> image.  This does work, however, it has to be done each time you log-in.
>  It is better than nothing.  Upstream also appears to have a bug
> reported on it, and they suggest installation of mate-desktop 16.2 with
> caja 16.3, neither of which has made it to the Debian distribution as of
> yet.
Note that the version numbers above should have been mate-desktop 16.0.2
and caja 16.0.3.
> 
>>> mike
>>>
>>
> 

-- 
73's,
WB5VQX -- The Very Quick X-ray

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Michael Milliman]

On 05/21/2017 05:48 AM, Jimmy Johnson wrote:
> On 05/21/2017 03:25 AM, Michael Milliman wrote:
>>
>>
>> On 05/21/2017 05:09 AM, Jimmy Johnson wrote:
>>> On 05/21/2017 12:57 AM, Pascal Hambourg wrote:
 Le 21/05/2017 à 09:55, Jimmy Johnson a écrit :
>>>
> No, you should NOT have deleted the partition, now your partition
> table
> is messed up.

 Bullshit. This is just a Gnome error.
>>>
>>> Unless you are deleting the last partition your partition table is going
>>> to be messed up. I hope you enjoy your B.S. You can workaround by using
>>> UUID, but personally I do not care for a messed up partition table.
>> I also call B.S. on this response.  The OPs problem has absolutely
>> nothing to do with the partition table or the UUIDs of the various
>> partitions.  If it did, the system would not have gotten to the point of
>> starting GNOME.  Adding, deleting and resizing partitions, using the
>> appropriate tools, is relatively save in the modern era.  I have, on
>> many occasions over the years deleted and re-arranged the partitions on
>> my system to accommodate changing needs and have had no problems
>> whatsoever.
> 
> Michael what I'm saying is if you have sda1,sda2,sda3, partitions and
> you delete sda2 partition, sda3 becomes sda2 and if you make a new
> partition, even in the same unused space it will become sda3. So, in the
> end the drive will read sda1,sda3,sda2 and personally I can't live like
> that, I have to many systems to tend too. But as it's been mentioned you
> can use UUID if your fstab and that reminds me, if you delete or format
> a partition the UUID will change, #blkid will give you the UUID's.  I
> hear your argument, but I say back-up and start over, do it right.
The Debian Installer uses UUIDs in the entries in the /etc/fstab file,
so changing the numbering of the partitions (/dev/sda2 vs. /dev/sda3)
does not have an effect on the overall functioning of the system.  You
can also use partition labels in the fstab file as well, as I do
frequently, as I move data from drive to drive on occasion and simply
relabel the partitions to move with the data.  With that, there is no
need to change the fstab when I move data around.

However, the OP's post does not mention anything of this nature.  The OP
deleted the existing Debian partition(s) leaving the existing Windows
partition(s) alone.  No mention was made of the ordering of the
partitions on the drive.  The OP then re-installed Debian with the
Debian installer, effectively starting from scratch with Debian.
Everything seems to work, except GNOME is crashing on boot.  There are
several things that can cause this, and I have caused some of them on my
system before, however the fact that this is a fresh install limits the
possible causes, the most likely of them being a missing (non-free?)
video driver or some such required by GNOME to run properly.  The way
the OP went about scrapping and re-installing the Debian system is valid
and should not have caused a problem under normal circumstances.  Hence
the suspicion of a missing driver (again probably non-free, and likely
Radeon as well...I've had similar issues with my laptop).

-- 
73's,
WB5VQX -- The Very Quick X-ray

Re: Questions after doing update and upgrade on Stretch

[Dejan Jocic]

On 21-05-17, Richard Owlett wrote:
> I had done:
>   apt-get update
>   apt-get upgrade
> The tail end of the output was:
> ...
> Setting up libkde3support4 (4:4.14.26-2) ...
> Setting up libktexteditor4 (4:4.14.26-2) ...
> Setting up libkdewebkit5 (4:4.14.26-2) ...
> Setting up libkhtml5 (4:4.14.26-2) ...
> Setting up libplasma3 (4:4.14.26-2) ...
> Setting up kdelibs5-plugins (4:4.14.26-2) ...
> Processing triggers for initramfs-tools (0.130) ...
> update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> I: The initramfs will attempt to resume from /dev/sda5
> I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> I: Set the RESUME variable to override this.
> Processing triggers for libc-bin (2.24-10) ...
> root@stretch-2nd:/home/richard#
> 
> Before asking for confirmation to do the "upgrade" it said 3 packages would
> not be upgraded.
> If it said which packages, I didn't spot it.
> I then reran with following result.
> 
> root@stretch-2nd:/home/richard# apt-get upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages were automatically installed and are no longer
> required:
>   dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7
> mate-indicator-applet
>   mate-indicator-applet-common python3-psutil python3-setproctitle
> Use 'apt autoremove' to remove them.
> The following packages have been kept back:
>   linux-image-686-pae xorg xserver-xorg
> 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> root@stretch-2nd:/home/richard#
> 
> My questions:
> 
> 1. In the first run, I don't understand:
>  Processing triggers for initramfs-tools (0.130) ...
>  update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
>  I: The initramfs will attempt to resume from /dev/sda5
>  I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
>  I: Set the RESUME variable to override this.
>  As /dev/sda5 is my SWAP.
> 

Actually, after bit of digging, that part became much more clear,
because resume option is used to specify partition device for software
suspend, and swap is logical choice for that.

Re: Questions after doing update and upgrade on Stretch

[Pascal Hambourg]

Le 21/05/2017 à 16:35, Richard Owlett a écrit :

On 05/21/2017 09:23 AM, Pascal Hambourg wrote:


Check with blkid that sda5 has this UUID.


Gparted reports that UUID for /dev/sda5


Then it is fine.


I'll hold off on that until I can double-check on packages that were
reported as "automatically installed" but no longer needed. I thought
that one was installed manually.


Don't worry. These packages won't be automatically removed unless you 
run apt-get autoremove.

Re: Questions after doing update and upgrade on Stretch

[songbird]

Richard Owlett wrote:
> I had done:
>apt-get update
>apt-get upgrade
> The tail end of the output was:
> ...
> Setting up libkde3support4 (4:4.14.26-2) ...
> Setting up libktexteditor4 (4:4.14.26-2) ...
> Setting up libkdewebkit5 (4:4.14.26-2) ...
> Setting up libkhtml5 (4:4.14.26-2) ...
> Setting up libplasma3 (4:4.14.26-2) ...
> Setting up kdelibs5-plugins (4:4.14.26-2) ...
> Processing triggers for initramfs-tools (0.130) ...
> update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> I: The initramfs will attempt to resume from /dev/sda5
> I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> I: Set the RESUME variable to override this.
> Processing triggers for libc-bin (2.24-10) ...
> root@stretch-2nd:/home/richard#

  last bit is new message from initramfs upgrade.
i edited my /etc/default/grub file to make sure
there is no resume going on at all by changing the
line:

GRUB_CMDLINE_LINUX="root=LABEL=ROOT_00 noresume"

your own line may look different.  :)


> Before asking for confirmation to do the "upgrade" it said 3 packages 
> would not be upgraded.
> If it said which packages, I didn't spot it.

  you'd need dist-upgrade to grab the new kernel version
that is all that is about.


> I then reran with following result.
>
> root@stretch-2nd:/home/richard# apt-get upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages were automatically installed and are no longer 
> required:
>dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 
> libindicator3-7 mate-indicator-applet
>mate-indicator-applet-common python3-psutil python3-setproctitle
> Use 'apt autoremove' to remove them.
> The following packages have been kept back:
>linux-image-686-pae xorg xserver-xorg
> 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> root@stretch-2nd:/home/richard#
>
> My questions:
>
> 1. In the first run, I don't understand:
>   Processing triggers for initramfs-tools (0.130) ...
>   update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
>   I: The initramfs will attempt to resume from /dev/sda5
>   I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
>   I: Set the RESUME variable to override this.
>   As /dev/sda5 is my SWAP.

  'splained above...


> 2. I don't understand any implications of:
>   The following packages have been kept back:
> linux-image-686-pae xorg xserver-xorg

  the difference between apt-get upgrade and apt-get dist-upgrade.

  covered by the man page.


  songbird

Re: Packaging problem: impossible to build package from source

[songbird]

Michele wrote:

> Hello everyone.
...
> Does anyone have a clue about what's going on? I'm totally new to 
> packaging but it's surprising that a standard source package downloaded 
> from official debian servers doesn't work out of the box...

  have you installed the build dependencies?

  # apt-get build-dep ?

  if you can find a similar package in complexity
you can grab that source version and look at what
it does and clone it for your own use.

  $ apt-get source 

  $ cp -a  
  ...edit stuff...
  ...build...


also:

  i'm not sure if the package build-essential is up
to date, but it lists some basics.

and:

  there are references and the mentors list which may
be able to answer specific questions.

  that is all i can think of to point you in directions
which may help.


  songbird

Re: Questions after doing update and upgrade on Stretch

[Richard Owlett]

On 05/21/2017 09:23 AM, Pascal Hambourg wrote:

Le 21/05/2017 à 15:34, Richard Owlett a écrit :


1. In the first run, I don't understand:
 Processing triggers for initramfs-tools (0.130) ...
 update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
 I: The initramfs will attempt to resume from /dev/sda5
 I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
 I: Set the RESUME variable to override this.
 As /dev/sda5 is my SWAP.


Check with blkid that sda5 has this UUID.


Gparted reports that UUID for /dev/sda5





2. I don't understand any implications of:
 The following packages have been kept back:
   linux-image-686-pae xorg xserver-xorg


These packages cannot be upgraded due to dependency changes.
This is usually solved with dist-upgrade.


I'll hold off on that until I can double-check on packages that were 
reported as "automatically installed" but no longer needed. I thought 
that one was installed manually. Won't be able to follow up until this 
afternoon.


Thank you.

Re: Questions after doing update and upgrade on Stretch

[Dejan Jocic]

On 21-05-17, Richard Owlett wrote:
> I had done:
>   apt-get update
>   apt-get upgrade
> The tail end of the output was:
> ...
> Setting up libkde3support4 (4:4.14.26-2) ...
> Setting up libktexteditor4 (4:4.14.26-2) ...
> Setting up libkdewebkit5 (4:4.14.26-2) ...
> Setting up libkhtml5 (4:4.14.26-2) ...
> Setting up libplasma3 (4:4.14.26-2) ...
> Setting up kdelibs5-plugins (4:4.14.26-2) ...
> Processing triggers for initramfs-tools (0.130) ...
> update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> I: The initramfs will attempt to resume from /dev/sda5
> I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> I: Set the RESUME variable to override this.
> Processing triggers for libc-bin (2.24-10) ...
> root@stretch-2nd:/home/richard#
> 
> Before asking for confirmation to do the "upgrade" it said 3 packages would
> not be upgraded.
> If it said which packages, I didn't spot it.
> I then reran with following result.
> 
> root@stretch-2nd:/home/richard# apt-get upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages were automatically installed and are no longer
> required:
>   dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7
> mate-indicator-applet
>   mate-indicator-applet-common python3-psutil python3-setproctitle
> Use 'apt autoremove' to remove them.
> The following packages have been kept back:
>   linux-image-686-pae xorg xserver-xorg
> 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> root@stretch-2nd:/home/richard#
> 
> My questions:
> 
> 1. In the first run, I don't understand:
>  Processing triggers for initramfs-tools (0.130) ...
>  update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
>  I: The initramfs will attempt to resume from /dev/sda5
>  I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
>  I: Set the RESUME variable to override this.
>  As /dev/sda5 is my SWAP.
> 
> 2. I don't understand any implications of:
>  The following packages have been kept back:
>linux-image-686-pae xorg xserver-xorg
> 
> TIA
> 
> 
> 
> 
As for number 1 can't say much about it, I do not get it either. But 2
happens because you've used apt-get upgrade instead of apt-get
dist-upgrade. Packages that will uninstall some packages already
installed on your system and that will change some dependencies 
require dist-upgrade. It happens always in case of linux-image packages. 
It will leave your previous working linux-image on though, but will 
uninstall one older than that, so you will always end up with chance to 
boot in working kernel, if new one messes up some things.

Re: [A bit OT] Diagnosing home network

[Dan Purgert]

Mark Fletcher wrote:
>
> My home network consists of 2 Debian machines, one Jessie and one 
> Stretch, an LFS mini-ITX machine acting as my firewall, another LFS 
> laptop that is connected only occasionally, a Windows 8.1 laptop, 3 
> iPhones of varying ages, 2 iPads, 1 Android tablet device, a couple of 
> other proprietary tablets and a Buffalo Linkstation that provides most 
> of the connectivity.

Quick google doesn't show any "Linkstation" devices with more than one
ethernet port (much less wifi).  Do you perhaps mean an "Airstation"?
Could you provide the model number, so we can look it up?

> [...]
> I have my doubts about cross-LAN throughput. For example, as I write I 
> am using WinSCP on the Windows 8.1 laptop to copy a movie file from my 
> Jessie box to the laptop. (The movie concerned is not copyright before 
> anyone asks). The Jessie box is connected to the LinkStation by wired 
> ethernet, and the Windows 8.1 laptop by WiFi. I am getting a transfer 
> rate consistently across the life of the connection of 880KB/s. I'd 
> expect it to be a lot faster than that. I checked the WinSCP software is 
> capable of limiting the connection speed, but is set not to.


880KB (we'll call it 1 MB) / kilobytes per second is about 8 megabits
per second (1 byte = 8 bits).  8 mbit is a touch low (but in the
"range") of what you can expect from 802.11g.  802.11n may also fall
this low, but generally only when there's interference / poor signal.

A VERY rough rule of thumb is that on a perfectly clear channel, you can
expect your throughput to be approximately 1/3 to 1/2 of the "on the
box" speed (so 802.11g - 54mbit/sec yields roughly 18-24 mbit) for ONE
device connected to the AP.

>From there, you have to divide up the available throughput by number of
clients (i.e. a given wifi client's speed is 1/n, assuming that all
clients are using the same technology).  So if your wifi was *perfect*
for 802.11g, and one client got 24 mbit -- 2 clients would average 12
mbit each, 3 would average 8, and so on.  

In addition to "your clients", you have to contend with neighbors on the
same channels (who add to the 1/n throughput troubles).  5 GHz helps
here, as it's less likely that the clients in your home will see the 5
GHz signal from your neighbors, even if you are on the same channel.

> [...]
>
> I'd like to be able to diagnose what's going on here, why the transfer 
> was so slow. Any recommendations for tools I should research? I am very 
> willing to read man pages etc, but am a bit lost where to start. Google 
> gave me a lot of Windows-based stuff which I could look into but I would 
> prefer to use Linux-based tools if possible.
>
> Pointers to tools I should research -- and even better, links to good 
> tutorials on those tools if you know any -- would be much appreciated.

iperf would be a solid start.  Run it from one machine to another (e.g.
the wireless laptop to a wired desktop).  Don't try running it on the
router / access point / switch (if you have any of those), as iperf can
be resource intensive, so you "lose" a lot of speed due to their
processor not being able to keep up with the packet generation.

Also check your wifi channel usage -- 2.4 GHz should be on channel 1, 6,
or 11 (if you're somewhere where 13 is allowed, you could try that too).
If you use any other channel (2-5 or 7-10), you're going to be getting a
lot of interference (and throughput losses) from your neighbors.


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: Questions after doing update and upgrade on Stretch

[Pascal Hambourg]

Le 21/05/2017 à 15:34, Richard Owlett a écrit :


1. In the first run, I don't understand:
 Processing triggers for initramfs-tools (0.130) ...
 update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
 I: The initramfs will attempt to resume from /dev/sda5
 I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
 I: Set the RESUME variable to override this.
 As /dev/sda5 is my SWAP.


Check with blkid that sda5 has this UUID.


2. I don't understand any implications of:
 The following packages have been kept back:
   linux-image-686-pae xorg xserver-xorg


These packages cannot be upgraded due to dependency changes.
This is usually solved with dist-upgrade.

Questions after doing update and upgrade on Stretch

[Richard Owlett]

I had done:
  apt-get update
  apt-get upgrade
The tail end of the output was:
...
Setting up libkde3support4 (4:4.14.26-2) ...
Setting up libktexteditor4 (4:4.14.26-2) ...
Setting up libkdewebkit5 (4:4.14.26-2) ...
Setting up libkhtml5 (4:4.14.26-2) ...
Setting up libplasma3 (4:4.14.26-2) ...
Setting up kdelibs5-plugins (4:4.14.26-2) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
I: The initramfs will attempt to resume from /dev/sda5
I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
I: Set the RESUME variable to override this.
Processing triggers for libc-bin (2.24-10) ...
root@stretch-2nd:/home/richard#

Before asking for confirmation to do the "upgrade" it said 3 packages 
would not be upgraded.

If it said which packages, I didn't spot it.
I then reran with following result.

root@stretch-2nd:/home/richard# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer 
required:
  dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 
libindicator3-7 mate-indicator-applet

  mate-indicator-applet-common python3-psutil python3-setproctitle
Use 'apt autoremove' to remove them.
The following packages have been kept back:
  linux-image-686-pae xorg xserver-xorg
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
root@stretch-2nd:/home/richard#

My questions:

1. In the first run, I don't understand:
 Processing triggers for initramfs-tools (0.130) ...
 update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
 I: The initramfs will attempt to resume from /dev/sda5
 I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
 I: Set the RESUME variable to override this.
 As /dev/sda5 is my SWAP.

2. I don't understand any implications of:
 The following packages have been kept back:
   linux-image-686-pae xorg xserver-xorg

TIA

Re: Desktop Background Bites the Dust

[RavenLX]

On 05/20/2017 01:00 AM, Jimmy Johnson wrote:

On 05/19/2017 07:19 PM, David Christensen wrote:

I've been having problems with Xfce wallpaper on Debian 8.8 for a month
or more.  It broke after an apt-get update/ apt-get upgrade.  I filed a
bug report, received one reply, tried the suggestions to no avail, and
replied.  I'm still waiting for a response:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860925


David if it makes any difference, recently Debian installed a Debian 
Stretch Theme and the Next wallpaper or the wallpaper you where using 
could have been changed or I should say probably did get changed, I run 
testing and Sid so I'm used to many themes being wiped out and replaced, 
it's the way of testing and not something you would expect from a stable 
system which Stretch is not, yet.  As I told Cindy, you can find the 
installed wallpaper in /usr/share/wallpaper.


I haven't noticed any new wallpapers (I too am running Debian 8.8 with 
XFCE and have my wallpaper set to one I like which I saved in 
~/Pictures/Wallpaper) I also had no problems with the wallpapers going 
away and also was able to change them in the settings. I do notice that 
they don't all *stay* listed in the settings (except the current one 
being used) if they are located somewhere other than the default 
wallpaper directory. But other than that, no problems here, so far.


I did update using apt-get dist-upgrade and not apt-get upgrade. Maybe 
that made a difference?

Re: [trinity-users] Re: Strange clicking noise from my laptop hard drive

[RavenLX]

On 05/19/2017 09:24 AM, Philip Ashmore wrote:

I got a new hard disk.
I still get the same clicking, but now it also sometimes happens before 
I type in the passphrase to unlock the luks encrypted lvm partition the 
OS sits on.

Maybe it's the hard disk controller.
I also took out the Broadcom wifi/bluetooth pci express card as it was 
acting up too.

Maybe it's time to retire this Samsung NP-RF711-S07UK.
Bought in 2012, that's four years more than the warranty.

Regards,
Philip Ashmore

Still using the Samsung, no clicks at the moment.


I have a IBM/Lenovo T61 a friend gave me brand new (as a gift) back in 
2007. It's still going! Running Debian 8.8 with XFCE. However, I too 
hear some faint clicking noises from time to time and wonder if the HD 
is dying. I have a spare HD (has only 80GB and Windows Vista Home 
Premium pre-installed on it). I don't want to really replace the HD 
(whether new - as I can't afford it or the original 80GB one). But it's 
been working otherwise, no problems or errors.


My HP Pavilion g7 I've had maybe 4 or 5 years now (forgot when I 
actually got it) and it is my "main" system I use all day every day. 
Never any clicking noises or problems (set up the same with Debian 8.8 
with XFCE). That one sometimes would run a bit hot (so I put fans under 
it and have some power management packages installed).


I'm not sure why some systems react a certain way and other's don't. But 
if you put a new HD in and the clicking is still there, then you just 
ruled out the HD, at least.


Next thing I think you could check is the fan, and the system 
temperatures. Maybe a fan is starting to go or just needs cleaning and 
oiling?

Re: Virtual Machines: Newbie / novice questions

[RavenLX]

On 05/18/2017 09:35 AM, Mark Fletcher wrote:

This is the most unbelievable overkill. Windows VMs work just fine in
VirtualBox. When it comes to backup, I have my backup scripts check the
machines are down and if they are, include the virtual disks in the main
system backup, and if not, skip them for that night. There is no
Windows-level backup, it's all done at the host level.


My backups are done in the host too. Thing is, I want to back up the 
settings (ie. shared directory settings, machine settings, etc.) as 
well. I can't remember all the settings to the VMs I use. Exporting will 
back up everything in one neat package.



For this to work it has to be OK to down the Windows machines in order
to back them up,otherwise you risk Windows deciding to do a pointless
disk write in the middle of your backup and invalidate it. That isn't a
problem for me; if it were, I would either schedule a maintenance window
and back them up then, or look into Windows-level backup solutions
(which _still_ have no need for the nuclear-warhead-to-slice-a-banana
approach described above).


I shut down virtual machines so they aren't running during the export 
process.



Restore is smooth, and no license issues -- the Windows machine never
knows anything happened.


However, the virtual hard disk is a pretty large size. My method 
compresses it further so that the size of the backup is much smaller.


This has been the easiest and most effective way I have found so far. 
However, I might take a closer look at backing up only the virtual 
machine's hard drive along with a text file describing the machine's 
settings, then try to re-create the machine and see if it will lose the 
licensing or not.


Right now I have a lot on my plate so what I'm doing is still going to 
have to be the process until I find time to dig deeper into this.


Thank you for your reply and info.

Re: Error on install: Repository "couldn't be accessed"

[RavenLX]

On 05/18/2017 09:06 AM, Liam O'Toole wrote:
[snipped...]

I had that happened. I then changed all the http://ftp.* to
http://httpredir.debian.org. I learned of this here:

https://wiki.debian.org/SourcesList#Example_sources.list

Then I apt-get update and it worked fine from there.


Just a FYI: the recommended redirector is now http://deb.debian.org/.



Thank you! The wiki probably either needs updating or was updated since 
I looked last.

Re: [RESOLU (presque)] Lire des vidéos sur Vimeo avec Firefox?

[maderios]

On 05/21/2017 02:56 AM, Vincent Lefevre wrote:


J'avais media.autoplay.enabled à false. Le passer à true résout le
problème... en quelque sorte, parce que ça a aussi un inconvénient
de jouer les vidéos automatiquement sur les autres sites.

Bonjour
Concernant flash, on peut empêcher le lancement automatique des vidéo 
avec le réglage "ask to activate"


--
Maderios

[RÉSOLU] Re: Comment faire tourner Opendkim sur une Socket ?

[Ph. Gras]

Oui Fabien,

> L'avertissement semble normal
>> May 20 15:00:28 ns3001166 postfix/smtpd[30318]: warning: connect to Milter 
>> service unix:/var/run/opendkim/opendkim.sock: No such file or directory
> par rapport à la conf active:
>> smtpd_milters = unix:/opendkim/opendkim.sock

ce n'est pas faux, mais comme j'avais essayé à peu près tous les chemins…

Le fond du problème est que Postfix est en chroot et ne peut parcourir toute 
l'arborescence,
donc Il faut créer un répertoire pour la socket dans la sienne :
mkdir -p /var/spool/postfix/var/run/opendkim

et donner à opendkim la possibilité d'y accéder :
usermod -G opendkim postfix

(c'est la commande à utiliser à l'exclusion de toute autre, ne me demandez pas 
pourquoi)

La suite coule de source :
vi /etc/default/opendkim
..
#SOCKET="local:/var/run/opendkim/opendkim.sock" # default
SOCKET="local:/var/spool/postfix/var/run/opendkim/opendkim.sock"
..

vi /etc/postfix/main.cf
..
# DKIM
milter_default_action = accept
milter_protocol = 6
smtpd_milters = unix:/var/run/opendkim/opendkim.sock
non_smtpd_milters = $smtpd_milters
..

On remarque dans la configuration de Postfix que le chemin est relatif à celui 
du dossier
postfix, dans /var/spool

service opendkim restart
ps -ax | grep opendkim
27972 ?Ssl0:00 /usr/sbin/opendkim -x /etc/opendkim.conf -u opendkim 
-P /var/run/opendkim/opendkim.pid -p 
local:/var/spool/postfix/var/run/opendkim/opendkim.sock
30253 pts/0S+ 0:00 grep opendkim

service postfix restart

Je me mail et je vois que j'ai bien ma signature Dkim dans l'en-tête.

Bon dimanche,

Ph. Gras

Re: [RESOLU (presque)] Lire des vidéos sur Vimeo avec Firefox?

[Gaëtan PERRIER]

Le Sun, 21 May 2017 02:56:36 +0200
Vincent Lefevre  a écrit:

> J'avais media.autoplay.enabled à false. Le passer à true résout le
> problème... en quelque sorte, parce que ça a aussi un inconvénient
> de jouer les vidéos automatiquement sur les autres sites.

La valeur par défaut est à true

A+

Gaëtan


pgpe00FZe5im0.pgp
Description: PGP signature

Re: madam scrubbing?

[Dan Ritter]

On Sat, May 20, 2017 at 09:26:57PM -0400, Boyan Penkov wrote:
> Hello,
> 
> I have mdadm installed, and have three sets of RAID1 partitions set up. 
> 
> I have not explicitly configured any scrubbing, but do see some entries in 
> the weekly and monthly cron scripts to do so.  However, the machine I have 
> this on is down quite often, and I want to run this using anacreon.  
> 
> My other anacreon jobs do run; point is: how can I verify that the scrub job 
> is successful (and view the output on potentially bad sectors)?
> 

mdadm can send mail; look at the Monitor mode in the man page.

-dsr-

Re: puppy Linux reports problems with USB/network drive

[Pascal Hambourg]

Le 21/05/2017 à 04:56, Albert Hodge a écrit :


When I plugged it into the USB port it gave a warning message,  that the
NTFS -3g driver was able to mount the NTFS partition but says, Dirty
volume mount was forced by the "force" mount option. It is mounted
read/write, but advice is only write to it in emergency situation.
recommendation is boot windows and fix the filesystem first!

It's going to be a while before I can get a system built to run winxp,
is there a Linux option I can run on this old computer to fix the drive?


You can try ntfsck or ntfsfix from ntfs-3g (formerly ntfsprogs).
Use with caution.

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Pascal Hambourg]

Le 21/05/2017 à 12:48, Jimmy Johnson a écrit :


Michael what I'm saying is if you have sda1,sda2,sda3, partitions and
you delete sda2 partition, sda3 becomes sda2 and if you make a new
partition, even in the same unused space it will become sda3.


Bullshit again. Unless the partition table is implicitly reordered (no 
partitioning tool I know does this), primary partitions are not 
renumbered when deleting or adding a partition. There can be sda3 
without sda2. Only logical partitions may be renumbered when deleting or 
adding another logical partition, because there cannot be sda5 without sda6.



So, in the
end the drive will read sda1,sda3,sda2 and personally I can't live like
that


Out-of order partitions are harmless. Partition numbers are just 
numbers. I guess you must hate LVM too.



I have to many systems to tend too. But as it's been mentioned you
can use UUID if your fstab


You *should* use UUIDs or any other persistent identifier unless you 
have a very good reason not to. Disk and partition device names are not 
persistent, hence not reliable as volume identifiers. The Debian 
installer does use UUIDs by default.


Anyway, this again has nothing to do with the OP's problem.

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Jimmy Johnson]

On 05/21/2017 03:25 AM, Michael Milliman wrote:



On 05/21/2017 05:09 AM, Jimmy Johnson wrote:

On 05/21/2017 12:57 AM, Pascal Hambourg wrote:

Le 21/05/2017 à 09:55, Jimmy Johnson a écrit :



No, you should NOT have deleted the partition, now your partition table
is messed up.


Bullshit. This is just a Gnome error.


Unless you are deleting the last partition your partition table is going
to be messed up. I hope you enjoy your B.S. You can workaround by using
UUID, but personally I do not care for a messed up partition table.

I also call B.S. on this response.  The OPs problem has absolutely
nothing to do with the partition table or the UUIDs of the various
partitions.  If it did, the system would not have gotten to the point of
starting GNOME.  Adding, deleting and resizing partitions, using the
appropriate tools, is relatively save in the modern era.  I have, on
many occasions over the years deleted and re-arranged the partitions on
my system to accommodate changing needs and have had no problems whatsoever.


Michael what I'm saying is if you have sda1,sda2,sda3, partitions and 
you delete sda2 partition, sda3 becomes sda2 and if you make a new 
partition, even in the same unused space it will become sda3. So, in the 
end the drive will read sda1,sda3,sda2 and personally I can't live like 
that, I have to many systems to tend too. But as it's been mentioned you 
can use UUID if your fstab and that reminds me, if you delete or format 
a partition the UUID will change, #blkid will give you the UUID's.  I 
hear your argument, but I say back-up and start over, do it right.

--
Jimmy Johnson

Debian Sid/Testing - Plasma 5.8.6 - EXT4 at sda15
Registered Linux User #380263

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Michael Milliman]

On 05/21/2017 05:09 AM, Jimmy Johnson wrote:
> On 05/21/2017 12:57 AM, Pascal Hambourg wrote:
>> Le 21/05/2017 à 09:55, Jimmy Johnson a écrit :
> 
>>> No, you should NOT have deleted the partition, now your partition table
>>> is messed up.
>>
>> Bullshit. This is just a Gnome error.
> 
> Unless you are deleting the last partition your partition table is going
> to be messed up. I hope you enjoy your B.S. You can workaround by using
> UUID, but personally I do not care for a messed up partition table.
I also call B.S. on this response.  The OPs problem has absolutely
nothing to do with the partition table or the UUIDs of the various
partitions.  If it did, the system would not have gotten to the point of
starting GNOME.  Adding, deleting and resizing partitions, using the
appropriate tools, is relatively save in the modern era.  I have, on
many occasions over the years deleted and re-arranged the partitions on
my system to accommodate changing needs and have had no problems whatsoever.
-- 
73's,
WB5VQX -- The Very Quick X-ray

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Jimmy Johnson]

On 05/21/2017 12:57 AM, Pascal Hambourg wrote:

Le 21/05/2017 à 09:55, Jimmy Johnson a écrit :



No, you should NOT have deleted the partition, now your partition table
is messed up.


Bullshit. This is just a Gnome error.


Unless you are deleting the last partition your partition table is going 
to be messed up. I hope you enjoy your B.S. You can workaround by using 
UUID, but personally I do not care for a messed up partition table.

--
Jimmy Johnson

Debian Sid/Testing - Plasma 5.8.6 - EXT4 at sda15
Registered Linux User #380263

Re: Debian Developers Have Been Listening!

[Michael Fothergill]

On 20 May 2017 at 14:43, Cat  wrote:

> On Sat, May 20, 2017 at 02:20:15PM +0100, Michael Fothergill wrote:
> > If this is true and it is a doddle to convert an ordinary debian install
> > with systemd running on it to the old sysvinit format then why is there
> all
> > this sturm und drang and spam on this subject...??
>
> Fanaticism. For some it is not enough that it not be process 1. There can
> not
> be a single solitary trace of it on the system. Anywhere. At all.
>
> Purity above all.
>

​I think they should get to know some people who contracted a Clostridium
difficile infection and had a stool transplant​.

See here:

​https://en.wikipedia.org/wiki/Fecal_microbiota_transplant​


​I guess they see system "as a System difficile" infection, but the
developers have created their version of the stool transplant that works
just fine.

Problem solved.

MF​

>
> --
>   "A search of his car uncovered pornography, a homemade sex aid, women's
>   stockings and a Jack Russell terrier."
> - http://www.dailytelegraph.com.au/news/wacky/indeed/story-
> e6frev20-118083480
>

Re: Comment faire tourner Opendkim sur une Socket ?

[Fabien R]

On 20/05/2017 19:03, Ph. Gras wrote:

L'avertissement semble normal
> May 20 15:00:28 ns3001166 postfix/smtpd[30318]: warning: connect to Milter 
> service unix:/var/run/opendkim/opendkim.sock: No such file or directory
par rapport à la conf active:
> smtpd_milters = unix:/opendkim/opendkim.sock

--
Fabien

Re: Package on which Bug must be reported ? (Trackpad)

[Kaartic Sivaraam]

I'm current;y experiencing a little issue with my laptop itself. I'll 
reply back when it gets fixed.


Regards,
Kaartic
On Thursday 18 May 2017 01:03 AM, Dan Ritter wrote:

On Wed, May 17, 2017 at 11:06:26PM +0530, Kaartic Sivaraam wrote:

Issue 1 (with a related issue) :

I use Debian stretch on my laptop. The track pad of my laptop
isn't detected correctly. As a result, taps aren't considered as clicks
and I have to click the left / right button in the track pad for
clicking.This is the case with the "default GNOME". On "GNOME on
Wayland", this doesn't seem to be the issue. I guess the track pad is
detected correctly there as I could use taps for clicks.

Another related issues is with "Natural scrolling". I usually like to
use it. On the "default GNOME" turning the option on/off has no effect
and thus not allowing me to use Natural scrolling. This is again not an
issue with "GNOME on Wayland"

Please let me know in which package the above issue(s) and the ones that
follow are to be filed.

Can you use synclient to fix it?

The package in question is probably xserver-xorg-input-libinput

-dsr-

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Pascal Hambourg]

Le 21/05/2017 à 03:40, Fungi4All a écrit :

 Original Message 
Subject: Oh no something has gone wrong! after reinstalling Debian and Gnome.
Local Time: May 21, 2017 3:56 AM
UTC Time: May 21, 2017 12:56 AM
From: anilduggir...@fastmail.fm
To: debian-user@lists.debian.org

I had installed Windows 10 and Debian 8.8 (with LXDE) in dual boot
(UEFI) and everything was working. I wanted to reinstall Debian, so I
installed Debian again by deleting the debian partitions (I think
correctly) using the Debian installer partitioner and choosing the
Guided use largest continuous space option, this time I installed with
the Gnome desktop environment. I am getting a Oh No, Something has gone
wrong message, the system cannot recover' message after booting into
Debian. Should I have deleted the prior Debian entry in the EFI
partition?


No. The new installation deleted it automatically.


does this have anything to do with this error?


No.


Check the UUIDs of the system (ls -lh /dev/disk/by-UUID)


Irrelevant.
This is just a Gnome error, mostly due to lack of required features in 
the graphics subsystem. LXDE worked fine because it has fewer 
requirements than Gnome. Sometimes you just need to install non-free 
firmwares (often with a Radeon GPU). Sometimes you need to install newer 
kernel or Xorg drivers. Felix's answer instructs how to gather useful 
information.

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Pascal Hambourg]

Le 21/05/2017 à 09:55, Jimmy Johnson a écrit :

On 05/20/2017 05:56 PM, Anil Duggirala wrote:

I had installed Windows 10 and Debian 8.8 (with LXDE) in dual boot
(UEFI) and everything was working. I wanted to reinstall Debian, so I
installed Debian again by deleting the debian partitions (I think
correctly) using the Debian installer partitioner and choosing the
Guided use largest continuous space option, this time I installed with
the Gnome desktop environment. I am getting a Oh No, Something has gone
wrong message, the system cannot recover' message after booting into
Debian. Should I have deleted the prior Debian entry in the EFI
partition? does this have anything to do with this error? Is there any
other solution to this problem?
thanks a lot,


No, you should NOT have deleted the partition, now your partition table
is messed up.


Bullshit. This is just a Gnome error.

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

[Jimmy Johnson]

On 05/20/2017 05:56 PM, Anil Duggirala wrote:

I had installed Windows 10 and Debian 8.8 (with LXDE) in dual boot
(UEFI) and everything was working. I wanted to reinstall Debian, so I
installed Debian again by deleting the debian partitions (I think
correctly) using the Debian installer partitioner and choosing the
Guided use largest continuous space option, this time I installed with
the Gnome desktop environment. I am getting a Oh No, Something has gone
wrong message, the system cannot recover' message after booting into
Debian. Should I have deleted the prior Debian entry in the EFI
partition? does this have anything to do with this error? Is there any
other solution to this problem?
thanks a lot,


No, you should NOT have deleted the partition, now your partition table 
is messed up.  All you had to do was format or better yet just delete 
the files and reinstall, by deleting the files you can save /home. But 
now you need to look at that drive with a partition editor like gparted, 
maybe use a live-cd with gparted installed OR the wheezy live disc will 
let you install gparted.

--
Jimmy Johnson

Debian Sid/Testing - Plasma 5.8.6 - EXT4 at sda15
Registered Linux User #380263

Re: Re: Trouble importing gpg keys in stretch

[Peter Miller]

Frank,

The answers are:
7
7
0

So, it doesn't look like the issue.

Thanks for your help anyway. Except, now I am left with a system I
can't update properly.

Cheers, PEte