Bug#406470: not reproducible here

2007-02-27 Thread Thomas Braun
On Tuesday 27 February 2007 10:46, Alexander Klauer wrote:
> Hi Thomas,
>
>
> (no reply-to was set; do you need CC:'s in the future?)

Hi Alexander,

no I don't need CC:'s because I'm subscribed to all kile bugs in debian.

> Thomas Braun:
> > > > - Do you have this behjavour always (or only after a start and stop
> > > > cycle of kile)?
> > >
> > > What do you mean by "start and stop cycle"? Anyway, when I check the
> > > option, kile immediately starts hogging, when I uncheck it, kile
> > > immediately behaves normally again.
> >
> > With start stop cycle I meant, quitting kile and then restarting kile.
>
> I see. Nope, a start-stop cycle is not required.

thanks.

> > > > - Do you have your home on a local device, or some remote stuff (nfs,
> > > > openafs, smb, or similiar)
> > >
> > > The home dirs are in OpenAFS.
> >
> > I think we found the culprit :)
> >
> > Kile is using a fifo to be able to insert tags from lyx-compliant apps
> > (This means e.g. gbib writes a bibtex reference to .lyxpipe.in and then
> > kile gets notified and inserts the reference).
> > But according to
> > http://www.dementia.org/twiki/bin/view/AFSLore/UsageFAQ#2_13_Can_I_create
> >_a _fifo_aka_nam Fifos are not supported by OpenAFS :(
> >
> > Currently I don't know a solution but I will ask some other kile devs for
> > help.
>
> Well, that explains things. If I may make two suggestions:
>
> 1. Kile tries to create a FIFO and when this fails, it creates a regular
> file instead:
>
> [pid  4968] 09:58:11.419907 mknod("/afs/.../home/xxx/.lyxpipe.in", S_IFIFO|
> 0644) = -1 EPERM (Operation not permitted)
> [pid  4968] 09:58:11.419981 dup(2)  = 13
> [pid  4968] 09:58:11.420047 fcntl64(13, F_GETFL) = 0x8001 (flags O_WRONLY|
> O_LARGEFILE)
> [pid  4968] 09:58:11.420102 close(13)   = 0
> [pid  4968] 09:58:11.420138 write(2, "Could not create pipe : Operatio"...,
> 48Could not create pipe : Operation not permitted) = 48
> [pid  4968] 09:58:11.420257 open("/afs/.../home/xxx/.lyxpipe.in", O_RDWR|
> O_LARGEFILE) = -1 ENOENT (No such file or directory)
> [pid  4968] 09:58:11.420326 open("/afs/.../home/xxx/.lyxpipe.in", O_RDWR|
> O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 13
>
Well actually kile really creates a regular file but due to some unfortunate 
testing after the creation of the fifo.
I try to prepare a short term fix and add point two to the kile 2.0 TODO 
list :)

> The regular file messes up the usual select/pipe semantics. It would be
> better (as a short term solution) to show the user a clean error message
> instead, something like "Sorry, but this functionality is unavailable
> because the file system of your home directory does not support FIFOs."
>
> 2. (long-term solution) Place the FIFO somewhere where they are supported
> for sure, e.g. in /tmp/kde-username/.

Thanks a lot,
Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#406470: not reproducible here

2007-02-27 Thread Alexander Klauer
Hi Thomas,


(no reply-to was set; do you need CC:'s in the future?)

Thomas Braun:
> > > - Do you have this behjavour always (or only after a start and stop
> > > cycle of kile)?
> >
> > What do you mean by "start and stop cycle"? Anyway, when I check the
> > option, kile immediately starts hogging, when I uncheck it, kile
> > immediately behaves normally again.
>
> With start stop cycle I meant, quitting kile and then restarting kile.

I see. Nope, a start-stop cycle is not required.

> > > - Do you have your home on a local device, or some remote stuff (nfs,
> > > openafs, smb, or similiar)
> >
> > The home dirs are in OpenAFS.
>
> I think we found the culprit :)
>
> Kile is using a fifo to be able to insert tags from lyx-compliant apps
> (This means e.g. gbib writes a bibtex reference to .lyxpipe.in and then
> kile gets notified and inserts the reference).
> But according to
> http://www.dementia.org/twiki/bin/view/AFSLore/UsageFAQ#2_13_Can_I_create_a
>_fifo_aka_nam Fifos are not supported by OpenAFS :(
>
> Currently I don't know a solution but I will ask some other kile devs for
> help.

Well, that explains things. If I may make two suggestions:

1. Kile tries to create a FIFO and when this fails, it creates a regular file 
instead:

[pid  4968] 09:58:11.419907 mknod("/afs/.../home/xxx/.lyxpipe.in", S_IFIFO|
0644) = -1 EPERM (Operation not permitted)
[pid  4968] 09:58:11.419981 dup(2)  = 13
[pid  4968] 09:58:11.420047 fcntl64(13, F_GETFL) = 0x8001 (flags O_WRONLY|
O_LARGEFILE)
[pid  4968] 09:58:11.420102 close(13)   = 0
[pid  4968] 09:58:11.420138 write(2, "Could not create pipe : Operatio"..., 
48Could not create pipe : Operation not permitted) = 48
[pid  4968] 09:58:11.420257 open("/afs/.../home/xxx/.lyxpipe.in", O_RDWR|
O_LARGEFILE) = -1 ENOENT (No such file or directory)
[pid  4968] 09:58:11.420326 open("/afs/.../home/xxx/.lyxpipe.in", O_RDWR|
O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 13

The regular file messes up the usual select/pipe semantics. It would be better 
(as a short term solution) to show the user a clean error message instead, 
something like "Sorry, but this functionality is unavailable because the file 
system of your home directory does not support FIFOs."

2. (long-term solution) Place the FIFO somewhere where they are supported for 
sure, e.g. in /tmp/kde-username/.


Thank you,
Alexander


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#406470: not reproducible here

2007-02-26 Thread Thomas Braun
On Monday 26 February 2007 11:44, Alexander Klauer wrote:
> Hi Thomas,
>
Hi Alexander,

> sorry for answering so late. I haven't received your answer by mail, only
> just saw it in the BTS.

no problem, I only thought we got rid of this problem ;)

> copy & paste:
> > I would need some further information:
> > - Do you have this behjavour always (or only after a start and stop cycle
> > of kile)?
>
> What do you mean by "start and stop cycle"? Anyway, when I check the
> option, kile immediately starts hogging, when I uncheck it, kile
> immediately behaves normally again.

With start stop cycle I meant, quitting kile and then restarting kile.

> > - Or only after having other programs used this feature?
>
> What feature? The user in question does not use LyX or latex directly.

Yes this was the question :)

> > - Can you give the output of "ls -la .lyx .lyxpipe.*" in your home
> > directory of the user issuing kile.ls -la .lyx .lyxpipe.*
>
> In my home dir:
> $ ls: .lyxpipe.*: No such file or directory
> .lyx:
> total 10
> drwxr--r--  2 xxx xxx 2048 2007-02-26 11:38 .
> drwxr-xr-x 82 xxx xxx 8192 2007-02-26 11:38 ..
>
> In the user's home dir:
> $ ls -la .lyx .lyxpipe.*
> ls: .lyxpipe.*: No such file or directory
> .lyx:
> total 77
> drwxr-xr-x 15   xxx xxx  2048 2007-01-11 17:47 .
> drwxrwxr-x 61 xxx xxx  6144 2007-02-23 16:15 ..
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 bind
> -rw-r--r--  1   xxx xxx  2960 2006-01-09 12:45 bstFiles.lst
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 clipart
> -rw-r--r--  1   xxx xxx  2310 2006-01-09 12:45 clsFiles.lst
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:46 doc
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 examples
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 help
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 images
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 kbd
> -rw-r--r--  1   xxx xxx35 2006-10-10 16:01 lastfiles
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 layouts
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 reLyX
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 scripts
> -rw-r--r--  1   xxx xxx 36262 2006-01-09 12:45 styFiles.lst
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 templates
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 ui
> drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:46 xfonts
>
> (Note that the problem is reproducible for both me and the user.)
>
> > - Do you have your home on a local device, or some remote stuff (nfs,
> > openafs, smb, or similiar)
>
> The home dirs are in OpenAFS.
>
I think we found the culprit :)

