Re: init script can't find /bin/dirname

2014-12-21 Thread Rob Owens
On Sun, Dec 21, 2014 at 06:07:20PM -0500, Rob Owens wrote:
> On Sun, Dec 21, 2014 at 10:32:07PM +0100, Sven Joachim wrote:
> > On 2014-12-21 21:58 +0100, Rob Owens wrote:
> > > I know I could add a PATH statement to the init script, but this problem
> > > is my own doing and I'd like to fix it right.  I "cross-graded" this
> > > system from 32-bit to 64-bit using this guide:
> > >
> > > www.ewan.cc/?q=node/90
> > >
> > > It worked pretty well, but not perfectly.  Some things got missed, like
> > > screen, ntp, and a couple other packages.  I'm thinking that maybe
> > > another missing package is preventing the mysql init script from
> > > checking for /usr/bin/dirname.
> > 
> > That seems to be unlikely, but you could add a line with "echo $PATH" to
> > the script to find out what PATH actually is.
> > 
> I will do this, but I can't reboot just yet to check it out.  I will
> post my findings later.

I rebooted and found that the path is fine:

/sbin:/usr/sbin:/bin:/usr/bin

So I'm still not sure why /etc/init.d/mysql cannot find "dirname" and
"basename" when running at system boot, but it can find them when run
from a terminal after boot.

Any advice would be appreciated!

-Rob


signature.asc
Description: Digital signature


Re: LACK OF REPONSE TO REQUESTS FOR HELP WHY?

2014-12-21 Thread tom arnall
Nate,

Thanks for your response. I ended up dealing with the problem by
switching to wicd, but the incident has helped me learn some things
about keyrings. I think my real problem was the one where you flounder
around to the point of desperation looking for a quick fix, instead of
taking the trouble to first get an understanding of the context, in
this case the basic functions of keyrings, before attempting to fix a
specific problem.

Regards,

Tom Arnall
Ensenada, BC

--
Honor Julian Assange. Honor Bradley Manning. Honor Edward Snowden.
Honor all those who have risked all to tell us what we must know to
remain free.



On 12/21/14, Nate Bargmann  wrote:
> * On 2014 21 Dec 01:40 -0600, tom arnall wrote:
>> I installed wheezy a week ago (with the installer which includes
>> xfce), and nm-applet was working fine. But today it won't start and
>> gives the message:
>>
>> WARNING: gnome-keyring:: couldn't connect to:
>> /home/tom/.cache/keyring-4LJPFc/pkcs11: No such file or directory
>
> I am running Sid (Unstable) on my laptop and I have several such
> ~/.cache/keyring-* directories. One of them shows:
>
> $ ls -l ~/.cache/keyring-6imVnR/
> total 0
> srwxr-xr-x 1 nate nate 0 Jul 7 2012 control=
> srwxr-xr-x 1 nate nate 0 Jul 7 2012 gpg=
> srwxr-xr-x 1 nate nate 0 Jul 7 2012 pkcs11=
> srwxr-xr-x 1 nate nate 0 Jul 7 2012 ssh=
>
> Are the permissions on your files the same? Is it possible that you
> initially logged into the desktop as root and then used NM to connect to
> a network? Perhaps just removing that directory (although that specific
> directory name may be stored by nm-applet *somewhere* so just removing
> the directory might not help) might help.
>
> The "files" are actually sockets so the leading 's' is apparently
> required.
>
> - Nate
>
> --
>
> "The optimist proclaims that we live in the best of all
> possible worlds. The pessimist fears this is true."
>
> Ham radio, Linux, bikes, and more: http://www.nnb.us
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmasterlists.debian.org
> Archive: https://lists.debian.org/20141221130512.gr2...@nnb.us
>
>


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cafkyrxp4hfegqhuquhitxh58uot6vwdeepbsaryicrurxoq...@mail.gmail.com



Re: remote printing for an USB printer

2014-12-21 Thread Brian
On Sun 21 Dec 2014 at 23:25:38 +, Brian wrote:

> This may or may not be significant for the printing process.

It would be useful to see the server log. If you do post it please do
not truncate or edit the beginning of it before sending.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/21122014234110.67fa8d861...@desktop.copernicus.demon.co.uk



Re: remote printing for an USB printer

2014-12-21 Thread Brian
On Sun 21 Dec 2014 at 20:46:55 +0100, Pierre Frenkiel wrote:

> On Sun, 21 Dec 2014, Brian wrote:
> 
> >On Sat 20 Dec 2014 at 22:03:50 +0100, Pierre Frenkiel wrote:
> >>  I think that a so mature OS as Debian should provide the same
> >>  facility.
> >
> >It does.
> 
>the experience proves that it does not: otherwise, why nobody could
>explain the problem I described and suggest a fix?

Describing a problem accurately (which you have done) and coming up with
a solid fix are two different things. 

>The only help I got up to now was: "do a correct setup"
>that is very helpful!

Getting no responses would be getting no help. I'll suspend judgement on
whether the Wheezy client is at fault. It could be the server. (Please
see the log). I have successfully set up a print queue for your printer;
details later if you want them.

