Re: systemd autocompletion does not work

[Michael Biebl]

Am 28.07.2017 um 06:14 schrieb Kamil Jońca:

> /etc/dbus-1/system.d/:
> 
> -rw-r--r-- 1 root root 3947 Apr 29  2014 org.freedesktop.systemd-shim.conf

Purge the systemd-shim package. This file from systemd-shim is breaking
systemd.



signature.asc
Description: OpenPGP digital signature

Re: systemd autocompletion does not work

[Kamil Jońca]

Michael Biebl  writes:

> Am 27.07.2017 um 19:09 schrieb Kamil Jońca:
>> 
>> 1. Box with debian sid, updated frequently
>> 2. Recently I realized that completion of systemd units does not work,
>> ie.
>> $sudo systemd restart  gives me "@" sign only.
>> I noticed that, at the moment of pressing tab I got in /var/log/auth.log
>> --8<---cut here---start->8---
>> 2017-07-27T19:01:37.228534+02:00 alfa dbus[685]: [system] Rejected
>> send message, 4 matched rules; type="method_call", sender=":1.507"
>> (uid=1000 pid=10335 comm="systemctl --full --no-legend --no-pager
>> list-unit-") interface="org.freedesktop.systemd1.Manager"
>> member="ListUnitFilesByPatterns" error name="(unset)"
>> requested_reply="0" destination="org.freedesktop.systemd1" (uid=0
>> pid=1 comm="/sbin/init ")
>
> Can you provide the systemd and dbus version and the output of
> ls -la /etc/dbus-1/system.d/ /usr/share/dbus-1/system.d/

$dpkg -l systemd dbus
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture   
 Description
+++--===-===-=
ii  dbus 1.10.20-1   amd64  
 simple interprocess messaging system (daemon and utilities)
ii  systemd  234-2   amd64  
 system and service manager

$ls -la /etc/dbus-1/system.d/ /usr/share/dbus-1/system.d/
/etc/dbus-1/system.d/:  
  
total 36
drwxr-xr-x 2 root root 4096 Jul 27 19:11 .
drwxr-xr-x 4 root root 4096 Jul  2 07:19 ..
-rw-r--r-- 1 root root 1144 Dec  9  2014 avahi-dbus.conf
-rw-r--r-- 1 root root 1630 Aug 18  2015 bluetooth.conf
-rw-r--r-- 1 root root 1569 Jun  5  2014 org.freedesktop.ColorManager.conf
-rw-r--r-- 1 root root  632 May 22  2014 org.freedesktop.PolicyKit1.conf
-rw-r--r-- 1 root root 1075 Nov 16  2014 org.freedesktop.RealtimeKit1.conf
-rw-r--r-- 1 root root 3947 Apr 29  2014 org.freedesktop.systemd-shim.conf
-rw-r--r-- 1 root root 1084 Apr 27  2015 pulseaudio-system.conf

/usr/share/dbus-1/system.d/:
total 60
drwxr-xr-x 2 root root  4096 Jul 22 11:17 .
drwxr-xr-x 6 root root  4096 Jul  2 07:18 ..
-rw-r--r-- 1 root root   947 Jul 12 16:01 org.freedesktop.hostname1.conf
-rw-r--r-- 1 root root   937 Jul 12 16:01 org.freedesktop.locale1.conf
-rw-r--r-- 1 root root 12499 Jul 12 16:01 org.freedesktop.login1.conf
-rw-r--r-- 1 root root  1604 Jul 12 16:01 org.freedesktop.network1.conf
-rw-r--r-- 1 root root   953 Jul 12 16:01 org.freedesktop.resolve1.conf
-rw-r--r-- 1 root root 12654 Jul 12 16:01 org.freedesktop.systemd1.conf
-rw-r--r-- 1 root root   947 Jul 12 16:01 org.freedesktop.timedate1.conf


KJ
-- 
http://wolnelektury.pl/wesprzyj/teraz/
It is the wise bird who builds his nest in a tree.

Re: systemd autocompletion does not work

[Michael Biebl]

Am 27.07.2017 um 19:09 schrieb Kamil Jońca:
> 
> 1. Box with debian sid, updated frequently
> 2. Recently I realized that completion of systemd units does not work,
> ie.
> $sudo systemd restart  gives me "@" sign only.
> I noticed that, at the moment of pressing tab I got in /var/log/auth.log
> --8<---cut here---start->8---
> 2017-07-27T19:01:37.228534+02:00 alfa dbus[685]: [system] Rejected send 
> message, 4 matched rules; type="method_call", sender=":1.507" (uid=1000 
> pid=10335 comm="systemctl --full --no-legend --no-pager list-unit-") 
> interface="org.freedesktop.systemd1.Manager" member="ListUnitFilesByPatterns" 
> error name="(unset)" requested_reply="0" 
> destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")

Can you provide the systemd and dbus version and the output of
ls -la /etc/dbus-1/system.d/ /usr/share/dbus-1/system.d/


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



signature.asc
Description: OpenPGP digital signature

Re: La chose dont on a discuté l’autre fois – ça a vraiment marché! Sandra

[whos . pascal]

Le 2017-07-10 12:31, Sandra Hatemenot a écrit :

Je l’ai fait sans vêtements et voilà ce qui s’est passé
http://bitly.com/2tyQzgX


est ce que je suis venu te demander d'envoyer de la merde dans ma boite 
mail ?

non !
alors dégages, toi et ton arnaque a la con dont je me bat les couilles 
royalement...!!

détruit mon ad-mail !!
je tai pas déjà dis daller te faire enculer avec tes putains de merdes 
de conneries 


mais tu comprend pas ce qu'on te dit gros batard de sac a merde...??? 
vas ta faire enculer !!!

Re: Parler est comme jouer au tennis avec des réceptions et envois de la balle Noemie

[whos . pascal]

Le 2017-07-08 10:27, Noemie Famousl a écrit :

J’adore les balles. Tu veux qu’on parle?
http://bitly.com/2sY4KIO



est ce que je suis venu te demander d'envoyer de la merde dans ma boite 
mail ?

non !
alors dégages, toi et ton arnaque a la con dont je me bat les couilles 
royalement...!!

détruit mon ad-mail !!
je tai pas déjà dis daller te faire enculer avec tes putains de merdes 
de conneries 


mais tu comprend pas ce qu'on te dit gros batard de sac a merde...??? 
vas ta faire enculer !!!

Re: Tu voudrais bien m’aider à devenir plus bavarde avec toi? Amandine

[whos . pascal]

Le 2017-07-05 12:18, Amandine Cruceru a écrit :

Je sens qu’on pourra trouver une langue commune sur plusieurs
sujets.
http://bitly.com/2sLnJGv


est ce que je suis venu te demander d'envoyer de la merde dans ma boite 
mail ?

non !
alors dégages, toi et ton arnaque a la con dont je me bat les couilles 
royalement...!!

détruit mon ad-mail !!
je tai pas déjà dis daller te faire enculer avec tes putains de merdes 
de conneries 


mais tu comprend pas ce qu'on te dit gros batard de sac a merde...??? 
vas ta faire enculer !!!

Re: N’hésites pas de commencer une conversation avec moi Elise

[whos . pascal]

Le 2017-07-04 13:10, Elise Bovzdarenko a écrit :

Je ne mords pas tu sais. Bon, sauf si t le demande…
http://bitly.com/2sI2MMI



est ce que je suis venu te demander d'envoyer de la merde dans ma boite 
mail ?

non !
alors dégages, toi et ton arnaque a la con dont je me bat les couilles 
royalement...!!

détruit mon ad-mail !!
je tai pas déjà dis daller te faire enculer avec tes putains de merdes 
de conneries 


mais tu comprend pas ce qu'on te dit gros batard de sac a merde...??? 
vas ta faire enculer !!!

Re: Faire de l'argent en ligne

[Fortune Internet]

Salut,

Imaginez si vous pouviez construire votre propre
produit dans votre marché, des entonnoirs, des
offres et des pages de marketing comme les gourous
le font, mais sans tout les maux
de tête ...

Imaginez des pages incroyables à conversion élevée
qui rapportent des abonnés affamés et des tonnes de
nouveaux clients à chaque jour en utilisant le
modèle le plus puissant qu'il est possible
d'utiliser ...

Les gens se démènent pour acheter vos produits ...

Imaginez maintenant que vous pourriez facilement
créer votre produit, des pages de vente, pages
d'inscription, pages de webinaire, pages de bonus,
pages d'affiliation et beaucoup plus ...

Maintenant vous pouvez avec ce système étonnant
qui a pris le monde du marketing par surprise ...

Cliquez ici pour voir ce système en action

En exploitant toutes les meilleurs pratiques qui
ont prouvés avoir un haut taux de conversion et qui
sont utilisées par les pros que vous pouvez
littéralement voir monter en flèche
vos profits ...

Jetez un oeil maintenant et vous verrez pourquoi tout
le monde est si excité à ce sujet:

=> http://machinedemarketing.com

Ce système est beaucoup plus puissant que beaucoup de
systèmes et vous transforme instantanément en maître du
marketing en ligne, indépendamment de l'expérience et
si vous avez un site ou non ...

Ne prenez pas seulement mon opinion, allez regarder
la démo EN DIRECT et voyez par vous-même. Il y a trop
pour tout vous expliquer dans cet e-mail ...

Je donne le feu vert et je sais que ceci transformera
la façon dont vous faites des affaires en ligne ...

Essayez-le pour seulement 1 euro

Pour votre réussite,

Samuel Hains

P.S. Il est actuellement en pré-lancement et en spécial,
mais seulement pour une période limitée. 

C'est votre seule chance de l'obtenir à ce prix incroyable ...

Allez ici maintenant: => http://machinedemarketing.com

Re: systemd autocompletion does not work

[Kamil Jońca]

Michael Biebl  writes:
[...]
>
> Are you sure you are using systemd as PID 1? Is systemd-sysv installed
> and have you rebooted since installing that package?
>
hm.
$ps ax

shows [..stripped..]

1 ?Ss 0:33 /sbin/init

then

$ll /sbin/init
lrwxrwxrwx 1 root root 20 Jul 20 15:13 /sbin/init -> /lib/systemd/systemd

$dpkg -l systemd-sysv
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture   
 Description
+++--===-===-=
ii  systemd-sysv 234-2   amd64  
 system and service manager - SysV links

Yes, computer was restarted.
KJ


-- 
http://wolnelektury.pl/wesprzyj/teraz/
If it's worth doing, it's worth doing for money.

Re: Stretch: xfce and xscreensaver

[Patrick Bartek]

On Thu, 27 Jul 2017 10:55:23 -0400 Greg Wooledge 
wrote:

> On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek wrote:
> > Or do what I did: dispense with a screensaver entirely.  Haven't
> > used one in years.  Waste of CPU cycles.  Besides modern computer
> > screens don't even need them anymore.  They aren't prone to image
> > burning like tube-type monitors were.  I just use xset or a power
> > management utility, if installed, to "sleep" the monitor display
> > after a set time of system idleness. Works great.
> 
> For many of us, the primary function of the screen saver isn't the
> prevention of image burn-in, but rather the locking of the session to
> prevent other people from taking control when we step away.

Maybe, for "many," but I think "most" use them because they are
used to them, and the "cool" pictures and designs they display.
Security is secondary.

> Personally I use i3lock for this.  Nice and simple.  I don't use any
> kind of automatic invocation or idle checking.  I just manually run it
> when I'm about to step away.  (Used to use xlock, from xlockmore, but
> that was removed from Debian several releases ago.)

 I lock my screen manually, too.  Much of my work involves studying
