Re: Debian 9.1 amd64 Xfce panel clock broken

[David Christensen]

On 08/11/17 04:57, John Ratliff wrote:



On Wed, Aug 09, 2017 at 05:13:55PM -0700, David Christensen wrote:

 Time Settings
   Timezone PST8PDT
 Appearance
   Layout   Digital
   Tooltip format   Wednesday 09 August 2017
 Clock Options
   Format   05:04:55 PM

Once I have made the above settings, but before choosing "Close", the
current time is displayed at the proper location in the Xfce panel. This
is
what I want.

- But when I click "Close", the current time disappears from the panel
--
e.g. Clock breaks.


Does the space for the clock disappear, or go blank?

If it's going blank, I suggest you look at color settings for
the clock -- you may have accidentally selected 100% transparent
text, or the same color as the background.

-dsr-




This is a known bug in the clock applet for Xfce. Last I checked the bug
tracker upstream, it hadn't been fixed. I have the same issue. You can't
adjust the clock settings without it erasing your format string and making
the clock blank. 


https://bugzilla.xfce.org/show_bug.cgi?id=11527



My workaround is to use the orange date/time panel item
instead.


I thought about that -- might as well until the Xfce clock gets fixed.


David

Re: Debian 9.1 amd64 Xfce panel clock broken

[David Christensen]

On 08/10/17 06:52, Charlie Kravetz wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 9 Aug 2017 22:48:37 -0700
David Christensen  wrote:


On 08/09/17 21:47, Charlie Kravetz wrote:


It almost sounds like the panel is too long for the monitor. The clock
is disappearing off the end of the panel. Is the clock the last thing
in panel? Try moving it to the other of the panel, and see if it still
disappears.


Clock is neither the first nor last item in the panel.


Clock works fine on Xfce on Debian Wheezy, Debian Jesse, FreeBSD 11.0,
and possibly others.


I'm looking for an error message from Xfce panel, or a way to obtain
error/ debug messages.


David



The only way I know to do that, if nothing shows up in
~/.xsession-errors, 



2017-08-11 21:46:11 dpchrist@tinkywinky ~
$ grep -i clock .xsession-errors

2017-08-11 21:46:15 dpchrist@tinkywinky ~
$ grep -i panel .xsession-errors

2017-08-11 21:46:23 dpchrist@tinkywinky ~
$ grep -i xfce .xsession-errors
dbus-update-activation-environment: setting 
XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/

xfce4-session-Message: SSH authentication agent is already running
(xfce4-session:5464): xfce4-session-WARNING **: gpg-agent returned no 
PID in the variables
(xfce4-terminal:5560): Gtk-WARNING **: Allocating size to GtkScrollbar 
0x55b9781683d0 without calling gtk_widget_get_preferred_width/height(). 
How does the code know the size to allocate?
(xfce4-terminal:5560): Gtk-WARNING **: Allocating size to GtkScrollbar 
0x55b9781687d0 without calling gtk_widget_get_preferred_width/height(). 
How does the code know the size to allocate?




is to run debug.

https://docs.xfce.org/xfce/xfce4-panel/debugging



Maybe later.


David

Re: Debian 9.1 amd64 Xfce panel clock broken

[David Christensen]

On 08/10/17 11:51, Ralph Katz wrote:


On 08/09/2017 06:13 PM, David Christensen wrote:

debian-user:

I have a Dell Inspiron E1505 laptop with an Intel Core Duo T7400
CPU, 2 GB RAM, 16 GB SSD, and a fresh install of
debian-9.1.0-amd64-xfce-CD-1.iso, with all updates and upgrades as
of now:

2017-08-09 16:59:07 root@tinkywinky ~ # cat /etc/debian_version
9.1

2017-08-09 16:59:18 root@tinkywinky ~ # uname -a Linux tinkywinky
4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) x86_64
GNU/Linux

2017-08-09 16:59:22 root@tinkywinky ~ # dpkg-query --show xfce4
xfce44.12.3


I would like to use the Xfce panel "clock" item.  Unfortunately, it
is broken:

- If I right-click on the Xfce panel and choose "Panel
Preferences...", the "Panel" dialog appears.

- Selecting Panel -> Items tab, "Clock" appears in the list of
panel items.

- If I select Panel -> Items -> Clock and click the "Edit the
currently selected item" button, the "Clock" dialog appears.

- I then configure Clock as follows:

Time Settings TimezonePST8PDT Appearance Layout
Digital Tooltip formatWednesday 09 August 2017 Clock Options
Format05:04:55 PM

Once I have made the above settings, but before choosing "Close",
the current time is displayed at the proper location in the Xfce
panel. This is what I want.

- But when I click "Close", the current time disappears from the
panel -- e.g. Clock breaks.


Mine works, but settings look different.  I made no changes to clock
properties, 


When I open Panel Preferences -> Items -> Clock -> Edit the currently 
selected item, the defaults are:


  Time Settings
Timezone
  Appearance
Layout  Digital
Tooltip format  Custom Format
  Clock Options
Format  Custom Format



yet my field Timezone is blank.  Maybe try that?


Failure is the same.



There is an .xfce4-session.verbose-log , though I don't know what
you'll find.


Nothing:

2017-08-11 21:43:27 dpchrist@tinkywinky ~
$ find . -name .xfce4-session.verbose-log
./.xfce4-session.verbose-log

2017-08-11 21:43:34 dpchrist@tinkywinky ~
$ grep -i clock .xfce4-session.verbose-log



David

Re: Debian 9.1 amd64 Xfce panel clock broken

[David Christensen]

On 08/11/17 03:39, Dan Ritter wrote:

On Wed, Aug 09, 2017 at 05:13:55PM -0700, David Christensen wrote:

 Time Settings
   Timezone PST8PDT
 Appearance
   Layout   Digital
   Tooltip format   Wednesday 09 August 2017
 Clock Options
   Format   05:04:55 PM

Once I have made the above settings, but before choosing "Close", the
current time is displayed at the proper location in the Xfce panel. This is
what I want.

- But when I click "Close", the current time disappears from the panel --
e.g. Clock breaks.


Does the space for the clock disappear, or go blank?


The clock disappears (all the other items on the panel rearrange to fill 
the void).



David

Re: Thunderbird almost unusable after upgrade

[Jape Person]

On 08/11/2017 06:27 PM, Javier Barroso wrote:

Hello,

On Fri, Aug 11, 2017 at 9:43 PM, Sven Hartge  wrote:

Sven Joachim  wrote:

On 2017-08-10 10:24 -0400, Jape Person wrote:



After this upgrade

thunderbird:amd64 (1:52.2.1-4, 1:52.2.1-4+b1)

Thunderbird in Cinnamon DE is almost completely useless because
portions of its windows / text / toolbars don't repaint until the
window is resized. Is anyone else seeing this?



Yes, see https://bugs.debian.org/871629.


Confirmation: Rebuilding 1:52.2.1-4 with gcc-6/g++-6 as the compiler
fixes the problem.


You can also download thunderbird and its addons from
http://snapshot.debian.org/package/icedove/1%3A52.2.1-4/, selecting
your architecture

See what packages have you installed from icedove them:

  aptitude search '?and(?source-package(icedove),?installed)'