> >>  This also shows that the sharing is correctly setup on the server side.
> >
> >For the Android.
> 
> I would be curious to understand how a CUPS sharing  setup on the server
> could work for Android and not for Linux?

A guess, because you would know more about how an Android works than I:
the Android can process Bonjour broadcasts directly whereas a Wheezy
client needs some help. I'm Androidless so could be wromg.
 
> >Where is the printer queue set up? On the client or on the server?
> 
>I don't understand at all this question: how could I setup on the client
>a printer connected via USB on the server?
>On the client, the only thing you can do is to add a shared printer,
>but not modify it's setup.

You have misunderstand the question.

> >Empty the error_log with '>/var/log/error_log'; print ; send the client
> >log to the list if you wish.
> 
>   I join the client error_log, severely cut as it became huge very quickly
>   you can remark all lines like "Print file accepted - job ID 2025"
>   which explains why the queue is growing on the server, but not why it
>   does that.
> 
> >> cups-browsed needs to be correctly set up on the server for the client
> >to be able to see the advertised queues.  > > "listen 192.168.1.12"
> should not be the least bit necessary.
>   I installed cups-browsed, but that changed nothing, which seems noraml,
>   as the lient already sees the print queue and can print to it.
>   I repeat: the problem is not that I can't print, but that I print
>   too much!

It is impossible for a Wheezy client to discover the queues on a 1.7
CUPS server without the help of cups-browsed on the server. Please read
the documentation.


> D [21/Dec/2014:16:55:49 +0100] [Job 35] Create-Job IPP/2.0
> D [21/Dec/2014:16:55:49 +0100] [Job 35] 
> printer-uri="ipp://192.168.1.12:631/printers/phsm"

Your queue on 192.168.1.12 is phsm

> D [21/Dec/2014:16:55:49 +0100] [Job 35] requesting-user-name="frenkiel"
> D [21/Dec/2014:16:55:49 +0100] [Job 35] job-name="prn_pr_31736"
> D [21/Dec/2014:16:55:49 +0100] [Job 35] 
> document-format="application/postscript"
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Get-Jobs: successful-ok 
> (successful-ok)
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Create-Job: successful-ok 
> (successful-ok)
> I [21/Dec/2014:16:55:49 +0100] [Job 35] Print file accepted - job ID 2025.
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Set job-printer-state-message to 
> "Print file accepted - job ID 2025.", current level=INFO

The queue accepts the job.

> D [21/Dec/2014:16:55:49 +0100] [Job 35] job-id=2025
> D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
> D [21/Dec/2014:16:55:49 +0100] Discarding unused printer-state-changed 
> event...
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Sending file 1 using chunking...
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Send-Document: successful-ok 
> (successful-ok)
> D [21/Dec/2014:16:55:49 +0100] [Job 35] PAGE: 1 1
> D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
> I [21/Dec/2014:16:55:49 +0100] [Job 35] Waiting for job to complete.
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Set job-printer-state-message to 
> "Waiting for job to complete.", current level=INFO

Everything looks ok.

> D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
> D [21/Dec/2014:16:55:49 +0100] Discarding unused printer-state-changed 
> event...
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Get-Job-Attributes: successful-ok 
> (successful-ok)
> D [21/Dec/2014:16:55:49 +0100] [Job 35] update_reasons(attr=0(), 
> s="+cups-ipp-conformance-failure-report,cups-ipp-missing-job-state")

Oops. What's going on here?

> I [21/Dec/2014:16:55:49 +0100] [Job 35] 
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Set job-printer-state-message to 
> "Waiting for job to complete.", current level=INFO
> D [21/Dec/2014:16:55:49 +0100] [Job 35] update_reasons(attr=1(none), 
> s="(null)")
> D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
> D [21/Dec/2014:16:55:49 +0100] Discarding unused printer-state-changed 
> event...
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Get-P

Re: init script can't find /bin/dirname

2014-12-21 Thread Rob Owens
On Sun, Dec 21, 2014 at 10:32:07PM +0100, Sven Joachim wrote:
> On 2014-12-21 21:58 +0100, Rob Owens wrote:
> 
> > The /etc/init.d/mysql script on one of my systems is complaning that it
> > can't find /bin/dirname and /bin/basename.  Line 24 of the script is
> > this:
> >
> > SELF=$(cd $(dirname $0); pwd -P)/$(basename $0)
> >
> > Both dirname and basename live in /usr/bin, not /bin.
> 
> Which should be fine from the script's point of view as long as
> $remote_fs is in the "Required-Start" header (i.e. /usr is guaranteed to
> be mounted).
> 
It is.  In any case, /usr is part of the / partition.  In case it
matters, /var is a separate partition.  And I'm using software raid 1
for both / and /var.

> > I know I could add a PATH statement to the init script, but this problem
> > is my own doing and I'd like to fix it right.  I "cross-graded" this
> > system from 32-bit to 64-bit using this guide:
> >
> > www.ewan.cc/?q=node/90
> >
> > It worked pretty well, but not perfectly.  Some things got missed, like
> > screen, ntp, and a couple other packages.  I'm thinking that maybe
> > another missing package is preventing the mysql init script from
> > checking for /usr/bin/dirname.
> 
> That seems to be unlikely, but you could add a line with "echo $PATH" to
> the script to find out what PATH actually is.
> 
I will do this, but I can't reboot just yet to check it out.  I will
post my findings later.