what's on the screen without any input.  It's an annoyance when it
"blanks" and I have to log back in disrupting my train of thought.

That's why we have so many choices and configurations.

B

Re: systemd autocompletion does not work

[Michael Biebl]

Am 27.07.2017 um 22:20 schrieb Kamil Jońca:
> Michael Biebl  writes:
> 
>> Am 27.07.2017 um 19:09 schrieb Kamil Jońca:
>>>
>>> 1. Box with debian sid, updated frequently
>>> 2. Recently I realized that completion of systemd units does not work,
>>> ie.
>>> $sudo systemd restart  gives me "@" sign only.
>>
>> ...
>>
>>> What am I missing?
>>
>> The tool is called systemctl, not systemd.
> 
> You're right, my typo.
> But what am I missing?
> KJ
> 

Are you sure you are using systemd as PID 1? Is systemd-sysv installed
and have you rebooted since installing that package?



signature.asc
Description: OpenPGP digital signature

Re: systemd autocompletion does not work

[Kamil Jońca]

Michael Biebl  writes:

> Am 27.07.2017 um 19:09 schrieb Kamil Jońca:
>> 
>> 1. Box with debian sid, updated frequently
>> 2. Recently I realized that completion of systemd units does not work,
>> ie.
>> $sudo systemd restart  gives me "@" sign only.
>
> ...
>
>> What am I missing?
>
> The tool is called systemctl, not systemd.

You're right, my typo.
But what am I missing?
KJ

-- 
http://wolnelektury.pl/wesprzyj/teraz/
Beware the one behind you.

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Patrick Flaig]

Hi Michael,

great, that was the problem, removed the file, recreated the initramfs, now it 
works like a charm.
Thanks a lot for the help.

Patrick

> Am 27.07.2017 um 21:29 schrieb Michael Biebl :
> 
> Am 27.07.2017 um 20:21 schrieb Patrick Flaig:
>> Sure, this is the content:
>> 
>> cat /tmp/foo/lib/systemd/network/99-default.link 
> 
> Thanks Patrick.
> So, it seems the udev maintainer scripts detected at virtualized
> environment which causes the following code to be triggered:
> 
> https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/udev.postinst#n49
> 
> The /etc/systemd/network/99-default.link file overrides the the package
> provided one from /lib/systemd/network/99-default.link
> 
> So, in order to enable the new naming scheme, remove
> /etc/systemd/network/99-default.link then rebuild the initramfs.
> 
> On the next boot you should have the new network interface names.
> 
> Regards,
> Michael
> 
> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 

