Your message dated Sun, 28 Nov 2010 20:42:01 +0100
with message-id <[email protected]>
and subject line Re: crashes if a document like pdf is opened inside
has caused the Debian Bug report #519524,
regarding epiphany: crashes if a document like pdf is opened inside
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
519524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519524
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: epiphany
Severity: important
Hallo,
I use the epiphany in the fluxbox window manager. Probably it is a fluxbox
Problem.
Often if I open a pdf or doc linked in the internet epipahny trys to start the
application for this document and than it crashed. It crashed most so that I
have to login into the window manager again.
I think it would nice if epiphany asks if I want to start the application for
this document and show the document there or if I want to see it inside the
browser.
Thanks
Torsten
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (990, 'testing'), (90, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Wednesday, 25. August 2010 06:06:22 Andreas Beckmann wrote:
> On Friday, 13. March 2009 18:39:47 Torsten Wiebke wrote:
> > Am Fri, 13 Mar 2009 17:39:06 +0100
> >
> > schrieb Josselin Mouette <[email protected]>:
> > > what you describe sounds like a crash of the X server to me, not a
> > > crash in epiphany (in which case you would only have to reopen
> > > epiphany).
>
> Does this still happen with current versions of X.Org and the NVIDIA driver
> (195.36.31-2 entered unstable yesterday)?
Since we haven't heard from the submitter since we asked for more information
a few months ago, I assume the problem does no longer exist and I'm closing
this report now.
If the problem is still reproducible with current driver versions (195.36.31-6
in testing/unstable or 260.19.21-1 in experimental), feel free to reopen this
bug report.
Andreas
--- End Message ---