> > I can run '/etc/init.d/mysql start' from a terminal and it works fine,
> > because it picks up the PATH associated with the terminal.  So this is
> > only a boot-time issue.
> >
> > So is there a package or a  global setting somewhere that sets the PATH 
> > for init scripts?
> 
> PATH is set directly by init.  If I read the source code correctly,
> sysvinit sets it to "/sbin:/usr/sbin:/bin:/usr/bin" while systemd uses
> "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin".
> 
This is a Wheezy system, running with sysvinit.  

'man init' says:

ENVIRONMENT
   Init sets the following environment variables for all its
   children:

   PATH   /bin:/usr/bin:/sbin:/usr/sbin

So maybe it's not a path issue after all.  What else could it be then?
The boot messages clearly indicate that it's failing to find
/bin/dirname and /bin/basename.

Thanks for your help.

-Rob


signature.asc
Description: Digital signature


Re: remote printing for an USB printer

2014-12-21 Thread Lisi Reisz
On Sunday 21 December 2014 21:59:10 Lisi Reisz wrote:
> On Sunday 21 December 2014 19:46:55 Pierre Frenkiel wrote:
> > > On Sat 20 Dec 2014 at 22:03:50 +0100, Pierre Frenkiel wrote:
> > >>   I think that a so mature OS as Debian should provide the same
> > >>   facility.
> > >
> > > It does.
> >
> >     the experience proves that it does not: otherwise, why nobody could
> >     explain the problem I described and suggest a fix?
>
> I thought I had.
>
> >     The only help I got up to now was: "do a correct setup"
> >     that is very helpful!
>
> Have you tried looking at the settings in CUPS in the manner I described?

Wires crossing in the ethernet.  Sorry Pierre.  I'll aim to answer your other 
email tomorrow.

Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201412212220.20392.lisi.re...@gmail.com



Re: remote printing for an USB printer

2014-12-21 Thread Lisi Reisz
On Sunday 21 December 2014 19:46:55 Pierre Frenkiel wrote:
> > On Sat 20 Dec 2014 at 22:03:50 +0100, Pierre Frenkiel wrote:
> >>   I think that a so mature OS as Debian should provide the same
> >>   facility.
> >
> > It does.
>
>     the experience proves that it does not: otherwise, why nobody could
>     explain the problem I described and suggest a fix?

I thought I had.

>     The only help I got up to now was: "do a correct setup"
>     that is very helpful!

Have you tried looking at the settings in CUPS in the manner I described?

Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201412212159.10081.lisi.re...@gmail.com



Re: init script can't find /bin/dirname

2014-12-21 Thread Sven Joachim
On 2014-12-21 21:58 +0100, Rob Owens wrote:

> The /etc/init.d/mysql script on one of my systems is complaning that it
> can't find /bin/dirname and /bin/basename.  Line 24 of the script is
> this:
>
> SELF=$(cd $(dirname $0); pwd -P)/$(basename $0)
>
> Both dirname and basename live in /usr/bin, not /bin.

Which should be fine from the script's point of view as long as
$remote_fs is in the "Required-Start" header (i.e. /usr is guaranteed to
be mounted).

> I know I could add a PATH statement to the init script, but this problem
> is my own doing and I'd like to fix it right.  I "cross-graded" this
> system from 32-bit to 64-bit using this guide:
>
> www.ewan.cc/?q=node/90
>
> It worked pretty well, but not perfectly.  Some things got missed, like
> screen, ntp, and a couple other packages.  I'm thinking that maybe
> another missing package is preventing the mysql init script from
> checking for /usr/bin/dirname.

That seems to be unlikely, but you could add a line with "echo $PATH" to
the script to find out what PATH actually is.

> I can run '/etc/init.d/mysql start' from a terminal and it works fine,
> because it picks up the PATH associated with the terminal.  So this is
> only a boot-time issue.
>
> So is there a package or a  global setting somewhere that sets the PATH 
> for init scripts?

PATH is set directly by init.  If I read the source code correctly,
sysvinit sets it to "/sbin:/usr/sbin:/bin:/usr/bin" while systemd uses
"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin".

Cheers,
   Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87y4q0g04o@turtle.gmx.de



init script can't find /bin/dirname

2014-12-21 Thread Rob Owens
The /etc/init.d/mysql script on one of my systems is complaning that it
can't find /bin/dirname and /bin/basename.  Line 24 of the script is
this:

SELF=$(cd $(dirname $0); pwd -P)/$(basename $0)

Both dirname and basename live in /usr/bin, not /bin.

I know I could add a PATH statement to the init script, but this problem
is my own doing and I'd like to fix it right.  I "cross-graded" this
system from 32-bit to 64-bit using this guide:

www.ewan.cc/?q=node/90

It worked pretty well, but not perfectly.  Some things got missed, like
screen, ntp, and a couple other packages.  I'm thinking that maybe
another missing package is preventing the mysql init script from
checking for /usr/bin/dirname.