Re: cups jobs queue

[Brian]

On Thu 27 Jul 2017 at 13:06:33 +0200, Pol Hallen wrote:

> ?waitjob=false
> 
> thanks :)

A very neat and elegant solution. For those who are mystified or
wondering what the fuss about:

Pol Hallen has a *local* queue set up with a device_uri like

  ipp://192.168.1.100/printers/E460DN

He meets the problem he has descibed. Changing the device_uri to

  ipp://192.168.1.100/printers/E460DN?waitjob=false

exercises the power of IPP and allows all jobs to be queued on the
server.

-- 
Brian.

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Michael Biebl]

Am 27.07.2017 um 20:21 schrieb Patrick Flaig:
> Sure, this is the content:
> 
> cat /tmp/foo/lib/systemd/network/99-default.link 

Thanks Patrick.
So, it seems the udev maintainer scripts detected at virtualized
environment which causes the following code to be triggered:

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/udev.postinst#n49

The /etc/systemd/network/99-default.link file overrides the the package
provided one from /lib/systemd/network/99-default.link

So, in order to enable the new naming scheme, remove
/etc/systemd/network/99-default.link then rebuild the initramfs.

On the next boot you should have the new network interface names.

Regards,
Michael


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



signature.asc
Description: OpenPGP digital signature

Re: Power draw from UPS

[Jörg-Volker Peetz]

Maybe this is helpful
APC UPS - ArchWiki https://wiki.archlinux.org/index.php/APC_UPS
Please report back if and how it works.

Regards,
jvp.

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Patrick Flaig]

Sure, this is the content:

cat /tmp/foo/lib/systemd/network/99-default.link 
# This machine is most likely a virtualized guest, where the old persistent
# network interface mechanism (75-persistent-net-generator.rules) did not work.
# This file disables /lib/systemd/network/99-default.link to avoid
# changing network interface names on upgrade. Please read
# /usr/share/doc/udev/README.Debian.gz about how to migrate to the currently
# supported mechanism.

The content of the README, doesn’t help that much as 99-default.link doesn’t 
seem to be a symlink.

cat /usr/share/doc/udev/README.Debian 
This documents udev integration Debian specifics. Please see man udev(7) and
its referenced manpages for general documentation.

Network interface naming

Since version 197 udev has a builtin persistent name generator which checks
firmware/BIOS provided index numbers or slot names (similar to biosdevname),
falls back to slot names (PCI numbers, etc., in the spirit of
/dev/disks/by-path/), and then optionally falls back to MAC address, and
generates names based on these properties. This provides "location oriented"
names for PCI cards such as "enp0s1" for ethernet, or wlp1s0" for a WIFI card
so that replacing a broken network card does not change the name. As location
based naming does not work well for USB devices, these use a MAC based naming
schema (see /lib/udev/rules.d/73-usb-net-by-mac.rules).

This has been enabled by default since udev 220-7, which affects new
installations/hardware. Existing installations/hardware which already got
covered by the old 75-persistent-net-generator.rules will keep their interface
names, see below.

You can disable these stable names and go back to the kernel-provided ones
(which don't have a stable order) in one of two ways:

  - Put "net.ifnames=0" into the kernel command line (e. g. in
/etc/default/grub's GRUB_CMDLINE_LINUX_DEFAULT, then run "update-grub").

  - Disable the default *.link rules with
"ln -s /dev/null /etc/systemd/network/99-default.link"
and rebuild the initrd with "update-initramfs -u".

See this page for more information:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

Legacy persistent network interface naming
~~
Debian releases up to 8 ("Jessie") and Ubuntu up to 15.04 had an udev rule
/lib/udev/rules.d/75-persistent-net-generator.rules which fixed the name of a
network interface that it got when its MAC address first appeared in a
dynamically created /etc/udev/rules.d/70-persistent-net.rules file.

This had inherent race conditions (which sometimes caused collisions and
interface names like "rename1"), required having to write state into /etc
(which isn't possible for read-only root), and did not work in virtualized
environments.

This old schema is deprecated in Debian 9 ("Stretch"), and will not
be supported any more in Debian 10.

Migration to the current network interface naming
~
On package upgrade systems will keep their current names, but they will need to
be manually migrated by Debian 10 / Ubuntu 18.04 LTS.  If you rely on the old
names in custom ifupdown stanzas, firewall scripts or other networking
configuration, these need to be updated to the new names.

First, determine all relevant network interface names: those in
/etc/udev/rules.d/70-persistent-net.rules, or if that does not exist (in
virtual machines), in "ip link" or /sys/class/net/.

Then for every interface name use a command like

  grep -r eth0 /etc

to find out where it is being used.

Then on "real hardware" machines, rename the file to
70-persistent-net.rules.old; on VMs remove the file
/etc/udev/rules.d/80-net-setup-link.rules instead.

Reboot, adjust configuration files, and test your system.

Custom net interface naming
~~~
In some cases it is convenient to define your own specific names for network
interfaces. These can be customized in two different ways:

 * You can create your own names via udev rules, based on arbitrary attribute
   and property matches. See man udev(7) for documentation how to write udev
   rules. For example, you can create /etc/udev/rules.d/76-netnames.rules with

    snip --
   # identify device by MAC address
   SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="11:22:aa:bb:cc:33", 
NAME="eth-dmz"

   # identify by vendor/model ID
   SUBSYSTEM=="net", ACTION=="add", ENV{ID_VENDOR_ID}=="0x8086", \
   ENV{ID_MODEL_ID}=="0x1502", NAME="eth-intel-gb"

   # USB device by path
   # get ID_PATH if not present yet
   ENV{ID_PATH}=="", IMPORT{builtin}="path_id"
   SUBSYSTEM=="net", ACTION=="add", ENV{ID_PATH}=="*-usb-0:3:1*", 
NAME="eth-blue-hub"
    snip --

   The name of the rules file needs to have a prefix smaller than "80" so that
   it runs before /lib/udev/rules.d/80-net-setup-link.rules, and should have a
   prefix bigger than "75

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Michael Biebl]

Am 27.07.2017 um 19:50 schrieb Patrick Flaig:
> Oh my fault, 99-default.link is available, I checked the wrong folder.
> The file is containing some text, saying that the machine is most likely a 
> virtualized guest.

Can you paste the contents verbatim.


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



signature.asc
Description: OpenPGP digital signature

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Patrick Flaig]

Oh my fault, 99-default.link is available, I checked the wrong folder.
The file is containing some text, saying that the machine is most likely a 
virtualized guest.

> Am 27.07.2017 um 19:28 schrieb Michael Biebl :
> 
> Am 27.07.2017 um 18:55 schrieb debian-li...@patschie.de:
> 
>>> Am 27.07.2017 um 18:25 schrieb Michael Biebl :
>>> lsinitramfs /boot/initrd.img-$(uname -r) | grep 99-default.link
>>> lib/systemd/network/99-default.link
>> Missing
> 
> Odd. Do you have that file on the host system?
> Can you check with debsums -as udev systemd.
> 
> /usr/share/initramfs-tools/hooks/udev should copy that link file into
> the initramfs.
> 
> Do you by chance have any custom initramfs hooks in
> /etc/initramfs-tools/hooks which override the udev hook?
> 
> 

Re: systemd autocompletion does not work

[Michael Biebl]

Am 27.07.2017 um 19:09 schrieb Kamil Jońca:
> 
> 1. Box with debian sid, updated frequently
> 2. Recently I realized that completion of systemd units does not work,
> ie.
> $sudo systemd restart  gives me "@" sign only.

...

> What am I missing?

The tool is called systemctl, not systemd.




signature.asc
Description: OpenPGP digital signature

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Michael Biebl]

