Absolutely. I used encrypted filenames option and my Private.sig has
exactly 2 lines. Anyway, I have moved my data on the cryptsetup
partition a half of a year ago, and for that reason I have not so much
to add.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
I searched several times. Also the '@@' string was among the last
searches.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: evince 2.30.3-0ubuntu1.2
ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
Uname: Linux 2.6.32-32-generic x86_64
Architecture:
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/802435
Title:
evince crashed during pdf search
To manage notifications about this bug go to:
apport-bug -c /var/crash/_usr_bin_evince.1000.crash
The above command complained:
The program crashed on an assertion failure, but the message could not be
retrieved. Apport does not support reporting these crashes.
For that reason I'm attaching crash file directly.
** Attachment added:
nautilus syslog
** Attachment added: nautilus.syslog
http://launchpadlibrarian.net/37179924/nautilus.syslog
--
nautilus crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/479124
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
nautilus thread stack trace
** Attachment added: nautilus thread stack trace
http://launchpadlibrarian.net/37179951/nautilus.thread.stack.trace
--
nautilus crashed with SIGSEGV in PyThreadState_New()
https://bugs.launchpad.net/bugs/479124
You received this bug notification because you are a
Thank you, Martin, it usually complicated for me to determine which dbg
package needed. I think my crash file provides more info, but how should
I add it here? Attachment whole file from /var/crash? For now I'll
attack syslog lines and threadstack trace.
--
nautilus crashed with SIGSEGV in
I have the same situation as Vadim. It's accidental crash but it happens
very often. Even now I have this kind of crash report in /var/crash. I
installed dbg package for nautilus, may be if I send you my report it
will be more usefull?
--
nautilus crashed with SIGSEGV in PyThreadState_New()
Thank you. I get it. But I have one more thing to ask.
When I do for example: kill -s SIGSEGV $$
I get core file in current directory and *.crash file.
But when I do: kill -s SIGABRT $$
I only get core file. So I can't fulfil the other reports correct. What shall
I do?
--
nautilus (hardy)
Public bug reported:
Binary package hint: nautilus
Description:Ubuntu 8.04.2
Release:8.04
nautilus:
Installed: 1:2.22.5.1-0ubuntu1
Candidate: 1:2.22.5.1-0ubuntu1
Version table:
*** 1:2.22.5.1-0ubuntu1 0
500 http://ru.archive.ubuntu.com hardy-updates/main Packages
10 matches
Mail list logo