I can run '/etc/init.d/mysql start' from a terminal and it works fine,
because it picks up the PATH associated with the terminal.  So this is
only a boot-time issue.

So is there a package or a  global setting somewhere that sets the PATH 
for init scripts?

-Rob



signature.asc
Description: Digital signature


Re: Inserting a field in a LibreOffice email subject line for a bulk mailing.

2014-12-21 Thread Gary Dale

On 21/12/14 01:27 PM, Gary Dale wrote:

On 21/12/14 10:59 AM, Lisi Reisz wrote:
Does one of the LO fans know how to insert a field in a LibreOffice 
email

subject line for a bulk mailing?

Lisi



LibreOffice has its own e-mail discussion list.

I've never needed to do it because I've used a simple work-around bash 
script. I use LibreOffice to produce a customized attachment (usually 
a certificate for someone) then use an exported text file and the read 
command to allow me to extract the custom information I need.


I can use this to build custom subject and body parts, plus add the 
appropriate attachment, using a command-line mail program.


Here's a quick and dirty example of how to do it:

#! /bin/bash
cat $1.text | while read addr first last; do
  echo "sending e-mail to" $first $last "at" $addr
  echo "Dear" $first $last > salutation.text
  cat $2.text >>salutation.text
  if [[ "$4" == "" ]]; then
mutt $addr -s "$3" 

Oops, sorry. That script adds a standard attachment. To add a custom 
attachment, build the name using one of the read fields.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54972c44.4090...@torfree.net



Re: USB drive mounted Read-only; what to do ?

2014-12-21 Thread Ric Moore

On 12/21/2014 04:31 AM, Andrei POPESCU wrote:


On one hand I don't think it's such a big burden to use su/do or similar
for this type of operation, on the other hand it's slightly easier to
pick the wrong device and destroy your data.


Andrei, the issue of IF the pen-drive was automounted on insertion has 
not been raised. What do you think?? 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.
Linux user# 44256


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/549726e6.2090...@gmail.com



Re: remote printing for an USB printer

2014-12-21 Thread Pierre Frenkiel

On Sat, 20 Dec 2014, Lisi Reisz wrote:


Go into CUPS web interface.  Go to Administration -> printers -> click on the
printer that you want -> click on the administration drop down menu and alter
the server settings to give you what you want.


  hi Lisi,
  what I want is to get, when I print 1 page, only 1 sheet, and not 100.
  What do you suggest to achieve this goal?

  As in a big number of documents about print sharing with CUPS, you
  don't say whether the command must be run on the server or on the client.
  In this case, it is really not obvious as

  1/ on the server, as already said, the config is perfectly correct
 and I don't see what I could modify.
  2/ on the client, you can't modify anything, as when you try to modify
 default options, you are redirected to the server.

   I did an other try, after enabling the debug option, and as before:
   - I got a printed sheet, and several others, until I canceled all the jobs.
   - in less than 3 seconds, the print queue on the server became filled with
 more than 100 entries.

I join a part of the log files(the error_log of the server for a few
seconds had more than 5 lines)

Can anybody understand something after reading them?

best regards,
--
Pierre FrenkielThe following attachment was sent,
but NOT saved in the Fcc copy:
A Text/PLAIN (Name="access_log.server") segment of about 12,906 bytes.
The following attachment was sent,
but NOT saved in the Fcc copy:
A Text/PLAIN (Name="access_log.client") segment of about 318 bytes.
The following attachment was sent,
but NOT saved in the Fcc copy:
A Text/PLAIN (Name="error_log.server") segment of about 23,321 bytes.
The following attachment was sent,
but NOT saved in the Fcc copy:
A Text/PLAIN (Name="error_log.client") segment of about 41,143 bytes.


Re: remote printing for an USB printer

2014-12-21 Thread Pierre Frenkiel

On Sun, 21 Dec 2014, Brian wrote:


On Sat 20 Dec 2014 at 22:03:50 +0100, Pierre Frenkiel wrote:

  I think that a so mature OS as Debian should provide the same
  facility.


It does.


   the experience proves that it does not: otherwise, why nobody could
   explain the problem I described and suggest a fix?

   The only help I got up to now was: "do a correct setup"
   that is very helpful!




  This also shows that the sharing is correctly setup on the server side.


For the Android.


I would be curious to understand how a CUPS sharing  setup on the server
could work for Android and not for Linux?


Where is the printer queue set up? On the client or on the server?


   I don't understand at all this question: how could I setup on the client
   a printer connected via USB on the server?
   On the client, the only thing you can do is to add a shared printer,
   but not modify it's setup.


Empty the error_log with '>/var/log/error_log'; print ; send the client
log to the list if you wish.


  I join the client error_log, severely cut as it became huge very quickly
  you can remark all lines like "Print file accepted - job ID 2025"
  which explains why the queue is growing on the server, but not why it
  does that.


> cups-browsed needs to be correctly set up on the server for the client
to be able to see the advertised queues.  > > "listen 192.168.1.12"