Am 27.07.2017 um 18:55 schrieb debian-li...@patschie.de:

>> Am 27.07.2017 um 18:25 schrieb Michael Biebl :
>> lsinitramfs /boot/initrd.img-$(uname -r) | grep 99-default.link
>> lib/systemd/network/99-default.link
> Missing

Odd. Do you have that file on the host system?
Can you check with debsums -as udev systemd.

/usr/share/initramfs-tools/hooks/udev should copy that link file into
the initramfs.

Do you by chance have any custom initramfs hooks in
/etc/initramfs-tools/hooks which override the udev hook?




signature.asc
Description: OpenPGP digital signature

systemd autocompletion does not work

[Kamil Jońca]

1. Box with debian sid, updated frequently
2. Recently I realized that completion of systemd units does not work,
ie.
$sudo systemd restart  gives me "@" sign only.
I noticed that, at the moment of pressing tab I got in /var/log/auth.log
--8<---cut here---start->8---
2017-07-27T19:01:37.228534+02:00 alfa dbus[685]: [system] Rejected send 
message, 4 matched rules; type="method_call", sender=":1.507" (uid=1000 
pid=10335 comm="systemctl --full --no-legend --no-pager list-unit-") 
interface="org.freedesktop.systemd1.Manager" member="ListUnitFilesByPatterns" 
error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" 
(uid=0 pid=1 comm="/sbin/init ")
2017-07-27T19:01:37.235178+02:00 alfa dbus[685]: [system] Rejected send 
message, 4 matched rules; type="method_call", sender=":1.508" (uid=1000 
pid=10337 comm="systemctl --full --no-legend --no-pager list-units") 
interface="org.freedesktop.systemd1.Manager" member="ListUnitsByPatterns" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" 
(uid=0 pid=1 comm="/sbin/init ")
2017-07-27T19:01:37.235466+02:00 alfa dbus[685]: [system] Rejected send 
message, 4 matched rules; type="method_call", sender=":1.508" (uid=1000 
pid=10337 comm="systemctl --full --no-legend --no-pager list-units") 
interface="org.freedesktop.systemd1.Manager" member="ListUnitsFiltered" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" 
(uid=0 pid=1 comm="/sbin/init ")
2017-07-27T19:01:37.253102+02:00 alfa dbus[685]: [system] Rejected send 
message, 4 matched rules; type="method_call", sender=":1.510" (uid=1000 
pid=10342 comm="systemctl --full --no-legend --no-pager list-unit-") 
interface="org.freedesktop.systemd1.Manager" member="ListUnitFilesByPatterns" 
error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" 
(uid=0 pid=1 comm="/sbin/init ")
--8<---cut here---end--->8---

What am I missing?
KJ


-- 
http://wolnelektury.pl/wesprzyj/teraz/
I have ways of making money that you know nothing of.
-- John D. Rockefeller

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[debian-lists]

> Am 27.07.2017 um 18:25 schrieb Michael Biebl :
> 
> Am 27.07.2017 um 18:04 schrieb debian-li...@patschie.de:
>> Hi Michael,
>> 
>> I forgot to mention that I also recreated the initramfs: 
>> after several tries just to update it, I deleted the initramfs and recreated 
>> it completely.
>> But still the same effect.
>> 
>> Is there a way to manually check the contents of the initramfs, just to make 
>> sure that the 70-persistent-net.rules isn’t there?
> 
> 
> lsinitramfs /boot/initrd.img-$(uname -r) | grep  70-persistent-net.rules
> 
> This should come up empty.
Confirmed
> 
> The new naming is setup via /lib/udev/rules.d/80-net-setup-link.rules
> and a link file called  99-default.link
99-default.link is missing
> 
> lsinitramfs /boot/initrd.img-$(uname -r) | grep  80-net-setup-link.rules
> lib/udev/rules.d/80-net-setup-link.rules
Available
> lsinitramfs /boot/initrd.img-$(uname -r) | grep 99-default.link
> lib/systemd/network/99-default.link
Missing
> 
> Is this a bare metal or a VM?
VirtualBox VM, as well as the Stretch clean install system, where the 
predictable names are working fine. 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Patrick Flaig]

> Am 27.07.2017 um 18:25 schrieb Michael Biebl :
> 
> Am 27.07.2017 um 18:04 schrieb debian-li...@patschie.de:
>> Hi Michael,
>> 
>> I forgot to mention that I also recreated the initramfs: 
>> after several tries just to update it, I deleted the initramfs and recreated 
>> it completely.
>> But still the same effect.
>> 
>> Is there a way to manually check the contents of the initramfs, just to make 
>> sure that the 70-persistent-net.rules isn’t there?
> 
> 
> lsinitramfs /boot/initrd.img-$(uname -r) | grep  70-persistent-net.rules
> 
> This should come up empty.
Confirmed
> 
> The new naming is setup via /lib/udev/rules.d/80-net-setup-link.rules
> and a link file called  99-default.link
99-default.link is missing
> 
> lsinitramfs /boot/initrd.img-$(uname -r) | grep  80-net-setup-link.rules
> lib/udev/rules.d/80-net-setup-link.rules
Available
> lsinitramfs /boot/initrd.img-$(uname -r) | grep 99-default.link
> lib/systemd/network/99-default.link
Missing
> 
> Is this a bare metal or a VM?
VirtualBox VM, as well as the Stretch clean install system, where the 
predictable names are working fine. 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Patrick Flaig]

Thanks,

confirmed, the initrd doesn’t contain any udev rule files in /etc/udev/rules.d
 
> Am 27.07.2017 um 18:11 schrieb Greg Wooledge :
> 
> On Thu, Jul 27, 2017 at 06:04:49PM +0200, debian-li...@patschie.de wrote:
>> Is there a way to manually check the contents of the initramfs, just to make 
>> sure that the 70-persistent-net.rules isn’t there?
> 
> mkdir /tmp/foo &&
> cd /tmp/foo &&
> unmkinitramfs /boot/initrd.whatever
> 
> (The old way of just running cpio won't work any more, because the new
> initrd.img files are a concatenation of multiple cpio archives.)
> 