Kile is using a fifo to be able to insert tags from lyx-compliant apps (This 
means e.g. gbib writes a bibtex reference to .lyxpipe.in and then kile gets 
notified and inserts the reference).
But according to 
http://www.dementia.org/twiki/bin/view/AFSLore/UsageFAQ#2_13_Can_I_create_a_fifo_aka_nam
Fifos are not supported by OpenAFS :(

Currently I don't know a solution but I will ask some other kile devs for 
help.

Thanks
Thomas Braun


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#406470: not reproducible here

2007-02-26 Thread Alexander Klauer
Hi Thomas,


sorry for answering so late. I haven't received your answer by mail, only just 
saw it in the BTS.

copy & paste:
> I would need some further information:
> - Do you have this behjavour always (or only after a start and stop cycle
> of kile)?

What do you mean by "start and stop cycle"? Anyway, when I check the option, 
kile immediately starts hogging, when I uncheck it, kile immediately behaves 
normally again.

> - Or only after having other programs used this feature?

What feature? The user in question does not use LyX or latex directly.

> - Can you give the output of "ls -la .lyx .lyxpipe.*" in your home
> directory of the user issuing kile.ls -la .lyx .lyxpipe.*

In my home dir:
$ ls: .lyxpipe.*: No such file or directory
.lyx:
total 10
drwxr--r--  2 xxx xxx 2048 2007-02-26 11:38 .
drwxr-xr-x 82 xxx xxx 8192 2007-02-26 11:38 ..

In the user's home dir:
$ ls -la .lyx .lyxpipe.*
ls: .lyxpipe.*: No such file or directory
.lyx:
total 77
drwxr-xr-x 15   xxx xxx  2048 2007-01-11 17:47 .
drwxrwxr-x 61 xxx xxx  6144 2007-02-23 16:15 ..
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 bind
-rw-r--r--  1   xxx xxx  2960 2006-01-09 12:45 bstFiles.lst
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 clipart
-rw-r--r--  1   xxx xxx  2310 2006-01-09 12:45 clsFiles.lst
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:46 doc
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 examples
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 help
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 images
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 kbd
-rw-r--r--  1   xxx xxx35 2006-10-10 16:01 lastfiles
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 layouts
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 reLyX
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 scripts
-rw-r--r--  1   xxx xxx 36262 2006-01-09 12:45 styFiles.lst
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 templates
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 ui
drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:46 xfonts

(Note that the problem is reproducible for both me and the user.)

> - Do you have your home on a local device, or some remote stuff (nfs,
> openafs, smb, or similiar)

The home dirs are in OpenAFS.


Best regards,
Alexander


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#406470: not reproducible here

2007-01-12 Thread Thomas Braun
Hello,

I had a look on the affected code but I didn't sav any obvious errors.
I also can't confirm the bug here on debian testing.

I would need some further information:
- Do you have this behjavour always (or only after a start and stop cycle of 
kile)?
- Or only after having other programs used this feature?
- Can you give the output of "ls -la .lyx .lyxpipe.*" in your home directory 
of the user issuing kile.
- Do you have your home on a local device, or some remote stuff (nfs, openafs, 
smb, or similiar)

Thanks,
Thomas Braun (member of the kile team)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]