should not be the least bit necessary.
  I installed cups-browsed, but that changed nothing, which seems noraml,
  as the lient already sees the print queue and can print to it.
  I repeat: the problem is not that I can't print, but that I print
  too much!
D [21/Dec/2014:16:55:49 +0100] [Job 35] Create-Job IPP/2.0
D [21/Dec/2014:16:55:49 +0100] [Job 35] 
printer-uri="ipp://192.168.1.12:631/printers/phsm"
D [21/Dec/2014:16:55:49 +0100] [Job 35] requesting-user-name="frenkiel"
D [21/Dec/2014:16:55:49 +0100] [Job 35] job-name="prn_pr_31736"
D [21/Dec/2014:16:55:49 +0100] [Job 35] document-format="application/postscript"
D [21/Dec/2014:16:55:49 +0100] [Job 35] Get-Jobs: successful-ok (successful-ok)
D [21/Dec/2014:16:55:49 +0100] [Job 35] Create-Job: successful-ok 
(successful-ok)
I [21/Dec/2014:16:55:49 +0100] [Job 35] Print file accepted - job ID 2025.
D [21/Dec/2014:16:55:49 +0100] [Job 35] Set job-printer-state-message to "Print 
file accepted - job ID 2025.", current level=INFO
D [21/Dec/2014:16:55:49 +0100] [Job 35] job-id=2025
D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
D [21/Dec/2014:16:55:49 +0100] Discarding unused printer-state-changed event...
D [21/Dec/2014:16:55:49 +0100] [Job 35] Sending file 1 using chunking...
D [21/Dec/2014:16:55:49 +0100] [Job 35] Send-Document: successful-ok 
(successful-ok)
D [21/Dec/2014:16:55:49 +0100] [Job 35] PAGE: 1 1
D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
I [21/Dec/2014:16:55:49 +0100] [Job 35] Waiting for job to complete.
D [21/Dec/2014:16:55:49 +0100] [Job 35] Set job-printer-state-message to 
"Waiting for job to complete.", current level=INFO
D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
D [21/Dec/2014:16:55:49 +0100] Discarding unused printer-state-changed event...
D [21/Dec/2014:16:55:49 +0100] [Job 35] Get-Job-Attributes: successful-ok 
(successful-ok)
D [21/Dec/2014:16:55:49 +0100] [Job 35] update_reasons(attr=0(), 
s="+cups-ipp-conformance-failure-report,cups-ipp-missing-job-state")
I [21/Dec/2014:16:55:49 +0100] [Job 35] 
D [21/Dec/2014:16:55:49 +0100] [Job 35] Set job-printer-state-message to 
"Waiting for job to complete.", current level=INFO
D [21/Dec/2014:16:55:49 +0100] [Job 35] update_reasons(attr=1(none), s="(null)")
D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
D [21/Dec/2014:16:55:49 +0100] Discarding unused printer-state-changed event...
D [21/Dec/2014:16:55:49 +0100] [Job 35] Get-Printer-Attributes: successful-ok 
(successful-ok)
D [21/Dec/2014:16:55:49 +0100] PID 32121 (/usr/lib/cups/backend/ipp) stopped 
with status 4.
I [21/Dec/2014:16:55:49 +0100] [Job 35] Backend returned status 4 (stop printer)
D [21/Dec/2014:16:55:49 +0100] Discarding unused job-state-changed event...
I [21/Dec/2014:16:55:49 +0100] [Job 35] Printer stopped due to backend errors; 
please consult the error_log file for details.
D [21/Dec/2014:16:55:49 +0100] cupsdMarkDirty(J-)
D [21/Dec/2014:16:55:49 +0100] cupsdSetBusyState: newbusy="Printing jobs and 
dirty files", busy="Dirty files"
D [21/Dec/2014:16:55:49 +0100] cupsdSetBusyState: newbusy="Printing jobs and 
dirty files", busy="Printing jobs and dirty files"
D [21/Dec/2014:16:55:49 +0100] cupsdMarkDirty(J-)
D [21/Dec/2014:16:55:49 +0100] cupsdSetBusyState: newbusy="Dirty files", 
busy="Printing jobs and dirty files"
D [21/Dec/2014:16:55:49 +0100] cupsdSetBusyState: newbusy="Dirty files", 
busy="Dirty files"
D [21/Dec/2014:16:55:49 +0100] [Job 35] Sending job to queue tagged as raw...
D [21/Dec/2014:16:55:49 +0100] [Job 35] job-sheets=none
D 

Re: USB drive mounted Read-only; what to do ?

2014-12-21 Thread Ron
On Sun, 21 Dec 2014 19:30:39 +
Brian  wrote:

> > Only fly in the ointment is that gparted still complains that:
> > Unable to open /dev/sdi read-write (Read-only file system).  /dev/sdi has 
> > been opened read-only.  

> Hve you not yet come to terms with the fact that your USB stick has
> cocked its toes up?

I still doubt that, given I can read the contents.
 
Cheers,
 
Ron.
-- 
Democracy substitutes election by the incompetent many
 for appointment by the corrupt few.
-- George Bernard Shaw

   -- http://www.olgiati-in-paraguay.org --
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141221164617.2fe18...@ron.cerrocora.org



