Re: [evince] problems with specific filename
- From: Juanjo Marín <juanjomarin96 yahoo es>
- To: "michael henn uni-ulm de" <michael henn uni-ulm de>
- Cc: "evince-list gnome org" <evince-list gnome org>
- Subject: Re: [evince] problems with specific filename
- Date: Fri, 1 Jul 2011 10:29:12 +0100 (BST)
----- Mensaje original -----
> De: Michael henn <michael henn uni-ulm de>
> Para: evince-list gnome org
> CC:
> Enviado: jueves 30 de junio de 2011 17:52
> Asunto: [evince] problems with specific filename
>
> Hello everyone,
>
> I've posted this in the IRC channel, but got no answer, so i try it this
> way:
>
> I tried the following in my home directory:
>
> $ echo "test" | a2ps -o .bashthis
> $ evince .bashthis
>
> Then evince opens with a big red bar saying:
> Dokument konnte nicht geöffnet werden
> Fehler beim Öffnen der Datei: Keine Berechtigung
>
> meaning something like:
> Document could not be opened
> error while opening the file: no authorization
>
> The interesting part is: The problem only occurs if i'm in my home
> folder and the filename starts with ".bash". gv opens the file without
> any problems.
>
> When i try this (notice the missing h in "bash"):
>
> $ echo "test" | a2ps -o .basthis
> $ evince .basthis
>
> it also works fine.
> So ... what problem does evince have with files in my homedirectory
> beginning with ".bash"?
Michael,
This is strange. I can't reproduce this in my Fedora 15 box with Evince 3.0.2.
I think is not related with Evince, maybe with any "security" measure added by
your distribution. Which is your distro and version of Evince ?
This is the trace of systems calls related with the file:
$ strace -f evince .bashthis 2>&1 | grep bashthis
execve("/usr/bin/evince", ["evince", ".bashthis"], [/* 49 vars */]) = 0
[pid 10909] stat64("/home/jjmarin/.bashthis", <unfinished ...>
[pid 10909] lstat64("/home/jjmarin/.bashthis", {st_mode=S_IFREG|0664, st_size=17694, ...}) = 0
[pid 10914] lstat64("/home/jjmarin/.bashthis", {st_mode=S_IFREG|0664, st_size=17694, ...}) = 0
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY|O_LARGEFILE) = 17
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY <unfinished ...>
[pid 10912] lstat64("/home/jjmarin/.bashthis", <unfinished ...>
[pid 10912] lstat64("/home/jjmarin/.bashthis", {st_mode=S_IFREG|0664, st_size=17694, ...}) = 0
[pid 10912] lstat64("/home/jjmarin/.bashthis", {st_mode=S_IFREG|0664, st_size=17694, ...}) = 0
[pid 10921] lstat64("/home/jjmarin/.bashthis", <unfinished ...>
[pid 10912] lstat64("/home/jjmarin/.bashthis", <unfinished ...>
[pid 10909] stat64("/home/jjmarin/.bashthis", {st_mode=S_IFREG|0664, st_size=17694, ...}) = 0
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
[pid 10909] stat64("/home/jjmarin/.bashthis", {st_mode=S_IFREG|0664, st_size=17694, ...}) = 0
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
[pid 10914] open("/home/jjmarin/.bashthis", O_RDONLY) = 24
I think doing a trace like this maybe can give you an idea what's wrong.
Cheers,
-- Juanjo Marin
[Date Prev][
Date Next] [Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]