Download to Download/icedove and install with apt install
./Download/icedove/*.deb

Regards




I was just getting frustrated enough to do the recompile. Ugh. I'm old, 
have poor eyesight, and was not anxious to do that while recovering from 
pneumonia.


I'll give it a shot.

Thank you much for the reminder. I used to love to do things the hard 
way, but that's not my thing any more. Just spent today doing a system 
installation and configuration for a system that lost a solid state drive.


JP

Re: How to Troubleshoot Xen VM Failure 1stpvguest

[Andy Smith]

Hi Ray,

On Fri, Aug 11, 2017 at 06:52:21PM -0700, ray wrote:
> on Debian 9 with latest Xen on a laptop, I tried to build a pv guest.  I 
> would like to understand how to determine what the failure was.
> 
> *** This is how the image was created:
> # xen-create-image --hostname=1stpvguest  --vcpus=2 --dhcp --pygrub --dist 
> stretch
> # xl create /etc/xen/1stpvguest.cfg

Use "xl create -c /etc/xen/1stpvguest.cfg" to immediately open the
console and watch it boot.

> Parsing config from /etc/xen/1stpvguest.cfg
> libxl: error: libxl_bootloader.c:635:bootloader_finished: bootloader failed - 
> consult logfile /var/log/xen/bootloader.1.log

Bootloader (pygrub) failed to provide you with a kernel/initramfs
that was bootable by Xen.

> # cat bootloader.1.log

[…]

> [Errno 2] No such file or directory
> Error opening /boot/initrd.img- in guest

Seems like pygrub decided that the selected (by default timeout)
entry's initramfs was "/boot/initrd.img-" and then it couldn't open
that file from inside the guest's filesystem.

It would be worth examining your /boot/grub/grub.cfg file to see if
the initramfs is really listed as "/boot/initrd.img-". If it isn't
then pygrub is confused by your grub config. If it is then your grub
config looks broken.

You can also run pygrub standalone to see what it makes of your guest's
filesystem. Example:

$ sudo /usr/lib/xen-4.8/bin/pygrub -l /dev/vg/debtest1_xvda
Using  to parse /boot/grub/grub.cfg
WARNING:root:grub2's saved_entry/next_entry not supported
WARNING:root:Unknown directive else
WARNING:root:Unknown directive menuentry_id_option
WARNING:root:Unknown directive else
WARNING:root:Unknown directive menuentry_id_option
WARNING:root:Unknown directive export
WARNING:root:Unknown directive font
WARNING:root:Unknown directive else
WARNING:root:Unknown directive else
WARNING:root:Unknown directive font
WARNING:root:Unknown directive load_video
WARNING:root:Unknown directive terminal_output
WARNING:root:Unknown directive else
WARNING:root:Unknown directive else
WARNING:root:Unknown directive export
WARNING:root:Unknown image directive load_video
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive load_video
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown image directive load_video
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive if
WARNING:root:Unknown image directive else
WARNING:root:Unknown image directive fi
WARNING:root:Unknown directive source
WARNING:root:Unknown directive elif
WARNING:root:Unknown directive source
title: Debian GNU/Linux
  root: None
  kernel: /boot/vmlinuz-4.12.0-trunk-amd64
  args: root=UUID=d924a9db-5223-4e42-8e79-7006daf90eda ro console=hvc0
  initrd: /boot/initrd.img-4.12.0-trunk-amd64
title: Debian GNU/Linux, with Linux 4.12.0-trunk-amd64
  root: None
  kernel: /boot/vmlinuz-4.12.0-trunk-amd64
  args: root=UUID=d924a9db-5223-4e42-8e79-7006daf90eda ro console=hvc0
  initrd: /boot/initrd.img-4.12.0-trunk-amd64
title: Debian GNU/Linux, with Linux 4.12.0-trunk-amd64 (recovery mode)
  root: None
  kernel: /boot/vmlinuz-4.12.0-trunk-amd64
  args: root=UUID=d924a9db-5223-4e42-8e79-7006daf90eda ro single console=hvc0
  initrd: /boot/initrd.img-4.12.0-trunk-amd64

> *** The above did not display on the desktop.  So here is the grub file 
> extract:
> GRUB_DEFAULT=0

[…]

This isn't a grub config, it's an /etc/default/grub file that is
used to generate a grub config, e.g. when you type "update-grub".
Assuming grub-pc package, the generated grub config will be at
/boot/grub/grub.cfg inside the guest's filesystem. Have a look at
that one.

> GRUB_TIMEOUT=3
> GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
> GRUB_CMDLINE_LINUX_DEFAULT="quiet"
> GRUB_CMDLINE_LINUX=""
> GRUB_CMDLINE_XEN="dom0_mem=1024M,max:1024M"

This looks like it might be the /etc/default/grub file from your
dom0, so doubly irrelevant when debugging guest booting issues.

> Should a console have come up?

You will only be attached to the console of a Xen guest that you
just created, if you use "-c".

> How to I determine what the problem was?

The error message came from pygrub, so the problem is either with
pygrub or with the configuration pygrub is working with.

As an aside, pygrub is not a great way to boot Xen guests. I would
recommend looking into pvgrub2:

https://wiki.xenproject.org/wiki/PvGrub2#Debian

Also the xen-user mailing list is a good place to ask support
questions, as there are probably more admins who use Xen there.

https://lists.xenproject.org/mailman/listinfo/xen-users

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Btrs vs ext4. Which one is more reliable?

[Andy Smith]

Hello,

On Thu, Aug 10, 2017 at 07:04:09AM -0400, Dan Ritter wrote:
> On Wed, Aug 09, 2017 at 09:46:09PM -0400, David Niklas wrote:
> > On Sat, 29 Jul 2017 04:59:40 +
> > Andy Smith  wrote:
> > 
> > Also, my use case is at home where the power can and *does* fail. I also
> > find myself using the latest kernel and oftentimes an experimental driver
> > for my AMD graphics card, hence my need for a *very* stable fs over
> > sudden unmount.

Dan's broken quoting implies that I wrote the above, but I didn't.

Cheers,
Andy

How to Troubleshoot Xen VM Failure 1stpvguest

[ray]

on Debian 9 with latest Xen on a laptop, I tried to build a pv guest.  I would 
like to understand how to determine what the failure was.

*** This is how the image was created:
# xen-create-image --hostname=1stpvguest  --vcpus=2 --dhcp --pygrub --dist 
stretch
# xl create /etc/xen/1stpvguest.cfg
Parsing config from /etc/xen/1stpvguest.cfg
libxl: error: libxl_bootloader.c:635:bootloader_finished: bootloader failed - 
consult logfile /var/log/xen/bootloader.1.log
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [3802] 
exited with error status 1
libxl: error: libxl_create.c:1223:domcreate_rebuild_done: cannot (re-)build 
domain: -3
libxl: error: libxl.c:1575:libxl__destroy_domid: non-existant domain 1
libxl: error: libxl.c:1534:domain_destroy_callback: unable to destroy guest 
with domid 1
libxl: error: libxl.c:1463:domain_destroy_cb: destruction of domain 1 failed

*** The above referenced the log file.  Here it is:

# cat bootloader.1.log
Using  to parse /boot/grub/menu.lst
ESC(BESC)0ESC[1;24rESC[m^OESC[?7hESC[?1hESC=ESC[HESC[JESC[?1hESC=
pyGRUB  version 0.6
  pyGRUB  version 0.6
 ┌┐
 │ Debian GNU/Linux 9 │
 │ Debian GNU/Linux 9 (Single-User)   │
 │ Debian GNU/Linux 9 (Default Kernel)│
 │ Debian GNU/Linux 9 (Default Kernel, Single-User)   │
 └┘
Use the ^ and ┴ keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, 'a' to modify the kernel arguments
before booting, or 'c' for a command line.

 Will boot selected entry in  1 seconds


[Errno 2] No such file or directory
Error opening /boot/initrd.img- in guest
root@MC:/var/log/xen# 

*** The above did not display on the desktop.  So here is the grub file extract:
GRUB_DEFAULT=0
GRUB_TIMEOUT=3
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
GRUB_CMDLINE_XEN="dom0_mem=1024M,max:1024M"
dom0_max_vcpus=1 dom0_vcpus_pin=1
GRUB_SERIAL_COMMAND="serial --unit=0 --speed=19200 --word=8 --parity=no 
--stop=1"
GRUB_TERMINAL="console serial"
GRUB_TIMEOUT=5
GRUB_CMDLINE_XEN="com1=19200,8n1 console=com1,vga"
GRUB_CMDLINE_LINUX="console=tty0 console=hvc0"


***  From the above, I expected to see a console with progress.  A console did 
not come up.  

Should a console have come up?

How to I determine what the problem was?

Thanks,
Ray

Re: erro krb5

[Gonzalo Rivero]

El vie, 11-08-2017 a las 16:48 -0400, Luis Ernesto Garcia Reyes
escribió:
> Saludos instale un AD+ Samba 4 y todo perfecto:
>  
> #klist 
>  
> Ticket cache: FILE:/tmp/krb5cc_0 Default principal: administrator@CAS
> A.CU Valid starting Expires Service principal 26/02/17 17:46:10
> 27/02/17 03:46:10 krbtgt/casa...@casa.cu renew until 27/02/17
> 17:46:07
>  
> Pero cuando reinicio el servidor y ejecuto klist de nuevo
> root@dc1:~# klist
> klist: Credentials cache file '/tmp/krb5cc_0' not found
>  
> No tengo idea porque ocurre esto. Saludos

yo me quedé en grupos de trabajo, ¿pero, tenés algo que limpie tmp en
cada apagado o inicio?, por eso no está el krb5cc_0. 

Tal vez efectivamente sea un archivo temporal que crea el samba
mientras está funcionando, ¿está levantado el servicio?, service samba
status (o algo así, también me quedé en el mundo pre-systemd antes de
pasarme a freebsd, /etc/init.d/samba status debería funcionar todavía)

How to keep Debian Linux patched with latest security updates automatically

[Herb Garcia]

I found this article on Linux Today. I know a few of us have asked
questions about this maybe this might clear up a few of them.

http://www.linuxtoday.com/security/how-to-keep-debian-linux-patched-with-latest-security-updates-automatically-170808131008.html

I hope this helps

-HP Garcia

Re: Big problem computer not booting

[Jimmy Johnson]

On 08/11/2017 01:45 AM, Fungi4All wrote:

From: field.engin...@gmail.com


To: debian-user@lists.debian.org

On 08/10/2017 12:00 PM, kelsang sherab wrote:

I run Debian stretch on MacBook Air

I did a restore backup from previous system[debian Jessie ]





I don"t know, but maybe I can help with the network, do an "#ifconfig
-a" to get the name of your interface and then "#ifconfig
(name-of-interface) up" and see if that helps get things going.


I suspect this has to do with the settings of systemd trying to bring a
functional network up before it completes the sequence, but as it is
set to give up at a point it finds yet a different place to get stuck.
I remember a while I had found where to set the time limit but didn't
record the find and while on wifi I have to deal with this delayed booting
myself.
But, on the above problem out of curiosity I found this piece that may
be helpful.  https://ubuntuforums.org/showthread.php?t=2254677
It seems on such machines the interrupts get all twisted and tangled
up.  Quote from the link:
"The ivrs table is wrong, it points to non existant IOAPIC[0] and IOAPIC[255], 
so to override this i use this commandline in grub:
ivrs_ioapic[7]=00:14.0 ivrs_ioapic[8]=00:00.1."


The tip is he restored from a previous system, so his network interface 
probable got a new name, it should be simple to fix if net-tools is 
installed. It's 2x60 seconds before the connection will timeout and 
continue to boot.


Cheers,
--
Jimmy Johnson

Debian Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda6
Registered Linux User #380263

Re: usb flash drives / sd

[Doug]

On 08/11/2017 05:11 PM, Dan Ritter wrote:

On Fri, Aug 11, 2017 at 02:25:01PM -0500, Doug wrote:

On 08/11/2017 01:46 PM, ju...@tutanota.com wrote:

There are three major types of flash chip types : SLC - MLC - TLC

how-to check my usbkey/sd/memory card ?

--
Securely sent with Tutanota.

I am not being a wiseguy.
What is the difference, and why does it matter?

The basic difference is the number of bits recorded in a single
cell, and that affects both the storage density and its
long term reliability.

More bits == more dense but less reliable.

To compensate for long term reliability, SSD manufacturers use
a variety of strategies involving staging data in RAM,
compressing it, and implementing other special storage
structures.

On a removable-media flash device, none of those strategies
are used.

-dsr-


Perhaps I misunderstood. I thought you were referring to usb flash drives.
Do you mean these little chip gizmos that go into digital cameras?

(Hope I am not being a nuisance.)

--doug

Re: Thunderbird almost unusable after upgrade

[Gene Heskett]

On Friday 11 August 2017 14:53:01 Doug wrote:

> On 08/11/2017 10:12 AM, Gene Heskett wrote:
> > On Friday 11 August 2017 10:54:22 Greg Wooledge wrote:
> >> On Fri, Aug 11, 2017 at 10:48:59AM -0400, Gene Heskett wrote:
> >>> I have a 5 or 6 machine home network, most of which are running
> >>> linuxcnc to carve wood or metal. Linuxcnc, generally needs
> >>> realtime support so that when a machine needs direction as to what
> >>> to do next, linuxcnc has at the most 10 microseconds to respond.
> >>
> >> So why do you run a *web browser* on this machine?  Put it in the
> >> work shed or wherever, and control it like a server or an
> >> appliance.
> >
> > Chuckle.  2 of them are in fact in a 12x16 shed in the back yard,
> > and occasionally I might need to step over to the other idle machine
> > and look something up, so both have FF installed, but with the dram
> > shortage FF causes, I don't run LCNC and FF at the same time on
> > either atom powered machine.  Ditto the garage and its currently 2
> > machines.
> >
> >> Put your web browser on your desktop computer, and upgrade it to
> >> something that is supported.
> >
> > That I have in the planning stage, starting with a fresh HD. But
>
>  *wheezy is an old friend and I have excised the majority of its
> warts over the years.*
>
> First off, I have some scripts that greatly simplify things for me,
> and which depends on dbus, which I read is deprecated, so what
> replaces it?
>
>
> It still works, doesn't it?
> As Anne Landers used to say, "If it ain't broke, don't fix it." Sounds
> like good advice to me.
>
> --doug

There's an echo in here. Oh, its you.  :)

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

Re: Thunderbird almost unusable after upgrade

[Javier Barroso]

Hello,

On Fri, Aug 11, 2017 at 9:43 PM, Sven Hartge  wrote:
> Sven Joachim  wrote:
>> On 2017-08-10 10:24 -0400, Jape Person wrote:
>
>>> After this upgrade
>>>
>>> thunderbird:amd64 (1:52.2.1-4, 1:52.2.1-4+b1)
>>>
>>> Thunderbird in Cinnamon DE is almost completely useless because
>>> portions of its windows / text / toolbars don't repaint until the
>>> window is resized. Is anyone else seeing this?
>
>> Yes, see https://bugs.debian.org/871629.
>
> Confirmation: Rebuilding 1:52.2.1-4 with gcc-6/g++-6 as the compiler
> fixes the problem.

You can also download thunderbird and its addons from
http://snapshot.debian.org/package/icedove/1%3A52.2.1-4/, selecting
your architecture

See what packages have you installed from icedove them:

 aptitude search '?and(?source-package(icedove),?installed)'

Download to Download/icedove and install with apt install
./Download/icedove/*.deb

Regards

Re: usb flash drives / sd

[Dan Ritter]

On Fri, Aug 11, 2017 at 02:25:01PM -0500, Doug wrote:
> 
> On 08/11/2017 01:46 PM, ju...@tutanota.com wrote:
> > There are three major types of flash chip types : SLC - MLC - TLC
> > 
> > how-to check my usbkey/sd/memory card ?
> > 
> > -- 
> > Securely sent with Tutanota.
> 
> I am not being a wiseguy.
> What is the difference, and why does it matter?

The basic difference is the number of bits recorded in a single
cell, and that affects both the storage density and its
long term reliability.

More bits == more dense but less reliable.

To compensate for long term reliability, SSD manufacturers use
a variety of strategies involving staging data in RAM,
compressing it, and implementing other special storage
structures.

On a removable-media flash device, none of those strategies
are used.

-dsr-

Re: usb flash drives / sd

[Dan Ritter]

On Fri, Aug 11, 2017 at 08:46:08PM +0200, ju...@tutanota.com wrote:
> There are three major types of flash chip types : SLC - MLC - TLC
> 
> how-to check my usbkey/sd/memory card ?

Doesn't matter for that -- your usb key, SD or similar external
removable storage will be the cheapest thing that they can find
that day, which mostly means MLC right now. It cannot support
long-term usage and is best considered as a temporary storage 
spot, useful mostly for transfer to more reliable systems.

-dsr-

erro krb5

[Luis Ernesto Garcia Reyes]

Saludos instale un AD+ Samba 4 y todo perfecto:

 

#klist

 

Ticket cache: FILE:/tmp/krb5cc_0 Default principal: administra...@casa.cu Valid 
starting Expires Service principal 26/02/17 17:46:10 27/02/17 03:46:10 
krbtgt/casa...@casa.cu renew until 27/02/17 17:46:07

 

Pero cuando reinicio el servidor y ejecuto klist de nuevo

root@dc1:~# klist

klist: Credentials cache file '/tmp/krb5cc_0' not found

 

No tengo idea porque ocurre esto. Saludos

Re: Help with USB audio card

[Rodolfo Medina]

Rodolfo Medina  writes:

> Curt  writes:
>
>> On 2017-08-07, Rodolfo Medina  wrote:
>>>
>>> Besides, I ran alsamixer, selected the USB card and unmuted everything.
>>> But then, when I try to record, no sound is recorded.  I do:
>>>
>>
>> This makes no sense BTW. Unmuted everything? You're *recording*, so what
>> you want to do in alsamixer is to select your external usb audio card
>> (F6), display its capture device(s) (F5), and toggle on the input
>> channel of your choice (space bar).
>>
>> But I assume you have arrived at this crucial result in one way or another.
>
>
> I did.  Besides, the USB card does not even work with headphones: when
> headphones are plugged into it, no sound is heard from them.


I had the USB work with headphones doing:

 $ mplayer -ao alsa:device=hw=2.0 

Can this help to solve also the recording problem...?  I get no sound recorded
doing:

 $ sox -t alsa hw:2,0 output.wav

Rodolfo

Re: module not loading on startup

[Gary Dale]

On 11/08/17 03:39 PM, Pascal Hambourg wrote:

Le 11/08/2017 à 08:32, Gary Dale a écrit :


I eventually tracked the problem down to a UDEV persistent rule (now 
deleted) and also the need to modify /etc/network/interfaces to use 
the name the name of the new NIC (enp5s0 instead of eth0 - since it 
wasn't carried over in the upgrade from Jessie). However because I 
installed the Realtek module, the r8169 kernel module isn't 
automatically loading.


Check files in /etc/modprobe.d/ for some "blacklist r8169" command and 
comment it out. You may need to rebuild the initramfs with 
update-initramfs -u.


Thanks. There was a blacklist file for the r8168-dkms module but the 
line about the r8169 driver was already commented out. I removed it anyway.


I decided to byte the bullet and just add the r8169 to /etc/modules. 
It's unlikely to ever hurt.

what should I do if I want to adopt one orphaned package?

[慕 冬亮]

Dear all,

I want to adopt one package - Bochs [bochs: IA-32 PC 
emulator (package 
info)] which is orphaned since 2011 
days. And the current version in sid is 2.6-5.

The official website shows that the latest version of Bochs is 2.6.9. And 
the history for bochs is as follows:

  *   May 3, 2015: Bochs 
2.6.8 is now 
available.
  *   November 2, 2014: Bochs 
2.6.7 is now 
available.
  *   June 15, 2014: Bochs 
2.6.6 is now 
available.
  *   June 1, 2014: Bochs 
2.6.5 is now 
available.
  *   May 26, 2013: Bochs 
2.6.2 is now 
available.
  *   April 7, 2013: Bochs 
2.6.1 is now 
available.
  *   September 2, 2012: Bochs 
2.6 is now available.

What should I do and which document should I read in advance?

I have been using Debian for three years. I have some knowledge about 
Debian package development. I only have a little experience in debian software 
packaging.

Besides, I have a problem in subscribing debian-devel mailing list with 
current email. I confirmed the email, but with no any response.


--

My best regards to you.

 No System Is Safe!
 Dongliang Mu

Re: Thunderbird almost unusable after upgrade

[Sven Hartge]

Sven Joachim  wrote:
> On 2017-08-10 10:24 -0400, Jape Person wrote:

>> After this upgrade
>>
>> thunderbird:amd64 (1:52.2.1-4, 1:52.2.1-4+b1)
>>
>> Thunderbird in Cinnamon DE is almost completely useless because
>> portions of its windows / text / toolbars don't repaint until the
>> window is resized. Is anyone else seeing this?

> Yes, see https://bugs.debian.org/871629.

Confirmation: Rebuilding 1:52.2.1-4 with gcc-6/g++-6 as the compiler
fixes the problem.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: module not loading on startup

[Pascal Hambourg]

Le 11/08/2017 à 08:32, Gary Dale a écrit :


I eventually tracked the problem down to a UDEV persistent rule (now 
deleted) and also the need to modify /etc/network/interfaces to use the 
name the name of the new NIC (enp5s0 instead of eth0 - since it wasn't 
carried over in the upgrade from Jessie). However because I installed 
the Realtek module, the r8169 kernel module isn't automatically loading.


Check files in /etc/modprobe.d/ for some "blacklist r8169" command and 
comment it out. You may need to rebuild the initramfs with 
update-initramfs -u.

Re: usb flash drives / sd

[Doug]

On 08/11/2017 01:46 PM, ju...@tutanota.com wrote:

There are three major types of flash chip types : SLC - MLC - TLC

how-to check my usbkey/sd/memory card ?

--
Securely sent with Tutanota. 


I am not being a wiseguy.
What is the difference, and why does it matter?

--doug

Re: usb flash drives / sd

[Sven Hartge]

ju...@tutanota.com wrote:

> There are three major types of flash chip types : SLC - MLC - TLC
> how-to check my usbkey/sd/memory card ?

Break open, find flash chip, type part number into google.

Non-destructive? No way.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Thunderbird almost unusable after upgrade

[Liam O'Toole]

On 2017-08-11, Gene Heskett  wrote:

(...)

> First off, I have some scripts that greatly simplify things for me, and 
> which depends on dbus, which I read is deprecated, so what replaces it?

Dbus is still around in stretch, and has many dependent packages. I
don't think it's going anywhere soon.

-- 

Liam

usb flash drives / sd

[jumpy]

There are three major types of flash chip types : SLC - MLC - TLC

how-to check my usbkey/sd/memory card ?

--
Securely sent with Tutanota.

Re: Thunderbird almost unusable after upgrade

[Doug]

On 08/11/2017 10:12 AM, Gene Heskett wrote:

On Friday 11 August 2017 10:54:22 Greg Wooledge wrote:


On Fri, Aug 11, 2017 at 10:48:59AM -0400, Gene Heskett wrote:

I have a 5 or 6 machine home network, most of which are running
linuxcnc to carve wood or metal. Linuxcnc, generally needs realtime
support so that when a machine needs direction as to what to do
next, linuxcnc has at the most 10 microseconds to respond.

So why do you run a *web browser* on this machine?  Put it in the work
shed or wherever, and control it like a server or an appliance.


Chuckle.  2 of them are in fact in a 12x16 shed in the back yard, and
occasionally I might need to step over to the other idle machine and
look something up, so both have FF installed, but with the dram shortage
FF causes, I don't run LCNC and FF at the same time on either atom
powered machine.  Ditto the garage and its currently 2 machines.


Put your web browser on your desktop computer, and upgrade it to
something that is supported.

That I have in the planning stage, starting with a fresh HD. But


*wheezy is an old friend and I have excised the majority of its warts over 
the years.*

First off, I have some scripts that greatly simplify things for me, and
which depends on dbus, which I read is deprecated, so what replaces it?


It still works, doesn't it?
As Anne Landers used to say, "If it ain't broke, don't fix it." Sounds like
good advice to me.

--doug

change to postfix from backports

[mj]

Hi,

Quick question: I have a wheezy system (yes, we will upgrade) that needs 
a more recent postfix. Postfix 2.11 is in backports, and I would like to 
upgrade to that.


We are using dovecot from the regular repo, and posfix authenticated to 
dovecot via sasl.


Is it safe to upgrade from standard wheezy postfix to the one from 
backports? Will sasl (normally) still work as it does now?


Best regards,
MJ

Re: delay the start of a service until LACP negotiation is complete

[Sven Hartge]

John Ratliff  wrote:
> 

>> Do you really need STP? Do you really need STP on that group of
>> ports?  Why not disable it completely.

> I'm not aware of any way to disable spanning tree on a per port basis,
> and no, I cannot disable it on the switch entirely.

Ah, Cisco. Yes, they don't do that, right.

S°

-- 
Sigmentation fault. Core dumped.

Re: delay the start of a service until LACP negotiation is complete

[John Ratliff]

> Do you really need STP? Do you really need STP on that group of ports?
> Why not disable it completely.

I'm not aware of any way to disable spanning tree on a per port basis, and
no, I cannot disable it on the switch entirely.

>
> I have the same, but the systemd.unit restarts conntrackd automatically
> if it dies, so there is no problem.
>
> If you use systemd-networkd to control your interfaces, you could enable
> systemd-networkd-wait-online.service and have conntrackd depend on
> network-online.target to make it start _after_ the network is really
> online.
>
> Unfortunately ifupdown got this feature only after the release of
> Stretch.

I tried this, as I am on stretch, but I get the same errors as before. If
you don't think they're a problem, I will leave it be for now.

Thanks.

Re: customizing systemd config

[Christian Seiler]

Hi there,

On 08/11/2017 04:42 AM, Gregory Seidman wrote:
> I'm trying to recreate under systemd something I had previously cobbled
> together with shell scripts and init levels under sysvinit.
> 
> Only a few services ran under init 2, the default set in /etc/inittab,
> including privoxy and ssh; the rest of the services I wanted running, such
> as fetchmail, exim4, courier-imap, apache2, etc. would be started at init
> level 3. Those services required an encrypted volume (actually a RAID that
> was an encrypted LVM PV for a VG with several volumes) to be configured and
> mounted before they could be started.

I've blogged about this very scenario a while back:
https://blog.iwakd.de/headless-luks-decryption-via-ssh

Note that I wrote that mainly to explain some details about
systemd using a specific example, I personally am not actually
using that kind of setup. For a headless server of mine I use
full disk encryption (LUKS) for everything except /boot and
unlock the entire system in the initramfs. I also mention that
approach in my blog post, but wanted to stress it here again
because I think that the initramfs-based decryption is the
better way to do this. For that alternative take a look at:
https://projectgus.com/2013/05/encrypted-rootfs-over-ssh-with-debian-wheezy/

Regards,
Christian

Re: Btrs vs ext4. Which one is more reliable?

[Christian Seiler]

Hi there,

On 08/11/2017 06:29 PM, Dejan Jocic wrote:
> On 11-08-17, Christian Seiler wrote:
>> You can also set DefaultTimeoutStopSec= in /etc/systemd/system.conf
>> to alter the default for all units (though individual settings for
>> units will still override that).
>>
> Thank you for suggestion. I did find that solution, some time ago, can't
> remember exactly where. But it was followed by warning that it is bad
> idea, can't remember exactly why. Do you have any hint of why it could
> be bad idea to limit timeout, or I've just misunderstood whatever I've
> read about it?

Well, there's a reason the default is 90s. And for some services even
that might be too short. Take for example a database server where the
regular stop script might take 10 minutes to shut down properly (when
no error occurs).

On the other hand for other services you can easily get away with a
lot less of a timeout. For example, I have apt-cache-ng running on
my system (to cache stuff for sbuild), and I think it's perfectly
reasonable to set the stop timeout for that service to 10s or even
lower because that's just a stupid proxy. On the other hand I've
never experienced apt-cacher-ng to take longer than 1s or so to stop,
so I haven't bothered.

The right timeout is always a balancing act - and systemd's default
is a compromise to provide something that won't break most use cases
but still cause the system to shut down after a finite time.

It's up to you to decide what the best option here is. I wouldn't
set the default to anything lower than 30s myself, but that's just
a gut feeling, and I don't actually have any hard data to back that
number up.

> As for more reliable during shutdown part, not in
> my experience, at least on Stretch.

I don't recall ever running into the timeout on shutdown since Stretch
has been released as stable. And I am running a couple of Strech
systems myself, both at home and at work.

> It was on Jessie though, where that
> feature was hitting me not more than once in every 15-20
> shutdowns/reboots. 

Even every 15-20 shutdowns is too much. I never experience those
unless something's wrong. And then I debug hat problem to see what
is causing it and get rid of the root problem so that it doesn't
occur again.

Regards,
Christian

Re: Help with USB audio card

[Ric Moore]

On 08/10/2017 09:06 AM, Rodolfo Medina wrote:

Curt  writes:


On 2017-08-07, Rodolfo Medina  wrote:


Besides, I ran alsamixer, selected the USB card and unmuted everything.  But
then, when I try to record, no sound is recorded.  I do:



This makes no sense BTW. Unmuted everything? You're *recording*, so what
you want to do in alsamixer is to select your external usb audio card
(F6), display its capture device(s) (F5), and toggle on the input
channel of your choice (space bar).

But I assume you have arrived at this crucial result in one way or another.



I did.  Besides, the USB card does not even work with headphones: when
headphones are plugged into it, no sound is heard from them.


If you were running pulseaudio, you would merely select the headphones. 
I suggest you use USB headphones. They are cheap. Works a charm. Ric



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

Re: delay the start of a service until LACP negotiation is complete

[Sven Hartge]

John Ratliff  wrote:
> 
>> John Ratliff  wrote:

>>> I have a 4 port LAGG (LACP / bond-mode 4) interface named bond0. It
>>> seems to take about 45 seconds after the links come up to negotiate
>>> with the switch.

>> This long delay is not normal. For me LACP-based bonds never take
>> longer than 1 or at most 2 seconds to be operational.
>>
>> This smells of STP. Disable STP on the switch for that port or change
>> to rSTP.

> The ports are trunk ports carrying multiple vlans. I have enabled
> spanning-tree portfast trunk on the port channel. It still takes around 5
> seconds, but that's significantly faster. 

Do you really need STP? Do you really need STP on that group of ports?
Why not disable it completely.

> However, I have another slight issue. When conntrackd is started on
> boot, it gives me some errors:

> Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30 2017] 
> (pid=1157) [notice] using user-space event filtering
> Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30 2017] 
> (pid=1157) [notice] netlink event socket buffer size has been set to  262142 
> bytes
> Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30 2017] 
> (pid=1157) [notice] initialization completed
> Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30 2017] 
> (pid=1157) [notice] -- starting in console mode --
> Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30 2017] 
> (pid=1157) [ERROR] no dedicated links available!

> I don't get these errors if I run my delay script. I wonder if this is a
> problem.

I have the same, but the systemd.unit restarts conntrackd automatically
if it dies, so there is no problem.

If you use systemd-networkd to control your interfaces, you could enable
systemd-networkd-wait-online.service and have conntrackd depend on
network-online.target to make it start _after_ the network is really
online.

Unfortunately ifupdown got this feature only after the release of
Stretch.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Btrs vs ext4. Which one is more reliable?

[Dejan Jocic]

On 11-08-17, Christian Seiler wrote:
> Am 2017-08-10 16:02, schrieb Dejan Jocic:
> > On 10-08-17, David Wright wrote:
> > > On Thu 10 Aug 2017 at 07:04:09 (-0400), Dan Ritter wrote:
> > > > On Wed, Aug 09, 2017 at 09:46:09PM -0400, David Niklas wrote:
> > > > > On Sat, 29 Jul 2017 04:59:40 +
> > > > > Andy Smith  wrote:
> > > > >
> > > > > Also, my use case is at home where the power can and *does* fail. I 
> > > > > also
> > > > > find myself using the latest kernel and oftentimes an experimental 
> > > > > driver
> > > > > for my AMD graphics card, hence my need for a *very* stable fs over
> > > > > sudden unmount.
> > > >
> > > > Buy a cheap UPS with a USB or serial connection to your
> > > > computer. Even if it only supplies power for 2 minutes, that's
> > > > enough time for the computer to receive the power outage signal
> > > > and do an orderly shutdown.
> > > 
> > > Two minutes barely covers the timeouts that can often occur when
> > > shutting down systemd; the commonest timeout period here seems
> > > to be 90 seconds. I wouldn't mind reducing them if that's possible.
> > > Processes got just a few seconds with sysvinit before they were
> > > killed.
> > > 
> > 
> > Yes, those 90 sec waiting for nothing is one of the most annoying
> > "features" of systemd that I would love to get rid of.
> 
> You can set TimeoutStopSec= for some units explicitly, for example
> via drop-in. Example:
> 
> mkdir -p /etc/systemd/system/XYZ.service.d
> cat > /etc/systemd/system/XYZ.service.d/stop-timeout.conf < [Service]
> TimeoutStopSec=10s
> EOF
> 
> Even if the service is only provided by an init script this will
> still work.
> 
> You can also set DefaultTimeoutStopSec= in /etc/systemd/system.conf
> to alter the default for all units (though individual settings for
> units will still override that).
> 

Thank you for suggestion. I did find that solution, some time ago, can't
remember exactly where. But it was followed by warning that it is bad
idea, can't remember exactly why. Do you have any hint of why it could
be bad idea to limit timeout, or I've just misunderstood whatever I've
read about it?

> > And most annoying
> > aspect of it is that problem is rarely constant. It can exist in one
> > release in systemd, vanish in other, and then come back again in next
> > release. And it can occur once in every 10 shutdowns/reboots, or not
> > occur once in every 10 shutdowns/reboots.
> 
> That is an indication that you have a race condition during
> shutdown.
> 
> The "90s" thing is basically just systemd saying: yeah, I've tried
> to shutdown a specific unit and it's still active, now I'm going
> to wait for the timeout before I send a hard SIGKILL. You can't
> really compare that to sysvinit, because sysvinit doesn't actually
> track processes properly, so what most often would happen is that
> the init script would send a TERM signal to a process, the better
> ones maybe also a KILL signal after some time, before they'd just
> consider the service stopped. But if other processes had been
> started by the service, sysvinit wouldn't care about them, and
> only kill those in the final "let's kill all that's still left
> over" killing spree. systemd by contrast actually tracks what's
> happening with a service and kills the remaining processes.
> 
> That said: what could happen here is that the systemd unit created
> for a given service has a bug. For example it could not be ordered
> correctly and hence systemd tries to stop it too early while other
> services still depend on it.
> 
> Or the stop command that is called by systemd hangs because it
> tries to do something that it shouldn't do during shutdown (for
> example start another service).
> 
> See the following page for information on how to debug shutdown
> issues with systemd (and keep in mind that Debian has systemd stuff
> installed  in /lib and not /usr/lib):
> https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
> 
> I've found systemd to be far more reliable during shutdown (even
> if you have to wait for a timeout if something's gone wrong),
> because at least there is a timeout. With sysvinit I've sometimes
> had the problem that a shutdown script would hang and then nothing
> further would happen and the computer would never properly shut
> down. This was especially frustrating with headless machines. What
> systemd does do is make it much more apparent if there's a
> misconfiguration somewhere.
> 
> Regards,
> Christian
> 

Thank you for your explanation. I do understand why it is happening, did
some reading about that subject even before I've ran on that bug, but it
is still annoying. As for more reliable during shutdown part, not in
my experience, at least on Stretch. It was on Jessie though, where that
feature was hitting me not more than once in every 15-20
shutdowns/reboots. 


Anyway, thank you for your time and help.

Re: pepperflashplugin-nonfree para opera

[Dixan Rivas]

Si, con el apt-get lo puedes instalar, si te continua fallando puedes
intentar bajar solo binarios y compilarlo en tu ordenador.

El 11 ago. 2017 16:57, "marcelo"  escribió:

El 11/08/17 a las 11:59, Dixan Rivas escribió:

apt-get remove --purge $(dpkg --list | grep pepperflashplugin | cut -c5-40)
algo así eliminas el plugin.

Saludos

El 11 ago. 2017 15:55, "marcelo"  escribió:



El 07/08/17 a las 11:31, Cristian Mitchell escribió:

no me pude aguantar lo acabo de resolver

lo primero es que el repositorio de opera para debian esta una versión vieja
bájate la ultima del sitio oficial
el otro problema que me tiro fue con las key
por las dudas desinstálalo si te lo permitió

dpkg -P pepperflashplugin-nonfree

y reinstálalo

apt -i pepperflashplugin-nonfree

Hola amigo al poner dpkg -P pepperflashplugin-nonfree me sale
dpkg: aviso: no se tendrá en cuenta la petición de desinstalar
perpperflashplugin-nonfree porque no está instalado
sera porque lo instale con apt get install???
despues al poner apt install -i pepperflashplugin-nonfree me sale
E: No se conoce la opción de línea de órdenes «i» [de -i].
espero indicaciones gracias


Me funcionó perfecto.
No quiero abusar, pero ahora para instalarlo vasta con
apt get install pepperflashplugin-nonfree
Gracias

Re: Btrs vs ext4. Which one is more reliable?

[Christian Seiler]

Am 2017-08-10 16:02, schrieb Dejan Jocic:

On 10-08-17, David Wright wrote:

On Thu 10 Aug 2017 at 07:04:09 (-0400), Dan Ritter wrote:
> On Wed, Aug 09, 2017 at 09:46:09PM -0400, David Niklas wrote:
> > On Sat, 29 Jul 2017 04:59:40 +
> > Andy Smith  wrote:
> >
> > Also, my use case is at home where the power can and *does* fail. I also
> > find myself using the latest kernel and oftentimes an experimental driver
> > for my AMD graphics card, hence my need for a *very* stable fs over
> > sudden unmount.
>
> Buy a cheap UPS with a USB or serial connection to your
> computer. Even if it only supplies power for 2 minutes, that's
> enough time for the computer to receive the power outage signal
> and do an orderly shutdown.

Two minutes barely covers the timeouts that can often occur when
shutting down systemd; the commonest timeout period here seems
to be 90 seconds. I wouldn't mind reducing them if that's possible.
Processes got just a few seconds with sysvinit before they were
killed.



Yes, those 90 sec waiting for nothing is one of the most annoying
"features" of systemd that I would love to get rid of.


You can set TimeoutStopSec= for some units explicitly, for example
via drop-in. Example:

mkdir -p /etc/systemd/system/XYZ.service.d
cat > /etc/systemd/system/XYZ.service.d/stop-timeout.conf <
And most annoying
aspect of it is that problem is rarely constant. It can exist in one
release in systemd, vanish in other, and then come back again in next
release. And it can occur once in every 10 shutdowns/reboots, or not
occur once in every 10 shutdowns/reboots.


That is an indication that you have a race condition during
shutdown.

The "90s" thing is basically just systemd saying: yeah, I've tried
to shutdown a specific unit and it's still active, now I'm going
to wait for the timeout before I send a hard SIGKILL. You can't
really compare that to sysvinit, because sysvinit doesn't actually
track processes properly, so what most often would happen is that
the init script would send a TERM signal to a process, the better
ones maybe also a KILL signal after some time, before they'd just
consider the service stopped. But if other processes had been
started by the service, sysvinit wouldn't care about them, and
only kill those in the final "let's kill all that's still left
over" killing spree. systemd by contrast actually tracks what's
happening with a service and kills the remaining processes.

That said: what could happen here is that the systemd unit created
for a given service has a bug. For example it could not be ordered
correctly and hence systemd tries to stop it too early while other
services still depend on it.

Or the stop command that is called by systemd hangs because it
tries to do something that it shouldn't do during shutdown (for
example start another service).

See the following page for information on how to debug shutdown
issues with systemd (and keep in mind that Debian has systemd stuff
installed  in /lib and not /usr/lib):
https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1

I've found systemd to be far more reliable during shutdown (even
if you have to wait for a timeout if something's gone wrong),
because at least there is a timeout. With sysvinit I've sometimes
had the problem that a shutdown script would hang and then nothing
further would happen and the computer would never properly shut
down. This was especially frustrating with headless machines. What
systemd does do is make it much more apparent if there's a
misconfiguration somewhere.

Regards,
Christian

Re: pepperflashplugin-nonfree para opera

[marcelo]

El 11/08/17 a las 11:59, Dixan Rivas escribió:
apt-get remove --purge $(dpkg --list | grep pepperflashplugin | cut 
-c5-40) algo así eliminas el plugin.


Saludos

El 11 ago. 2017 15:55, "marcelo" > escribió:




El 07/08/17 a las 11:31, Cristian Mitchell escribió:

no me pude aguantar lo acabo de resolver

lo primero es que el repositorio de opera para debian esta una
versión vieja
bájate la ultima del sitio oficial
el otro problema que me tiro fue con las key
por las dudas desinstálalo si te lo permitió

dpkg -P pepperflashplugin-nonfree

y reinstálalo

apt -i pepperflashplugin-nonfree

Hola amigo al poner dpkg -P pepperflashplugin-nonfree me sale
dpkg: aviso: no se tendrá en cuenta la petición de desinstalar
perpperflashplugin-nonfree porque no está instalado
sera porque lo instale con apt get install???
despues al poner apt install -i pepperflashplugin-nonfree me sale
E: No se conoce la opción de línea de órdenes «i» [de -i].
espero indicaciones gracias



Me funcionó perfecto.
No quiero abusar, pero ahora para instalarlo vasta con
apt get install pepperflashplugin-nonfree
Gracias

Error! Bad dkms.conf file after apt-get upgrade

[Larry Dighera]

Hello all,
After running 'apt-get install upgrade' the system reported the data below.
How can I overcome this issue?  

Is it just a matter of loading a proper dkms.conf file, perhaps from another 
Stretch installation, or is there an official dkms.conf file that I can 
download somewhere, or is it a matter of removing the dkms package and 
reinstalling it, or repairing/reinstalling it?

I am grateful for any assistance/insight into this issue you are able to 
provide.  ADVthanksANCE.
Best regards,Larry

===
Fri Aug 11 08:26:01 PDT 2017

Setting up linux-image-4.9.0-3-amd64 (4.9.30-2+deb9u3) ...
Progress: [ 89%]
/etc/kernel/postinst.d/dkms:
/usr/sbin/dkms: line 485: .: /var/lib/dkms/rtl8814/4.3.21/source/dkms.conf: 
cannot execute binary file
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 8
dpkg: error processing package linux-image-4.9.0-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for hicolor-icon-theme (0.15-1) ...
Progress: [ 90%]
Setting up git (1:2.11.0-3+deb9u1) ...
Progress: [ 92%]
Progress: [ 93%]
Setting up linux-headers-4.9.0-3-amd64 (4.9.30-2+deb9u3) ...
Progress: [ 95%]
/etc/kernel/header_postinst.d/dkms:
/usr/sbin/dkms: line 485: .: /var/lib/dkms/rtl8814/4.3.21/source/dkms.conf: 
cannot execute binary file
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 8
Failed to process /etc/kernel/header_postinst.d at 
/var/lib/dpkg/info/linux-headers-4.9.0-3-amd64.postinst line 11.
dpkg: error processing package linux-headers-4.9.0-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-4.9.0-3-amd64
 linux-headers-4.9.0-3-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


Upgrade Debian system before continuing (apt-get install dist-upgrade) [Y/n]? ^[
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up linux-headers-4.9.0-3-amd64 (4.9.30-2+deb9u3) ...
Progress: [  0%]
/etc/kernel/header_postinst.d/dkms:
/usr/sbin/dkms: line 485: .: /var/lib/dkms/rtl8814/4.3.21/source/dkms.conf: 
cannot execute binary file
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 8
Failed to process /etc/kernel/header_postinst.d at 
/var/lib/dpkg/info/linux-headers-4.9.0-3-amd64.postinst line 11.
dpkg: error processing package linux-headers-4.9.0-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up linux-image-4.9.0-3-amd64 (4.9.30-2+deb9u3) ...
/etc/kernel/postinst.d/dkms:
/usr/sbin/dkms: line 485: .: /var/lib/dkms/rtl8814/4.3.21/source/dkms.conf: 
cannot execute binary file
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 8
dpkg: error processing package linux-image-4.9.0-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-headers-4.9.0-3-amd64
 linux-image-4.9.0-3-amd64
E: Sub-process /usr/bin/dpkg returned an error code 
(1)===

Re: Thunderbird almost unusable after upgrade

[Gene Heskett]

On Friday 11 August 2017 10:54:22 Greg Wooledge wrote:

> On Fri, Aug 11, 2017 at 10:48:59AM -0400, Gene Heskett wrote:
> > I have a 5 or 6 machine home network, most of which are running
> > linuxcnc to carve wood or metal. Linuxcnc, generally needs realtime
> > support so that when a machine needs direction as to what to do
> > next, linuxcnc has at the most 10 microseconds to respond.
>
> So why do you run a *web browser* on this machine?  Put it in the work
> shed or wherever, and control it like a server or an appliance.
>
Chuckle.  2 of them are in fact in a 12x16 shed in the back yard, and 
occasionally I might need to step over to the other idle machine and 
look something up, so both have FF installed, but with the dram shortage 
FF causes, I don't run LCNC and FF at the same time on either atom 
powered machine.  Ditto the garage and its currently 2 machines.

> Put your web browser on your desktop computer, and upgrade it to
> something that is supported.

That I have in the planning stage, starting with a fresh HD. But wheezy 
is an old friend and I have excised the majority of its warts over the 
years.

First off, I have some scripts that greatly simplify things for me, and 
which depends on dbus, which I read is deprecated, so what replaces it?

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)
Genes Web page 

Re: pepperflashplugin-nonfree para opera

[Dixan Rivas]

apt-get remove --purge $(dpkg --list | grep pepperflashplugin | cut -c5-40)
algo así eliminas el plugin.

Saludos

El 11 ago. 2017 15:55, "marcelo"  escribió:



El 07/08/17 a las 11:31, Cristian Mitchell escribió:

no me pude aguantar lo acabo de resolver

lo primero es que el repositorio de opera para debian esta una versión vieja
bájate la ultima del sitio oficial
el otro problema que me tiro fue con las key
por las dudas desinstálalo si te lo permitió

dpkg -P pepperflashplugin-nonfree

y reinstálalo

apt -i pepperflashplugin-nonfree

Hola amigo al poner dpkg -P pepperflashplugin-nonfree me sale
dpkg: aviso: no se tendrá en cuenta la petición de desinstalar
perpperflashplugin-nonfree porque no está instalado
sera porque lo instale con apt get install???
despues al poner apt install -i pepperflashplugin-nonfree me sale
E: No se conoce la opción de línea de órdenes «i» [de -i].
espero indicaciones gracias

Re: pepperflashplugin-nonfree para opera

[marcelo]

El 07/08/17 a las 11:31, Cristian Mitchell escribió:

no me pude aguantar lo acabo de resolver

lo primero es que el repositorio de opera para debian esta una versión 
vieja

bájate la ultima del sitio oficial
el otro problema que me tiro fue con las key
por las dudas desinstálalo si te lo permitió

dpkg -P pepperflashplugin-nonfree

y reinstálalo

apt -i pepperflashplugin-nonfree

Hola amigo al poner dpkg -P pepperflashplugin-nonfree me sale
dpkg: aviso: no se tendrá en cuenta la petición de desinstalar 
perpperflashplugin-nonfree porque no está instalado

sera porque lo instale con apt get install???
despues al poner apt install -i pepperflashplugin-nonfree me sale
E: No se conoce la opción de línea de órdenes «i» [de -i].
espero indicaciones gracias

Re: Thunderbird almost unusable after upgrade

[Greg Wooledge]

On Fri, Aug 11, 2017 at 10:48:59AM -0400, Gene Heskett wrote:
> I have a 5 or 6 machine home network, most of which are running linuxcnc 
> to carve wood or metal. Linuxcnc, generally needs realtime support so 
> that when a machine needs direction as to what to do next, linuxcnc has 
> at the most 10 microseconds to respond.

So why do you run a *web browser* on this machine?  Put it in the work
shed or wherever, and control it like a server or an appliance.

Put your web browser on your desktop computer, and upgrade it to
something that is supported.

Re: Btrs vs ext4. Which one is more reliable?

[Gary Dale]

On 10/08/17 09:44 AM, David Wright wrote:

On Thu 10 Aug 2017 at 07:04:09 (-0400), Dan Ritter wrote:

On Wed, Aug 09, 2017 at 09:46:09PM -0400, David Niklas wrote:

On Sat, 29 Jul 2017 04:59:40 +
Andy Smith  wrote:

Also, my use case is at home where the power can and *does* fail. I also
find myself using the latest kernel and oftentimes an experimental driver
for my AMD graphics card, hence my need for a *very* stable fs over
sudden unmount.

Buy a cheap UPS with a USB or serial connection to your
computer. Even if it only supplies power for 2 minutes, that's
enough time for the computer to receive the power outage signal
and do an orderly shutdown.

Two minutes barely covers the timeouts that can often occur when
shutting down systemd; the commonest timeout period here seems
to be 90 seconds. I wouldn't mind reducing them if that's possible.
Processes got just a few seconds with sysvinit before they were
killed.



Still it is sufficient to do an orderly shutdown when power is lost 
and your network hardware might be off.
The bigger issue is why would anyone use experimental drivers and the 
latest kernel when they are worried about reliability?

Re: Thunderbird almost unusable after upgrade

[Gene Heskett]

On Friday 11 August 2017 01:45:03 MENGUAL Jean-Philippe wrote:

> Le 11/08/2017 à 07:38, Gene Heskett a écrit :
> > On Thursday 10 August 2017 14:48:52 MENGUAL Jean-Philippe wrote:
> >> Hi,
> >>
> >> I am not sure I understand your mail in details. What I can say is
> >> that we tried building against gtk2 and it works. It is just a
> >> build option switch to change. Why do you think Debian package will
> >> not do it?
> >
> > It hasn't played a video, except some commercials in front of the
> > video in several weeks. I can't download the binary from mozilla
> > because its built against gtk3, and the dependency's it needs are
> > not available in the wheezy repo's. I haven't tried to build from
> > src, no clue where to get it even.
>
> Wheezy is quite old, is it impossible to switch to Jessie at least?

I have a 5 or 6 machine home network, most of which are running linuxcnc 
to carve wood or metal. Linuxcnc, generally needs realtime support so 
that when a machine needs direction as to what to do next, linuxcnc has 
at the most 10 microseconds to respond.  The last truely realtime kernel 
was built some time back as  3.4-9-rtai-686-pae. The rtai is a very 
invasive patch in that it takes over the machine and runs the linux 
kernel as a subtask.

No one has built a 4.x.x kernel with that patchkit and has had any real 
success, the one jessie install I have is on an armhf (respberry pi 3b)
but its is running on mesa interface cards which means a 1 millisecond 
response time is adequate. That machine is running a newer kernel in the 
rt-preempt flavor, a 4.4.4-rt9-v7+, but while newer builds have been 
tried, they all ignore the local keyboard to the extent it both unusable 
and dangerous as it leaves a 300+ kilogram machine moving when it should 
have stopped when I took my finger off the jog key. That is a pi 
physical architecture problem that a thought experiment I had might 
solve but haven't bought the hardware to test the theory yet. I am also 
following the forum and reviews on pines new rock64 board as a possible 
replacement of the r-pi.

Wheezy is stable, running from power outage to power outage, which might 
be several months. This particular machine has a UPS, backed up by a 
20KW automatic standby generator on a pad behind the garage, and its 
uptime is 47 days, since the last update that needed a reboot. The 
generator is needed as the wife is dieing of COPD, and lack of air 
conditioning  may hasten the time of her last breath.

Wheezy is an old friend I can get things done with. Jessie could get that 
way, but I've 3 machines that will need all the interfacing replaced if 
I made the version jump for all.  Its an LTS, so I've 3 years of 
security updates still.

> Anyway, have you reported the problem?
>
I have not, I understand there is a bug number but I have not found it in 
the mail morgue here.

> > Why should I have to build FF from src, this isn't gentoo or arch?
>
> I dont say you should, I say it is a working solution and we submitted
> it to maintainers of the package. Dont hesitate to reply the bug
> report I gave to help us to convince them to rebuild the package
> according to this requirement for DebiaN 7 and 8.

That would be great, and I'd add my two cents if I knew the address, bug 
number, and my passwd.

>  It is a known bug we reported under number 870719.

Ah, there's the bug number, now where is that address?

Found it, plea sent. Somehow, the passwd was bypassed. I hope it gets 
thru.

[...]

Thanks Jean-Philippe

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

Re: If you only knew how tired I am of loneliness Barbara

[gerald dunbar]

Why

On Aug 8, 2017 4:07 PM, "Barbara Staninska"  wrote:

>
>
> Do you want to be my lodestar tonight?  http://bitly.com/2umI7zi
>

Re: debian 9.1 dpkg error when installing xemacs and erlang

[Rémy Noulin]

Hi Mark,
After running:
apt-get install emacs25-el

I get another error:

While compiling erlang-edoc-xml-context in file
/usr/share/xemacs21/site-lisp/erlang/erlang-edoc.el:
  !! File error (("Cannot open load file" "xmltok"))

According to apt-file, xmltok is in emacs25-el and should be already
installed:

emacs25-common: /usr/share/emacs/25.1/lisp/nxml/xmltok.elc
emacs25-el: /usr/share/emacs/25.1/lisp/nxml/xmltok.el.gz

Cheers,
Remy


On Fri, Aug 11, 2017 at 3:41 AM, Mark Fletcher  wrote:

> On Thu, Aug 10, 2017 at 06:37:41PM +0200, Rémy Noulin wrote:
> > On a freshly installed debian 9.1, apt-get fails to install xemacs due to
> > some compilation related to erlang, here is the interesting part of log:
> >
> > Compiling /usr/share/xemacs21/site-lisp/erlang/erldoc.el...
> > While compiling toplevel forms in file
> > /usr/share/xemacs21/site-lisp/erlang/erldoc.el:
> >   !! File error (("Cannot open load file" "cl-lib"))
> > >>Error occurred processing erldoc.el: Cannot open load file: cl-lib
> >
> > Compiling /usr/share/xemacs21/site-lisp/erlang/path.el...
> > Wrote /usr/share/xemacs21/site-lisp/erlang/path.elc
> > Done
> > ERROR: install script from erlang-mode package failed
> > dpkg: error processing package xemacs21-mule (--configure):
> >  subprocess installed post-installation script returned error exit
> status 1
> > dpkg: dependency problems prevent configuration of xemacs21:
> >  xemacs21 depends on xemacs21-mule (>= 21.4.24-4) |
> xemacs21-mule-canna-wnn
> > (>= 21.4.24-4) | xemacs21-nomule (>= 21.4.24-4); however:
> >   Package xemacs21-mule is not configured yet.
> >   Package xemacs21-mule-canna-wnn is not installed.
> >   Package xemacs21-nomule is not installed.
> >
> > dpkg: error processing package xemacs21 (--configure):
> >  dependency problems - leaving unconfigured
> > Errors were encountered while processing:
> >  xemacs21-mule
> >  xemacs21
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> >
>
> OK so it looks like it can't complete the build because the cl-lib
> component it needs is missing.
>
> A good guess would be that this file is in another package that isn't
> installed, that the package for xemacs assumes will be installed but
> which isn't in its dependencies. That would arguably be a bug, but even
> if it is a bug that doesn't help you much, you still need to navigate
> out of the situation you are in.
>
> So here's how to determine where that cl-lib component is:
>
> 1. Install apt-file if you don't have it already.
> 2. sudo apt-file update
> 
> 3. apt-file search cl-lib
>
> On my system the 3rd command produces:
>
> aolserver4-doc: /usr/share/doc/aolserver4-doc/
> html/devel/tcl/tcl-libraries.html
> emacs24-common: /usr/share/emacs/24.5/lisp/emacs-lisp/cl-lib.elc
> emacs24-el: /usr/share/emacs/24.5/lisp/emacs-lisp/cl-lib.el.gz
> emacs25-common: /usr/share/emacs/25.1/lisp/emacs-lisp/cl-lib.elc
> emacs25-el: /usr/share/emacs/25.1/lisp/emacs-lisp/cl-lib.el.gz
> maxima-src: /usr/share/maxima/5.38.1/src/numerical/f2cl-lib.lisp
>
> aolserver4-doc and maxima-src are probably red herrings. You need one or
> more of emacs2{4,5}-{common,el} installed. I _think_ you are going to
> want to go either with the -24 or -25 series, not both, and if you held
> a gun to my head I would say it's probably the -el package rather than
> the -common package that you need, but that could easily be wrong. See
> which ones are not already installed on your system -- something that's
> already there isn't the missing package! :)
>
> Hope that helps.
>
> Mark
>
>

Re: Why debian put ~/bin beginning of $PATH

[Byung-Hee HWANG (황병희, 黃炳熙)]

> Why put ~/bin beginning ?

2 weeks ago, i installed new Ruby. At that time it was proper to me. By
the Debian rule, users can test new program. Yes i think in positive. 

Sincerely,

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

Re: delay the start of a service until LACP negotiation is complete

[John Ratliff]

> John Ratliff  wrote:
>
>> I have a 4 port LAGG (LACP / bond-mode 4) interface named bond0. It
>> seems
>> to take about 45 seconds after the links come up to negotiate with the
>> switch.
>
> This long delay is not normal. For me LACP-based bonds never take longer
> than 1 or at most 2 seconds to be operational.
>
> This smells of STP. Disable STP on the switch for that port or change to
> rSTP.
>
> Grüße,
> Sven.
>
> --
> Sigmentation fault. Core dumped.
>
>

The ports are trunk ports carrying multiple vlans. I have enabled
spanning-tree portfast trunk on the port channel. It still takes around 5
seconds, but that's significantly faster. However, I have another slight
issue. When conntrackd is started on boot, it gives me some errors:

Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [notice] using user-space event filtering
Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [notice] netlink event socket buffer size has been set to
262142 bytes
Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [notice] initialization completed
Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [notice] -- starting in console mode --
Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [ERROR] no dedicated links available!

I don't get these errors if I run my delay script. I wonder if this is a
problem.

Thanks.

--John

Re: sieve - "malformed email address"es - space at EOL?

[Zenaan Harkness]

On Fri, Aug 11, 2017 at 08:20:02AM -0500, David Wright wrote:
> On Fri 11 Aug 2017 at 21:41:02 (+1000), Zenaan Harkness wrote:
> > On Fri, Aug 11, 2017 at 11:03:20AM +0100, Darac Marjal wrote:
> > > On Fri, Aug 11, 2017 at 01:14:21PM +1000, Zenaan Harkness wrote:
> > > > Any sieve gurus?
> > > > 
> > > > (YES, I finally made it off of procmail, and sieve is AWEsome in
> > > > comparison - oh happy days :)
> > > > 
> > > > So two sieve failures (dodgy incoming emails got through gmail)
> > > > exposed themselves in relation to sieve in the last few days as
> > > > follows:
> > > > 
> > > > 
> > > > 1)
> > > > The first is simply a "superfluous" space char at the end of the line
> > > > on the "From:" line, as follows (ignore leading spaces):
> > > > 
> > > >   From: "EFA" ⋅
> > > > 
> > > > Note the deceptively cheeky little space char at the end of the line
> > > > - and yes, either EFA or some middle man has a dodgy MUA/ mail
> > > > processing agent.
> > > > 
> > > > QUESTION:
> > > > Why is a single space at this EOL, so malformed as to cause sieve to
> > > > spit the dummy with an error?
> > > 
> > > According to RFC5322 (which obsoleted RFC2822, which obsoleted RFC822), 
> > > the from field is defined as:
> > > 
> > >   from=   "From:" mailbox-list CRLF
> > >   mailbox-list=   (mailbox *("," mailbox)) / obs-mbox-list
> > >   mailbox =   name-addr / addr-spec
> > >   name-addr   =   [display-name] angle-addr
> > >   angle-addr  =   [CFWS] "<" addr-spec ">" [CFWS] /
> > >   obs-angle-addr
> > >   obs-mbox-list   =   *([CFWS] ",") mailbox *("," [mailbox / CFWS])
> > > 
> > > (addr-spec is an email address). So, the simplest parsing of that line is 
> > > as a single mailbox where display-name is
> > > EFA (That is, display-name is actually ' "EFA" ', but the spaces are 
> > > optional whitespace within the quoted-string and
> > > the quotes delimit the content), and the remainder is an angle-addr. 
> > > Angle-addr DOES, as you can see, allow for CFWS
> > > (Comment and/or Folding White Space) after the closing angle bracket.
> > > 
> > > So, I would say that the From header *is* RFC compliant and you should 
> > > consider raising a bug.
> > 
> > Thank you.
> > 
> > That's "fully guru, man, fully guru!" :D
> 
> I'm having a little difficulty following this conversation,
> particularly the bit about a "deceptively cheeky little space char".
> I don't see a space at the end, but this character "⋅", ie
> 
> Character   ⋅
> Character nameDOT OPERATOR
> Hex code point22C5
> Decimal code point8901
> Hex UTF-8 bytes   E2 8B 85
> Octal UTF-8 bytes 342 213 205
> UTF-8 bytes as Latin-1 characters bytes   â <8B> <85> 
> 
> so I have to ask whether you're reading this line in a font that is
> lacking this character or makes it too small to see. I'm reading and
> replying variously in neep, hack and h16 (all of these are monospace)
> which all show it clearly as a centred dot (not easily distinguishable
> from MIDDLE DOT, code point 00b7).

Ah yes, that would be from mutt - displaying such chars as dots.

Sorry about that.

In my incoming-email file it's actually a space.

Re: sieve - "malformed email address"es - space at EOL?

[David Wright]

On Fri 11 Aug 2017 at 21:41:02 (+1000), Zenaan Harkness wrote:
> On Fri, Aug 11, 2017 at 11:03:20AM +0100, Darac Marjal wrote:
> > On Fri, Aug 11, 2017 at 01:14:21PM +1000, Zenaan Harkness wrote:
> > > Any sieve gurus?
> > > 
> > > (YES, I finally made it off of procmail, and sieve is AWEsome in
> > > comparison - oh happy days :)
> > > 
> > > So two sieve failures (dodgy incoming emails got through gmail)
> > > exposed themselves in relation to sieve in the last few days as
> > > follows:
> > > 
> > > 
> > > 1)
> > > The first is simply a "superfluous" space char at the end of the line
> > > on the "From:" line, as follows (ignore leading spaces):
> > > 
> > >   From: "EFA" ⋅
> > > 
> > > Note the deceptively cheeky little space char at the end of the line
> > > - and yes, either EFA or some middle man has a dodgy MUA/ mail
> > > processing agent.
> > > 
> > > QUESTION:
> > > Why is a single space at this EOL, so malformed as to cause sieve to
> > > spit the dummy with an error?
> > 
> > According to RFC5322 (which obsoleted RFC2822, which obsoleted RFC822), the 
> > from field is defined as:
> > 
> >   from=   "From:" mailbox-list CRLF
> >   mailbox-list=   (mailbox *("," mailbox)) / obs-mbox-list
> >   mailbox =   name-addr / addr-spec
> >   name-addr   =   [display-name] angle-addr
> >   angle-addr  =   [CFWS] "<" addr-spec ">" [CFWS] /
> >   obs-angle-addr
> >   obs-mbox-list   =   *([CFWS] ",") mailbox *("," [mailbox / CFWS])
> > 
> > (addr-spec is an email address). So, the simplest parsing of that line is 
> > as a single mailbox where display-name is
> > EFA (That is, display-name is actually ' "EFA" ', but the spaces are 
> > optional whitespace within the quoted-string and
> > the quotes delimit the content), and the remainder is an angle-addr. 
> > Angle-addr DOES, as you can see, allow for CFWS
> > (Comment and/or Folding White Space) after the closing angle bracket.
> > 
> > So, I would say that the From header *is* RFC compliant and you should 
> > consider raising a bug.
> 
> Thank you.
> 
> That's "fully guru, man, fully guru!" :D

I'm having a little difficulty following this conversation,
particularly the bit about a "deceptively cheeky little space char".
I don't see a space at the end, but this character "⋅", ie

Character   ⋅
Character name  DOT OPERATOR
Hex code point  22C5
Decimal code point  8901
Hex UTF-8 bytes E2 8B 85
Octal UTF-8 bytes   342 213 205
UTF-8 bytes as Latin-1 characters bytes â <8B> <85> 

so I have to ask whether you're reading this line in a font that is
lacking this character or makes it too small to see. I'm reading and
replying variously in neep, hack and h16 (all of these are monospace)
which all show it clearly as a centred dot (not easily distinguishable
from MIDDLE DOT, code point 00b7).

Cheers,
David.

Re: Thunderbird almost unusable after upgrade

[Jape Person]

On 08/10/2017 10:40 AM, Sven Joachim wrote:

On 2017-08-10 10:24 -0400, Jape Person wrote:


After this upgrade

thunderbird:amd64 (1:52.2.1-4, 1:52.2.1-4+b1)

Thunderbird in Cinnamon DE is almost completely useless because 
portions of its windows / text / toolbars don't repaint until the 
window is resized. Is anyone else seeing this?


Yes, see https://bugs.debian.org/871629.

Using different desktop themes or logging in as a different user 
results in same behavior.


I'm curious to know whether this is being seen in different
desktop environments, too.


This is independent of the desktop environment.

Cheers, Sven




Thanks, Sven.

Ugh! What a nasty set of behaviors!

Makes me "pine" for "mutt".

;-)

Re: Debian 9.1 amd64 Xfce panel clock broken

[John Ratliff]

> On Wed, Aug 09, 2017 at 05:13:55PM -0700, David Christensen wrote:
>> Time Settings
>>   Timezone   PST8PDT
>> Appearance
>>   Layout Digital
>>   Tooltip format Wednesday 09 August 2017
>> Clock Options
>>   Format 05:04:55 PM
>>
>> Once I have made the above settings, but before choosing "Close", the
>> current time is displayed at the proper location in the Xfce panel. This
>> is
>> what I want.
>>
>> - But when I click "Close", the current time disappears from the panel
>> --
>> e.g. Clock breaks.
>
> Does the space for the clock disappear, or go blank?
>
> If it's going blank, I suggest you look at color settings for
> the clock -- you may have accidentally selected 100% transparent
> text, or the same color as the background.
>
> -dsr-
>
>

This is a known bug in the clock applet for Xfce. Last I checked the bug
tracker upstream, it hadn't been fixed. I have the same issue. You can't
adjust the clock settings without it erasing your format string and making
the clock blank. My workaround is to use the orange date/time panel item
instead.

--John

Re: sieve - "malformed email address"es - space at EOL?

[Zenaan Harkness]

On Fri, Aug 11, 2017 at 11:03:20AM +0100, Darac Marjal wrote:
> On Fri, Aug 11, 2017 at 01:14:21PM +1000, Zenaan Harkness wrote:
> > Any sieve gurus?
> > 
> > (YES, I finally made it off of procmail, and sieve is AWEsome in
> > comparison - oh happy days :)
> > 
> > So two sieve failures (dodgy incoming emails got through gmail)
> > exposed themselves in relation to sieve in the last few days as
> > follows:
> > 
> > 
> > 1)
> > The first is simply a "superfluous" space char at the end of the line
> > on the "From:" line, as follows (ignore leading spaces):
> > 
> >   From: "EFA" ⋅
> > 
> > Note the deceptively cheeky little space char at the end of the line
> > - and yes, either EFA or some middle man has a dodgy MUA/ mail
> > processing agent.
> > 
> > QUESTION:
> > Why is a single space at this EOL, so malformed as to cause sieve to
> > spit the dummy with an error?
> 
> According to RFC5322 (which obsoleted RFC2822, which obsoleted RFC822), the 
> from field is defined as:
> 
>   from=   "From:" mailbox-list CRLF
>   mailbox-list=   (mailbox *("," mailbox)) / obs-mbox-list
>   mailbox =   name-addr / addr-spec
>   name-addr   =   [display-name] angle-addr
>   angle-addr  =   [CFWS] "<" addr-spec ">" [CFWS] /
>   obs-angle-addr
>   obs-mbox-list   =   *([CFWS] ",") mailbox *("," [mailbox / CFWS])
> 
> (addr-spec is an email address). So, the simplest parsing of that line is as 
> a single mailbox where display-name is
> EFA (That is, display-name is actually ' "EFA" ', but the spaces are optional 
> whitespace within the quoted-string and
> the quotes delimit the content), and the remainder is an angle-addr. 
> Angle-addr DOES, as you can see, allow for CFWS
> (Comment and/or Folding White Space) after the closing angle bracket.
> 
> So, I would say that the From header *is* RFC compliant and you should 
> consider raising a bug.

Thank you.

That's "fully guru, man, fully guru!" :D


> > 2)
> > The dodgiest "To:" line I have literally ever seen, as follows:
> > 
> > To: 
> > 
> > Notice the colon, AND the semi colon, in this "email address".
> 
> This is allowed by RFC 6854 (March 2013), which updates RFC5322 to allow 
> "Group Syntax" in the From and Sender fields.
> RFC5322 already allowed group syntax in To, Cc, BCc etc fields. Groups 
> consist of:
> 
>   group   =   display-name ":" [group-list] ";" [CFWS]
>   group-list  =   mailbox-list / CFWS / obs-group-list
> 
> In other words, they consist of a display name, then a colon, then a list of 
> mailboxes and a final semi-colon. The
> list of mailboxes is optional, so here we have a group called 
> "Undisclosed-Recipient" with no members. Or, in other
> words, this message is not addressed to anybody (it's probably been 
> blind-copied to others, though).
> 
> RFC 6854, in allowing group syntax in the From Field allows one to say "This 
> message is not from anyone" or "This
> message is from a group of authors" and, in theory, should mean that no-one 
> needs to use "nore...@example.org" or
> "direct...@example.com" as a From address.

Sounds like I'm running an implementation of sieve which is a bit
behind the times.

> > Again gmail passed it right through.
> > 
> > I can actually accept this failure of sieve to pass the email through
> > - such an addy is indeed rather egregious.
> > 
> > BUT, it would be nice to have sieve actuallly OUTPUT the actual
> > problematic email address, and to this end, does anyone know some
> > magical incantation to add to sieve, so I can see all problematic
> > (and only the problematic) lines of incoming emails, as "error
> > output" by sieve to the cmd line?
> 
> This depends on your implementation of sieve. Dovecot's implementation, 
> Pigeonhole, will log to ~/.dovecot.sieve.log
> by default.

Hmm. Gnu mailutils. Seems it's a little out of date with the RFCs,
failing to e.g. detect "Undisclosed-Recipient:;" AND balking on a
harmless space char ... perhaps it's designed to only work well
assuming some other mailutils pre-processing.

Oh well, try dovecot-sieve it is.

Thank you very much.


> -- 
> For more information, please reread.

:) - Great .sig

Re: screenlock lock trops bien - stretch-

[Benoit B]

Idem j'utilise LXDE, j'ai désinstallé lxlock et light-locker (comme
j'hésitais entre les deux)...
apt-get remove...
J'ai aussi enlevé le bouton de lxpanel.
--
Benoit


Le 9 août 2017 à 11:56, Gabriel Santonja  a écrit :
> Bonjour,
> Je viens de migrer sur stretch a partir de jessie.
> Je tourne sur LXDE et quand je locke le pc avec  screenlock impossible de
> sortir de l'ecran noir
> le seul moyen de revenir sur la session est de repasser sur tty1 (ctrl - alt
> - f1) qui est maintenant l ecran de login gdm3.
>
> Auriez vous une idée je seche ...
> Merci

Re: Virtualbox for stretch and buster not in repos

[Hans]

Sorry, I just forgot about Oracle policy terms. Yes, you are right and I am 
wrong. 

Best

Hans

> Short Answer: Because of Oracle.
> 
> Longer Answer: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794466
> 
> Summary: Virtualbox will at the current state of affairs never be in
> Testing or any stable release or stable-backports ever again.
> 
> Grüße,
> Sven.

Re: Virtualbox for stretch and buster not in repos

[Sven Hartge]

Robert Menes  wrote:

> Is there a reason why virtualbox hasn't migrated into stretch or
> buster yet? 

Short Answer: Because of Oracle.

Longer Answer: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794466

Summary: Virtualbox will at the current state of affairs never be in
Testing or any stable release or stable-backports ever again.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Virtualbox for stretch and buster not in repos

[Hans]

Am Freitag, 11. August 2017, 07:08:41 CEST schrieb Robert Menes:
Did you install the virtualbox-dkms package?

If yes, did it build?

If yes, can you modprobe virtualbox?

If everything fails, try kvm and aqemu as a substitute.

Best

Hans
> Hi all,
> 
> On my home desktop, I'm running Debian on the testing channel (currently
> at "buster"). A recent apt-get upgrade appears to have broken or removed
> a few vital virtualbox packages, including virtualbox-dkms.
> 
> Launching any VM in virtualbox throws this error message:
> 
> [error]
> 
> The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there
> is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms
> package and load the kernel module by executing
> 
> 'modprobe vboxdrv'
> 
> as root.
> 
> where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The
> support driver is not installed. On linux, open returned ENOENT.
> 
> [/error]
> 
> Running modprobe as the error message suggests, though, gives me:
> 
> modprobe: FATAL: Module vboxdrv not found in directory
> /lib/modules/4.11.0-1-amd64
> 
> Current I'm running the 4.11.0-1-amd64 kernel, but can easily boot and run
> a 4.9 kernel (which is the last good working kernel I have).
> 
> apt-cache search on my desktop doesn't bring up results for any virtualbox
> package, except for 'virtualbox-guest-additions-iso'.
> 
> Is there a reason why virtualbox hasn't migrated into stretch or buster
> yet? While only a minor inconvenience of having to boot with another
> kernel, I would like to have the newer packages available for a consistent
> upgrade.
> 
> Thanks, all.
> 
> --Robert

Virtualbox for stretch and buster not in repos

[Robert Menes]

Hi all,

On my home desktop, I'm running Debian on the testing channel (currently
at "buster"). A recent apt-get upgrade appears to have broken or removed
a few vital virtualbox packages, including virtualbox-dkms.

Launching any VM in virtualbox throws this error message:

[error]

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there
is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms
package and load the kernel module by executing

'modprobe vboxdrv'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The
support driver is not installed. On linux, open returned ENOENT.

[/error]

Running modprobe as the error message suggests, though, gives me:

modprobe: FATAL: Module vboxdrv not found in directory
/lib/modules/4.11.0-1-amd64

Current I'm running the 4.11.0-1-amd64 kernel, but can easily boot and run
a 4.9 kernel (which is the last good working kernel I have).

apt-cache search on my desktop doesn't bring up results for any virtualbox
package, except for 'virtualbox-guest-additions-iso'.

Is there a reason why virtualbox hasn't migrated into stretch or buster
yet? While only a minor inconvenience of having to boot with another
kernel, I would like to have the newer packages available for a consistent
upgrade.

Thanks, all.

--Robert
-- 
Nobody's ever lost in life...they're merely taking the scenic route.
==
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
==
-BEGIN GEEK CODE BLOCK-
Version: 3.1.2
GCS/S/M/MU d- s+: a38 C++(+++) UL>$ P++ L+++ E+ W+ N+ o+ K++ w--- O-
M !V PS+ PE Y+ PGP(+) t+ 5++ X++ R tv b+++ DI+++ D++(---) G++ e+ h-
r++ y+
--END GEEK CODE BLOCK--

Re: Debian meetup on Aug 16th in Stockholm?

[Luna Jernberg]

Signed up and will try to show up, however a bit sick now but there is
still a couple of days left so i hope i will feel better for the
Debian Day :)

On 8/8/17, Helio Loureiro  wrote:
> Don't worry too much.  For locals at the company, it is just a show up :)
>
> Abs,
> Helio Loureiro
> http://helio.loureiro.eng.br
> https://se.linkedin.com/in/helioloureiro
> http://twitter.com/helioloureiro
>
>
> 2017-08-07 23:11 GMT+02:00 Martin Schöön :
>
>> Den 2017-08-07 skrev Helio Loureiro :
>> > Hi,
>> >
>> > I booked a room here.  I'm trying to get some snacks and beverages
>> > sponsored by company as well.
>> >
>> > Debian day at Ericsson
>> > August 16th - Wednesday
>> > 16:00 to 18:00
>> > Gr=C3=B6nlandsgatan 31
>> > Room Stratus
>> > Kista
>>
>> Noted. I hope I am still on vacation but if I am back in the
>> salt mines of Kista and the weather is not too good...
>>
>> >
>> > Please subscribe to attend so, in case I get the sponsorship, I can
>> > dimension the food.  At the least I can guarantee the coffee :)
>> >
>> > https://goo.gl/forms/t395Q5agCciDDbDR2
>>
>> Is it possible to sign up 'tentatively'? I'll give it a try.
>>
>> >
>> > I plan to present a quick workshop about debian packaging (~1h).  It
>> would
>> > be nice if more people could bring more talks.
>>
>> I am just a useless but happy user...
>>
>> /Martin
>>
>>
>

Re: Debian 9.1 amd64 Xfce panel clock broken

[Dan Ritter]

On Wed, Aug 09, 2017 at 05:13:55PM -0700, David Christensen wrote:
> Time Settings
>   TimezonePST8PDT
> Appearance
>   Layout  Digital
>   Tooltip format  Wednesday 09 August 2017
> Clock Options
>   Format  05:04:55 PM
> 
> Once I have made the above settings, but before choosing "Close", the
> current time is displayed at the proper location in the Xfce panel. This is
> what I want.
> 
> - But when I click "Close", the current time disappears from the panel --
> e.g. Clock breaks.

Does the space for the clock disappear, or go blank?

If it's going blank, I suggest you look at color settings for
the clock -- you may have accidentally selected 100% transparent
text, or the same color as the background.

-dsr-

Re: Firefox-Esr version 52.3.0

[andre_debian]

On Thursday 10 August 2017 22:33:39 Pierre L. wrote:
> Tu peux tenter en les réactivant 1 à 1, l'un après l'autre, et trouver
> ainsi le fautif ;)
> (bouton du menu "Redémarrer modules désactivés")
> J'ai souvenir d'un plugin qui parlait de problème de compatibilité avec
> les futures versions de FF, à voir...
> il doit certainement y avoir un plugin/addon qui t'embistrouille ? 

Hello,

J'ai beau désactivé plugins et modules, j'ai toujours ces messages d'erreur :

(/home/andre/firefox-esr/plugin-container:3801): GLib-GObject-CRITICAL **: 
g_object_ref: assertion 'object->ref_count > 0' failed

Merci,

andré

Re: sieve - "malformed email address"es - space at EOL?

[Darac Marjal]

On Fri, Aug 11, 2017 at 01:14:21PM +1000, Zenaan Harkness wrote:

Any sieve gurus?

(YES, I finally made it off of procmail, and sieve is AWEsome in
comparison - oh happy days :)

So two sieve failures (dodgy incoming emails got through gmail)
exposed themselves in relation to sieve in the last few days as
follows:


1)
The first is simply a "superfluous" space char at the end of the line
on the "From:" line, as follows (ignore leading spaces):

  From: "EFA" ⋅

Note the deceptively cheeky little space char at the end of the line
- and yes, either EFA or some middle man has a dodgy MUA/ mail
processing agent.

QUESTION:
Why is a single space at this EOL, so malformed as to cause sieve to
spit the dummy with an error?


According to RFC5322 (which obsoleted RFC2822, which obsoleted RFC822), 
the from field is defined as:


  from=   "From:" mailbox-list CRLF
  mailbox-list=   (mailbox *("," mailbox)) / obs-mbox-list
  mailbox =   name-addr / addr-spec
  name-addr   =   [display-name] angle-addr
  angle-addr  =   [CFWS] "<" addr-spec ">" [CFWS] /
  obs-angle-addr
  obs-mbox-list   =   *([CFWS] ",") mailbox *("," [mailbox / CFWS])

(addr-spec is an email address). So, the simplest parsing of that line 
is as a single mailbox where display-name is EFA (That is, display-name 
is actually ' "EFA" ', but the spaces are optional whitespace within the 
quoted-string and the quotes delimit the content), and the remainder is 
an angle-addr. Angle-addr DOES, as you can see, allow for CFWS (Comment 
and/or Folding White Space) after the closing angle bracket.


So, I would say that the From header *is* RFC compliant and you should 
consider raising a bug.





2)
The dodgiest "To:" line I have literally ever seen, as follows:

To: 

Notice the colon, AND the semi colon, in this "email address".


This is allowed by RFC 6854 (March 2013), which updates RFC5322 to allow 
"Group Syntax" in the From and Sender fields. RFC5322 already allowed 
group syntax in To, Cc, BCc etc fields. Groups consist of:


  group   =   display-name ":" [group-list] ";" [CFWS]
  group-list  =   mailbox-list / CFWS / obs-group-list

In other words, they consist of a display name, then a colon, then a 
list of mailboxes and a final semi-colon. The list of mailboxes is 
optional, so here we have a group called "Undisclosed-Recipient" with no 
members. Or, in other words, this message is not addressed to anybody 
(it's probably been blind-copied to others, though).


RFC 6854, in allowing group syntax in the From Field allows one to say 
"This message is not from anyone" or "This message is from a group of 
authors" and, in theory, should mean that no-one needs to use 
"nore...@example.org" or "direct...@example.com" as a From address.




Again gmail passed it right through.

I can actually accept this failure of sieve to pass the email through
- such an addy is indeed rather egregious.

BUT, it would be nice to have sieve actuallly OUTPUT the actual
problematic email address, and to this end, does anyone know some
magical incantation to add to sieve, so I can see all problematic
(and only the problematic) lines of incoming emails, as "error
output" by sieve to the cmd line?


This depends on your implementation of sieve. Dovecot's implementation, 
Pigeonhole, will log to ~/.dovecot.sieve.log by default. 



Manually reducing the lines being processed by sieve, running sieve
each time, till I finally figured out exactly which lines of which
emails is causing the problem, is quite the biatch TBH :)


TIA,
Zen



--
For more information, please reread.


signature.asc
Description: PGP signature

Re: CUPS

[Benoit B]

Oui j'y suis parvenu tout récemment en essayant les pilotes de CUPS un
par un avec différents config possible.

Et c'est finalement le pilote Brother HL-2030 Foomatic/hl1250 qui est
parvenu à imprimer une page.

Et ne ne suis pas parvenu à faire fonctionner le pilote
CUPS+Gutenprint V5.2.11 qui était utilisé avant le passage a
stretch...

Mais finalement j'ai essayé tellement de choses au hasard que je ne
suis pas sûr de la cause exacte...
Si je remet le CUPS+Gutenprint V5.2.11, ça ne fonctionne plus, voila
la seule chose reproductible. Désolé de ne pas pouvoir apporter
quelque chose de constructif.

Bonne journée

--
Benoit


Le 8 août 2017 à 14:30, Pierre L.  a écrit :
> Salut,
>
> Petite remontée de sujet... pardonnez... mais il me semble que le
> problème n'est toujours pas résolu, et je viens apporter mon petit grain
> de sel ! (faut dire que je n'avais pas encore pris le temps de
> rebrancher cette imprimante!)
>
> Idem ici, Brother HL2030 qui fonctionne bien, quand elle n'est pas
> raciste avec les pingouins...
>
> Installation très simple : Partagée par un Raspbian 8 Jessie à jour, sur
> le LAN, via CUPS :
> - page de test depuis l'interface CUPS https, ca clignote un coup, ca
> réveille l'engin, pas d'impression :'(
> - client Debian 9 Stretch (upgradé depuis 8), idem, pas d'impression :'(
> - client Debian 8 Jessie, pas d'impression :'(
> - client Win7, ca imprime !
>
> Donc l'analyse du noob en la matière, c'est que vu qu'un Win7 est le
> seul capable d'imprimer correctement vers le CUPS de la Raspbian, c'est
> que ca vient de Debian (coté client) qui est complètement dans les choux
> avec cette imprimante...
>
> Sinon ca a avancé de ton coté Benoît ? Des news depuis ?
> Ca sent le gros sale bug debianesque !
>
>
>
>> Bonjour à tous,
>>
>> Depuis la mise à jour vers stretch, mon imprimante, ne réagit plus
>> quand je lui envois une tâche.
>>
>> Rien dans page_log, ni dans error_log.
>> Seulement dans access_log
>> localhost - - [29/Jun/2017:14:10:54 +0200] "POST
>> /printers/Brother-HL-2030-series HTTP/1.1" 200 398 Print-Job
>> successful-ok
>>
>>
>> Description:Brother HL-2030 series Location:mars Driver:Brother
>> HL-2035 Foomatic/hl1250 (recommended) (grayscale)
>> Connection:usb://Brother/HL-2030%20series?serial=A7J883842
>> Defaults:job-sheets=none, none media=iso_a4_210x297mm sides=one-side
>>
>> J'ai supprimé et recréé dans cups rien n'y fait.
>>
>> Comment diagnostiquer ?
>>
>> Merci d'avance.
>>
>> --
>> Benoit
>>
>
>

Re: delay the start of a service until LACP negotiation is complete

[Sven Hartge]

John Ratliff  wrote:

> I have a 4 port LAGG (LACP / bond-mode 4) interface named bond0. It seems
> to take about 45 seconds after the links come up to negotiate with the
> switch.

This long delay is not normal. For me LACP-based bonds never take longer
than 1 or at most 2 seconds to be operational.

This smells of STP. Disable STP on the switch for that port or change to
rSTP.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Big problem computer not booting

[Fungi4All]

From: field.engin...@gmail.com

> To: debian-user@lists.debian.org
>
> On 08/10/2017 12:00 PM, kelsang sherab wrote:
>> I run Debian stretch on MacBook Air
>>
>> I did a restore backup from previous system[debian Jessie ]
>>
>> Now machine is not booting
>>
>> upon boot the machine gives the normal GRUB menu:
>> Debian GNU/Linux
>> Advanced options for Debian GNU/linux
>>
>> Click the 1st one
>>
>> saying
>> Loading etc
>> Loading initial ram disk
>>
>> then a list of checks
>>
>> [ 0.049346] DMAR-IR:[Firmware Bug] : ioapic 2 has no mappin iommu,
>> interrupt remapping will be disabled
>> /dev/sda2: clean, 348430/7118848 files, 7186186/28466432 blocks
>> [ 3.895353] sd 6:0:0:0: [sdb] No Caching mode page found
>> [ 3.895361] sd 6:0:0:0: [sdb] Assuming drive cache: write trhough
>> [FAILED] Failed to start Network Manager Wait Online.
>> See "systemctl status NetwrokManager-wait-online.service" for details.
>> then a list of things starting all [OK]
>>
>> and then nothing happens
>>
>> Switching the machine off and re-starting it into the advance option i
>> get some root access and i see al my files.I am not able to connect to the 
>> internet
>> When trying to do something like apt-get update
>> the system returns that a shared library libapt-pkg.so.4.12 is not
>> installed.
>> but I have no internet access so I cannot either find the lib or install
>> it. And so I cannot update the system and it feels like a catch 22
>> I could really do with some help
>
> I don"t know, but maybe I can help with the network, do an "#ifconfig
> -a" to get the name of your interface and then "#ifconfig
> (name-of-interface) up" and see if that helps get things going.

I suspect this has to do with the settings of systemd trying to bring a
functional network up before it completes the sequence, but as it is
set to give up at a point it finds yet a different place to get stuck.
I remember a while I had found where to set the time limit but didn't
record the find and while on wifi I have to deal with this delayed booting
myself.
But, on the above problem out of curiosity I found this piece that may
be helpful.  https://ubuntuforums.org/showthread.php?t=2254677
It seems on such machines the interrupts get all twisted and tangled
up.  Quote from the link:
"The ivrs table is wrong, it points to non existant IOAPIC[0] and IOAPIC[255], 
so to override this i use this commandline in grub:
ivrs_ioapic[7]=00:14.0 ivrs_ioapic[8]=00:00.1."

plasma-discover (packagekit) and apt-listchanges integration

[Felipe Salvador]

Hi list,
when I see update notifications I use apt-get to update the
system, in this way a get news and changelogs via email by apt-listchanges.

Is there a mode to get news and changelogs using plasma-discover (kde
update manager) when you perform an update?

Debian GNU/Linux 9.1 (stretch) 

Regards 
-- 
Felipe Salvador

module not loading on startup

[Gary Dale]

I'm running Stretch.

I had to replace/upgrade the motherboard on one of my computers. While 
that went fairly smoothly, I lost the network. Since the new motherboard 
had an RTL8168 NIC, I stupidly tried Realtek's module. Not my best plan.  :(


I eventually tracked the problem down to a UDEV persistent rule (now 
deleted) and also the need to modify /etc/network/interfaces to use the 
name the name of the new NIC (enp5s0 instead of eth0 - since it wasn't 
carried over in the upgrade from Jessie). However because I installed 
the Realtek module, the r8169 kernel module isn't automatically loading.


I deleted the r8168 module and renamed the r8169.bak to r8169.ko, 
updated the initramfs and even reinstalled the 4.9 kernel but the r8169 
module still need to loaded manually after boot, requiring the NIC to be 
brought up manually as well.


I realize I can just add the module to /etc/modules but that's not very 
elegant and the hardware probe should be able to load it like it used to 
before I screwed it up. Any ideas on how I can fix my mistake?