Re: USB drive mounted Read-only; what to do ?

2014-12-21 Thread Brian
On Sun 21 Dec 2014 at 11:34:38 -0300, Renaud OLGIATI wrote:

> Only fly in the ointment is that gparted still complains that:
> Unable to open /dev/sdi read-write (Read-only file system).  /dev/sdi has 
> been opened read-only.

Hve you not yet come to terms with the fact that your USB stick has
cocked its toes up?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/21122014192833.de8a90d9e...@desktop.copernicus.demon.co.uk



Re: USB drive mounted Read-only; what to do ?

2014-12-21 Thread Brian
On Sun 21 Dec 2014 at 11:31:19 +0200, Andrei POPESCU wrote:

> On Sb, 20 dec 14, 19:50:51, Bob Proulx wrote:
> > 
> > Good question.  It feels like we have come full circle.  That was the
> > way it was before the introduction of devfs and udev.  It appears that
> > things now have returned to the way it was before udev.  Which won't
> > bother the old-school Unix folks because we already lived through that
> > and already know how to deal with it.  But why haven't the next
> > generation started complaining about it?  If it works for them, then
> > how?  The changelog says they are obsolete.  But then what is the
> > replacement for them?
> 
> If my understanding is correct, "normal" read/write permissions are 
> handled by udisks and should work regardless of whether a user happened 
> to be the first one set up (usually by debian-installer) or not.

I'm not too familiar with udisks but that is my understanding too.
 
> Whether it is a good idea to restrict writing to the raw device only to 
> root-equivalent users is a different question.

It is. Is there an explanatory answer? Following upstream rules allows
the Debian patch to be removed, which implies it has some unstated
consequences.

> On one hand I don't think it's such a big burden to use su/do or similar 
> for this type of operation, on the other hand it's slightly easier to 
> pick the wrong device and destroy your data.

Someone without root access cannot dd, cp or cat a Debian ISO to a USB
stick. I rather liked the Wheezy ability to do this and to use fdisk
without worrying. One moment of inattentiveness or the wrong letter with
root access would ruin one's day.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141221192733.gn19...@copernicus.demon.co.uk



Re: Inserting a field in a LibreOffice email subject line for a bulk mailing.

2014-12-21 Thread Gary Dale

On 21/12/14 10:59 AM, Lisi Reisz wrote:

Does one of the LO fans know how to insert a field in a LibreOffice email
subject line for a bulk mailing?

Lisi



LibreOffice has its own e-mail discussion list.

I've never needed to do it because I've used a simple work-around bash 
script. I use LibreOffice to produce a customized attachment (usually a 
certificate for someone) then use an exported text file and the read 
command to allow me to extract the custom information I need.


I can use this to build custom subject and body parts, plus add the 
appropriate attachment, using a command-line mail program.


Here's a quick and dirty example of how to do it:

#! /bin/bash
cat $1.text | while read addr first last; do
  echo "sending e-mail to" $first $last "at" $addr
  echo "Dear" $first $last > salutation.text
  cat $2.text >>salutation.text
  if [[ "$4" == "" ]]; then
mutt $addr -s "$3" To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54971116.60...@torfree.net



Re: remote printing for an USB printer

2014-12-21 Thread Brian
On Sat 20 Dec 2014 at 22:03:50 +0100, Pierre Frenkiel wrote:

> On Sat, 20 Dec 2014, Brian wrote:
> 
> >. . .
> >This shows you have the android correctly set up for printing.
> 
>   not exactly: I said that I didn't have anything to setup: just launching the
>   application and wait for 10 seconds.
>   I think that a so mature OS as Debian should provide the same
>   facility.

It does.

>   This also shows that the sharing is correctly setup on the server side.

For the Android.

> >This shows you do not have the wheezy client correctly set up for
> >printing.
>   very useful! If the client was correctly setup, I sould not need to
>   post for help...

Stating the obvious (or the apparently obvious) can concentrate the mind. :)
 
> >"Successfully"? In what way?
> >Either the job was successful or it wasn't. Which is it? Printing or no
> >printing?
>I thought I clearly described what happened:
>   - I get a paper sheet whose content is what I sent to the printer, but:
>   - on the client, the job remains in the queues, and the printer is
> marked as "stopped"

Where is the printer queue set up? On the client or on the server?

>   - on the server, the printer queue grows indefinitely, and the printer
> spits page after page, until I cancel the job on the client, and all
> jobs on the server.
> 
>I don't see an other way to describe more clearly what is happening.
>
> >Enable debug logging on client and server; cupsctl(8). Print. Examine logs.
> 
>Ok. I'll see whether this can lead to some explanation

Empty the error_log with '>/var/log/error_log'; print ; send the client
log to the list if you wish.
 
> >Say what cups version is on the server.
>   on the server: 1.7.5-9 (jessie, i386)
>   on the client: 1.5.3-5+deb7u4 (wheezy, amd64)

cups-browsed needs to be correctly set up on the server for the client
to be able to see the advertised queues.

"listen 192.168.1.12" should not be the least bit necessary.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141221181940.gm19...@copernicus.demon.co.uk



