Re: Libreoffice mail merge not working

[Paolo Cavallini]

Il 14/05/2016 00:28, Rodary Jacques ha scritto:

> Try convert your docs in .doc (not readable in recent MsOffice), .docx
> (not readable in old MsOffice :-) )or better in pdf, where the p stands
> for portable, remember. Or best learn LaTex to generate wonderful PDF docs.

Bonjour Jacques,
thanks for your reply. However, I'm missing your point: I need to do a
series of pdf from a Libreoffice doc, based on a db table, and I suspect
this function is broken in Debian Sid. How converting to something else
could help?
All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html

Re: emacs menu line disappeared

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, May 14, 2016 at 06:16:54AM +0200, Kjetil brinchmann Halvorsen wrote:
> Thanks, did, its in .emacs now, but has NO effect!

Hmm. No permanent effect -- or no effect at all?

What happens when you start your Emacs with the -Q command line option?
(this skips most custom and site-specific initialization).

Can you then change the toolbar visibility?

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

iEYEARECAAYFAlc2xDcACgkQBcgs9XrR2kZO5wCfdRqYWY86DYH28yw2AilOmZOC
7KIAn0fbU9QMnpB2U4dcA0JgNngIyrBQ
=zJLB
-END PGP SIGNATURE-

Re: Anytime I touch a print function, get error but it works

[cbannister]

On Fri, May 13, 2016 at 04:23:16PM -0400, Gene Heskett wrote:
> Fixed it right up, thank you very much, Curt.  Since it had to create 
> that path in /etc from scratch, is there a way to ask dpkg what provides 
> this file so that I can make the mental connection to something I have 
> installed recently?

Yes, I use:

dpkg -S /path/to/file/filename

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: Network manager (again)

[Hans]

Am Samstag, 14. Mai 2016, 05:27:06 schrieb Bhasker C V:

Hi,
try wicd (vicd-ncurses, wicd-gtk, wicd-cli). It may fit your needs. And you can 
have entries in /etc/network/interfaces, so you can be already connected 
without any window-manager.

Good luck!

Hans
> Hi
> 
>   I am finding it difficult to settle on a good network manager which
> can work for my case
> 
> 1. My home dir is luks/ext4 and mounted manually after logging in for
> the first time
> 2. My GUI is started after mounting my home dir and by manual startx only
> 
> I could never get my network manager to store passwords in the user dir.
> I do not like the passwords stored in
> /etc/NeworkManager/sytem-connections with plain passwords visible so
> anybody can open them if they have physical access to the machine/disk
> (usb live stick etc., )
> 
> If I pull up the properties of nm-applet and change the option to
> "Store password only for this user", nm-applet does not connect since
> the keyring is no automatically unlocked due to startx
> 
> Can anyone help me with fixing this network-manager so the passwords are
> stored per-user in my luks home rather than /etc/...  OR tell me how to
> enable nm-applet to automatically trigger opening gnome-keyring ?

Re: emacs menu line disappeared

[Kjetil brinchmann Halvorsen]

Thanks, did, its in .emacs now, but has NO effect!

Kjetil

On Fri, May 13, 2016 at 10:15 PM,  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, May 13, 2016 at 08:03:36PM +0200, Kjetil brinchmann Halvorsen
> wrote:
> > On one of the latest updates (I am running unstable+sid) emacs
> > is behaving strangely.  Usually it shows a menu line with large icons,
> now
> > there is only the titles with small fonts.  The menus work as before,
> > though. But the movement bars on the right have disappeared. And when I
> am<
> > opening a .tex file (auctex installed) the usual icons for running tex,
> > viewing errors, see the pdf, etc, disappeared. What happened?
>
> Perhaps some default changed. You can change it by issuing
>
>   M-x customize-variable RET tool-bar-mode RET
>
> Set it to "on" and either "apply changes" (to have the setting just for
> the current session) or "Apply and Save" to set permanently.
>
> HTH
> - -- tomás
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iEYEARECAAYFAlc2NeQACgkQBcgs9XrR2kYdjgCaAxJ3vqhTzyZs0RfxGdJ9AskG
> d+kAn0nNIYU1gEK3WxlOtFzxsNfeUN/x
> =DkjE
> -END PGP SIGNATURE-
>
>

Network manager (again)

[Bhasker C V]

Hi

  I am finding it difficult to settle on a good network manager which
can work for my case

1. My home dir is luks/ext4 and mounted manually after logging in for
the first time
2. My GUI is started after mounting my home dir and by manual startx only

I could never get my network manager to store passwords in the user dir.
I do not like the passwords stored in
/etc/NeworkManager/sytem-connections with plain passwords visible so
anybody can open them if they have physical access to the machine/disk
(usb live stick etc., )

If I pull up the properties of nm-applet and change the option to 
"Store password only for this user", nm-applet does not connect since
the keyring is no automatically unlocked due to startx

Can anyone help me with fixing this network-manager so the passwords are
stored per-user in my luks home rather than /etc/...  OR tell me how to
enable nm-applet to automatically trigger opening gnome-keyring ?

-- 
Bhasker C V
Secure Mails: 
http://pgp.mit.edu/pks/lookup?op=get&search=0x4D05FEEC54E47413
Registered Linux User: #306349 

-Re: configuring softwarecollections.org repository on debian jessie

[Rodary Jacques]

Le jeudi 12 mai 2016, 21:55:24 Liam O'Toole a écrit :
> On 2016-05-12, soko.tica  wrote:
> > --001a1146456672df2d0532a72b01
> > Content-Type: text/plain; charset=UTF-8
> > 
> > Hello list,
> > 
> > I need to install a package (php54) on a VM running debian jessie (Here is
> > why https://www.virtualmin.com/documentation/web/multiplephp ). I have
> > managed to install rhscl-php54-epel-6-x86_64-1-2.noarch.rpm through alien
> > package, but don't know how to isntall
> > php54 php54-php-mysqlnd. Repo rhscl isn't in /etc/apt/sources.list but in
> > /etc/yum.repos.d/ and I wasn't able to find php54 php54-php-mysqlnd. Any
> > help will be appreciated. Thanks in advance.
> 
> You are trying to install Red Hat packages on a Debian OS. What's more,
> you are tring to install packages from Red Hat Software Collections,
> which require manipulation of their environment to run properly. You'd
> be much better off doing that on a CentOS machine.
> 
> Otherwise, prepare to enter a world of pain. :)
If alien (which is a Debian software, isn't it) says you can, why not? 
You just need to 
be careful, trying a fake install first (dpkg --noinstall --no-act). I switched 
to Debian for that kind 
of safety, being tired to note all my changes and go back painfully afterwards. 
I remember 
(1998-99) when I installed gnome-0.nn ten times! But I can't live without 
BSD-games ( try "cal 
09 1752" (even MacOsX has it) and "pom 2712" it's unforgettable) nor without 
xanim to read 
old Quicktime CDs from an USB stick! I don't think Debian needs worship!
Jacques

Re: Anytime I touch a print function, get error but it works

[Gene Heskett]

On Friday 13 May 2016 17:46:22 Rodary Jacques wrote:

> Le vendredi 13 mai 2016, 10:01:53 Gene Heskett a écrit :
> > The system is wheezy, 32 bit except for the running kernel, all up
> > to date but with quite a few added packages as my interests are best
> > described as eclectic.
> >
> > The error is:
> > p11-kit: invalid config filename, will be ignored in the
> > future: /etc/pkcs11/modules/gnome-keyring-module
> >
> > There seems to be zero docs on this so called "p11-kit", but I can't
> > purge it without destroying the system.
> >
> > So it actually refers to /etc/pkcs11/modules/gnome-key-ring.
> >
> > Does this have a reason to exist, and if so, what the heck is it?
> >
> > And what dies if I blow it away by hand?
> >
> > Thanks.
> >
> > Cheers, Gene Heskett
>
> Have a look at https://p11-glue.freedesktop.org/p11-kit.html. Does it
> help? Jacques

Also, that is an outline for its reason to exist.  Comprehension begins.

Thanks Jacques.


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: update-rc.d creates unexpected sequence numbers

[Gene Heskett]

On Friday 13 May 2016 16:10:17 to...@tuxteam.de wrote:

> On Fri, May 13, 2016 at 03:35:29PM -0400, Gene Heskett wrote:
>
> [...]
>
> > But for the above comparison to work correctly, you (and everybody
> > responding to your message) would have to post the version number of
> > the parent package that held this file too.  No use comparing apples
> > to tangerines. :)
>
> Gene, you have me confused now. This is *exactly* what we did: we
> compared the version of the package containing update-rc.d and the
> program file's sha1sum. Both match.
>
> We still get different behaviours, thus there must be something
> different in the execution environment. At least we know now where
> *not* to look :-)
>
> regards
> -- tomás