Re: Need to upgrade to jessie need help

[David Wright]

On Tue 25 Jul 2017 at 20:56:31 (-0700), Patrick Bartek wrote:
> On Wed, 26 Jul 2017 00:24:00 +0100 Brian  wrote:
> 
> > On Tue 25 Jul 2017 at 16:14:52 -0700, Patrick Bartek wrote:
> > 
> > > On Tue, 25 Jul 2017 20:06:01 +0100 Brian 
> > > wrote:
> > > 
> > > > On Tue 25 Jul 2017 at 07:04:29 -0700, Patrick Bartek wrote:
> > > > 
> > > > > On Tue, 25 Jul 2017 11:42:12 +0530 VigneshDhanraj G
> > > > >  wrote:
> > > > > 
> > > > > > Hi Team,
> > > > > > 
> > > > > > I am using kernel 3.2.x, i know that support from wheezy will
> > > > > > be stopped soon. can i upgrade to jessie with same kernel
> > > > > > version.
> > > > > > 
> > > > > > Is that correct way of handling?
> > > > > 
> > > > > LTS (Long Term Support) for Wheezy ends May 2018.  So, you have
> > > > > time to consider all your options.
> > > > 
> > > > I have got it into my head that LTS for wheezy focuses on security
> > > > fixes and package updates are either non-existent or few and far
> > > > between. There may be reasons for staying with that distribution
> > > > but I am very unsure what "supported" for the next year means. As
> > > > far as non-security issues are concerned it appears not to have
> > > > any great significance.
> > > 
> > > I get upgrades, both security and "other," several times a week
> > > most of the time.  I check daily.  I've never gone more than a week
> > > without something coming down the pike.  In fact, just a couple
> > > days ago, I got a fairly lengthy one for multiple apps, libraries,
> > > etc. IIRC, none were security related.  In other words, Wheezy is
> > > still alive support-wise.
> > 
> > A mention of the names of some of these apps would be helpful. A
> > record will be in your logs.
> 
> Why?

Because without evidence, it seems likely that you have confused your
wheezy server with a jessie system; there was a point release for
jessie from 8.8 to 8.9 between 23rd and 24th of this month. I've
searched in vain for an upgrade this month on wheezy which lacks a
CVE number.

> My system, a box under my desk I custom built 10.5 years ago which
> has been upgraded numerous times since, is minimal and very
> non-typical: No desktop, just a window manager and a single panel with
> menus.  Even X is minimal.  No games. No wifi. Apache isn't installed
> Neither is samba. No local DNS.  No email server.  There is no local
> network. I'm only connected to the Internet. Nothing is installed that
> isn't needed.  So, what gets upgraded on my system will have little
> bearing on yours. Just take satisfaction that Wheezy is supported and
> will continue to be until May 2018.

My wheezy server is, I would hope, a fairly typical desktop for a
person using X, fvwm, LaTeX, firefox, emacs, CUPS, libreoffice, etc.
As I process my email with mutt on it, I upgrade it at least every day
if any packages arrive (it updates and downloads every three hours).
Here's the month of July, each one annotated with the corresponding CVEs.

Start-Date: 2017-07-02  23:13:25
Commandline: apt-get upgrade
Upgrade: vorbis-tools:i386 (1.4.0-1, 1.4.0-1+deb7u1)
End-Date: 2017-07-02  23:13:40

 CVE-2015-6749 CVE-2014-9638 CVE-2014-9639 CVE-2014-9640

Start-Date: 2017-07-03  15:18:11
Commandline: apt-get upgrade
Upgrade: sudo:i386 (1.8.5p2-1+nmu3+deb7u3, 1.8.5p2-1+nmu3+deb7u4)
End-Date: 2017-07-03  15:18:25

 CVE-2017-1000368

Start-Date: 2017-07-06  07:36:43
Commandline: apt-get upgrade
Upgrade: libgcrypt11:i386 (1.5.0-5+deb7u5, 1.5.0-5+deb7u6), 
libgraphite2-2.0.0:i386 (1.3.6-1~deb7u2, 1.3.10-1~deb7u1)
End-Date: 2017-07-06  07:36:57

 CVE-2017-7771 CVE-2017-7772 CVE-2017-7773 CVE-2017-7774 CVE-2017-7775 
CVE-2017-7776 CVE-2017- CVE-2017-7778

Start-Date: 2017-07-08  08:41:41
Commandline: apt-get upgrade
Upgrade: libmpg123-0:i386 (1.14.4-1+deb7u1, 1.14.4-1+deb7u2)
End-Date: 2017-07-08  08:41:46

 CVE-2017-10683

Start-Date: 2017-07-09  08:01:44
Commandline: apt-get upgrade
Upgrade: libsqlite3-0:i386 (3.7.13-1+deb7u3, 3.7.13-1+deb7u4)
End-Date: 2017-07-09  08:01:56

 CVE-2017-10989

Start-Date: 2017-07-11  23:32:46
Commandline: apt-get upgrade
Upgrade: libtiff4:i386 (3.9.6-11+deb7u6, 3.9.6-11+deb7u7)
End-Date: 2017-07-11  23:32:58

 CVE-2017-9936

Start-Date: 2017-07-14  07:53:48
Commandline: apt-get upgrade
Upgrade: bind9-host:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 
9.8.4.dfsg.P1-6+nmu2+deb7u17), dnsutils:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 
9.8.4.dfsg.P1-6+nmu2+deb7u17), libdns88:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 
9.8.4.dfsg.P1-6+nmu2+deb7u17), libisccc80:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 
9.8.4.dfsg.P1-6+nmu2+deb7u17), liblwres80:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 
9.8.4.dfsg.P1-6+nmu2+deb7u17), libbind9-80:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 
9.8.4.dfsg.P1-6+nmu2+deb7u17), libisccfg82:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 
9.8.4.dfsg.P1-6+nmu2+deb7u17), libisc84:i386 (9.8.4.dfsg.P1-6+nmu2+deb7u16, 
9.8.4.dfsg.P1-6+nmu2+deb7u17)
End-Date: 2017-07-14  07:54:07

 CVE-2017-3142 CVE-2017-3143

Start-Date: 2017-07-14  12:58:26
Commandline: apt-

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Michael Biebl]

Am 27.07.2017 um 18:04 schrieb debian-li...@patschie.de:
> Hi Michael,
> 
> I forgot to mention that I also recreated the initramfs: 
> after several tries just to update it, I deleted the initramfs and recreated 
> it completely.
> But still the same effect.
> 
> Is there a way to manually check the contents of the initramfs, just to make 
> sure that the 70-persistent-net.rules isn’t there?


lsinitramfs /boot/initrd.img-$(uname -r) | grep  70-persistent-net.rules

This should come up empty.

The new naming is setup via /lib/udev/rules.d/80-net-setup-link.rules
and a link file called  99-default.link