Re: wordperfect 5.1 for unix, and debian?

2014-12-21 Thread Gary Dale

On 20/12/14 10:21 PM, Karen Lewellen wrote:

Not you Patrick, someone else.
I am sort of quoting
"I still do not know what you have against suggesting> it is  far superior to wordperfect.

Odd idea about a virtual machine too.
The is far superior is the sort of thing I mean.  Especially when so 
many others have reasons to appreciate their own  word processor 
preferences.

Kare

I believe I'm the person who made the remark. It's based on comparing 
features, ease of use and stability. If you took an independent 
evaluation of the current crop of word processors available in the 
world, and compared them against WP51, I doubt anyone would rate WP51 
above the major free options.


At some point we should just accept that some products are just better 
than others. Familiarity may make you comfortable with a product but the 
computer world never stands still. Clinging to the past leads to 
problems with keeping things current - such as finding a way to run 
WordPerfect on a platform that the manufacturer no longer supports.


I also recall WP's reveal codes. Funny thing is, I've never missed them. 
LibreOffice and OpenOffice.org before it never messed up my documents 
enough to make me want to see what they were doing.


As for whether the user interface is good or bad, I don't really care. I 
hate a lot of the current crop of user interfaces because they try to 
get too clever. The best user interface is the one that works for that 
particular user.


For the great unwashed masses of us who don't spend all day "word 
processing", we want one that allows us to find the features we want 
when we need them. LibreOffice does that. A lot of the new crop of 
interfaces like to hide things away to make the top bar smaller. This 
effectively gives you an extra layer of menu to get to the feature you 
want. It may look snazzy but it doesn't help me process words.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54970f18.5060...@torfree.net



Re: wordperfect 5.1 for unix, and debian?

2014-12-21 Thread Curt
On 2014-12-21, Henrique de Moraes Holschuh  wrote:

>> Why do we all have to like the same word processor?
>
> Indeed.  And some of us actually like *document* processors (best example in
> Debian: lyx) for extremely consistent output (and IMHO, much higher
> productivity).

(I knew I was right to leave this thread open; I see it *is* getting
rather snippy elsewhere.)

I use a simple latex template + latex2rtf + abiword (sufficient for my
brain-damaged needs). Not that anyone cares, but there ya go.

> There is an entire world out there of text processing that decouples
> presentation from content...
>




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnm9dtlk.30v.cu...@einstein.electron.org



Inserting a field in a LibreOffice email subject line for a bulk mailing.

2014-12-21 Thread Lisi Reisz
Does one of the LO fans know how to insert a field in a LibreOffice email 
subject line for a bulk mailing?

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201412211559.27219.lisi.re...@gmail.com



Re: USB drive mounted Read-only; what to do ?

2014-12-21 Thread Ron
On Sun, 21 Dec 2014 12:00:52 -0200
Eduardo M KALINOWSKI  wrote:

> >> #   ls -l /dev/sdi
> >> brw-rw---T 1 root floppy 8, 128 Dec 19 07:59 /dev/sdi  

> > Anyone know where I could find info on the special permission denoted by 
> > the leading b in the permissions above,   
 
> That's not a permission, it indicates it's a block device.
 
> > and same for the trailing T ?  
 
> Sticky bit is set.
 
> "info ls" brings the coreutils manual, where these flags are described
> (see section "What information is listed").

Thanks to your help, and that of  Eduardo M KALINOWSKI, I have managed to get 
rid of the sticky bit, by running successively:

# ls -l /dev/sdi
brw-rw---T 1 root floppy 8, 128 Dec 21 10:44 /dev/sdi

# chmod a+x /dev/sdi

# ls -l /dev/sdi
brwxrwx--t 1 root floppy 8, 128 Dec 21 10:44 /dev/sdi

# chmod a+rw /dev/sdi

# ls -l /dev/sdi
brwxrwxrwt 1 root floppy 8, 128 Dec 21 10:44 /dev/sdi

# chmod o-t /dev/sdi

# ls -l /dev/sdi
brwxrwxrwx 1 root floppy 8, 128 Dec 21 10:44 /dev/sdi

As you can see above, you need first a chhmod a+rw that converts the T in t, 
after which a chmod o-t removes the t; chmod o-T does not work. Maybe there is 
a simpler way, but this one did work.

Only fly in the ointment is that gparted still complains that:
Unable to open /dev/sdi read-write (Read-only file system).  /dev/sdi has been 
opened read-only.
 
Cheers,
 
Ron.
-- 
 L'è el dì di Mort, alegher!

   -- http://www.olgiati-in-paraguay.org --
 


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141221113438.59a6b...@ron.cerrocora.org



Re: USB drive mounted Read-only; what to do ?

2014-12-21 Thread Eduardo M KALINOWSKI
On 12/21/2014 11:49 AM, Renaud (Ron) OLGIATI wrote:
> On Fri, 19 Dec 2014 15:07:25 -0300
> Renaud (Ron) OLGIATI  wrote:
>
>> #   ls -l /dev/sdi
>> brw-rw---T 1 root floppy 8, 128 Dec 19 07:59 /dev/sdi
> Anyone know where I could find info on the special permission denoted by the 
> leading b in the permissions above, 

