Ubuntu
evince package

Evince Segmentation Fault on Launch

Bug #572028 reported by Nidoo on 2010-04-30

This bug report is a duplicate of: Bug #571725: evince not open. Edit Remove

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	evince (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: evince

Beautiful release of Lucid, unfortunately as the summary states on launch I get a segmentation fault for evince.

** (evince:3423): WARNING **: Error creating last_settings file: Error opening file '/home/jp/.gnome2/evince/last_settings': No such file or directory

Segmentation fault

I double checked if this directory exists, and it does not. Reinstalling Evince does not create the directory/file.

Anything else you need please let me know.

Regards,
Nidoo

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: evince 2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Apr 30 01:19:49 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
LANG=en_CA.utf8
SHELL=/bin/bash
SourcePackage: evince

Tags:

Revision history for this message

Nidoo (jtwpayn-gmail) wrote on 2010-04-30:

Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
KernLog.txt Edit (7.6 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (131 bytes, text/plain; charset="utf-8")

Revision history for this message

John McDougall (sysadmin-mcdougallshome) wrote on 2010-04-30:

I have the same error as Nidoo. distribution information is the same except I am running Lucid 64 bit.

Revision history for this message

Richard (g-launchpad-mcgillivary-org) wrote on 2010-04-30:

Seeing similiar issue here, below is the last bit of an strace showing the permission denied.

clock_gettime(CLOCK_MONOTONIC, {849, 930237457}) = 0
lstat64("/home/rmcgilli/.gnome2/evince/last_settings", 0xbf90338c) = -1 ENOENT (No such file or directory)
open("/home/rmcgilli/.gnome2/evince/last_settings", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = -1 EACCES (Permission denied)
write(2, "\n** (evince:21948): WARNING **: "..., 152
** (evince:21948): WARNING **: Error creating last_settings file: Error opening file '/home/rmcgilli/.gnome2/evince/last_settings': Permission denied

If you manually create the file evince will start up (touch <full file from error message>)

Incase it's important my home dir is enrcypted so the filesystem type is fuse; here's the mount entry

gvfs-fuse-daemon on /export2/home/rmcgilli/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=rmcgilli)

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-04-30:

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Changed in evince (Ubuntu):
status:	New → Invalid

Revision history for this message

Richard (g-launchpad-mcgillivary-org) wrote on 2010-05-03:

Just done some more testing and if I move the evince directory to a none fuse filesystem with a symlink , the last_settings file gets created

e.g.

lstat64("/home/rmcgilli/.gnome2/evince/last_settings", 0xbfbc753c) = -1 ENOENT (No such file or directory)
open("/home/rmcgilli/.gnome2/evince/last_settings", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 9
fstat64(9, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
close(9) = 0
lstat64("/home/rmcgilli/.gnome2/evince/last_settings", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0

Quick look around and a bug(44886)has previously been reported with fuse 2.4 and O_WRONLY|O_CREAT , but was fixed; so wonder if this is a regression; will see if I can find the bug.

However, this means it's not an evince bug; but a fuse bug.

Can we unlink this bug from 571725 as they are not the same bug.

Revision history for this message

Kirill Kabardin (kkabardin) wrote on 2010-05-04:

>> However, this means it's not an evince bug; but a fuse bug.
It's not evince bug in your case, but in my case evice can't create file, because it needs to create parent directory "~/.gnome2/evince" first, which doesn't exist. It seems more like packaging bug to me, or even bug in evince itself.