Yes, I believe we are on the same page, so obviously there is something  
else gone aglay in the environment as you suggested.  You are I believe, 
making progress in discovering that, so I'll bow out and try not to 
confuse an issue about which I apparently know not well enough.

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: Anytime I touch a print function, get error but it works

[Gene Heskett]

On Friday 13 May 2016 13:13:08 to...@tuxteam.de wrote:

> On Fri, May 13, 2016 at 03:59:28PM +, Curt wrote:
>
> [...]
>
> >  Provides a way to load and enumerate PKCS#11 modules. Provides a
> >  standard configuration setup for installing PKCS#11 modules in such
> > a way that they're discoverable.
> >
> > Whatever that means.
>
> PKCS#11 is a standard interface [1] to cryptographic tokens (e.g.
> smartcards and its ilk).
>
> [1] https://en.wikipedia.org/wiki/PKCS_11

Interesting Tomas, thank you. Looks like the recent hulabalou with libssl 
may have created it.  But I haven't had a "smart card" plugged in in 
yonks.  My new brother mfc may have a smart card slot in the front panel 
though, which might pull that in.  It as several different slots, even a 
master end usb so maybe I could plug my Nikon camera in directly and 
print straight from it.  If I can get it to connect, the socket in the 
camera is getting flaky.
>
> regards
> -- t


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: Libreoffice mail merge not working

[Rodary Jacques]

Le vendredi 13 mai 2016, 08:31:55 Paolo Cavallini a écrit :
> Hi all,
> my Libreoffice fails to generate a series of document starting froma a
> template and a database. It used to work, but historically it has always
> been a fragile solution. For instance, I was never able to send the
> resulting document to a series of email addresses.
> I suspect this is due to Debian version using a different JVM from the
> official one (I assume if this would be an upstream issue this would
> have been noticed and probably fixed long ago).
> Is someone able to use this function?
> All the best, and thanks a lot.
Try convert your docs in .doc (not readable in recent MsOffice), .docx (not 
readable in old 
MsOffice :-) )or better in pdf, where the p stands for portable, remember. Or 
best learn LaTex 
to generate  wonderful PDF docs.
Regards
Jacques

Re: Anytime I touch a print function, get error but it works

[Rodary Jacques]

Le vendredi 13 mai 2016, 10:01:53 Gene Heskett a écrit :
> The system is wheezy, 32 bit except for the running kernel, all up to
> date but with quite a few added packages as my interests are best
> described as eclectic.
> 
> The error is:
> p11-kit: invalid config filename, will be ignored in the
> future: /etc/pkcs11/modules/gnome-keyring-module
> 
> There seems to be zero docs on this so called "p11-kit", but I can't
> purge it without destroying the system.
> 
> So it actually refers to /etc/pkcs11/modules/gnome-key-ring.
> 
> Does this have a reason to exist, and if so, what the heck is it?
> 
> And what dies if I blow it away by hand?
> 
> Thanks.
> 
> Cheers, Gene Heskett
Have a look at https://p11-glue.freedesktop.org/p11-kit.html. Does it help?
Jacques

Re: update-rc.d creates unexpected sequence numbers

[Michael Biebl]

Am 13.05.2016 um 16:16 schrieb CN:
> On Fri, May 13, 2016, at 09:14 PM, to...@tuxteam.de wrote:
>> Jessie/Sid here. But the more important thing is... what version of
>> sysv-rc is yours? What update-rc.d are you using?
>>
> 
> "dpkg -l sysv-rc" show this from local host:
> 
> ii sysv-rc2.88dsf-41+deb7u1

that's wheezy

> "2.88dsf-59" from my VPS provider.

that's jessie


So you are using the wheezy version on your local host which doesn't
necessarily use insserv but static priorities.

If insserv is used, the start priorities are dynamically computed and
what you pass to update-rc.d is ignored.

https://wiki.debian.org/LSBInitScripts/DependencyBasedBoot


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



signature.asc
Description: OpenPGP digital signature

Re: [a...@cityscape.co.uk: Re: mutt attachment error]

[Sven Hartge]

Haines Brown  wrote:

> Yes, I discovered that to be the case. So I am now able to configure the
> attachment file as I want:

>   message_size_limit = 200M

But you do know, that just because your MTA does allow mails bigger than
200MiB (which will be ~130MB before base64 encoding), other MTA will
accept those mails.

>From my daily experience as mail server operator for a German University
I can tell you, that most ISPs or mail services have a limit somewhere
between 30MiB and 50MiB (after encoding).

So increasing your local message_size_limit does nothing for you, if you
want to send those big mails elsewhere.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: gtk key theme

[Luis Finotti]

OK, I think I've figured it out.  It seems that Firefox (and other GTK
programs, like Chromium) are still reading .gtkrc-2.0.  Adding the key
theme line to it fixed my problem.

[a...@cityscape.co.uk: Re: mutt attachment error]

[Haines Brown]

- Forwarded message from Brian  -

Date: Fri, 13 May 2016 18:08:49 +0100
From: Brian 
To: debian-user@lists.debian.org
Subject: Re: mutt attachment error
User-Agent: Mutt/1.5.23 (2014-03-12)

It appears from another mail

  https://lists.debian.org/debian-user/2016/05/msg00565.html

that you are *not* using Exim's non-split configuration. 

Yes, I discovered that to be the case. So I am now able to configure the
attachment file as I want:

  # exim -bP | grep size
  bounce_return_size_limit = 100K
  header_line_maxsize = 0
  header_maxsize = 1048576
  message_size_limit = 200M

Thanks for your patience.

Re: Anytime I touch a print function, get error but it works

[Gene Heskett]

On Friday 13 May 2016 11:59:28 Curt wrote:

> On 2016-05-13, Gene Heskett  wrote:
> > The system is wheezy, 32 bit except for the running kernel, all up
> > to date but with quite a few added packages as my interests are best
> > described as eclectic.
> >
> > The error is:
> > p11-kit: invalid config filename, will be ignored in the
> > future: /etc/pkcs11/modules/gnome-keyring-module
>
> I found this bug (old, from 2012):
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687953
>
> Solution for invalid config filename? Change the filename (from
> 'gnome-keyring-module' to 'gnome-keyring.module').

Fixed it right up, thank you very much, Curt.  Since it had to create 
that path in /etc from scratch, is there a way to ask dpkg what provides 
this file so that I can make the mental connection to something I have 
installed recently?

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: smtp problems on "confirmed working" smtp server

[Demian Smith]

 Addendum, in case anybody wonders, port 465 is not blocked either:
─demian@anonymous ~
╰─$ telnet mail.riseup.net 465
Trying 198.252.153.227...
Connected to mail.riseup.net.
Escape character is '^]'.

Hopefully anyone will be able to offer any form of advice what to look
for ...

D

 ★ On 16/05/11 10:27 p.m. Demian Smith wrote ★