That's not a permission, it indicates it's a block device.

> and same for the trailing T ?

Sticky bit is set.

"info ls" brings the coreutils manual, where these flags are described
(see section "What information is listed").

-- 
You are magnetic in your bearing.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5496d294.7050...@kalinowski.com.br



Re: USB drive mounted Read-only; what to do ?

2014-12-21 Thread Brad Rogers
On Sun, 21 Dec 2014 10:49:43 -0300
Renaud (Ron) OLGIATI  wrote:

Hello Renaud,

>> #   ls -l /dev/sdi
>> brw-rw---T 1 root floppy 8, 128 Dec 19 07:59 /dev/sdi
>Anyone know where I could find info on the special permission denoted
>by the leading b in the permissions above, and same for the trailing T ?

See;
http://www.comptechdoc.org/os/linux/usersguide/linux_ugfilesp.html
for a good, but not complete view of what each bit is for.

For example, the page doesn't explain the difference between t & T or s
& S.  For that, see;
https://en.wikipedia.org/wiki/File_system_permissions

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
But they didn't tell him the first two didn't count
Tin Soldiers - Stiff Little Fingers


pgpGISvmqAEPO.pgp
Description: OpenPGP digital signature


Re: USB drive mounted Read-only; what to do ?

2014-12-21 Thread Ron
On Fri, 19 Dec 2014 15:07:25 -0300
Renaud (Ron) OLGIATI  wrote:

> #   ls -l /dev/sdi
> brw-rw---T 1 root floppy 8, 128 Dec 19 07:59 /dev/sdi

Anyone know where I could find info on the special permission denoted by the 
leading b in the permissions above, and same for the trailing T ?
 
Cheers,
 
Ron.
-- 
 In war, truth is the first casualty.
   -- U Thant

   -- http://www.olgiati-in-paraguay.org --
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141221104943.1941c...@ron.cerrocora.org



Lid state incorrectly reported

2014-12-21 Thread Jean Commère
Hi,

I am using debian Jessie and systemd (215-7) is not handling
the lid state correctly after I reopen it. (the lid state stay to close)

So, because of the following commit, my system constantly suspend until I 
reboot it.
http://cgit.freedesktop.org/systemd/systemd/commit/?id=ed4ba7e4f652150310d062ffbdfefb4521ce1054


I have used the program in the following thread to test the lid state
(His problem was similar : lid state incorrectly set on boot)
https://lists.debian.org/debian-user/2014/10/msg02216.html

If I suspend manually the lid state stay to open and the problem does not arise.

I have a Samsung NP-N150-JP04FR

What can I do to fix that ?

thank you


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141221115915.GA1395@mut-laptop



Re: LACK OF REPONSE TO REQUESTS FOR HELP WHY?

2014-12-21 Thread Nate Bargmann
* On 2014 21 Dec 01:40 -0600, tom arnall wrote:
> I installed wheezy a week ago (with the installer which includes
> xfce), and nm-applet was working fine. But today it won't start and
> gives the message:
> 
> WARNING: gnome-keyring:: couldn't connect to:
> /home/tom/.cache/keyring-4LJPFc/pkcs11: No such file or directory

I am running Sid (Unstable) on my laptop and I have several such
~/.cache/keyring-* directories.  One of them shows:

$ ls -l ~/.cache/keyring-6imVnR/
total 0
srwxr-xr-x 1 nate nate 0 Jul  7  2012 control=
srwxr-xr-x 1 nate nate 0 Jul  7  2012 gpg=
srwxr-xr-x 1 nate nate 0 Jul  7  2012 pkcs11=
srwxr-xr-x 1 nate nate 0 Jul  7  2012 ssh=

Are the permissions on your files the same?  Is it possible that you
initially logged into the desktop as root and then used NM to connect to
a network?  Perhaps just removing that directory (although that specific
directory name may be stored by nm-applet *somewhere* so just removing
the directory might not help) might help.

The "files" are actually sockets so the leading 's' is apparently
required.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141221130512.gr2...@n0nb.us



Re: USB drive mounted Read-only; what to do ?

2014-12-21 Thread Andrei POPESCU
On Sb, 20 dec 14, 19:50:51, Bob Proulx wrote:
> 
> Good question.  It feels like we have come full circle.  That was the
> way it was before the introduction of devfs and udev.  It appears that
> things now have returned to the way it was before udev.  Which won't
> bother the old-school Unix folks because we already lived through that
> and already know how to deal with it.  But why haven't the next
> generation started complaining about it?  If it works for them, then
> how?  The changelog says they are obsolete.  But then what is the
> replacement for them?

If my understanding is correct, "normal" read/write permissions are 
handled by udisks and should work regardless of whether a user happened 
to be the first one set up (usually by debian-installer) or not.

Whether it is a good idea to restrict writing to the raw device only to 
root-equivalent users is a different question.

On one hand I don't think it's such a big burden to use su/do or similar 
for this type of operation, on the other hand it's slightly easier to 
pick the wrong device and destroy your data.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature