Re: sshd fails to bind to port to IP on boot

[tomas]

On Thu, Sep 26, 2019 at 05:34:02PM -0400, yoda woya wrote:
> when I use this, the binding fails:
> Port 2022
> #AddressFamily any
> ListenAddress x.x.x.x
> #ListenAddress ::
> 
> but if I do , it binds it to the ip on boot
> Port 2022
> #AddressFamily any
> #ListenAddress x.x.x
> #ListenAddress ::
> 
> 
> How can i fix this.  I want sshd to run only on this one IP

Are you sure that specific interface is up at the time sshd
starts?

To double check that, you could try to restart sshd manually
(check with your init's system's instructions) once the machine
is up: does it then succeed in binding?

Cheers
-- t


signature.asc
Description: Digital signature

Diagnosing lockups

[Charlie Gibbs]

I've set up a new machine with Buster (my first foray, my other
machines are still running Stretch).  It frequently locks up so
hard that I have to hit the reset button.  It seems to happen when
scrolling a Notepad window in Windows XP, which is running under 
VirtualBox 6.0.10 r132072.


The machine has an ASUS P5L-MX motherboard and I'm using its onboard
VGA adapter.

I suspect a video driver issue.  Can anyone point me to some info
on configuring and troubleshooting such things?  Up until now any
machine I've installed Linux on has Just Worked.  I've heard of
various gotchas but this is the first time I've been bitten.

Here's the output of a little diagnostic script I put together
based on stuff I cribbed from Stack Exchange:

$ cat /proc/version
Linux version 4.19.0-5-amd64 (debian-ker...@lists.debian.org) (gcc 
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08)


$ lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ 
Integrated Graphics Controller (rev 02)

Subsystem: ASUSTeK Computer Inc. 82945G/GZ Integrated Graphics 
Controller
Kernel driver in use: i915
Kernel modules: i915

$ lsmod | grep "kms\|drm"
drm_kms_helper200704  1 i915
drm   483328  6 drm_kms_helper,i915

$ find /dev -group video
/dev/fb0
/dev/dri/card0

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 
root=UUID=13c0f985-950e-42ec-a1a6-0766ef3c7025 ro quiet


$ find /etc/modprobe.d/
/etc/modprobe.d/

$ cat /etc/modprobe.d/*kms*
cat: '/etc/modprobe.d/*kms*': No such file or directory

$ ls /etc/X11/xorg.conf
ls: cannot access '/etc/X11/xorg.conf': No such file or directory

$ glxinfo | grep -i "vendor\|rendering"
direct rendering: Yes
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
Vendor: Intel Open Source Technology Center (0x8086)
OpenGL vendor string: Intel Open Source Technology Center

$ grep LoadModule /var/log/Xorg.0.log
[27.469] (II) LoadModule: "glx"
[28.044] (II) LoadModule: "intel"
[28.228] (II) LoadModule: "modesetting"
[28.313] (II) LoadModule: "fbdev"
[28.346] (II) LoadModule: "vesa"
[28.440] (II) LoadModule: "fbdevhw"
[28.509] (II) LoadModule: "dri3"
[28.509] (II) LoadModule: "dri2"
[28.509] (II) LoadModule: "present"
[32.436] (II) LoadModule: "libinput"

$ egrep -i " connected|card detect|primary dev|Setting driver" 
/var/log/Xorg.0.log
[28.402] (II) intel(0): Using Kernel Mode Setting driver: i915, 
version 1.6.0 20180719


--
cgi...@surfnaked.ca (Charlie Gibbs)

Re: Starting processes after installation

[David Wright]

On Wed 25 Sep 2019 at 18:12:25 (+0200), Sebastian Hyrwall wrote:
> On 2019-09-25 14:36, Dan Ritter wrote:
> > Sebastian Hyrwall wrote: 
> >> Just a question. Is there anyone except me that thinks that autostarting
> >> processes after installation , via apt, is completely bonkers?

No, I think that's over the top.

> >> It's been like this for ages but can anyone name any good reason for
> >> this to be default?

Simply put, because a majority of people, perhaps, expect to install
packages in the expectation that they'll start performing their task
right away.

> >> There must be a damn good one or it would have been disabled long time ago.
> > It turns out that Debian is relatively old. I've been using it
> > since 1996 or so, and it was in version 2.1 back then. (I
> > haven't bothered to check this.)

1996 takes you back to buzz, the first release, and its successor, rex.
The following spring, Bruce Perens wrote:

——✄——

We will be attacked because:
[…]
4. Linux isn't quite ready for the naive user yet, it shows, and anyone
   who wants to attack us will latch onto this.
[…]
Regarding the problem of Linux being inaccessable to naive users, this
is something we must deal with at least as well as Microsoft has if we
are to compete with Microsoft in the same market. First, one might ask
if we really want to do that. If we do, there has to be a lot more work
on hardware auto-configuration and GUI tools. If we don't want to do
this work, we might as well live with criticism on that issue.

——✄——

> > Back then, nearly all servers could do reasonable things without
> > any additional configuration. FTPd, httpd, ntpd, sendmail: the
> > install process could reasonably pop good enough values in a
> > config file without any user intervention, start the daemon, and
> > it would Just Work.
> 
> I agree in a way. But nowadays things are more complex. There is for
> example rarely a httpd getting installing without configuration getting
> altered.

One can always find a service that needs configuration beyond what
Debian either configures by default (like, say, ntp) or by means of a
series of questions (like, say, exim).

> Oh and I don't have to war-dial anymore to find servers :)
> 
> > Debian has three real options:
> >
> > 1. Don't change policy. Many daemons will start up smoothly;
> > some of them will come up with snakeoil SSL certs, and some of
> > them will come up with configs that are technically working but
> > don't do anything useful without further configuration. The
> > good thing about this is that you can do things like install a
> > web application that depends on a database and get a working but
> > not-very-useful system immediately. The bad thing is that the
> > default choices are probably wrong, and you need to go do config
> > immediately anyway.
> 
> Don't we already have start dependencies? If you install that "web
> application" it should depend on that database and the database should
> start up also. In case a "web application" was script-based (php etc)
> I've yet to see any
> 
> "apt install" that immediately gets you a working httpd+php+db anyway
> without configuration.
> 
> I especially like some something where they force you to change a
> variable in the configuration file to show that you've checked it and
> refusing to start before that.

Apart from your choice of "force", that's a fair description of, say,
installation of exim. Others are more passive, like wicd, which can't
do much connecting without being told what to connect to.

Bruce mentioned hardware auto-configuration and GUI tools above.
He didn't need to mention starting daemons automatically by default
because IIRC it was already the case in buzz.

> > 2. Change the policy to default to off. Good: better security,
> > fewer running-but-badly-configured services. Bad: it's hard to
> > get a database user and schema installed when the database isn't
> > running, so users/admins will need to do more explicit work.
> > It's really terrible to install sshd on a remote server, reboot
> > it, and then discover that sshd doesn't start by default.
> 
> If you install for example "mysql-server" now it doesn't prompt you to
> create a user anyway so why is the extra step of starting the server
> before creating the user a problem.
> 
> For "sshd" etc there can of course be exceptions for "critical services"
> which there is in many other distributions/operating systems.
> 
> A good example is "redis-server". It did start up very smoothly right
> after install binding to 0.0.0.0 without auth :D Same with "memcache" if
> I'm not mistaken.
> 
> Don't we need more security not less? Can't we sacrifice a few extra
> commands for that security?

More or less than what? There's little doubt that systems are being
configured more and more securely release by release. That's laudable,
even though many users get surprised or annoyed by it because "things
don't work like they used to". I don't follow your "sacrifice a few
extra 

Re: sshd fails to bind to port to IP on boot

[Roberto C . Sánchez]

On Thu, Sep 26, 2019 at 05:34:02PM -0400, yoda woya wrote:
>when I use this, the binding fails:
>Port 2022
>#AddressFamily any
>ListenAddress x.x.x.x
>#ListenAddress ::
>but if I do , it binds it to the ip on boot
>Port 2022
>#AddressFamily any
>#ListenAddress x.x.x
>#ListenAddress ::
>How can i fix this.  I want sshd to run only on this one IP

What is the exact error message when it fails?

Regards,

-Roberto
-- 
Roberto C. Sánchez

Re: Starting processes after installation

[Gene Heskett]

On Thursday 26 September 2019 17:25:11 Greg Wooledge wrote:

> On Thu, Sep 26, 2019 at 05:08:26PM -0400, Gene Heskett wrote:
> > On Thursday 26 September 2019 16:44:01 Greg Wooledge wrote:
> > > On Thu, Sep 26, 2019 at 04:42:15PM -0400, Gene Heskett wrote:
> > > > And here I am, to announce that my wintel boxes will only be
> > > > updated to stretch because there is not a buster compatible LCNC
> > > > available yet. That I suspect will be a while as switching to
> > > > python-3.7, and to wayland will take some time for our limited
> > > > manpower.  Too many changes, too fast.  Not poiinting fingers,
> > > > just facts our people will have to code around.
> > >
> > > I don't know much about python, but you definitely don't have to
> > > run Wayland, if you don't want to.  Lots and lots of us don't.
> >
> > Since it seems to be installed  by default, how does one go about
> > expunging it?
>
> It's not.
>
> The only time you get Wayland installed during the normal Debian
> installation is if you select to install Gnome, either explicitly, or
> by selecting to install a Desktop Environment and then not specifying
> which one you want.

That desn't seem to be the case with the arm variants, pieces of x are 
missing, I have assumed due to wayland replaceing them.. Not your fault 
of coarse. But the guys who have made LCNC run on rpi4's haven't 
mentioned problems with it yet.

The buster game is new, and the rules are obviously still being written.

> If you just install "Standard", and un-check "Desktop Environment" and
> all of its sub-choices, you don't get X or Wayland or any of that
> stuff. After that, you can install "xorg" to get the X server, fonts,
> libraries, and core utilities, plus a window manager (or Desktop
> Environment) package of your choice.  Maybe a terminal emulator, if
> you aren't a huge fan of xterm.  Then you're all set.

I normally choose xfce4 on resource limited machines.
 
> The advantage of doing it THIS way is that you get a chance to install
> firmware, microcode, video drivers, etc. before some dumb-ass policy
> decision tries to launch a Display Manager before you've had a chance
> to make X work.  (Yeah, yeah, you could in theory interact with the
> GRUB menu and force Debian to boot in multi-user.target instead of
> graphical.target. And, hey, you might actually *have* to, if the
> unconfigured X + Display Manager combo locks up your hardware badly
> enough.)
>
:-)

> Or, you can select a Desktop Environment other than Gnome during the
> installation.  You still end up facing the firmware/etc. issues, but
> at least Wayland won't be installed, and EVEN BETTER STILL, Gnome will
> not be installed!  Rejoice!
>
> There are lots and lots of choices.  Almost none of them give you
> Wayland.

Somebody really should write up those variations so we can make more 
intelligent choices. xfce4 is missing a pager. But whatever armbian puts 
on a rock64 has one. But I don't recall seeing its gui's name in print.

Thanks Greg.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Starting processes after installation

[deloptes]

Greg Wooledge wrote:

> On Thu, Sep 26, 2019 at 05:08:26PM -0400, Gene Heskett wrote:
>> On Thursday 26 September 2019 16:44:01 Greg Wooledge wrote:
>> 
>> > On Thu, Sep 26, 2019 at 04:42:15PM -0400, Gene Heskett wrote:
>> > > And here I am, to announce that my wintel boxes will only be updated
>> > > to stretch because there is not a buster compatible LCNC available
>> > > yet. That I suspect will be a while as switching to python-3.7, and
>> > > to wayland will take some time for our limited manpower.  Too many
>> > > changes, too fast.  Not poiinting fingers, just facts our people
>> > > will have to code around.
>> >
>> > I don't know much about python, but you definitely don't have to run
>> > Wayland, if you don't want to.  Lots and lots of us don't.
>> 
>> Since it seems to be installed  by default, how does one go about
>> expunging it?
> 
> It's not.
> 
> The only time you get Wayland installed during the normal Debian
> installation is if you select to install Gnome, either explicitly, or
> by selecting to install a Desktop Environment and then not specifying
> which one you want.
> 
> If you just install "Standard", and un-check "Desktop Environment" and
> all of its sub-choices, you don't get X or Wayland or any of that stuff.
> After that, you can install "xorg" to get the X server, fonts, libraries,
> and core utilities, plus a window manager (or Desktop Environment)
> package of your choice.  Maybe a terminal emulator, if you aren't a huge
> fan of xterm.  Then you're all set.
> 
> The advantage of doing it THIS way is that you get a chance to install
> firmware, microcode, video drivers, etc. before some dumb-ass policy
> decision tries to launch a Display Manager before you've had a chance to
> make X work.  (Yeah, yeah, you could in theory interact with the GRUB menu
> and force Debian to boot in multi-user.target instead of graphical.target.
> And, hey, you might actually *have* to, if the unconfigured X + Display
> Manager combo locks up your hardware badly enough.)
> 
> Or, you can select a Desktop Environment other than Gnome during the
> installation.  You still end up facing the firmware/etc. issues, but at
> least Wayland won't be installed, and EVEN BETTER STILL, Gnome will not
> be installed!  Rejoice!
> 
> There are lots and lots of choices.  Almost none of them give you
> Wayland.

+1 here

always install minimal debian and whatever you need on top.

sshd fails to bind to port to IP on boot

[yoda woya]

when I use this, the binding fails:
Port 2022
#AddressFamily any
ListenAddress x.x.x.x
#ListenAddress ::

but if I do , it binds it to the ip on boot
Port 2022
#AddressFamily any
#ListenAddress x.x.x
#ListenAddress ::


How can i fix this.  I want sshd to run only on this one IP

Re: Starting processes after installation

[Greg Wooledge]

On Thu, Sep 26, 2019 at 05:08:26PM -0400, Gene Heskett wrote:
> On Thursday 26 September 2019 16:44:01 Greg Wooledge wrote:
> 
> > On Thu, Sep 26, 2019 at 04:42:15PM -0400, Gene Heskett wrote:
> > > And here I am, to announce that my wintel boxes will only be updated
> > > to stretch because there is not a buster compatible LCNC available
> > > yet. That I suspect will be a while as switching to python-3.7, and
> > > to wayland will take some time for our limited manpower.  Too many
> > > changes, too fast.  Not poiinting fingers, just facts our people
> > > will have to code around.
> >
> > I don't know much about python, but you definitely don't have to run
> > Wayland, if you don't want to.  Lots and lots of us don't.
> 
> Since it seems to be installed  by default, how does one go about 
> expunging it?

It's not.

The only time you get Wayland installed during the normal Debian
installation is if you select to install Gnome, either explicitly, or
by selecting to install a Desktop Environment and then not specifying
which one you want.

If you just install "Standard", and un-check "Desktop Environment" and
all of its sub-choices, you don't get X or Wayland or any of that stuff.
After that, you can install "xorg" to get the X server, fonts, libraries,
and core utilities, plus a window manager (or Desktop Environment)
package of your choice.  Maybe a terminal emulator, if you aren't a huge
fan of xterm.  Then you're all set.

The advantage of doing it THIS way is that you get a chance to install
firmware, microcode, video drivers, etc. before some dumb-ass policy
decision tries to launch a Display Manager before you've had a chance to
make X work.  (Yeah, yeah, you could in theory interact with the GRUB menu
and force Debian to boot in multi-user.target instead of graphical.target.
And, hey, you might actually *have* to, if the unconfigured X + Display
Manager combo locks up your hardware badly enough.)

Or, you can select a Desktop Environment other than Gnome during the
installation.  You still end up facing the firmware/etc. issues, but at
least Wayland won't be installed, and EVEN BETTER STILL, Gnome will not
be installed!  Rejoice!

There are lots and lots of choices.  Almost none of them give you
Wayland.

Re: Starting processes after installation

[Gene Heskett]

On Thursday 26 September 2019 16:44:01 Greg Wooledge wrote:

> On Thu, Sep 26, 2019 at 04:42:15PM -0400, Gene Heskett wrote:
> > And here I am, to announce that my wintel boxes will only be updated
> > to stretch because there is not a buster compatible LCNC available
> > yet. That I suspect will be a while as switching to python-3.7, and
> > to wayland will take some time for our limited manpower.  Too many
> > changes, too fast.  Not poiinting fingers, just facts our people
> > will have to code around.
>
> I don't know much about python, but you definitely don't have to run
> Wayland, if you don't want to.  Lots and lots of us don't.

Since it seems to be installed  by default, how does one go about 
expunging it?

Thanks.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Starting processes after installation

[Greg Wooledge]

On Thu, Sep 26, 2019 at 04:42:15PM -0400, Gene Heskett wrote:
> And here I am, to announce that my wintel boxes will only be updated to 
> stretch because there is not a buster compatible LCNC available yet. 
> That I suspect will be a while as switching to python-3.7, and to 
> wayland will take some time for our limited manpower.  Too many changes, 
> too fast.  Not poiinting fingers, just facts our people will have to 
> code around.

I don't know much about python, but you definitely don't have to run
Wayland, if you don't want to.  Lots and lots of us don't.

Re: Starting processes after installation

[Gene Heskett]

On Wednesday 25 September 2019 17:15:56 Gene Heskett wrote:

> On Wednesday 25 September 2019 15:57:47 Greg Wooledge wrote:
> > On Wed, Sep 25, 2019 at 03:51:39PM -0400, Gene Heskett wrote:
> > > Neither of these links adresses the 2 main problems, wrong
> > > networking setup after the first reboot (see ip r) if you are
> > > running a static network defined in each machines /etc/host files,
> > > and only fixable by removing avahi-daemon and dhcpdc
> >
> > Your Raspbian issues are off topic here.
> >
> > Go bitch at Raspbian for shipping a broken or misconfigured DHCP
> > client daemon as their default.  P.S. it's spelled "dhcpcd".  The
> > last two letters stand for "client daemon", which is how you can
> > remember it. The spelling may be important if you actually want to
> > search for information about it, rather than just whining in the
> > wrong place. Again.
>
> Same exact network problem, and fix exists on armbian, on a rock64,
> and on your own 10.0 debian-arm net install tried on both rpi3 and
> rpi4, and I have a 10.1 amd64 dvd I just now dl'd and burned for net
> install under my right hand which will get tried on an intel box
> tomorrow. I will apologize if needed. And you know that too, as I have
> in the past when I was wrong.

And here I am, to announce that my wintel boxes will only be updated to 
stretch because there is not a buster compatible LCNC available yet. 
That I suspect will be a while as switching to python-3.7, and to 
wayland will take some time for our limited manpower.  Too many changes, 
too fast.  Not poiinting fingers, just facts our people will have to 
code around.

Progress is being made on the arm front although its not been done with 
debian due to the debian-arm net installer installing arm64 rather than 
armhf. Even on an rpi3b. SPI isn't working 100% yet but has passed some 
tests.

One comment re the arms if anybody here cares, the big sandwich style two 
piece heat sink assemblies sold by the various vendors, seriously 
encroach on the space occupied by a 40 pin header connector, and 
requires cutting away for clearance, on both the heat sink and the 40 
pin header, cut so far it actually cuts into the threaded screw holes 
that attach it to the pi's, and leaves the leg boss only marginally 
attached to the rest of the sink and very easily bent.  And I still had 
to grind about 1.5mm off each end of the connector body to get it to fit 
between the sinks legs.  So while its purty, and does an excellent job 
of cooling, I can't recommend it unless you do have access to a milling 
machine to correct it. Use the smaller stick on sinks and an adequate 
fan.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Problems with Buster and Bluetooth

[deloptes]

David Parker wrote:

> This issue seems to not be fixed entirely, after all.  Yesterday, the
> earbuds would pair but not connect when I powered them on.  I had to
> connect them manually each time, using either bluetoothctl or
> blueman-manager.  At one point they disconnected, and subsequent attempts
> to reconnect them resulted in a "Device or resource busy" error in syslog.
> I had to remove them and go through the pairing and connection process
> again to fix it.
> 
> So, there's definitely still a problem here, although they do work most of
> the time, which is better than where I started.

Hmmm - what priority PA is running at?

I don't know really why it is a problem - I think this new combination of
BT+PA is not quite ready yet, but was forced to us without alternative. I
suffer in a different way by the replacement of bluez4.

Anyway - what you also can try is try to fine tune PA - for example there
were options regarding latency and so on.

Also the signal strength - is it breaking when you are moving?

and so on.

I do not think you have to remove pairing to solve the problem - could be
you restart BT+PA.

Also try running pulseaudio with -v or -vv or -vvv to get more information
and find out where is exactly your problem.

I also read about LE that this is still somehow buggy, but if you say it was
working for you before ... 

regards

Re: Problems with Buster and Bluetooth

[David Parker]

This issue seems to not be fixed entirely, after all.  Yesterday, the
earbuds would pair but not connect when I powered them on.  I had to
connect them manually each time, using either bluetoothctl or
blueman-manager.  At one point they disconnected, and subsequent attempts
to reconnect them resulted in a "Device or resource busy" error in syslog.
I had to remove them and go through the pairing and connection process
again to fix it.

So, there's definitely still a problem here, although they do work most of
the time, which is better than where I started.

On Tue, Sep 24, 2019 at 5:52 PM deloptes  wrote:

> Mark Fletcher wrote:
>
> > On Tue, Sep 24, 2019 at 01:21:03PM -0400, David Parker wrote:
> >> Ok, I think I may have solved the connectivity issue.  Some additional
> >> Googling revealed that GDM starts an instance of PulseAudio, and that
> >> conflicts with the PulseAudio server used by the Bluetooth device.  The
> >> steps to stop GDM from starting PulseAudio can be found online, and I've
> >> adapted them for Buster here:
> >>
> >> (as root):
> >> echo "autospawn = no" >> /var/lib/gdm3/.config/pulse/client.conf
> >> echo "daemon-binary = /bin/true" >>
> >> /var/lib/gdm3/.config/pulse/client.conf su - Debian-gdm -c "mkdir -p
> >> /var/lib/gdm3/.config/systemd/user" su - Debian-gdm -c "ln -s /dev/null
> >> /var/lib/gdm/.config/systemd/user/pulseaudio.socket"
> >>
> >
> > Ah -- that old chestnut! I had that problem back in the day (wheezy or
> > stretch, I don't remember which) with a pair of high-end bluetooth
> > headphones.
> >
> > I recently fresh-installed Buster, I've used Bluetooth with a speaker
> > but not with my headphones without problems, but I just checked and I
> > _do_ have 2 instances of pulseaudio running, one as my regular user and
> > one as Debian-. Isn't that a bug in Debian's setup? Is there
> > some reason one would want things that way?
> >
> > Mark
>
> I just check, I do not use gdm - don't have it installed, but I also have
> two processes. I found this and many other entries dedicated to the topic
>
> https://lists.debian.org/debian-user/2015/11/msg01119.html
>
> However I do not have any issues with audio - very strange - also the date
> of the thread.
>
> regards
>
>
>

-- 
Dave Parker '11
Database & Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177

Re: Icon for minimized window.

[Reco]

Hi.

On Thu, Sep 26, 2019 at 09:39:38AM -0700, pe...@easthope.ca wrote:
> Now when a window is minimized, nothing visible remains.  I don't know 
> how to retrieve it.  I must have clicked a configuration button 
> inadvertently but haven't found it.  Tips?

Right click on a panel, select "Panel Settings". Choose "Panel Applets"
tab.  Add "Task Bar (Window List)" applet to the panel.

Reco

Icon for minimized window.

[peter]

Hi,

This refers to the LXDE desktop.

Until recently, minimization of a window left a small button in the 
system panel or bar (whatever is the correct term) at the bottom of 
the display. A click on the button would open the window again.

Now when a window is minimized, nothing visible remains.  I don't know 
how to retrieve it.  I must have clicked a configuration button 
inadvertently but haven't found it.  Tips?

Thanks,... Peter E.



-- 
https://en.wikibooks.org/wiki/Medical_Machines
Tel: +1 604 670 0140Bcc: peter at easthope. ca

cannot change gdm3 background

[Renato Gallo]

I changed the background gdm picture in greeter.dconf-defaults and ran 
dpkg-reconfigure gdm3 but I still have that horrible gray thing. 

here's my /etc/gdm3/greeter.dconf-defaults 

# These are the options for the greeter session that can be set 
# through GSettings. Any GSettings setting that is used by the 
# greeter session can be set here. 

# Note that you must configure the path used by dconf to store the 
# configuration, not the GSettings path. 


# Theming options 
# === 
# - Change the GTK+ theme 
[org/gnome/desktop/interface] 
# gtk-theme='Adwaita' 
# - Use another background 
[org/gnome/desktop/background] 
# picture-uri='file:///usr/share/themes/Adwaita/backgrounds/stripes.jpg' 
# picture-options='zoom' 
picture-uri='file:///usr/share/themes/KGB/backgrounds/kgb.jpg' 
picture-options='zoom' 
# - Or no background at all 
[org/gnome/desktop/background] 
# picture-options='none' 
# primary-color='#00' 

# Login manager options 
# = 
[org/gnome/login-screen] 
logo='/usr/share/images/vendor-logos/logo-text-version-128.png' 

# - Disable user list 
# disable-user-list=true 
# - Disable restart buttons 
# disable-restart-buttons=true 
# - Show a login welcome message 
# banner-message-enable=true 
# banner-message-text='Welcome' 

# Automatic suspend 
# = 
[org/gnome/settings-daemon/plugins/power] 
# - Time inactive in seconds before suspending with AC power 
# 1200=20 minutes, 0=never 
# sleep-inactive-ac-timeout=1200 
# - What to do after sleep-inactive-ac-timeout 
# 'blank', 'suspend', 'shutdown', 'hibernate', 'interactive' or 'nothing' 
# sleep-inactive-ac-type='suspend' 
# - As above but when on battery 
# sleep-inactive-battery-timeout=1200 
# sleep-inactive-battery-type='suspend' 


Renato Gallo 

Re: Debian Buster update error

[Roberto C . Sánchez]

On Thu, Sep 26, 2019 at 08:45:45AM -0400, Greg Wooledge wrote:
> On Thu, Sep 26, 2019 at 08:34:18AM -0400, Roberto C. Sánchez wrote:
> > On Thu, Sep 26, 2019 at 12:19:41PM +, c...@riseup.net wrote:
> > > drwx-- 2 root root  12K Jul 22 12:57 lost+found/
> > 
> > This entry is concerning.  A typical directory shows up as taking 4 KB.
> > For it to take up more it must have (or have had at some point) many
> > files.
> 
> This is normal for lost+found directories.  They are intentionally created
> with a bunch of files inside them, and then those files are deleted,
> in order to expand the size of the directory inode, in order to make
> room to accomodate a bunch of files being added to it during an fsck.
> 
> Just in case it ever needs it.
> 

Wow.  I learned something today.

Sure enough, most of the filesystems on my machine were created in early
2005 and every single lost+found directory (most of them with mtimes in
early 2005, so never having had anything them since the filesystems were
creatd) are 16 KB.

Neat.  Thanks for the info.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Debian Buster update error

[Greg Wooledge]

On Thu, Sep 26, 2019 at 08:34:18AM -0400, Roberto C. Sánchez wrote:
> On Thu, Sep 26, 2019 at 12:19:41PM +, c...@riseup.net wrote:
> > drwx-- 2 root root  12K Jul 22 12:57 lost+found/
> 
> This entry is concerning.  A typical directory shows up as taking 4 KB.
> For it to take up more it must have (or have had at some point) many
> files.

This is normal for lost+found directories.  They are intentionally created
with a bunch of files inside them, and then those files are deleted,
in order to expand the size of the directory inode, in order to make
room to accomodate a bunch of files being added to it during an fsck.

Just in case it ever needs it.

Re: Debian Buster update error

[CEO]

On Thu, Sep 26, 2019 at 08:11:14AM -0400, Roberto C. Sánchez wrote:
> On Thu, Sep 26, 2019 at 11:58:28AM +, c...@riseup.net wrote:
> > 
> > ~> dpkg -l | grep linux
> > ii  binutils-x86-64-linux-gnu  2.31.1-16
> > amd64GNU binary utilities, for x86-64-linux-gnu target
> > ii  console-setup-linux1.193~deb10u1
> > all  Linux specific part of console-setup
> > ii  firmware-linux 20190114-2
> > all  Binary firmware for various drivers in the Linux kernel
> > (metapackage)
> > ii  firmware-linux-free3.4
> > all  Binary firmware for various drivers in the Linux kernel
> > ii  firmware-linux-nonfree 20190114-2
> > all  Binary firmware for various drivers in the Linux kernel
> > (meta-package)
> > ii  libselinux1:amd64  2.8-1+b1
> > amd64SELinux runtime shared libraries
> > ii  libv4l-0:amd64 1.16.3-3
> > amd64Collection of video4linux support libraries
> > ii  libv4lconvert0:amd64   1.16.3-3
> > amd64Video4linux frame format conversion library
> > ii  linux-base 4.6
> > all  Linux image base package
> > ii  linux-compiler-gcc-8-x86   4.19.67-2+deb10u1
> > amd64Compiler for Linux on x86 (meta-package)
> > ii  linux-headers-4.19.0-5-amd64   4.19.37-5+deb10u2
> > amd64Header files for Linux 4.19.0-5-amd64
> > ii  linux-headers-4.19.0-5-common  4.19.37-5+deb10u2
> > all  Common header files for Linux 4.19.0-5
> > ii  linux-headers-4.19.0-6-amd64   4.19.67-2+deb10u1
> > amd64Header files for Linux 4.19.0-6-amd64
> > ii  linux-headers-4.19.0-6-common  4.19.67-2+deb10u1
> > all  Common header files for Linux 4.19.0-6
> > ii  linux-headers-amd644.19+105+deb10u1
> > amd64Header files for Linux amd64 configuration (meta-package)
> > ii  linux-image-4.19.0-5-amd64 4.19.37-5+deb10u2
> > amd64Linux 4.19 for 64-bit PCs (signed)
> > iF  linux-image-4.19.0-6-amd64 4.19.67-2+deb10u1
> > amd64Linux 4.19 for 64-bit PCs (signed)
> > ii  linux-image-amd64  4.19+105+deb10u1
> > amd64Linux for 64-bit PCs (meta-package)
> > ii  linux-kbuild-4.19  4.19.67-2+deb10u1
> > amd64Kbuild infrastructure for Linux 4.19
> > ii  linux-libc-dev:amd64   4.19.67-2+deb10u1
> > amd64Linux support headers for userspace development
> > ii  util-linux 2.33.1-0.1
> > amd64miscellaneous system utilities
> > ii  util-linux-locales 2.33.1-0.1
> > all  locales files for util-linux
> > ~> uname -a
> > Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
> > x86_64 GNU/Linux
> > 
> 
> OK, then try:
> 
> sudo apt remove linux-headers-4.19.0-5-amd64 linux-headers-4.19.0-5-common 
> linux-image-4.19.0-5-amd64
> 
> Then the output of these commands:
> 
> df -h
> 
> ls -lh /boot
> 
Now the output is the following and hopefull, my computer will be able
to restart and Wifi will work after having removed the kernel.

df -h
FilesystemSize  Used Avail Use% Mounted on
udev  1.9G 0  1.9G   0% /dev
tmpfs 386M  6.2M  380M   2% /run
/dev/mapper/--vg-root  454G  112G  319G  26% /
tmpfs 1.9G 0  1.9G   0% /dev/shm
tmpfs 5.0M  4.0K  5.0M   1% /run/lock
tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
/dev/sda1 236M   83M  142M  37% /boot
tmpfs 386M  8.0K  386M   1% /run/user/1000
~> ls -lh /boot
total 70M
-rw-r--r-- 1 root root 202K Sep 20 13:51 config-4.19.0-6-amd64
drwxr-xr-x 5 root root 1.0K Sep 26 15:10 grub/
-rw-r--r-- 1 root root  61M Sep 26 15:10 initrd.img-4.19.0-6-amd64
drwx-- 2 root root  12K Jul 22 12:57 lost+found/
-rw-r--r-- 1 root root 3.3M Sep 20 13:51 System.map-4.19.0-6-amd64
-rw-r--r-- 1 root root 5.1M Sep 20 13:51 vmlinuz-4.19.0-6-amd64

> Regards,
> 
> -Roberto
> 
> -- 
> Roberto C. Sánchez
> 

Re: Debian Buster update error

[Roberto C . Sánchez]

On Thu, Sep 26, 2019 at 12:19:41PM +, c...@riseup.net wrote:
> > > 
> Now the output is the following and hopefull, my computer will be able
> to restart and Wifi will work after having removed the kernel.
> 
> df -h
> FilesystemSize  Used Avail Use% Mounted on
> udev  1.9G 0  1.9G   0% /dev
> tmpfs 386M  6.2M  380M   2% /run
> /dev/mapper/--vg-root  454G  112G  319G  26% /
> tmpfs 1.9G 0  1.9G   0% /dev/shm
> tmpfs 5.0M  4.0K  5.0M   1% /run/lock
> tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
> /dev/sda1 236M   83M  142M  37% /boot
> tmpfs 386M  8.0K  386M   1% /run/user/1000
> ~> ls -lh /boot
> total 70M
> -rw-r--r-- 1 root root 202K Sep 20 13:51 config-4.19.0-6-amd64
> drwxr-xr-x 5 root root 1.0K Sep 26 15:10 grub/
> -rw-r--r-- 1 root root  61M Sep 26 15:10 initrd.img-4.19.0-6-amd64
> drwx-- 2 root root  12K Jul 22 12:57 lost+found/

This entry is concerning.  A typical directory shows up as taking 4 KB.
For it to take up more it must have (or have had at some point) many
files.  On my system, a directory which I found that shows up as taking
12 KB (and I know has not had files removed from it) has over 1500
files.  If you look in that directory, you may find lots of file
fragments.  While they don't appear to be taking lots of room (no more
than 4-5 MB based on your df and ls output), the fact that you have
files there may indicate some sort of hardware problem.  Or possibly
something else that is causing the system to corrupt your files.

You should investigate that.

Regards,

-Roberto
-- 
Roberto C. Sánchez

Re: Debian Buster update error

[CSO]

On Thu, Sep 26, 2019 at 02:08:33PM +0200, Renato Gallo wrote:
> This email read confirmation is really annoying 
> 
I used other people's email setting files and have not figured out how
to turn it off yet. If you find it so annoying, why have you not turned
read confirmation off your email clients?

For example, I have not even noticed such thing. I will deal with this
issue after the buster update issue is solved. But if you do not like
all email confirmations, the best way would be turn it off in your own
email clients.
> Renato Gallo 
> 
> 
> - Original Message -
> From: c...@riseup.net
> To: "debian-user" 
> Sent: Thursday, September 26, 2019 1:58:28 PM
> Subject: Re: Debian Buster update error
> 
> On Thu, Sep 26, 2019 at 07:59:21AM -0400, Roberto C. Sánchez wrote:
> > On Thu, Sep 26, 2019 at 11:48:30AM +, c...@riseup.net wrote:
> > > On Thu, Sep 26, 2019 at 01:50:51PM +0200, steve wrote:
> > > > Le 26-09-2019, à 11:36:33 +, c...@riseup.net a écrit :
> > > > 
> > > > > 
> > > > > After applying your solution, it still does not work and gives me the
> > > > > following error
> > > > > 
> > > > > apt-get autoremove
> > > > > Reading package lists... Done
> > > > > Building dependency tree
> > > > > Reading state information... Done
> > > > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > > > > 1 not fully installed or removed.
> > > > > After this operation, 0 B of additional disk space will be used.
> > > > > Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
> > > > > /etc/kernel/postinst.d/initramfs-tools:
> > > > > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> > > > > 
> > > > > gzip: stdout: No space left on device
> > > > 
> > > > This your problem, no space left on devices.
> > > > 
> > > > Please copy here the output of
> > > > 
> > > > df -h
> > > > 
> > > The following is the output:
> > > 
> > > df -h
> > > FilesystemSize  Used Avail Use% Mounted on
> > > udev  1.9G 0  1.9G   0% /dev
> > > tmpfs 386M  6.2M  380M   2% /run
> > > /dev/mapper/--vg-root  454G  113G  319G  27% /
> > > tmpfs 1.9G 0  1.9G   0% /dev/shm
> > > tmpfs 5.0M  4.0K  5.0M   1% /run/lock
> > > tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
> > > /dev/sda1 236M  212M   12M  95% /boot
> > > tmpfs 386M  8.0K  386M   1% /run/user/1000
> > > 
> > 
> > Your /boot partition has only 12 MB free.  Additionally, kernel
> > 4.19.0-6-amd64 is quite old, as the current version is 4.19.0-11-amd64.
> > 
> > What is the output of these commands?
> > 
> > uname -a
> > 
> > dpkg -l | grep linux
> > 
> The following is the output:
> 
> ~> dpkg -l | grep linux
> ii  binutils-x86-64-linux-gnu  2.31.1-16
> amd64GNU binary utilities, for x86-64-linux-gnu target
> ii  console-setup-linux1.193~deb10u1
> all  Linux specific part of console-setup
> ii  firmware-linux 20190114-2
> all  Binary firmware for various drivers in the Linux kernel
> (metapackage)
> ii  firmware-linux-free3.4
> all  Binary firmware for various drivers in the Linux kernel
> ii  firmware-linux-nonfree 20190114-2
> all  Binary firmware for various drivers in the Linux kernel
> (meta-package)
> ii  libselinux1:amd64  2.8-1+b1
> amd64SELinux runtime shared libraries
> ii  libv4l-0:amd64 1.16.3-3
> amd64Collection of video4linux support libraries
> ii  libv4lconvert0:amd64   1.16.3-3
> amd64Video4linux frame format conversion library
> ii  linux-base 4.6
> all  Linux image base package
> ii  linux-compiler-gcc-8-x86   4.19.67-2+deb10u1
> amd64Compiler for Linux on x86 (meta-package)
> ii  linux-headers-4.19.0-5-amd64   4.19.37-5+deb10u2
> amd64Header files for Linux 4.19.0-5-amd64
> ii  linux-headers-4.19.0-5-common  4.19.37-5+deb10u2
> all  Common header files for Linux 4.19.0-5
> ii  linux-headers-4.19.0-6-amd64   4.19.67-2+deb10u1
> amd64Header files for Linux 4.19.0-6-amd64
> ii  linux-headers-4.19.0-6-common  4.19.67-2+deb10u1
> all  Common header files for Linux 4.19.0-6
> ii  linux-headers-amd644.19+105+deb10u1
> amd64Header files for Linux amd64 configuration (meta-package)
> ii  linux-image-4.19.0-5-amd64 4.19.37-5+deb10u2
> amd64Linux 4.19 for 64-bit PCs (signed)
> iF  linux-image-4.19.0-6-amd64 4.19.67-2+deb10u1
> amd64Linux 4.19 for 64-bit PCs (signed)
> ii  linux-image-amd64  4.19+105+deb10u1
> amd64Linux for 64-bit PCs (meta-package)
> ii  linux-kbuild-4.19  4.19.67-2+deb10u1
> amd64Kbuild infrastruct

Re: Debian Buster update error

[CSO]

> Date: Thu, 26 Sep 2019 12:16:58 +
> From: c...@riseup.net
> To: "Roberto C. Sánchez" , debian-user@lists.debian.org
> Subject: Re: Debian Buster update error
> 
> On Thu, Sep 26, 2019 at 08:11:14AM -0400, Roberto C. Sánchez wrote:
> > On Thu, Sep 26, 2019 at 11:58:28AM +, c...@riseup.net wrote:
> > > 
> > > ~> dpkg -l | grep linux
> > > ii  binutils-x86-64-linux-gnu  2.31.1-16
> > > amd64GNU binary utilities, for x86-64-linux-gnu target
> > > ii  console-setup-linux1.193~deb10u1
> > > all  Linux specific part of console-setup
> > > ii  firmware-linux 20190114-2
> > > all  Binary firmware for various drivers in the Linux kernel
> > > (metapackage)
> > > ii  firmware-linux-free3.4
> > > all  Binary firmware for various drivers in the Linux kernel
> > > ii  firmware-linux-nonfree 20190114-2
> > > all  Binary firmware for various drivers in the Linux kernel
> > > (meta-package)
> > > ii  libselinux1:amd64  2.8-1+b1
> > > amd64SELinux runtime shared libraries
> > > ii  libv4l-0:amd64 1.16.3-3
> > > amd64Collection of video4linux support libraries
> > > ii  libv4lconvert0:amd64   1.16.3-3
> > > amd64Video4linux frame format conversion library
> > > ii  linux-base 4.6
> > > all  Linux image base package
> > > ii  linux-compiler-gcc-8-x86   4.19.67-2+deb10u1
> > > amd64Compiler for Linux on x86 (meta-package)
> > > ii  linux-headers-4.19.0-5-amd64   4.19.37-5+deb10u2
> > > amd64Header files for Linux 4.19.0-5-amd64
> > > ii  linux-headers-4.19.0-5-common  4.19.37-5+deb10u2
> > > all  Common header files for Linux 4.19.0-5
> > > ii  linux-headers-4.19.0-6-amd64   4.19.67-2+deb10u1
> > > amd64Header files for Linux 4.19.0-6-amd64
> > > ii  linux-headers-4.19.0-6-common  4.19.67-2+deb10u1
> > > all  Common header files for Linux 4.19.0-6
> > > ii  linux-headers-amd644.19+105+deb10u1
> > > amd64Header files for Linux amd64 configuration (meta-package)
> > > ii  linux-image-4.19.0-5-amd64 4.19.37-5+deb10u2
> > > amd64Linux 4.19 for 64-bit PCs (signed)
> > > iF  linux-image-4.19.0-6-amd64 4.19.67-2+deb10u1
> > > amd64Linux 4.19 for 64-bit PCs (signed)
> > > ii  linux-image-amd64  4.19+105+deb10u1
> > > amd64Linux for 64-bit PCs (meta-package)
> > > ii  linux-kbuild-4.19  4.19.67-2+deb10u1
> > > amd64Kbuild infrastructure for Linux 4.19
> > > ii  linux-libc-dev:amd64   4.19.67-2+deb10u1
> > > amd64Linux support headers for userspace development
> > > ii  util-linux 2.33.1-0.1
> > > amd64miscellaneous system utilities
> > > ii  util-linux-locales 2.33.1-0.1
> > > all  locales files for util-linux
> > > ~> uname -a
> > > Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
> > > x86_64 GNU/Linux
> > > 
> > 
> > OK, then try:
> > 
> > sudo apt remove linux-headers-4.19.0-5-amd64 linux-headers-4.19.0-5-common 
> > linux-image-4.19.0-5-amd64
> > 
> > Then the output of these commands:
> > 
> > df -h
> > 
> > ls -lh /boot
> > 
Now the output is the following and hopefull, my computer will be able
to restart and Wifi will work after having removed the kernel.

df -h
FilesystemSize  Used Avail Use% Mounted on
udev  1.9G 0  1.9G   0% /dev
tmpfs 386M  6.2M  380M   2% /run
/dev/mapper/--vg-root  454G  112G  319G  26% /
tmpfs 1.9G 0  1.9G   0% /dev/shm
tmpfs 5.0M  4.0K  5.0M   1% /run/lock
tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
/dev/sda1 236M   83M  142M  37% /boot
tmpfs 386M  8.0K  386M   1% /run/user/1000
~> ls -lh /boot
total 70M
-rw-r--r-- 1 root root 202K Sep 20 13:51 config-4.19.0-6-amd64
drwxr-xr-x 5 root root 1.0K Sep 26 15:10 grub/
-rw-r--r-- 1 root root  61M Sep 26 15:10 initrd.img-4.19.0-6-amd64
drwx-- 2 root root  12K Jul 22 12:57 lost+found/
-rw-r--r-- 1 root root 3.3M Sep 20 13:51 System.map-4.19.0-6-amd64
-rw-r--r-- 1 root root 5.1M Sep 20 13:51 vmlinuz-4.19.0-6-amd64

> > Regards,
> > 
> > -Roberto
> > 
> > -- 
> > Roberto C. Sánchez
> > 

- End forwarded message -

Re: Debian Buster update error

[Roberto C . Sánchez]

On Thu, Sep 26, 2019 at 11:58:28AM +, c...@riseup.net wrote:
> 
> ~> dpkg -l | grep linux
> ii  binutils-x86-64-linux-gnu  2.31.1-16
> amd64GNU binary utilities, for x86-64-linux-gnu target
> ii  console-setup-linux1.193~deb10u1
> all  Linux specific part of console-setup
> ii  firmware-linux 20190114-2
> all  Binary firmware for various drivers in the Linux kernel
> (metapackage)
> ii  firmware-linux-free3.4
> all  Binary firmware for various drivers in the Linux kernel
> ii  firmware-linux-nonfree 20190114-2
> all  Binary firmware for various drivers in the Linux kernel
> (meta-package)
> ii  libselinux1:amd64  2.8-1+b1
> amd64SELinux runtime shared libraries
> ii  libv4l-0:amd64 1.16.3-3
> amd64Collection of video4linux support libraries
> ii  libv4lconvert0:amd64   1.16.3-3
> amd64Video4linux frame format conversion library
> ii  linux-base 4.6
> all  Linux image base package
> ii  linux-compiler-gcc-8-x86   4.19.67-2+deb10u1
> amd64Compiler for Linux on x86 (meta-package)
> ii  linux-headers-4.19.0-5-amd64   4.19.37-5+deb10u2
> amd64Header files for Linux 4.19.0-5-amd64
> ii  linux-headers-4.19.0-5-common  4.19.37-5+deb10u2
> all  Common header files for Linux 4.19.0-5
> ii  linux-headers-4.19.0-6-amd64   4.19.67-2+deb10u1
> amd64Header files for Linux 4.19.0-6-amd64
> ii  linux-headers-4.19.0-6-common  4.19.67-2+deb10u1
> all  Common header files for Linux 4.19.0-6
> ii  linux-headers-amd644.19+105+deb10u1
> amd64Header files for Linux amd64 configuration (meta-package)
> ii  linux-image-4.19.0-5-amd64 4.19.37-5+deb10u2
> amd64Linux 4.19 for 64-bit PCs (signed)
> iF  linux-image-4.19.0-6-amd64 4.19.67-2+deb10u1
> amd64Linux 4.19 for 64-bit PCs (signed)
> ii  linux-image-amd64  4.19+105+deb10u1
> amd64Linux for 64-bit PCs (meta-package)
> ii  linux-kbuild-4.19  4.19.67-2+deb10u1
> amd64Kbuild infrastructure for Linux 4.19
> ii  linux-libc-dev:amd64   4.19.67-2+deb10u1
> amd64Linux support headers for userspace development
> ii  util-linux 2.33.1-0.1
> amd64miscellaneous system utilities
> ii  util-linux-locales 2.33.1-0.1
> all  locales files for util-linux
> ~> uname -a
> Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
> x86_64 GNU/Linux
> 

OK, then try:

sudo apt remove linux-headers-4.19.0-5-amd64 linux-headers-4.19.0-5-common 
linux-image-4.19.0-5-amd64

Then the output of these commands:

df -h

ls -lh /boot

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Debian Buster update error

[Renato Gallo]

This email read confirmation is really annoying 

Renato Gallo 


- Original Message -
From: c...@riseup.net
To: "debian-user" 
Sent: Thursday, September 26, 2019 1:58:28 PM
Subject: Re: Debian Buster update error

On Thu, Sep 26, 2019 at 07:59:21AM -0400, Roberto C. Sánchez wrote:
> On Thu, Sep 26, 2019 at 11:48:30AM +, c...@riseup.net wrote:
> > On Thu, Sep 26, 2019 at 01:50:51PM +0200, steve wrote:
> > > Le 26-09-2019, à 11:36:33 +, c...@riseup.net a écrit :
> > > 
> > > > 
> > > > After applying your solution, it still does not work and gives me the
> > > > following error
> > > > 
> > > > apt-get autoremove
> > > > Reading package lists... Done
> > > > Building dependency tree
> > > > Reading state information... Done
> > > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > > > 1 not fully installed or removed.
> > > > After this operation, 0 B of additional disk space will be used.
> > > > Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
> > > > /etc/kernel/postinst.d/initramfs-tools:
> > > > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> > > > 
> > > > gzip: stdout: No space left on device
> > > 
> > > This your problem, no space left on devices.
> > > 
> > > Please copy here the output of
> > > 
> > > df -h
> > > 
> > The following is the output:
> > 
> > df -h
> > FilesystemSize  Used Avail Use% Mounted on
> > udev  1.9G 0  1.9G   0% /dev
> > tmpfs 386M  6.2M  380M   2% /run
> > /dev/mapper/--vg-root  454G  113G  319G  27% /
> > tmpfs 1.9G 0  1.9G   0% /dev/shm
> > tmpfs 5.0M  4.0K  5.0M   1% /run/lock
> > tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
> > /dev/sda1 236M  212M   12M  95% /boot
> > tmpfs 386M  8.0K  386M   1% /run/user/1000
> > 
> 
> Your /boot partition has only 12 MB free.  Additionally, kernel
> 4.19.0-6-amd64 is quite old, as the current version is 4.19.0-11-amd64.
> 
> What is the output of these commands?
> 
> uname -a
> 
> dpkg -l | grep linux
> 
The following is the output:

~> dpkg -l | grep linux
ii  binutils-x86-64-linux-gnu  2.31.1-16
amd64GNU binary utilities, for x86-64-linux-gnu target
ii  console-setup-linux1.193~deb10u1
all  Linux specific part of console-setup
ii  firmware-linux 20190114-2
all  Binary firmware for various drivers in the Linux kernel
(metapackage)
ii  firmware-linux-free3.4
all  Binary firmware for various drivers in the Linux kernel
ii  firmware-linux-nonfree 20190114-2
all  Binary firmware for various drivers in the Linux kernel
(meta-package)
ii  libselinux1:amd64  2.8-1+b1
amd64SELinux runtime shared libraries
ii  libv4l-0:amd64 1.16.3-3
amd64Collection of video4linux support libraries
ii  libv4lconvert0:amd64   1.16.3-3
amd64Video4linux frame format conversion library
ii  linux-base 4.6
all  Linux image base package
ii  linux-compiler-gcc-8-x86   4.19.67-2+deb10u1
amd64Compiler for Linux on x86 (meta-package)
ii  linux-headers-4.19.0-5-amd64   4.19.37-5+deb10u2
amd64Header files for Linux 4.19.0-5-amd64
ii  linux-headers-4.19.0-5-common  4.19.37-5+deb10u2
all  Common header files for Linux 4.19.0-5
ii  linux-headers-4.19.0-6-amd64   4.19.67-2+deb10u1
amd64Header files for Linux 4.19.0-6-amd64
ii  linux-headers-4.19.0-6-common  4.19.67-2+deb10u1
all  Common header files for Linux 4.19.0-6
ii  linux-headers-amd644.19+105+deb10u1
amd64Header files for Linux amd64 configuration (meta-package)
ii  linux-image-4.19.0-5-amd64 4.19.37-5+deb10u2
amd64Linux 4.19 for 64-bit PCs (signed)
iF  linux-image-4.19.0-6-amd64 4.19.67-2+deb10u1
amd64Linux 4.19 for 64-bit PCs (signed)
ii  linux-image-amd64  4.19+105+deb10u1
amd64Linux for 64-bit PCs (meta-package)
ii  linux-kbuild-4.19  4.19.67-2+deb10u1
amd64Kbuild infrastructure for Linux 4.19
ii  linux-libc-dev:amd64   4.19.67-2+deb10u1
amd64Linux support headers for userspace development
ii  util-linux 2.33.1-0.1
amd64miscellaneous system utilities
ii  util-linux-locales 2.33.1-0.1
all  locales files for util-linux
~> uname -a
Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
x86_64 GNU/Linux

> Regards,
> 
> -Roberto
> -- 
> Roberto C. Sánchez
>

Re: Debian Buster update error

[CSO]

On Thu, Sep 26, 2019 at 07:59:21AM -0400, Roberto C. Sánchez wrote:
> On Thu, Sep 26, 2019 at 11:48:30AM +, c...@riseup.net wrote:
> > On Thu, Sep 26, 2019 at 01:50:51PM +0200, steve wrote:
> > > Le 26-09-2019, à 11:36:33 +, c...@riseup.net a écrit :
> > > 
> > > > 
> > > > After applying your solution, it still does not work and gives me the
> > > > following error
> > > > 
> > > > apt-get autoremove
> > > > Reading package lists... Done
> > > > Building dependency tree
> > > > Reading state information... Done
> > > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > > > 1 not fully installed or removed.
> > > > After this operation, 0 B of additional disk space will be used.
> > > > Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
> > > > /etc/kernel/postinst.d/initramfs-tools:
> > > > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> > > > 
> > > > gzip: stdout: No space left on device
> > > 
> > > This your problem, no space left on devices.
> > > 
> > > Please copy here the output of
> > > 
> > > df -h
> > > 
> > The following is the output:
> > 
> > df -h
> > FilesystemSize  Used Avail Use% Mounted on
> > udev  1.9G 0  1.9G   0% /dev
> > tmpfs 386M  6.2M  380M   2% /run
> > /dev/mapper/--vg-root  454G  113G  319G  27% /
> > tmpfs 1.9G 0  1.9G   0% /dev/shm
> > tmpfs 5.0M  4.0K  5.0M   1% /run/lock
> > tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
> > /dev/sda1 236M  212M   12M  95% /boot
> > tmpfs 386M  8.0K  386M   1% /run/user/1000
> > 
> 
> Your /boot partition has only 12 MB free.  Additionally, kernel
> 4.19.0-6-amd64 is quite old, as the current version is 4.19.0-11-amd64.
> 
> What is the output of these commands?
> 
> uname -a
> 
> dpkg -l | grep linux
> 
The following is the output:

~> dpkg -l | grep linux
ii  binutils-x86-64-linux-gnu  2.31.1-16
amd64GNU binary utilities, for x86-64-linux-gnu target
ii  console-setup-linux1.193~deb10u1
all  Linux specific part of console-setup
ii  firmware-linux 20190114-2
all  Binary firmware for various drivers in the Linux kernel
(metapackage)
ii  firmware-linux-free3.4
all  Binary firmware for various drivers in the Linux kernel
ii  firmware-linux-nonfree 20190114-2
all  Binary firmware for various drivers in the Linux kernel
(meta-package)
ii  libselinux1:amd64  2.8-1+b1
amd64SELinux runtime shared libraries
ii  libv4l-0:amd64 1.16.3-3
amd64Collection of video4linux support libraries
ii  libv4lconvert0:amd64   1.16.3-3
amd64Video4linux frame format conversion library
ii  linux-base 4.6
all  Linux image base package
ii  linux-compiler-gcc-8-x86   4.19.67-2+deb10u1
amd64Compiler for Linux on x86 (meta-package)
ii  linux-headers-4.19.0-5-amd64   4.19.37-5+deb10u2
amd64Header files for Linux 4.19.0-5-amd64
ii  linux-headers-4.19.0-5-common  4.19.37-5+deb10u2
all  Common header files for Linux 4.19.0-5
ii  linux-headers-4.19.0-6-amd64   4.19.67-2+deb10u1
amd64Header files for Linux 4.19.0-6-amd64
ii  linux-headers-4.19.0-6-common  4.19.67-2+deb10u1
all  Common header files for Linux 4.19.0-6
ii  linux-headers-amd644.19+105+deb10u1
amd64Header files for Linux amd64 configuration (meta-package)
ii  linux-image-4.19.0-5-amd64 4.19.37-5+deb10u2
amd64Linux 4.19 for 64-bit PCs (signed)
iF  linux-image-4.19.0-6-amd64 4.19.67-2+deb10u1
amd64Linux 4.19 for 64-bit PCs (signed)
ii  linux-image-amd64  4.19+105+deb10u1
amd64Linux for 64-bit PCs (meta-package)
ii  linux-kbuild-4.19  4.19.67-2+deb10u1
amd64Kbuild infrastructure for Linux 4.19
ii  linux-libc-dev:amd64   4.19.67-2+deb10u1
amd64Linux support headers for userspace development
ii  util-linux 2.33.1-0.1
amd64miscellaneous system utilities
ii  util-linux-locales 2.33.1-0.1
all  locales files for util-linux
~> uname -a
Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
x86_64 GNU/Linux

> Regards,
> 
> -Roberto
> -- 
> Roberto C. Sánchez
> 

Re: Debian Buster update error

[Roberto C . Sánchez]

On Thu, Sep 26, 2019 at 11:48:30AM +, c...@riseup.net wrote:
> On Thu, Sep 26, 2019 at 01:50:51PM +0200, steve wrote:
> > Le 26-09-2019, à 11:36:33 +, c...@riseup.net a écrit :
> > 
> > > 
> > > After applying your solution, it still does not work and gives me the
> > > following error
> > > 
> > > apt-get autoremove
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > > 1 not fully installed or removed.
> > > After this operation, 0 B of additional disk space will be used.
> > > Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
> > > /etc/kernel/postinst.d/initramfs-tools:
> > > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> > > 
> > > gzip: stdout: No space left on device
> > 
> > This your problem, no space left on devices.
> > 
> > Please copy here the output of
> > 
> > df -h
> > 
> The following is the output:
> 
> df -h
> FilesystemSize  Used Avail Use% Mounted on
> udev  1.9G 0  1.9G   0% /dev
> tmpfs 386M  6.2M  380M   2% /run
> /dev/mapper/--vg-root  454G  113G  319G  27% /
> tmpfs 1.9G 0  1.9G   0% /dev/shm
> tmpfs 5.0M  4.0K  5.0M   1% /run/lock
> tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
> /dev/sda1 236M  212M   12M  95% /boot
> tmpfs 386M  8.0K  386M   1% /run/user/1000
> 

Your /boot partition has only 12 MB free.  Additionally, kernel
4.19.0-6-amd64 is quite old, as the current version is 4.19.0-11-amd64.

What is the output of these commands?

uname -a

dpkg -l | grep linux

Regards,

-Roberto
-- 
Roberto C. Sánchez

Re: Debian Buster update error

[CSO]

On Thu, Sep 26, 2019 at 01:50:51PM +0200, steve wrote:
> Le 26-09-2019, à 11:36:33 +, c...@riseup.net a écrit :
> 
> > 
> > After applying your solution, it still does not work and gives me the
> > following error
> > 
> > apt-get autoremove
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > 1 not fully installed or removed.
> > After this operation, 0 B of additional disk space will be used.
> > Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
> > /etc/kernel/postinst.d/initramfs-tools:
> > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> > 
> > gzip: stdout: No space left on device
> 
> This your problem, no space left on devices.
> 
> Please copy here the output of
> 
> df -h
> 
The following is the output:

df -h
FilesystemSize  Used Avail Use% Mounted on
udev  1.9G 0  1.9G   0% /dev
tmpfs 386M  6.2M  380M   2% /run
/dev/mapper/--vg-root  454G  113G  319G  27% /
tmpfs 1.9G 0  1.9G   0% /dev/shm
tmpfs 5.0M  4.0K  5.0M   1% /run/lock
tmpfs 1.9G 0  1.9G   0% /sys/fs/cgroup
/dev/sda1 236M  212M   12M  95% /boot
tmpfs 386M  8.0K  386M   1% /run/user/1000

Re: Debian Buster update error

[steve]

Le 26-09-2019, à 11:36:33 +, c...@riseup.net a écrit :



After applying your solution, it still does not work and gives me the
following error

apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64

gzip: stdout: No space left on device


This your problem, no space left on devices.

Please copy here the output of 


df -h

Re: Debian Buster update error

[CSO]

On Thu, Sep 26, 2019 at 10:17:15AM +0200, to...@tuxteam.de wrote:
> On Thu, Sep 26, 2019 at 07:55:36AM +, c...@riseup.net wrote:
> > Hi,
> > When update buster, it gives the following errors:
> > 
> > Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
> > /etc/kernel/postinst.d/initramfs-tools:
> > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> > 
> > gzip: stdout: No space left on device
> > E: mkinitramfs failure cpio 141 gzip 1
> > update-initramfs: failed for /boot/initrd.img-4.19.0-6-amd64 with 1.
> > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
> > code 1
> > dpkg: error processing package linux-image-4.19.0-6-amd64 (--configure):
> >  installed linux-image-4.19.0-6-amd64 package post-installation script
> >  subprocess returned error exit status 1
> >  Errors were encountered while processing:
> >   linux-image-4.19.0-6-amd64
> >   E: Sub-process /usr/bin/dpkg returned an error code (1)
> > 
> > Any ideas how to solve it?
> 
> It seems that your /boot filesystem is full -- perhaps because old
> kernel packages still lurk around.
> 
> You could try "sudo apt autoremove", which would remove unneeded
> packages (old kernel packages are among them).
> 
> If you're the prudent kind, you could try first "apt -s autoremove"
> to see what it would do (no need to sudo).
> 

After applying your solution, it still does not work and gives me the
following error

apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.19.0-6-amd64 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
code 1
dpkg: error processing package linux-image-4.19.0-6-amd64 (--configure):
 installed linux-image-4.19.0-6-amd64 package post-installation script
 subprocess returned error exit status 1
 Errors were encountered while processing:
  linux-image-4.19.0-6-amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Please note I installed buster two months ago and it is completely new
installation, not upgrade.
Mark
> Cheers
> -- t

Re: Debian Buster update error

[Ben Hutchings]

On Thu, 2019-09-26 at 07:55 +, c...@riseup.net wrote:
> Hi,
> When update buster, it gives the following errors:
> 
> Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> 
> gzip: stdout: No space left on device
> E: mkinitramfs failure cpio 141 gzip 1
> update-initramfs: failed for /boot/initrd.img-4.19.0-6-amd64 with 1.
> run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
> code 1
> dpkg: error processing package linux-image-4.19.0-6-amd64 (--configure):
>  installed linux-image-4.19.0-6-amd64 package post-installation script
>  subprocess returned error exit status 1
>  Errors were encountered while processing:
>   linux-image-4.19.0-6-amd64
>   E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Any ideas how to solve it?
[...]

There are several things you can try:

* Remove outdated kernel packages with "apt autoremove"
* Expand the /boot partition (but it seems you already found this is
  impossible)
* Exclude unneeded modules from the initramfs:
  - Change the MODULES setting in /etc/initramfs-tools/initrams.conf
to MODULES=dep
  - Run "update-initramfs -u"
  If you do this, the disk probably won't be bootable if you move it to
  another computer.
* Compress the initramfs harder:
  - Change the COMPRESS setting in initramfs.conf to COMPRESS=xz
  This will make kernel/initramfs updates very slow, though.

Ben.

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein




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

Re: Running a music player via cron

[A . Söldner]

To listen music under bash I always use cvlc from program vlc.

Maybe a other possibility.

Regards

Am 25.09.2019 um 17:24 schrieb Jean-Philippe MENGUAL:

Hello,

Since some Sid update (about 2 weeks), something may have happent in te
audio stack or the terminal because what worked no longer works.

So I am under Sid, MATE desktop, via lightdm, pulseaudio,
systemd, etc. Ont minor thing is that if I run an audio as a user or
root at boot before login invia lightem, audio does not work, but well...

Anyway, here I want to run mpv via a cron job under my regular user. The
command works, but via cron, I get an audio access problem.

The command:
killall mpv;/home/jp/radio 10 100

The result:


TERM environment variable not set.
setleds: Error reading current flags setting. Maybe you are not on the
console?: ioctl KDGKBLED: Ioctl() inapproprié pour un périphérique
TERM environment variable not set.
CTRL+C to exit
Playing: http://direct.franceinfo.fr/live/franceinfo-midfi.mp3
  (+) Audio --aid=1 (mp3 1ch 44100Hz)
ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
[ao/alsa] Playback open error: Device or resource busy
[ao/oss] Can't open audio device /dev/dsp: Device or resource busy
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
skipping unlock
[ao/jack] cannot open server
ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
couldn't open play stream: Device or resource busy
[ao/sndio] can't open sndio default
[ao] Failed to initialize audio driver 'sndio'
Could not open/initialize audio device -> no sound.
Audio: no audio
: 00:00:00 / 00:00:00 (0%) Cache:  0s


Exiting... (Errors when loading file)
TERM environment variable not set.


TERM environment variable not set.

Same with:
killall mpv;env DISPLAY=:0 /home/jp/radio 10 100

Here is the script:
https://paste.debian.net/1102308/

Thanks for your help


Regards

Re: Debian Buster update error

[tomas]

On Thu, Sep 26, 2019 at 07:55:36AM +, c...@riseup.net wrote:
> Hi,
> When update buster, it gives the following errors:
> 
> Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> 
> gzip: stdout: No space left on device
> E: mkinitramfs failure cpio 141 gzip 1
> update-initramfs: failed for /boot/initrd.img-4.19.0-6-amd64 with 1.
> run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
> code 1
> dpkg: error processing package linux-image-4.19.0-6-amd64 (--configure):
>  installed linux-image-4.19.0-6-amd64 package post-installation script
>  subprocess returned error exit status 1
>  Errors were encountered while processing:
>   linux-image-4.19.0-6-amd64
>   E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Any ideas how to solve it?

It seems that your /boot filesystem is full -- perhaps because old
kernel packages still lurk around.

You could try "sudo apt autoremove", which would remove unneeded
packages (old kernel packages are among them).

If you're the prudent kind, you could try first "apt -s autoremove"
to see what it would do (no need to sudo).

Cheers
-- t


signature.asc
Description: Digital signature

Debian Buster update error

[CSO]

Hi,
When update buster, it gives the following errors:

Setting up linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.19.0-6-amd64 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
code 1
dpkg: error processing package linux-image-4.19.0-6-amd64 (--configure):
 installed linux-image-4.19.0-6-amd64 package post-installation script
 subprocess returned error exit status 1
 Errors were encountered while processing:
  linux-image-4.19.0-6-amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Any ideas how to solve it?

When installing and setting up debian, I use all default setting with
whole disk encryption. So, since the problems seem to be the default
setting of boot section at the time of installation is too small, how do I 
increase it now when I have full disk encryption?

Also, my hardrive has 500 GB empty space left, so, there are plenty of
space. 

The debian development team probably should increase the default boot
section by 5 times or 10 times in order to meet the inceased software
demands.
Mark

Re: How To Install Debian 10.0.0

[Thomas Schmitt]

Hi,

Saurav Sarkar wrote:
> As the downloaded installation dvd is not working how can i install
> debian 10.0.0 ???

You could try with a USB stick.
See
  https://www.debian.org/CD/faq/#write-usb

(On MS-Windows it seems that program Rufus in "dd" mode is currently the
 best way to copy an image to a disk-like device. I have seen reports
 that the proposed win32diskimager is annoying. Mere hearsay, of course.)

--

Nevertheless, did you read the rest of my mail
  https://lists.debian.org/debian-user/2019/09/msg00863.html
Especially the advise to ask at debian...@lists.debian.org for info
about the error message about ldlinux.c32 and to test a netinst ISO for
better handling in experiments ?

I now add the advise to tell debian-cd the exact messages which you can
see on the screen, wenn the error occurs.

Plus the advise to subscribe to the Debian lists where you ask questions.
E.g. via
  https://lists.debian.org/debian-user/
  https://lists.debian.org/debian-cd/
Many of the participants do not add a Cc: for non-subscribed mail senders.


Have a nice day :)

Thomas

Customer Customization Support

[SHENZHEN LONGEN LIGHTING]

[1] Catalogue Request

Professional LED lights suppliers with more than 5 years experience.
Customer customization Support.
Provision of procurement serivices.

Adelina Li
SHENZHEN LONGEN LIGHTING CO.,LTD.
Mob(wechat):0086 18938048066  Tel:0755-85088066
A2 Building,Xinbaoji industrial park,Yintian,Xixiant Town,Bao'an 
district,Shenzhen.China

[2] View this email in your browser

You are receiving this email because of your relationship with SHENZHEN LONGEN 
LIGHTING. Please [3] reconfirmyour interest in receiving emails from us. If you 
do not wish to receive any more emails, you can [4] unsubscribe here.


 References:

1. mailto:380263...@qq.com
2. https://clt1072881.benchurl.com/c/v?e=EEDDA0&c=105EF1&t=0
3. https://clt1072881.benchurl.com/c/opt?e=EEDDA0&c=105EF1&t=0
4. https://clt1072881.benchurl.com/c/su?e=EEDDA0&c=105EF1&t=0

This message was sent to debian-user@lists.debian.org by 
sales1-adel...@longenled.com

You can modify/update your subscription via the link below.

Unsubscribe from all mailings
http://clt1072881.benchurl.com/c/su?e=EEDDA0&c=105EF1&l=2FCBFE53&email=fTHoM8aX4cmOiekgLiREPQODfNw3Y4%2FbUKEtWoQMMiA%3D&relid=A0B1AAA


Manage Subscription
http://clt1072881.benchurl.com/c/s?e=EEDDA0&c=105EF1&l=2FCBFE53&email=fTHoM8aX4cmOiekgLiREPQODfNw3Y4%2FbUKEtWoQMMiA%3D&relid=A0B1AAA


Forward Email
http://clt1072881.benchurl.com/c/f?e=EEDDA0&c=105EF1&l=2FCBFE53&email=fTHoM8aX4cmOiekgLiREPQODfNw3Y4%2FbUKEtWoQMMiA%3D&relid=A0B1AAA


Report Abuse
http://clt1072881.benchurl.com/Abuse?e=EEDDA0&c=105EF1&l=2FCBFE53&email=fTHoM8aX4cmOiekgLiREPQODfNw3Y4%2FbUKEtWoQMMiA%3D&relid=A0B1AAA


A2 Building,Xinbaoji industrial park,Yintian,Xixiant Town,Bao'an district, 
Shenzhen, Guangdong  1, China

Email Marketing
benchmarkemail.com
 [http://clt1072881.benchurl.com]



http://clt1072881.benchurl.com/c/opt?e=EEDDA0&c=105EF1&l=2FCBFE53&email=fTHoM8aX4cmOiekgLiREPQODfNw3Y4%2FbUKEtWoQMMiA%3D&relid=A0B1AAA


http://clt1072881.benchurl.com/c/su?e=EEDDA0&c=105EF1&l=2FCBFE53&email=fTHoM8aX4cmOiekgLiREPQODfNw3Y4%2FbUKEtWoQMMiA%3D&relid=A0B1AAA