lsinitramfs /boot/initrd.img-$(uname -r) | grep  80-net-setup-link.rules
lib/udev/rules.d/80-net-setup-link.rules
lsinitramfs /boot/initrd.img-$(uname -r) | grep 99-default.link
lib/systemd/network/99-default.link

Is this a bare metal or a VM?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Greg Wooledge]

On Thu, Jul 27, 2017 at 06:04:49PM +0200, debian-li...@patschie.de wrote:
> Is there a way to manually check the contents of the initramfs, just to make 
> sure that the 70-persistent-net.rules isn’t there?

mkdir /tmp/foo &&
cd /tmp/foo &&
unmkinitramfs /boot/initrd.whatever

(The old way of just running cpio won't work any more, because the new
initrd.img files are a concatenation of multiple cpio archives.)

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[debian-lists]

Hi Michael,

I forgot to mention that I also recreated the initramfs: 
after several tries just to update it, I deleted the initramfs and recreated it 
completely.
But still the same effect.

Is there a way to manually check the contents of the initramfs, just to make 
sure that the 70-persistent-net.rules isn’t there?

Patrick

> Am 27.07.2017 um 17:57 schrieb Michael Biebl :
> 
> Hi Patrick
> 
> Am 27.07.2017 um 17:15 schrieb debian-li...@patschie.de:
>> Hi,
>> 
>> I’m running into some troubles to enable the predictable network interface 
>> names for a system upgraded from Jessie.
>> 
>> What I figured out so far:
>> Setting net.ifnames=1 on the kernel command line doesn’t help and seems no 
>> longer to be supported parameter (at least "sysctl - a" doesn’t show it).
> 
> Setting that parameter should work, but it doesn't take precedence over
> an existing /etc/udev/rules.d/70-persistent-net.rules
> 
> Since net.ifnames=1 is the default since stretch, you don't need to set
> it explicitly though.
> 
>> Removing any /etc/udev/rules.d/ file handling the network interface doesn’t 
>> bring the desired effect of having predictable network interface names.
>> 
>> I started now to compare /lib/udev/rules.d from a clean stretch installation 
>> with the files on a upgraded system, the clean installation has much more 
>> files.
>> So next try reinstalling udev to get all missing/new rule files from 
>> stretch, but that didn’t work either.
>> 
>> Any ideas what I could try next or missed to check?
>> 
> 
> Most likely the file /etc/udev/rules.d/70-persistent-net.rules got
> embedded in the initramfs. So once you removed that file, you also need
> to rebuild the initramfs via update-initramfs -u
> 
> Michael
> 

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[Michael Biebl]

Hi Patrick

Am 27.07.2017 um 17:15 schrieb debian-li...@patschie.de:
> Hi,
> 
> I’m running into some troubles to enable the predictable network interface 
> names for a system upgraded from Jessie.
> 
> What I figured out so far:
> Setting net.ifnames=1 on the kernel command line doesn’t help and seems no 
> longer to be supported parameter (at least "sysctl - a" doesn’t show it).

Setting that parameter should work, but it doesn't take precedence over
an existing /etc/udev/rules.d/70-persistent-net.rules

Since net.ifnames=1 is the default since stretch, you don't need to set
it explicitly though.

> Removing any /etc/udev/rules.d/ file handling the network interface doesn’t 
> bring the desired effect of having predictable network interface names.
> 
> I started now to compare /lib/udev/rules.d from a clean stretch installation 
> with the files on a upgraded system, the clean installation has much more 
> files.
> So next try reinstalling udev to get all missing/new rule files from stretch, 
> but that didn’t work either.
> 
> Any ideas what I could try next or missed to check?
> 

Most likely the file /etc/udev/rules.d/70-persistent-net.rules got
embedded in the initramfs. So once you removed that file, you also need
to rebuild the initramfs via update-initramfs -u

Michael



signature.asc
Description: OpenPGP digital signature

Re: DHCP isn't updating DNS

[Joshua Schaeffer]

> You should consider moving towards "standard", but "interim"'s not a
> problem for now.
> https://deepthought.isc.org/article/AA-01091/0/ISC-DHCP-support-for-Standard-DDNS.html

I've actually made a few changes since I've posted this in trying to figure 
this out and I did change to standard. This appears to have not made any 
difference. DNS is still not getting updated, but I will definitely keep the 
setting at standard.
>
>>   allowclient-updates;
>
> I would recommend denying client-updates. This tells clients that they
> can do the DNS update themselves. Given that you're trying TSIGs below,
> that would mean deploying keys to all the clients etc etc. Better to
> "deny client-updates" and centralise the work through the DHCP server.

This was also a change I made. I definitely do not want (and do not allow) 
clients to update DNS, so I changed this to deny.
>
>
> Some other options I have are "update-static-leases on" (Make sure DNS
> is updated even for hosts with a static address) "update-optimization
> on" (Actually, for debugging purposes, I had that off for a while. If
> it's off the DNS will be updated every time. If it's on, then the DNS
> won't be updated if the lease hasn't changed. If you're changing from
> 'interim' to 'standard' you definitely want this off to ensure the
> records get changed).
I saw these as well when I reread through the dhcpd.conf man page, but haven't 
tried them yet. I'll give that a go.

>
> I'm assuming you've cut something out of your config here, but given the
> config above, there's nothing that applies the DDNS settings to hosts.
> The ddns-* settings should apply to everything in their current scope
> and below (so, if you've put them in your subnet6 block, for example,
> that should be fine).

Yes I didn't include my entire conf file as it is a little long. Here is my 
subnet6 declaration that I've been focusing on:

subnet6 2620:5:e000:201e::/64 {
default-lease-time2419200;
max-lease-time2419200;

# LDAP Servers.
pool6 {
allow members of "ldap_servers";
range6 2620:5:e000:201e:0:1::/96;
}
# Kerberos Servers.
pool6 {
allow members of "krb5_servers";
range6 2620:5:e000:201e:0:2::/96;
}
# DHCP Servers.
pool6 {
allow members of "dhcp_servers";
range6 2620:5:e000:201e:0:3::/96;
}
# Puppet Servers.
pool6 {
allow members of "puppet_servers";
range6 2620:5:e000:201e:0:4::/96;
}
# DNS Servers.
pool6 {
allow members of "dns_servers";
range6 2620:5:e000:201e:0:5::/96;
}
# Catch-all DHCP group.
pool6 {
range6 2620:5:e000:201e:0:d::/96;
}
}

In particular I've been testing with a client that gets added to the 
"dhcp_servers" class. I know the classification works as the client actually 
gets an IP address in the the range specified, I just can't get DHCP to update 
the DNS servers with the  and PTR records. Since all my subnet's use the 
same ddns-* settings I don't specify this at the subnet or pool level, I just 
leave it in the top scope.

Thanks for your response,
Joshua Schaeffer

Re: Need to upgrade to jessie need help

[David Wright]

On Tue 25 Jul 2017 at 16:16:44 (+0200), Dejan Jocic wrote:
> On 25-07-17, Greg Wooledge wrote:
> > Is there any way to permanently neuter apt-get autoremove, so that even
> > if something invokes it against my will, it will *never* remove anything?
> > 
> > And more, is there a way to get apt and apt-get to *stop* prompting me
> > to run it, and *stop* spamming me with a list of packages that it would
> > like me to remove?  (Maybe that's the same as the first question, maybe
> > not.)
> > 
> > My strategy so far has been "ignore the spam, and never willingly run
> > autoremove".  This mostly works, but I recently learned that tasksel
> > will apparently run an autoremove, without warning, whether I want it
> > to or not ().
> > 
> > If autoremove will also remove *kernels*, which this thread seems to
> > indicate is the case, then my concerns just went up another notch.
> > 
> > I suppose one could manually mark each and every single installed
> > package as "manually installed", but you'd have to remember to repeat
> > this periodically, and it seems clumsy and inelegant compared to some
> > sort of master switch that can just tell autoremove to go die in a fire.
> > 
> 
> Your fear from autoremove is silly. It

Please note that "it" is "they", viz: apt and apt-get, …

> will not remove anything you
> really need and, if you stick to default settings, 

… and that they have different defaults. What's more, apt's behaviour
may change between versions, so unqualified statements like this
should really be confirmed before being relied on.

> will keep all
> packages it replaced in /var/cache/apt/archives, as far as I know. And
> if you have some package that you really, really want to keep, you can
> always pin it, or put it on hold with apt-mark. It is not spam, it is
> keeping your system clean.

Cheers,
David.

Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

[debian-lists]

Hi,

I’m running into some troubles to enable the predictable network interface 
names for a system upgraded from Jessie.

What I figured out so far:
Setting net.ifnames=1 on the kernel command line doesn’t help and seems no 
longer to be supported parameter (at least "sysctl - a" doesn’t show it).
Removing any /etc/udev/rules.d/ file handling the network interface doesn’t 
bring the desired effect of having predictable network interface names.

I started now to compare /lib/udev/rules.d from a clean stretch installation 
with the files on a upgraded system, the clean installation has much more files.
So next try reinstalling udev to get all missing/new rule files from stretch, 
but that didn’t work either.

Any ideas what I could try next or missed to check?

Thanks a lot.

Patrick

Re: Stretch: xfce and xscreensaver

[Greg Wooledge]

On Thu, Jul 27, 2017 at 07:35:24AM -0700, Patrick Bartek wrote:
> Or do what I did: dispense with a screensaver entirely.  Haven't used
> one in years.  Waste of CPU cycles.  Besides modern computer screens
> don't even need them anymore.  They aren't prone to image burning
> like tube-type monitors were.  I just use xset or a power management
> utility, if installed, to "sleep" the monitor display after a set time
> of system idleness. Works great.

For many of us, the primary function of the screen saver isn't the
prevention of image burn-in, but rather the locking of the session to
prevent other people from taking control when we step away.

Personally I use i3lock for this.  Nice and simple.  I don't use any
kind of automatic invocation or idle checking.  I just manually run it
when I'm about to step away.  (Used to use xlock, from xlockmore, but
that was removed from Debian several releases ago.)

Re: Stretch: xfce and xscreensaver

[Patrick Bartek]

On Thu, 27 Jul 2017 09:52:42 +0400 Jerome BENOIT
 wrote:

> Hello Debian Users,
> 
> I have recently upgraded my box from Jessie to Stretch.
> I encountered a few little issues that I could fixed easily.
> Nevertheless, so far, I failed to fixed one of them, and a very
> annoying one.
> 
> During Xfce sessions, at random time my screen is filled with piece
> of outdated images that were created by xscreensaver.
> Most of the time, these images comes with an outdated error message
> from xscreensaver.
> 
> Any hint to fix is is welcome.

Instead of wasting time looking for the problem, I would first just
'apt-get purge xscreensaver' making sure all configure files are gone,
then reinstall, reconfigure.

Or do what I did: dispense with a screensaver entirely.  Haven't used
one in years.  Waste of CPU cycles.  Besides modern computer screens
don't even need them anymore.  They aren't prone to image burning
like tube-type monitors were.  I just use xset or a power management
utility, if installed, to "sleep" the monitor display after a set time
of system idleness. Works great.

B

Re: Stretch: xfce and xscreensaver

[Cindy-Sue Causey]

On 7/27/17, Johann Spies  wrote:
> On 27 July 2017 at 09:27, Jerome BENOIT 
> wrote:
>> It is configured to display the `deco' saver.
>
> I would try and move ~/.xscreensaver away (something like
> ~/.xscreensaver.bak) and then restart and reconfigure xscreensaver if
> I were in you position.


I like that idea. It's one I've not had to use much over the years,
but it's always high on my debug checklist. :)

Writing now because I tried lurking along behind the scenes. My setup
is a couple week old debootstrap'ed copy of Buster with Xfce4. I had
accidentally forgotten to install my xscreensaver which worked perfect
for this.

So I installed it and attempted to try your Deco theme. I don't
know when this warning popped up (in its own window), but suddenly
there it was sometime just after I clicked Applications > Settings >
Screensaver and then the Deco theme:

"The XScreenSaver daemon doesn't seem to be running on display ":0.0".
Launch it now?"

I have not one clue on that one. Have never seen it, never heard of it before.

A quick glance through search returns without visiting any webpages
shows words like "doesn't start automatically". Those inquiries appear
dated 3 or 4 years ago. That reminded me that I'd noticed my
screensaver had not been behaving perfectly in the last year or so,
but Life outside the computer has had precedence so I never
debugged.

I use the Fiberlamp option. I tried switching back to it, and that
message was still sitting there as though it might pertain to the
screensaver as a whole. Yes, you're right that no, not necessarily,
because once something like that pops up, it usually takes answering
it for it to go away. I clicked "ok", and so far (3 minutes and
counting) no smoke or flames... :)

A parting afterthought: This is occurring on a PC setup where I'd
previously been using a netbook'y laptop until a few weeks ago. That
may or may not be a factor in why I'm suddenly seeing this warning for
the first time ever

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Power draw from UPS

[Felix Miata]

g composed on 2017-07-27 12:27 (UTC+0200):

> Hi all, I want to get the power draw from a APC USB UPS. I have managed
> to run apcusbd and apctest. But how to invoke these tools to get the
> actual power draw in Watt x Ampere?

> I've found this page which describes how to read it via RS232 serial
> port.

> https://forums.anandtech.com/threads/got-an-apc-smart-ups-measure-real-
> power-with-it.55847/

> But I dont't have such a port neither a cable.

Sounds like you may be candidate for one of these:
http://www.ebay.ca/itm/152386308824
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

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

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

Re: Stretch: xfce and xscreensaver

[Johann Spies]

On 27 July 2017 at 09:27, Jerome BENOIT  wrote:
> It is configured to display the `deco' saver.