> Hi List,
> 
> I hope I did read the documentation sufficiently and have come to the
> right place with this request - if not, please don't hesitate telling me
> off. Unfortunately, forums.debian.net seems dead for 2 years, otherwise
> I would have posted there.
> 
> Since a couple of days I cannot send email with one of my smtps
> (mail.riseup.net) and have additional problems with other smtps. For the
> other smtps I can send messages, unless I attach any file to the mail.
> The main issue is the smtp of riseup failing completely with the message:
> "Sending of the message failed.
> The message could not be sent using Outgoing server (SMTP)
> mail.riseup.net for an unknown reason. Please verify that your Outgoing
> server (SMTP) settings are correct and try again."
> 
> I have confirmed with riseup that smtp is up and running and have, in
> fact, added the same account with the same details in a different OS
> where I don't see problems sending mails.
> 
> I have tested both ssl/tls and STARTTLS on all port (25, 465 and 578),
> all without any success. I suspected a DNS error first, but verified
> that my DNS resolves ok for the host, so I am now expecting that maybe
> some update did mess something on my system, but am not able to
> determine which update / which setting.
> 
> The last upgrades I did were as follows: https://paste.debian.net/683466
> 
> I did try a reinstall of icedove to no avail and also confirmed the same
> issue with kmail on the same system.
> 
> I am running Debian 8.4:
> 
> $ lsb_release -da
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Debian
> Description:Debian GNU/Linux 8.4 (jessie)
> Release:8.4
> Codename:   jessie
> 
> $ konsole --version
> KDE is KDE Development Platform: 4.14.2
> 
> My main mail client is icedove:
> $ icedove --version
> Icedove 38.7.0
> 
> but I tested the settings as well in KMail 4.14.1
> 
> 
> And I have www.deb-multimedia.org enabled in /etc/apt/sources.list.d/
> 
> 
> So, as you can see from my stumbling in the dark, I am totally lost for
> this one and any help or pointers would be appreciated, before I go and
> nuke the system for a reinstall...
> 
> Thanks in advance,
> Demian
> 
> 

Re: emacs menu line disappeared

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 13, 2016 at 08:03:36PM +0200, Kjetil brinchmann Halvorsen wrote:
> On one of the latest updates (I am running unstable+sid) emacs
> is behaving strangely.  Usually it shows a menu line with large icons, now
> there is only the titles with small fonts.  The menus work as before,
> though. But the movement bars on the right have disappeared. And when I am<
> opening a .tex file (auctex installed) the usual icons for running tex,
> viewing errors, see the pdf, etc, disappeared. What happened?

Perhaps some default changed. You can change it by issuing

  M-x customize-variable RET tool-bar-mode RET

Set it to "on" and either "apply changes" (to have the setting just for
the current session) or "Apply and Save" to set permanently.

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

iEYEARECAAYFAlc2NeQACgkQBcgs9XrR2kYdjgCaAxJ3vqhTzyZs0RfxGdJ9AskG
d+kAn0nNIYU1gEK3WxlOtFzxsNfeUN/x
=DkjE
-END PGP SIGNATURE-

Re: update-rc.d creates unexpected sequence numbers

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 13, 2016 at 03:35:29PM -0400, Gene Heskett wrote:

[...]

> But for the above comparison to work correctly, you (and everybody 
> responding to your message) would have to post the version number of the 
> parent package that held this file too.  No use comparing apples to 
> tangerines. :)

Gene, you have me confused now. This is *exactly* what we did: we compared
the version of the package containing update-rc.d and the program file's
sha1sum. Both match.

We still get different behaviours, thus there must be something different
in the execution environment. At least we know now where *not* to look :-)

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

iEYEARECAAYFAlc2NKkACgkQBcgs9XrR2kYIfACeL6dGdCmTMChYs78aWe+2dLCa
K5AAnjLqbv3AZjV1Xo34yj7MXZeuctRx
=eb+t
-END PGP SIGNATURE-

Re: Opera Won't Run on Wheezy [SOLVED]

[Patrick Bartek]

On Fri, 13 May 2016, Lisi Reisz wrote:

> On Friday 13 May 2016 01:39:23 Patrick Bartek wrote:
> > Guess I'm stuck with the unsupported Chrome.  No biggie.
> 
> Because Chrome is unsupported for Wheezy and 32 bit, pepper flash is 
> unsupported for Wheezy and 32 bit.  It makes no difference which of
> the browsers that you use that uses pepper flash, it will still be
> unsupported.
> 
> Lisi

That's what I at first thought, but that can't be it.  The installed
versions of all that's Chrome on my system hasn't changed since support
stopped a month ago, either before or after installing Opera twice. I
had even removed the Chrome repo, too. It looks like if you already have Chrome
installed, unsupported or not, Opera doesn't overwrite those files with
up-to-date ones. It just uses what's already there. So, I still have
old, now unsupported versions of the 4 standard plugins/extensions that
come default with Chrome and, thus, Opera.

The curiosity is that last week when I first installed Opera, and
immediately updated/upgraded, it ran fine.  No problems.  A week later,
it wouldn't.  And as far as I can determined, it hadn't been
upgraded in that week. I also checked dependencies, and Wheezy
generously met them. But something had to have changed.  I just can't
find out what.

Anyway, this is all academic. I won't be using Opera on Wheezy.  It's
been too much a bother.  However, I wonder if other LTS distros have
had this problem?

B

Re: update-rc.d creates unexpected sequence numbers

[Gene Heskett]

On Friday 13 May 2016 10:16:00 CN wrote:

> On Fri, May 13, 2016, at 09:14 PM, to...@tuxteam.de wrote:
> > Jessie/Sid here. But the more important thing is... what version of
> > sysv-rc is yours? What update-rc.d are you using?
>
> "dpkg -l sysv-rc" show this from local host:
>
> ii sysv-rc2.88dsf-41+deb7u1
>
> "2.88dsf-59" from my VPS provider.
>
> How embarrasing! I spent quite a while trying to get your second
> point, but to no avail. I am in the impression that there is only one
> copy of globally accessible update-rc.d, which is exactly located in
> /usr/sbin/, meaning that every time I type "update-rc.d" in shell,
> this exact version /usr/sbin/update-rc.d gets executed. The only
> special thing I notice is that it is a perl script.  Am I missing
> anything else?
>
> I do not know what I am doing. Regardless, I typed what you showed in
> previous message:
>
> sha1sum /usr/sbin/update-rc.d
>
> and got this result which I have no idea of its meaning:
>
> 19d097b7dbe7f0d0a551e40e9183656f81908088  /usr/sbin/update-rc.d
>
That is exactly what you asked for, the sha1sum of the file update-rc.d.

Although this is rarely done, it has a several billion to one chance of 
being different IF you have modified ANYTHING in that perl script.  But 
you would have had to do that as it was being installed, and recorded 
someplace so that you could do it again later to detect ANY CHANGE in 
that perl script, which would give you a different sha1sum.

Since I doubt that you did that, the only use might be to post it as you 
have, so that others could compare theirs to yours.  Indirectly, if 
several others get a different sha1sum that matches others, but is 
different from yours, then its time to compare version numbers.

If everybody is running the same version number, but everyone else is 
getting a different sha1sum, yours stands a very good chance of being 
contaminated somehow.  Bit rot on your hard drive would be slim because 
the hard drive itself keeps checksums and will re-read that data block 
until its good, and will usually put that good data into a spare sector, 
and will remap the spoiled sector to the newly allocated spare, all by 
itself.

A 100,000/1 better chance would be that you've had it in an editor that 
noticed the last line wasn't terminated by a newline or linefeed  and it 
added one. As some are fond of saying it doesn't mean squat, but the 
sha1sum goes BOOM in that event.

But for the above comparison to work correctly, you (and everybody 
responding to your message) would have to post the version number of the 
parent package that held this file too.  No use comparing apples to 
tangerines. :)

> Best regards,
> CN


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 

gtk key theme

[Luis Finotti]

Running Sid (and KDE), it seems that I cannot get GTK key theme "Emacs" to
work.

I used to have a file .gtkrc-3.0 with the line:

gtk-key-theme-name = "Emacs"

which gave me Emacs style key bindings on applications like Firefox.  It
stopped working recently, as apparently a new version of GTK came in (3.20
I think).

Googling around, it seemed like the configuration file now has to be on
.config/gtk-3.0/settings.ini.  So, I've added the line above to this new
configuration file.  I thought it worked for a while (maybe I'm mistaken ,
though), but it is not working now.  (I have now both files with the key
theme line.)

The closest I've come to a solution was these threads:

https://bugzilla.mozilla.org/show_bug.cgi?id=1269058
https://bugzilla.gnome.org/show_bug.cgi?id=766166

I've tried making a file (as in the second thread) for the usual key
bindings named .config/gtk-3.0/gtk.css with the content

-
@binding-set text-entry
{
  bind "a"
  {
"move-cursor" (paragraph-ends, -1, 0)
  };
  bind "e"
  {
"move-cursor" (paragraph-ends, 1, 0)
  };
  bind "k"
  {
"delete-from-cursor" (paragraph-ends, 1)

};

  bind
"u"


{

"move-cursor" (paragraph-ends, -1,
0)

"delete-from-cursor" (paragraph-ends,
1)


};

  bind
"w"


{

"delete-from-cursor" (word-ends,
-1)


};

}



entry { -gtk-key-bindings: text-entry;
}

textview { -gtk-key-bindings: text-entry; }
-

but also did not work.  (I also tried adding the content above directly on
settings.ini, but did not work either.)

I'm at a loss.  Does anyone have any ideas?

Thanks,

Luis

Re: Anytime I touch a print function, get error but it works

[Curt]

On 2016-05-13,   wrote:
>
> On Fri, May 13, 2016 at 03:59:28PM +, Curt wrote:
>
> [...]
>
>>  Provides a way to load and enumerate PKCS#11 modules. Provides a
>>  standard configuration setup for installing PKCS#11 modules in such a way 
>> that
>>  they're discoverable.
>> 
>> Whatever that means.
>
> PKCS#11 is a standard interface [1] to cryptographic tokens (e.g. smartcards
> and its ilk).

That explains why it's involved with gnome-keyring-thingmajig then.

> [1] https://en.wikipedia.org/wiki/PKCS_11
>
> regards
> - -- t
>
>


-- 
Hypertext--or should I say the ideology of hypertext?--is ultrademocratic and
so entirely in harmony with the demagogic appeals to cultural democracy that
accompany (and distract one’s attention from) the ever-tightening grip of 
plutocratic capitalism. - Susan Sontag

emacs menu line disappeared

[Kjetil brinchmann Halvorsen]

On one of the latest updates (I am running unstable+sid) emacs
is behaving strangely.  Usually it shows a menu line with large icons, now
there is only the titles with small fonts.  The menus work as before,
though. But the movement bars on the right have disappeared. And when I am<
opening a .tex file (auctex installed) the usual icons for running tex,
viewing errors, see the pdf, etc, disappeared. What happened?

Kjetil

Re: update-rc.d creates unexpected sequence numbers

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 13, 2016 at 10:16:00PM +0800, CN wrote:
> On Fri, May 13, 2016, at 09:14 PM, to...@tuxteam.de wrote:
> > Jessie/Sid here. But the more important thing is... what version of
> > sysv-rc is yours? What update-rc.d are you using?
> > 
> 
> "dpkg -l sysv-rc" show this from local host:
> 
> ii sysv-rc2.88dsf-41+deb7u1
> 
> "2.88dsf-59" from my VPS provider.

OK. Same version as here.

> How embarrasing! I spent quite a while trying to get your second point,
> but to no avail.

No worries :)

> I am in the impression that there is only one copy of
> globally accessible update-rc.d, which is exactly located in /usr/sbin/,
> meaning that every time I type "update-rc.d" in shell, this exact
> version /usr/sbin/update-rc.d gets executed. The only special thing I
> notice is that it is a perl script.  Am I missing anything else?

All correct.

> I do not know what I am doing. Regardless, I typed what you showed in
> previous message:
> 
> sha1sum /usr/sbin/update-rc.d
> 
> and got this result which I have no idea of its meaning:
> 
> 19d097b7dbe7f0d0a551e40e9183656f81908088  /usr/sbin/update-rc.d

This gives a "fingerprint" of the file. If it is identical to the
one I get in my box we can be (nearly) sure that both files are
identical. They are.

So the question now is... why they behave differently? I don't know
yet, but perhaps I come up with an idea.

regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlc2DHcACgkQBcgs9XrR2kYh1wCdFKi17ZB3VmSH5BAQkjb++tT5
tvAAnjfJFcK3iaXYz5PYBUbSKB0BGp08
=022Z
-END PGP SIGNATURE-

Re: Anytime I touch a print function, get error but it works

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 13, 2016 at 03:59:28PM +, Curt wrote:

[...]

>  Provides a way to load and enumerate PKCS#11 modules. Provides a
>  standard configuration setup for installing PKCS#11 modules in such a way 
> that
>  they're discoverable.
> 
> Whatever that means.

PKCS#11 is a standard interface [1] to cryptographic tokens (e.g. smartcards
and its ilk).

[1] https://en.wikipedia.org/wiki/PKCS_11

regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlc2CyQACgkQBcgs9XrR2ka/tQCfQme9oF8X+9M//WrdEumnWw+j
uRgAn2jhSmqcgFiZ2EeCM3SUXrh0eQqs
=bMbD
-END PGP SIGNATURE-

Re: mutt attachment error

[Ron Leach]

On 13/05/2016 12:10, Haines Brown wrote:

I'm still having no luck increasing maximum attachment size.

I create file: /etc/exim4/exim4.conf.localmacros
I leave it default permissions: -rw-r--r-- 1 root root
It has a single line: MESSAGE_SIZE_LIMIT = 200M
followed by CR.


I am no expert on line endings, but I had thought, and this wikipedia 
site


https://en.wikipedia.org/wiki/Newline

suggests, that the line ending that *should* be used in Linux is
x 0A (LF line feed), not
x 0D (CR)

If your autogenerated file shows the MESSAGE_SIZE_LIMIT = 200M 
followed immediately by <##> then the exim system 
(possibly) doesn't like the CR line ending.


[That was the advice given me on the debian-exim list earlier this 
month, where I had posted a similar question.  Brian has already 
mentioned that thread in an earlier message.]


Perhaps someone who knows for sure what the line-endings ought to be 
could chime in.


regards, Ron

Re: mutt attachment error

[Brian]

On Fri 13 May 2016 at 07:10:02 -0400, Haines Brown wrote:

> I'm still having no luck increasing maximum attachment size.
> 
> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by CR.
> And I restart exim: # invoke-rc.d exim4 reload
> 
> But:
> 
>  # exim -bP | grep size
>   bounce_return_size_limit = 100K
>   header_line_maxsize = 0
>   header_maxsize = 1048576
>   message_size_limit = 50M

It appears from another mail

  https://lists.debian.org/debian-user/2016/05/msg00565.html

that you are *not* using Exim's non-split configuration. 

Re: [s...@svenhartge.de: Re: mutt attachment error]

[Brian]

On Fri 13 May 2016 at 12:01:02 -0400, Haines Brown wrote:

[...snip...]

> > WARNING WARNING WARNING^MESC[9d# This file was generated dynamically 
> > from^MESC[10d# split config files in the /etc/exim4/conf.d/

[...snip...]

> I didn't understand the reference here to split configuration. I checked
> my exim configuration, and much to my surprise it was split. This is
> probably the problem, and now I have to figure out how to increase
> attachment size with a split configuration.

Or perform

  dpkg-reconfigure exim4-config

and choose the non-split config.

[s...@svenhartge.de: Re: mutt attachment error]

[Haines Brown]

- Forwarded message from Sven Hartge  -

Date: Fri, 13 May 2016 15:41:53 +0200
From: Sven Hartge 
To: debian-user@lists.debian.org
Subject: Re: mutt attachment error
User-Agent: tin/2.3.1-20141224 ("Tallant") (UNIX) (Linux/4.3.0-1-amd64 
(x86_64)) tinews.pl/1.1.39

Haines Brown  wrote:

> I'm still having no luck increasing maximum attachment size.

> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by CR.
> And I restart exim: # invoke-rc.d exim4 reload

> But:

>  # exim -bP | grep size
>   bounce_return_size_limit = 100K
>   header_line_maxsize = 0
>   header_maxsize = 1048576
>   message_size_limit = 50M

Please post the first 20 lines of /var/lib/exim4/config.autogenerated.
Please also do a "ls -al /var/lib/exim4/" and "stat
/var/lib/exim4/config.autogenerated" and post the results.

Just in case, my exim4.conf.localmacros file now has

  MESSAGE_SIZE_LIMIT = 200M #
  

but did not help.

The first 20 lines of config.autogenerated not so easy to copy because
of long lines, but this is what I get:

> ESC[?1049hESC[1;34rESC[mESC(BESC[4lESC[?7hESC[?25hESC=ESC=ESC=ESC \
> [39;49mESC[39;49mESC[mESC(BESC[HESC[2JESC[0;7mESC(B
> GNU nano 2.2.6 File: 
> /var/lib/exim4/config.autogenerated ESC[3;1HESC[mESC(B#^MESC[4d#
> WARNING WARNING WARNING^MESC[5d# WARNING WARNING WARNING^MESC[6d# 
> WARNING WARNING WARNING^MESC[7d# WARNING WARNING WARNING^MESC[8d#
> WARNING WARNING WARNING^MESC[9d# This file was generated dynamically 
> from^MESC[10d# split config files in the /etc/exim4/conf.d/
> directory.^MESC[11d# The config files are supplemented with package 
> installation/configuration^MESC[12d# settings managed by debconf. This
> data is stored in^MESC[13d# 
> /etc/exim4/update-exim4.conf.conf^MESC[14d# Any changes you make here
> will be lost.^MESC[15d# See 
> /usr/share/doc/exim4-base/README.Debian.gz and
> update-exim4.conf(8)^MESC[16d# for instructions of
> customization.^MESC[17d# WARNING WARNING 
> WARNING^MESC[18d# WARNING WARNING WARNING^MESC[19d# WARNING WARNING
> WARNING^MESC[20d# WARNING WARNING WARNING^MESC[21d# WARNING WARNING 
> WARNING^MESC[22d#^MESC[24dexim_path =
> /usr/sbin/exim4^MESC[26d.ifndef CONFDIR ^MESC[27dCONFDIR = 
> /etc/exim4^MESC[28d.endif^MESC[30dUPEX4CmacrosUPEX4C =
> 1^MESC[31d##ESC[32;16HESC[0;7mESC(B[
>  
> Read 899 lines (Warning: No write permission) ]^MESC[33d^GESC[mESC(B Get
> Help ESC[0;7mESC(B^OESC[mESC(B WriteOut ESC[0;7mESC(B^RESC[mESC(B 
> Read File ESC[0;7mESC(B^YESC[mESC(B Prev Page ESC[0;7mESC(B^KESC[mESC(B
> Cut Text ESC[0;7mESC(B^CESC[m
> C(B Cur Pos^MESC[34dESC[0;7mESC(B^XESC[mESC(B
> ExitESC[14GESC[0;7mESC(B^JESC[m
> ESC(B Justify ESC[0;7mESC(B^WESC[mESC(B Where Is ESC[0;7mESC(B^VESC[mESC(B 
> Next
> Page ESC[0;7mESC(B^UESC[mESC(B UnCut TextESC[0;7mESC(B^TESC[mESC(B To Spell^M
> ^MESC[27dCONFDIR = 
> /etc/exim4^MESC[28d.endif^MESC[30dUPEX4CmacrosUPEX4C =
> 1^MESC[31d##ESC[32;16HESC[0;7mESC(B[
>  

I didn't understand the reference here to split configuration. I checked
my exim configuration, and much to my surprise it was split. This is
probably the problem, and now I have to figure out how to increase
attachment size with a split configuration.

# ls -al /var/lib/exim4
total 36
drwxr-xr-x  2 root root 4096 May 13 11:39 .
drwxr-xr-x 60 root root 4096 Mar  6 13:50 ..
-rw-r--r--  1 root root4 Nov 20  2014 berkeleydbvers.txt
-rw-r--r--  1 root Debian-exim 23963 May 13 11:39 config.autogenerated

# stat /var/lib/exim4/config.autogenerated
  File: `config.autogenerated'
  Size: 23963   Blocks: 48 IO Block: 4096   regular file
Device: 817h/2071d  Inode: 1707426 Links: 1
Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (  109/Debian-exim)
Access: 2016-05-13 11:39:33.053442563 -0400
Modify: 2016-05-13 11:39:27.837516528 -0400
Change: 2016-05-13 11:39:32.945444094 -0400
 Birth: -

Haines

Re: Anytime I touch a print function, get error but it works

[Curt]

On 2016-05-13, Gene Heskett  wrote:
> The system is wheezy, 32 bit except for the running kernel, all up to 
> date but with quite a few added packages as my interests are best 
> described as eclectic.
>
> The error is:
> p11-kit: invalid config filename, will be ignored in the 
> future: /etc/pkcs11/modules/gnome-keyring-module

I found this bug (old, from 2012):

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

Solution for invalid config filename? Change the filename (from
'gnome-keyring-module' to 'gnome-keyring.module').

Logical, Captain.

> There seems to be zero docs on this so called "p11-kit", but I can't 
> purge it without destroying the system.


 Provides a way to load and enumerate PKCS#11 modules. Provides a
 standard configuration setup for installing PKCS#11 modules in such a way that
 they're discoverable.

Whatever that means.

> So it actually refers to /etc/pkcs11/modules/gnome-key-ring.
>
> Does this have a reason to exist, and if so, what the heck is it?
>
> And what dies if I blow it away by hand?
>
> Thanks.
>
> Cheers, Gene Heskett


-- 
Hypertext--or should I say the ideology of hypertext?--is ultrademocratic and
so entirely in harmony with the demagogic appeals to cultural democracy that
accompany (and distract one’s attention from) the ever-tightening grip of 
plutocratic capitalism. - Susan Sontag

Re:Re: Can not dial mobile broadband with Network-manager

[Wang]

I set the parameters as this site, but the connection can not be established. 
The error message in the daemon.log. It is showed as blew.

May 13 23:46:12 athena NetworkManager[1427]: (NetworkManager:1427): 
NetworkManager-wwan-CRITICAL **: modem_prepare_result: assertion 'state == 
NM_DEVICE_STATE_PREPARE' failed


Is it a bug of Network-Manager?




At 2016-05-13 14:58:05, "Tixy"  wrote:
>On Fri, 2016-05-13 at 00:25 +0800, Wang wrote:
>> I try to use Network-manager in GNOME to dial a mobile broadband
>> connection. My provider is China Unicom, and no username and password
>> is need. But when I complete the setting and try to dial, a dialog is
>> showed to input a password. If no password is inputed, the button for
>> connecting is not enabled.
>> 
>> How can I dial a mobile broadband without any password in the
>> Network-manager? Would you please tell me the method? Thank you very
>> much!
>
>Using Google I found this site...
>http://www.hw-group.com/products/HWg-Ares/HWg-Ares_GSM_APN_en.html
>
>And for China Unicom that suggests the username and password should both
>be 'guest'
>
>-- 
>Tixy
>

eCommerce Users

[I(ntel]

Hi,



Would you be interested eCommerce Decision makers contact information
for your marketing campaigns?



If you looking for particular titles from your target geography, please
let me know and i will get back to you with more information regarding
the same.



We also have other technology users like



Ø  Salesforce users

Ø  Epicor users

Ø  MS Dynamics users

Ø  CRM users

Ø  And many more..



Please review and let me know your selection.

Await your response!

Thanks,

Amaya James

Data Specialist



   To opt out please response Remove


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: Poweroff is not working on debian8.3

[cbannister]

On Thu, May 12, 2016 at 03:05:01AM +, GU, Gladys wrote:
> Hi, Debian, We have a system with debian8.3, the poweroff is not working and
> everytime it will be perform a restart instead. However when we use
> debian8.4, it works normally. Below is the log, do you have any advice?

Yes, use the latest version. 

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: Upgrading from 8.2 to 8.4

[Michael Lange]

On Fri, 13 May 2016 10:13:59 -0400
Steve Matzura  wrote:

> Are 'apt-get update' and 'apt-get dist-upgrade' sufficient?
> 
> 

Yes.

Regards

Michael



.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

There is a multi-legged creature crawling on your shoulder.
-- Spock, "A Taste of Armageddon", stardate 3193.9

Re: update-rc.d creates unexpected sequence numbers

[CN]

On Fri, May 13, 2016, at 09:14 PM, to...@tuxteam.de wrote:
> Jessie/Sid here. But the more important thing is... what version of
> sysv-rc is yours? What update-rc.d are you using?
> 

"dpkg -l sysv-rc" show this from local host:

ii sysv-rc2.88dsf-41+deb7u1

"2.88dsf-59" from my VPS provider.

How embarrasing! I spent quite a while trying to get your second point,
but to no avail. I am in the impression that there is only one copy of
globally accessible update-rc.d, which is exactly located in /usr/sbin/,
meaning that every time I type "update-rc.d" in shell, this exact
version /usr/sbin/update-rc.d gets executed. The only special thing I
notice is that it is a perl script.  Am I missing anything else?

I do not know what I am doing. Regardless, I typed what you showed in
previous message:

sha1sum /usr/sbin/update-rc.d

and got this result which I have no idea of its meaning:

19d097b7dbe7f0d0a551e40e9183656f81908088  /usr/sbin/update-rc.d

Best regards,
CN

-- 
http://www.fastmail.com - Access your email from home and the web

Upgrading from 8.2 to 8.4

[Steve Matzura]

Are 'apt-get update' and 'apt-get dist-upgrade' sufficient?

Re: Timing issue with fstab NFS mounts

[David Witbrodt]

> While the rest of my system is just cherry, I have not yet been able

> to solve the problem of why an NFS mount and associated binds don't
> work unless and until I wait a minute or two after the system comes

> up [...]

Sounds like the normal 90-second NFS grace period to me -- a feature,
not a bug.  If I run 'journalctl | grep grace' on one of my machines
I get:

May 12 17:50:07 fileserver kernel: NFSD: starting 90-second grace period (net 
81c64a00)


This _is_ configurable, but there is an open Debian (wishlist) bug
about that:

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


Some further discussion justifying the "lease time"/"grace period"
feature, including a possible workaround for the bug above, see:

https://access.redhat.com/solutions/42868


HTH,
Dave W.

Anytime I touch a print function, get error but it works

[Gene Heskett]

The system is wheezy, 32 bit except for the running kernel, all up to 
date but with quite a few added packages as my interests are best 
described as eclectic.

The error is:
p11-kit: invalid config filename, will be ignored in the 
future: /etc/pkcs11/modules/gnome-keyring-module

There seems to be zero docs on this so called "p11-kit", but I can't 
purge it without destroying the system.

So it actually refers to /etc/pkcs11/modules/gnome-key-ring.

Does this have a reason to exist, and if so, what the heck is it?

And what dies if I blow it away by hand?

Thanks.

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

Re: Timing issue with fstab NFS mounts

[David Wright]

On Fri 13 May 2016 at 07:28:50 (-0400), Dan Ritter wrote:
> On Fri, May 13, 2016 at 06:57:10AM -0400, Steve Matzura wrote:
> > On Fri, 13 May 2016 05:12:56 -0400, you wrote:
> > 
> > >The options field in fstab should include "_netdev" for devices
> > >which cannot be mounted until networking is stable.
> > 
> > I have never heard of that option. I'll try it and report back. Now,
> > what about the lines for the binds that immediately follow the network
> > device? Do the binds still operate even if the network device isn't
> > online yet? In other words, does the mounting of devices processing
> > stop until the line in fstab with _netdev in its options field is
> > processed, then the binds run? If so, then this is the answer to a
> > humble man's prayer. I've been wrestling with this literally for
> > months.
> 
> fstab is always evaluated in the order you write it, from top to
> bottom.

That may be true in wheezy but not in jessie. man fstab is out-of-date
and appears to be either unaware of initrd or unconcerned about its
effects. Anyway, check out read_fstab_entry().

> However, not all mount commands are equivalent. The
> usual call shortly after system boot is:
> 
> mount -a -t nonfs,nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs,gfs2,ceph -O 
> no_netdev
> 
> which says: mount everything except filesystems which are known to
> be dependent on networks, and also avoid filesystems which are marked
> as _netdev.
> 
> In this case, you want to mark all your bind mounts as _netdev
> as well.

Cheers,
David.

Re: mutt attachment error

[Sven Hartge]

Haines Brown  wrote:

> I'm still having no luck increasing maximum attachment size.

> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by CR.
> And I restart exim: # invoke-rc.d exim4 reload

> But:

>  # exim -bP | grep size
>   bounce_return_size_limit = 100K
>   header_line_maxsize = 0
>   header_maxsize = 1048576
>   message_size_limit = 50M

Please post the first 20 lines of /var/lib/exim4/config.autogenerated.
Please also do a "ls -al /var/lib/exim4/" and "stat
/var/lib/exim4/config.autogenerated" and post the results.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: mutt attachment error

[Sven Hartge]

David Wright  wrote:
> On Fri 13 May 2016 at 07:10:02 (-0400), Haines Brown wrote:
>> I'm still having no luck increasing maximum attachment size.
>> 
>> I create file: /etc/exim4/exim4.conf.localmacros
>> I leave it default permissions: -rw-r--r-- 1 root root
>> It has a single line: MESSAGE_SIZE_LIMIT = 200M
>> followed by CR.

> That's all correct (for unsplit configurations) †.

>> And I restart exim: # invoke-rc.d exim4 reload

> But you haven't reconfigured exim yet. As I pointed out,
> the Debian way to do that is:

> # dpkg-reconfigure exim4-config

> and that will *also* look after restarting exim in the
> appropriate way for your system.

No need to do this. The init-script will regenerate the configuration on
every start, restart and reload.

S°

-- 
Sigmentation fault. Core dumped.

Re: openvpn start failed and Jessie

[Eduardo M KALINOWSKI]

On Sex, 13 Mai 2016, Bonno Bloksma wrote:
Today I had a Jessie system where I made a little mistake with the  
openvpn config file name and after a restart of the service it did  
not come back, off course.

Off course it did not come back either after a full reboot of the system.

A colleage went to the system, we found the typo in the config file  
name (client.cinf in stead of client.conf)
Strangely it did not come back after a service openvpn restart nor  
after a service openvpn stop ; service openvpn start

Even stranger I could not find anything in the syslog about openvpn.

Now this might have something to do with the new system environment  
which seems to (try) to do some smart thing with *.conf files that  
exist at startup.

But...
1) Is there no other way to resolve this, other than a reboot?
2) As there was absolutely nothing in syslog, is there another place  
I should have looked about the service (re)start problem?


Try "systemctl daemon-reload", this causes systemd to reread  
configuration files. If it is looking for the openvpn .conf files,  
this might cause it to see the changed files.


You can control individual vpns using the service "openvpn@", so  
you can try "systemctl start openvpn@client".


Lastly, you could also try "systemctl status openvpn" and "systemctl  
status openvpn@client".


--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: mutt attachment error

[David Wright]

On Fri 13 May 2016 at 07:10:02 (-0400), Haines Brown wrote:
> I'm still having no luck increasing maximum attachment size.
> 
> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by CR.

That's all correct (for unsplit configurations) †.

> And I restart exim: # invoke-rc.d exim4 reload

But you haven't reconfigured exim yet. As I pointed out,
the Debian way to do that is:

# dpkg-reconfigure exim4-config

and that will *also* look after restarting exim in the
appropriate way for your system.

† I think it's good practice to put a comment line at the
end of the file. You wrote that you put a CR at the end,
but it's more likely to be a LF. Put a comment line, and
then you know (and can *see*) the problem is taken care of.

Cheers,
David.

Re: update-rc.d creates unexpected sequence numbers

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 13, 2016 at 09:09:56PM +0800, CN wrote:
> On Fri, May 13, 2016, at 08:46 PM, to...@tuxteam.de wrote:
> > 
> > Bizarre. Just tried in my box and it behaves as it should. It comes from
> > 
> >   sysv-rc 2.88dsf-41+deb7u1
> > 
> > What version is yours? And... just to double-check:
> > 
> >   tomas@rasputin:~$ sha1sum /usr/sbin/update-rc.d 
> >   19d097b7dbe7f0d0a551e40e9183656f81908088  /usr/sbin/update-rc.d
> > 
> > (pity that it hasn't --version and --debug options, though).
> > 
> 
> Hi!
> 
> I get the same weird results from 3 Debian hosts:
> 
> - Linux host1 4.3.3 $8 SMP (Wheezy i686, local host I am working on)
> 
> - Linux vps1 3.16.0-4-amd64 #1 SMP Debian 3.16.7 (from IaaS provider)
> 
> - Linux vps2 4.5.2-2 $1 SMP x86-64 (Jessie, from IaaS provider)

Jessie/Sid here. But the more important thing is... what version of
sysv-rc is yours? What update-rc.d are you using?

- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlc10x0ACgkQBcgs9XrR2kaMSwCfeKyQDch/C6YsIQPOlRLS3kFZ
prsAnRgjh/Jcq4s9J8uQXy+1SKmV0gEN
=OpJG
-END PGP SIGNATURE-

Re: update-rc.d creates unexpected sequence numbers

[CN]

On Fri, May 13, 2016, at 08:46 PM, to...@tuxteam.de wrote:
> 
> Bizarre. Just tried in my box and it behaves as it should. It comes from
> 
>   sysv-rc 2.88dsf-41+deb7u1
> 
> What version is yours? And... just to double-check:
> 
>   tomas@rasputin:~$ sha1sum /usr/sbin/update-rc.d 
>   19d097b7dbe7f0d0a551e40e9183656f81908088  /usr/sbin/update-rc.d
> 
> (pity that it hasn't --version and --debug options, though).
> 

Hi!

I get the same weird results from 3 Debian hosts:

- Linux host1 4.3.3 $8 SMP (Wheezy i686, local host I am working on)

- Linux vps1 3.16.0-4-amd64 #1 SMP Debian 3.16.7 (from IaaS provider)

- Linux vps2 4.5.2-2 $1 SMP x86-64 (Jessie, from IaaS provider)

Best regards,
CN

-- 
http://www.fastmail.com - Or how I learned to stop worrying and
  love email again

Re: update-rc.d creates unexpected sequence numbers

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, May 13, 2016 at 07:54:55PM +0800, CN wrote:
> Hi!
[...]

> Both of these two commands
> 
> update-rc.d my-program defaults 20 80
> update-rc.d my-program defaults start 20 2 3 4 5 . stop 80 0 1 6 .
> 
> yield the same incorrect sequence numbers in contrast to the results
> demonstrated here:

Bizarre. Just tried in my box and it behaves as it should. It comes from

  sysv-rc 2.88dsf-41+deb7u1

What version is yours? And... just to double-check:

  tomas@rasputin:~$ sha1sum /usr/sbin/update-rc.d 
  19d097b7dbe7f0d0a551e40e9183656f81908088  /usr/sbin/update-rc.d

(pity that it hasn't --version and --debug options, though).

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

iEYEARECAAYFAlc1zKwACgkQBcgs9XrR2kaeDwCcDd3cxVmt11nOhr0oYFogW8Lz
SY4An2LrkduRUnx5w/Ocij5Yu52w8Ffa
=2Y67
-END PGP SIGNATURE-

Re: Opera Won't Run on Wheezy [SOLVED]

[Lisi Reisz]

On Friday 13 May 2016 09:44:43 Curt wrote:
> On 2016-05-13, Lisi Reisz  wrote:
> > On Friday 13 May 2016 01:39:23 Patrick Bartek wrote:
> >> Guess I'm stuck with the unsupported Chrome.  No biggie.
> >
> > Because Chrome is unsupported for Wheezy and 32 bit, pepper flash is
> > unsupported for Wheezy and 32 bit.  It makes no difference which of the
> > browsers that you use that uses pepper flash, it will still be
> > unsupported.
>
> Chrome no longer receives updates in Wheezy period (whether 32 or 64 bit
> flavor).
>
> When did he say he was using a 32 bit machine btw?

He didn't and I didn't.  The statement, and I made it a general one, applies 
to two things:  Wheezy and 32 bit.  Both.  Separately.  (And together, of 
course.)  What has what the OP is using got to do with it?  It applies to a 
lot of us, and I had been trying to do as you suggested and had clarified the 
above for myself, so it seemed worth passing on.  

And my post was about pepper flash in other browsers, not Chrome.  Pepper 
flash is unsupported in Wheezy and 32 bit, in any or all browsers, because 
Chrome is unsupported in Wheezy and 32 bit.  Note: Wheezy AND 32 bit.  Not 
Wheezy 32 bit.

Lisi

Re: Posting picture files

[cbannister]

On Tue, May 10, 2016 at 07:52:46PM +0100, Brian wrote:
> On Wed 11 May 2016 at 06:36:43 +1200, cbannis...@slingshot.co.nz wrote:
> 
> > On Sun, May 01, 2016 at 11:57:34AM -0400, Gene Heskett wrote:
> > > On Sunday 01 May 2016 11:07:39 Sven Arvidsson wrote:
> > > >
> > > > "Do not submit an attachment larger than 10 KiB. Consider using
> > > > paste.debian.net and including a link in your post."
> > > >
> > > > From https://wiki.debian.org/DebianMailingLists#Posting_Rules.2C_Guide
> > > >lines.2C_and_Tips
> > > 
> > > Thanks Sven.  But it does seem rather archaic today, 100k would be a lot 
> > > more useful as attaching a well smunched screenshot is a lot less 
> > 
> > Well, it is a wiki. :)
> 
> Which anyone, including you, can contribute to. :)

Yeah, that's what I pointed out. I don't intend to go round editing posts
on other peoples behalf. :)

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

update-rc.d creates unexpected sequence numbers

[CN]

Hi!

/etc/init.d/my-program is correctly prepared with LSB header comments
like this:

#!/bin/sh
### BEGIN INIT INFO
# Provides: my-program
# Required-Start:   $postgresql
# Required-Stop:$postgresql
# Default-Start:2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: My program.
# Description:  My program.
### END INIT INFO

Both of these two commands

update-rc.d my-program defaults 20 80
update-rc.d my-program defaults start 20 2 3 4 5 . stop 80 0 1 6 .

yield the same incorrect sequence numbers in contrast to the results
demonstrated here:

https://debian-administration.org/article/28/Making_scripts_run_at_boot_time_with_Debian


cd /etc
ls rc5.d rc6.d

rc5.d:
README
S01motd
S01my-program
S01rsyslog
S02cron
S02dbus
S02ntp
S02postgresql
S02rsync
S02ssh
S02xfs
S03avahi-daemon
S03xdm
S04bootlogs
S04saned
S05minissdpd
S05rc.local
S05rmnologin

rc6.d:
K01minissdpd
K01saned
K01urandom
K01xdm
K02avahi-daemon
K02my-program
K02postgresql
K03sendsigs
K04rsyslog
K05hwclock.sh
K05umountnfs.sh
K06rpcbind
K07networking
K08umountfs
K09umountroot
K10reboot
README

I thought the linked files were S20my-program and K80my-program. Why
update-rc.d gives unexpected results? What is the procedure to get the
correct results?

Besides, why none of the sequence numbers with K is 100 minus the number
of the start link "S" according to the recommendations from "man
update-rc.d"?

-- 
http://www.fastmail.com - Access all of your messages and folders
  wherever you are

Re: Timing issue with fstab NFS mounts

[Dan Ritter]

On Fri, May 13, 2016 at 06:57:10AM -0400, Steve Matzura wrote:
> On Fri, 13 May 2016 05:12:56 -0400, you wrote:
> 
> >The options field in fstab should include "_netdev" for devices
> >which cannot be mounted until networking is stable.
> 
> I have never heard of that option. I'll try it and report back. Now,
> what about the lines for the binds that immediately follow the network
> device? Do the binds still operate even if the network device isn't
> online yet? In other words, does the mounting of devices processing
> stop until the line in fstab with _netdev in its options field is
> processed, then the binds run? If so, then this is the answer to a
> humble man's prayer. I've been wrestling with this literally for
> months.

fstab is always evaluated in the order you write it, from top to
bottom. However, not all mount commands are equivalent. The
usual call shortly after system boot is:

mount -a -t nonfs,nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs,gfs2,ceph -O 
no_netdev

which says: mount everything except filesystems which are known to
be dependent on networks, and also avoid filesystems which are marked
as _netdev.

In this case, you want to mark all your bind mounts as _netdev
as well.

-dsr-

openvpn start failed and Jessie

[Bonno Bloksma]

Hi,

Today I had a Jessie system where I made a little mistake with the openvpn 
config file name and after a restart of the service it did not come back, off 
course.
Off course it did not come back either after a full reboot of the system.

A colleage went to the system, we found the typo in the config file name 
(client.cinf in stead of client.conf)
Strangely it did not come back after a service openvpn restart nor after a 
service openvpn stop ; service openvpn start
Even stranger I could not find anything in the syslog about openvpn.
 
Now this might have something to do with the new system environment which seems 
to (try) to do some smart thing with *.conf files that exist at startup.
But... 
1) Is there no other way to resolve this, other than a reboot?
2) As there was absolutely nothing in syslog, is there another place I should 
have looked about the service (re)start problem?

Bonno Bloksma

Re: mutt attachment error

[Haines Brown]

I'm still having no luck increasing maximum attachment size.

I create file: /etc/exim4/exim4.conf.localmacros
I leave it default permissions: -rw-r--r-- 1 root root
It has a single line: MESSAGE_SIZE_LIMIT = 200M
followed by CR.
And I restart exim: # invoke-rc.d exim4 reload

But:

 # exim -bP | grep size
  bounce_return_size_limit = 100K
  header_line_maxsize = 0
  header_maxsize = 1048576
  message_size_limit = 50M

Re: Timing issue with fstab NFS mounts

[Steve Matzura]

Dan,

On Fri, 13 May 2016 05:12:56 -0400, you wrote:

>The options field in fstab should include "_netdev" for devices
>which cannot be mounted until networking is stable.

I have never heard of that option. I'll try it and report back. Now,
what about the lines for the binds that immediately follow the network
device? Do the binds still operate even if the network device isn't
online yet? In other words, does the mounting of devices processing
stop until the line in fstab with _netdev in its options field is
processed, then the binds run? If so, then this is the answer to a
humble man's prayer. I've been wrestling with this literally for
months.

Re: Iceweasel uses wrong charset

[Vincent Lefevre]

On 2016-05-11 12:10:25 +0200, to...@tuxteam.de wrote:
> This is happening only on local files? Perhaps FF is expecting that
> brain damaged byte order mark to recognize the file as UTF-8?

I reported a bug about that in the past:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1071816

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Iceweasel uses wrong charset

[Vincent Lefevre]

On 2016-05-11 11:55:33 +0200, Frédéric Marchal wrote:
> On Wednesday 11 May 2016 11:23:56 err...@free.fr wrote:
> > Why unicode like utf-8 is not default value in iceweasel ?
> > 
> > (it's time, we are in 2016 now)
> 
> Unicode is the default in firefox/iceweasel.

No, the default is windows-1252 (checked by testing with a fresh
profile).

> See 
> https://developer.mozilla.org/en-US/docs/Web/Guide/Localizations_and_character_encodings

which says that the default is windows-1252.

BTW, this page says: "New-authored locale-native UTF-8 content is
expected to declare its encoding, in which case the fallback encoding
does not participate in the processing of content." but I don't see
how one can declare the encoding for text files read locally with the
"file:" URL scheme.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Timing issue with fstab NFS mounts

[Dan Ritter]

On Fri, May 13, 2016 at 03:34:44AM -0400, Steve Matzura wrote:
> While the rest of my system is just cherry, I have not yet been able
> to solve the problem of why an NFS mount and associated binds don't
> work unless and until I wait a minute or two after the system comes
> up, then issue a 'mount -a'. I have tried putting 'mount -a'  into
> /etc/init.d/rc.local, and still no happiness. Is there something I
> need to check for before the fstab stuff starts, or should the NFS
> mount and associated binds be taken out of fstab and dealt elsewhere?
> This seems a kluge, but I cannot think of another way to get around
> this problem.

The options field in fstab should include "_netdev" for devices
which cannot be mounted until networking is stable.

-dsr-

Re: Opera Won't Run on Wheezy [SOLVED]

[Curt]

On 2016-05-13, Lisi Reisz  wrote:
> On Friday 13 May 2016 01:39:23 Patrick Bartek wrote:
>> Guess I'm stuck with the unsupported Chrome.  No biggie.
>
> Because Chrome is unsupported for Wheezy and 32 bit, pepper flash is 
> unsupported for Wheezy and 32 bit.  It makes no difference which of the 
> browsers that you use that uses pepper flash, it will still be unsupported.

Chrome no longer receives updates in Wheezy period (whether 32 or 64 bit
flavor).

When did he say he was using a 32 bit machine btw?

> Lisi
>
>


-- 
Hypertext--or should I say the ideology of hypertext?--is ultrademocratic and
so entirely in harmony with the demagogic appeals to cultural democracy that
accompany (and distract one’s attention from) the ever-tightening grip of 
plutocratic capitalism. - Susan Sontag

Timing issue with fstab NFS mounts

[Steve Matzura]

While the rest of my system is just cherry, I have not yet been able
to solve the problem of why an NFS mount and associated binds don't
work unless and until I wait a minute or two after the system comes
up, then issue a 'mount -a'. I have tried putting 'mount -a'  into
/etc/init.d/rc.local, and still no happiness. Is there something I
need to check for before the fstab stuff starts, or should the NFS
mount and associated binds be taken out of fstab and dealt elsewhere?
This seems a kluge, but I cannot think of another way to get around
this problem.

Thanks in advance as always.

Re: Can not dial mobile broadband with Network-manager

[Joe]

On Fri, 13 May 2016 08:11:19 +0100
Tixy  wrote:

> On Thu, 2016-05-12 at 18:48 +0100, Joe wrote:
> [...]
> > My configuration for a Huawei 3G dongle has *99# for the Number,
> > which obviously isn't correct  
> 
> Well it works doesn't it? And I bet it doesn't without it. So in my
> book that would make it correct ;-) (I remember using such special
> numbers to configure data connections on mobile phones in decades
> past)
> 

Yes, it works, the point is that NM doesn't actually need the dongle's
real telephone number, at least not for this provider. I'm fairly
confident (it was a while ago that I last created one) that the only
connection data needed was the ATN.

-- 
Joe

Re: Can not dial mobile broadband with Network-manager

[Tixy]

On Thu, 2016-05-12 at 18:48 +0100, Joe wrote:
[...]
> My configuration for a Huawei 3G dongle has *99# for the Number, which
> obviously isn't correct

Well it works doesn't it? And I bet it doesn't without it. So in my book
that would make it correct ;-) (I remember using such special numbers to
configure data connections on mobile phones in decades past)

-- 
Tixy