I would try and move ~/.xscreensaver away (something like
~/.xscreensaver.bak) and then restart and reconfigure xscreensaver if
I were in you position.

Regards.
Johann

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

Re: Thunderbird 52.2.1 and Enigmail

[Paul van der Vlis]

Op 25-07-17 om 23:18 schreef Daniel Bareiro:
> Hi all!
> 
> I just updated Thunderbird on Jessie. Support for the 45.x series has
> ended, so starting with this update Debian is now following the 52.x
> releases.

I've tried much, but it did not work. So I downgraded, this worked for me:

apt remove thunderbird icedove
apt install thunderbird=1:45.8.0-3~deb8u1
apt install thunderbird-l10n-nl=1:45.8.0-3~deb8u1
apt install lightning=1:45.8.0-3~deb8u1
apt install lightning-l10n-nl=1:45.8.0-3~deb8u1
apt install icedove=1:45.8.0-3~deb8u1
apt install enigmail=2:1.8.2-4~deb8u1
apt -t jessie-backports install xul-ext-sogo-connector

And you need some kind of pinning...

With regards,
Paul van der Vlis



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

Re: Power draw from UPS

[Darac Marjal]

On Thu, Jul 27, 2017 at 12:27:14PM +0200, g wrote:

Hi all, I want to get the power draw from a APC USB UPS. I have managed
to run apcusbd and apctest. But how to invoke these tools to get the
actual power draw in Watt x Ampere?


What model of UPS is it? Many of the newer models use a protocol called
"Microlink" (aka MODBUS over USB) . APC (and their parent Schneider
Electric) have been quite secretive about this protocol, unlike the
older protocol where they provided nice interface specifications.

So, firstly, make sure you're using a sufficently new version of APCUPSd
(3.14.13 or newer). Secondly, check that you're using the modbus
protocol: http://www.apcupsd.org/manual/manual.html#modbus-driver
Finally, if that doesn't help, then it may simply be that the UPS isn't
reporting the required information.



I've found this page which describes how to read it via RS232 serial
port.

https://forums.anandtech.com/threads/got-an-apc-smart-ups-measure-real-
power-with-it.55847/

But I dont't have such a port neither a cable.

Regards
Goran



--
For more information, please reread.


signature.asc
Description: PGP signature

Re: cups jobs queue

[Pol Hallen]

?waitjob=false

thanks :)
--
Pol

Re: Power draw from UPS

[Ron Leach]

On 27/07/2017 11:27, g wrote:

Hi all, I want to get the power draw from a APC USB UPS. I have managed


[...]

But I dont't have such a port neither a cable.



Our APC UPSs included a USB cable in the box.  The cable uses a USB 
plug at one end (into the linux machine) and a different plug at the 
other end, looking something similar to RJ11 or RJ45 sort of 
appearance, to plug into the APC UPS.


regards, Ron

Re: Power draw from UPS

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jul 27, 2017 at 12:27:14PM +0200, g wrote:
> Hi all, I want to get the power draw from a APC USB UPS. I have managed
> to run apcusbd and apctest. But how to invoke these tools to get the
> actual power draw in Watt x Ampere?
> 
> I've found this page which describes how to read it via RS232 serial
> port.
> 
> https://forums.anandtech.com/threads/got-an-apc-smart-ups-measure-real-
> power-with-it.55847/
> 
> But I dont't have such a port neither a cable.

It's most likely that the USB "appears" as a virtual serial
port. Try the command "lsusb" on a console. The option "-v"
makes it more verbose.

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

iEYEARECAAYFAll5wqkACgkQBcgs9XrR2kaYvACePSp8iQ14cVcu/PqHNt9vV5g6
uIEAnjGSsqlcE+hHWtn9HV7SsldLiqUw
=H773
-END PGP SIGNATURE-

Power draw from UPS

[g]

Hi all, I want to get the power draw from a APC USB UPS. I have managed
to run apcusbd and apctest. But how to invoke these tools to get the
actual power draw in Watt x Ampere?

I've found this page which describes how to read it via RS232 serial
port.

https://forums.anandtech.com/threads/got-an-apc-smart-ups-measure-real-
power-with-it.55847/

But I dont't have such a port neither a cable.

Regards
Goran

Re: funding & viability questions of GPL enforcement.

[Fungi4All]

> From: joel.r...@gmail.com
> To: debian-user 
> On Sat, Jul 22, 2017 at 3:29 AM, Alessandro Vesely  wrote:
>> On Thu 20/Jul/2017 22:18:25 +0200 Fungi4All wrote:
>>>[...]
>>
>>> For linux we all need to agree before we decide.
>>
>> Yeah, that"s a pita. It"s hard to change anything if everyone can veto.
> That"s sure indication that everything is getting too big -- the companies,
> of course, but also the projects, the software, ...
> ... and the egos.

Under the same logic how can it all be considered one "big" thing with so
many different participants? Are companies, projects, developers, sysadmins,
and users all equal parties? Do companies have egos? No, they have one
motive to make money and become the only player and decision maker.
What all these different entities need is organization, each with distinct goals
and principles of organization. Then each community will have its own
voice, cooperate with others, and form a direction, if that is possible.
In every industry there ever was when standards (of cooperation) were
developed there was development in the direction the industry had set.
This chaotic system of each one doing their own thing and see where it
gets everyone seems to be coming to an end. And at this end some are
more organized to benefit from the whole than others.
In terms of debian, it is an utopian proposition to expect it to compete as
a semi-democratic institution among the dictatorships. It also unthinkable
that individuals can have an influence among organizations. The
binding licensing agreements will in the future be either abolished or
will not be enforced as much as to matter, as far as being obstacles
to corporations making money.

Re: Stretch: xfce and xscreensaver

[Jerome BENOIT]

Hi Johann, thanks for your reply.

On 27/07/17 10:14, Johann Spies wrote:
> On 27 July 2017 at 07:52, Jerome BENOIT  wrote:
>> Hello Debian Users,
>>
>> I have recently upgraded my box from Jessie to Stretch.
>> I encountered a few little issues that I could fixed easily.
>> Nevertheless, so far, I failed to fixed one of them, and a very annoying one.
>>
>> During Xfce sessions, at random time my screen is filled with piece
>> of outdated images that were created by xscreensaver.
>> Most of the time, these images comes with an outdated error message from 
>> xscreensaver.
> 
> How did you configure xscreensaver?  I use XFCE and have no problems.
Good to know.

> My screensaver is configured to display images from a certain
> directory randomly.

It is configured to display the `deco' saver.

Cheers, Jerome

> 
> Regards
> Johann
> 

cups jobs queue

[Pol Hallen]

Hi folks :)

It happens that if the printer is off and from client (the printer is 
physically connect to cups server) I send some jobs, only first jobs 
sent to cups server, from second job all remains in the client.


I'd like send all job to cups server, next when I can power-on the 
printer I've all jobs to printing


It happens only with linux client, with windows no problem

any idea?

thanks :)

Pol